Appendix C. Verification Matrices

(2) Internal or external requirement driving the Agency to expedite publishing requirements.

(3) Date by which NPD or NPR needs to be published.

(4) Timeline for coordination showing the number of days for each step of the coordination as illustrated in Figure 4. Download a timeline template to enter number of days for each step in the expedited review, here: Expedited Review.

(5) Names of the reviewers that participated in the prereview.

If yes, compliant. If no, not compliant.

a. Use the NODIS DMS to create or revise directives within the timeline established in Figure 4.

b. Provide track changes document showing where proposed changes are made in the directive for a full or section revisions.

If yes, compliant. If no, not compliant.

Prior to Official Review

a. E-mail the draft directive to the respective ALR so that any information related to GAO and IG recommendations that require revisions to directives are appropriately captured and that the timeline for the directive to be approved aligns with the timeline for which NASA committed to corrective actions?

b. Submit an NHQ 184 Form, to include a purpose and justification for the directive, reasons for revising or issuing it, significant revisions that will be made, proposed required concurrers, required reviewers, and courtesy reviews, summary of cost/benefit impacts to implement new requirements in terms of financial, human resources, technical (e.g., associated costs to implement new requirements and what can be gained by implementing the new requirements), and potential for unintended consequences, and preference on submission of comments (e.g., direct entry in NODIS or via comment template loaded in NODIS)?

c. Submit the draft directive in NODIS so that OES DMT can review for compliance with content and structure requirements described in Chapter 3 of this directive?

d. Forward OES DMT's findings to the Responsible Office for corrective action and assist with expediting corrections?

e. Load the updated draft directive in the NODIS DMS and notify the OES DMT so that corrective actions can be verified?

If yes, compliant. If no, not compliant.

a. Submit an NHQ 184 Form, to include a purpose and justification for the directive, reasons for revising or issuing it, significant revisions that will be made, proposed required concurrers, required reviewers, and courtesy reviews, summary of cost/benefit impacts, and preference on submission of comments (e.g., direct entry in NODIS or via comment template loaded in NODIS).

b. Enter NPD/Load NPR in NODIS.

c. Schedule a kickoff meeting with OES DMT to brief on the directive before it is added to the schedule for review.

d. Disposition all comments provided on the directive's technical content and cost/benefit impacts to satisfy concerns of Concurring Offices and Centers and forward those dispositions to the DM to enter in NODIS.

e. Ensure completion of concurrences from Concurring Offices and Centers.

If yes, compliant. If no, not compliant

a. Update the directive in NODIS?

b. Assemble the directive’s clearance package documents in the following order, save as a combined pdf file, and e-mail it to DMT:

(1) Completed NHQ 117 Form to include:

(a) Evidence of concurrences from reviewing organizations and the concurrence of the responsible OIC.

(b) Name, number, and date of review for the DM, quality reviewer, and originator.

(c) Executive Summary that describes:

(i) Summary of purpose and justification for new or revised policy or requirement(s) and origin if revised, to include an explanation of why the new directive needs to be issued or why revisions need to be made (e.g., audit recommendation or Council action).

(ii) Summary of significant changes if the directive is being revised.

(iii) Summary of significant comments received during the review and how they were dispositioned.

(iv) Summary of disagreement with the IG, if any.

(v) Cost/benefit impacts for new resources that may be needed and a justification for why resources need to be expended.

(vi) Strategic impact (if any).

(vii) Description of Presidential initiative/external action (if any).

c. Final draft of the new or revised directive.

d. Background sheet retrieved from EOT’s website

e. Redline showing the changes made in a revised directive.

f. Directive's review report of all comments and dispositions retrieved from NODIS. If comments were collected via template, ensure that the template is legible in the clearance package.

g. Copy of e-mail from the LRO indicating completion of union review.

h. Any additional documents that convey executive direction and supporting material.

If yes, compliant. If no, not compliant.

(1) Paragraph 1, Policy provides a general statement of the principles, fundamental values, and general direction of the Agency or Center that is used to determine present and future decisions. Policy statements do not contain requirements "shall" statements and are introduced (e.g., "It is NASA Policy to" or "This directive establishes policy for").

(2) Paragraph 2, Applicability identifies the organizations to which the NPD or CPD applies. Include the following applicability statements.

(a) "This directive is applicable to NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers."

(b) If the directive applies to Jet Propulsion Laboratory (JPL), a Federally Funded Research and Development Center (FFRDC), include this statement, "This directive is applicable to the Jet Propulsion Laboratory, a Federally Funded Research and Development Center (FFRDC), only to the extent specified in the NASA/FFRDC Prime Contract." If the directive does not apply to JPL, an FFRDC, remove the applicability statement referencing JPL, and FFRDC, if mentioned. A directive does not apply to JPL, an FFRDC, unless it is on the Listing of the NASA Directives and Standards in the NASA/FFRDC Prime Contract and has been incorporated into the Prime Contract. Pending incorporation into the Prime Contract, use the following language: The applicability of this directive to the Jet Propulsion Laboratory, a Federally Funded Research and Development Center, is being assessed by NASA. This applicability statement will be updated as necessary when that assessment is completed.

(c) If the directive’s requirements are clearly delineated to specify applicability to other contractors, recipients of grants or cooperative agreements, or parties to other agreements as prescribed by paragraph 1.2.2 and Note 2 below, include this statement, "This directive is applicable to other contractors, recipients of grants or cooperative agreements, or parties to other agreements only to the extent delineated in this directive and specified in contracts, grants or cooperative agreements, or other agreements."

Note 1: Only list the type of document (i.e., contract, grant, or agreement) to which the directive applies. For example, if the directive is not applicable to a "grant," only list "contract or agreement" to indicate the directive's applicability.

Note 2: This statement alone is not sufficient to stipulate requirements for the contractor or recipient of the grant. Requirements can be delineated by adding a note after the requirements' paragraph. See paragraphs 2.6.1b and 2.19.6 note for examples of delineating requirements between civil servants and contractors or recipients of grants.

(d) For CPDs, include a statement like 3.6.2c(2)(a) above to ensure applicability at the Center and associated facilities.

(e) For NPDs and CPDs, include a statement that describes terms that denote action. See paragraph P.2b.

(f) For NPDs and CPDs, include a statement that describes document citations are assumed to be the latest version. See paragraph P.2h.

(g) If a document is listed as an authority, applicable document, and reference, add this statement, “Documents listed as authority, applicable documents, and reference documents may be cited as a different categorization, which characterizes its function in relation to the specific context.”

(h) If use of short titles is preferred when citing common authorities, applicable documents, or references, add a statement describing the use (e.g., The National Aeronautics and Space Act, 51 U.S.C. § 20111, herein referred to as the Space Act).

(3) Paragraph 3, Authority contains a list of the NPD or CPD and external authority(ies) or requirements that justify establishing the NPD or CPD. This latter category includes only those external sources that are the authority for the NPD or CPD. Place all other external sources in the Applicable Documents and Forms or References sections.

(4) Paragraph 4, Applicable Documents and Forms – contains a list of documents and forms cited in the body of the directive that contains provisions or other pertinent requirements directly related and necessary to the performance of the activities specified by the directive.

(5) Paragraph 5, Responsibility is an explanation of who (by position or organization) is responsible for implementing the policy stated in the NPD or CPD. Write responsibility statements in accordance with paragraph 3.2.1 and avoid dictating how an organizational leader is to organize or assign responsibilities within the leader’s organization.

(6) Paragraph 6, Delegation of Authority is reserved for direct delegation from the Administrator, OIC, or Center Director to a specific position (e.g., Agency Regulatory Policy Officer).

(7) Paragraph 7, Measurement/Verification is an explanation of how compliance with requirements will be measured. Specify the information that is needed to support senior management’s evaluation of performance for compliance and implementation. Where quantitative evaluation is possible, identify what data is to be collected, who collects the data, and who receives the data for evaluation. Cross-reference measurement/ verification data that responds to externally imposed requirements to provide traceability to those requirements, for example, Government Performance and Results Act reporting requirements. “Shall” statements are not included in this section.

Note: This information may be presented as text within the paragraph, as a verification matrix, as an attachment to the NPD or CPD that includes details of data and report of data, such as formats and timelines; or as a citation to an NPD, CPD, or another requirements document.

(8) Paragraph 8, Cancellation contains a list of directives that will be canceled upon issuance. If the issuance cancels one or more directives, cite the Directive Number(s), Title(s), and Effective Date(s). If the issuance does not cancel a directive, state “None.”

If yes, compliant. If no, not compliant.

e. Attachments contain supplementary material related to the main text in the NPD or CPD (e.g., definitions, acronyms, verification matrices, etc.) that are attached at the end.

(1) Ensure that attachments do not contain requirements (“shall” statements) for civil service employees, only supporting information for the NPD or CPD.

(2) Number paragraphs in attachments using the letter of the attachment (e.g., A.1, A.2), excluding attachments containing acronyms and definitions.

(3) Document any definitions for words and phrases used in the NPD or CPD in Attachment A.

(a) List the definitions in alphabetical order.

(b) Provide only definitions for terms that are unique to the NPD or CPD and only if the definitions are different than those used in dictionaries or other standard usage.

(c) Use bullets (e.g., “●”) for definitions with extended explanations.

(4) Document abbreviations and acronyms used in the NPD or CPD in Attachment B and list in alphabetical order. To avoid blank attachments, if there are no definitions placed in Attachment A, acronyms can be placed in Attachment A only if there are no other attachments that can be placed before the acronyms.

(5) Document verification/measurement matrices used in the NPD or CPD, in Attachment C. To avoid blank attachments, if there are no definitions placed in Attachment A or acronyms placed in Attachment B, a measurement/verification matrix can be placed in either of these attachments only if there are no other attachments that can be placed before the matrices.

Note: NPD and CPD attachments may be text and/or images. Contact your local DM for instructions.

a. Identify all requirements statements by using the term "shall" to denote mandatory compliance.

b. Designate at least one official (by position title) or organization or office title as responsible and accountable for development, implementation, maintenance, and/or verification of the requirement set forth in the "shall" statement.

c. Identify what action should be accomplished or what product should be provided to demonstrate compliance with the requirement.

d. Identify specific requirements, not general responsibilities with broad application.

e. Provide a description of how requirements will be measured/verified in the measurement/verification section of the directive.

f. Separately state each individual requirement statement (i.e., one "shall" statement per single paragraph and one "shall" statement per paragraph with subparagraphs).

g. Exclude replication of existing internal or external policy statements, procedural requirements, responsibilities, or text from other documents. However, paraphrasing or cross-referencing may be used to summarize information in a way that is significantly different from the original text (i.e., responsible office's own words). NASA directives may supplement, clarify, or make more stringent external requirements or designate who is responsible for implementation of external requirements.

h. Exclude technical requirements in NASA directives. Technical requirements may be included in NASA technical standards, then cited in NASA directives.

a. Authority document citations list the higher-level document(s) that authorize establishing the policy or requirements contained in the directive. Authority documents can be cited in the text of directives to provide the context, as determined by the Responsible Office.

b. Applicable documents and forms citations consist of documents and forms incorporated by reference in the text of the directive, contain provisions or other pertinent requirements directly related to and necessary for the performance of the activities specified by the directive, and use only controlled and current forms.

(1) Cite all applicable documents and forms listed in paragraph 4 at least once within the text of the NPD. Use statements to introduce applicable documents and forms (e.g., as required by, according to, under, or per).

(2) Conversely, list all applicable documents and forms cited within the text of the NPD in paragraph 4.

c. References are documents that may be cited in the text of the directive, but do not constitute requirements to perform activities in the directive. These documents may consist of internal and external requirements and other resources considered to be useful as background information for the reader (to help in understanding the subject matter).

(1) If citing reference documents listed in an NPD's attachment, cite at least once in the text of the directive. Use statements to introduce reference documents (e.g., additional information on this subject is available at/in..., for additional information, see...).

a. List documents in the following order: United States Code, Public Law, Executive Orders, Code of Federal Regulations, Federal Register Notices, Office of Management and Budget Circulars, NPDs, NPRs, NIDs, NPSs, NPIs, NCs, CPDs, CPRs, CIDs, NASA Technical Standards, NASA Forms, non-NASA Government standards, and other documents.

b. List numbered documents in numerical order first and non-numbered documents list in alphabetical order second within each category.

c. List document and form citations using the following format:

(1) National Aeronautics and Space Act, 51 U.S.C. § 20113 (a).

(2) White House Conference on the Arts Act of 1990, Pub. L. 101-509, 104 Stat. 1427 (1990).

(3) Regulatory Planning and Review, E. O. 12866, 3 CFR 638 (1993).

(4) National Space Grant College and Fellowship Program, 14 CFR pt. 1259.

(5) Environmental statements or availability, 71 FR 67389 (Nov. 21, 2006).

(6) OMB Circular A-19, Legislative Coordination and Clearance (09/20/1979).

(7) NPD 1400.1, Documentation and Promulgation of NASA Internal Requirements.

(8) NPR 1400.1, NASA Directives Procedural Requirements.

(9) NID 8000.104, Acquisition of Administrative Office Space.

(10) NC 1000.33, Partnership Council.

(11) NPS 3713.101, Policy Statement on Diversity, Equity, Inclusion, and Accessibility for NASA’s Workforce and Workplaces.

(12) NPI 1000.99, Role of Jet Propulsion Laboratory in NASA Decision-Making Processes.

(13) NASA-STD-8709.2, NASA Safety and Mission Assurance Roles and Responsibilities for Expendable Launch Vehicle Services.

(14) NHQ Form 184, NASA Directive Request Summary.

Note: For documents listed in paragraphs 3.3.2c(1)-(5), the name appears first and the citation location appears second. For documents listed in paragraphs 3.3.2c(6)-(12), the document type and number appear first and the name appears second.

d. Cite documents and forms within the text of directives as follows:

(1) Use the document name and citation location and exclude the name, after first use, when citing within the text of directives for documents described in paragraphs 3.3.2c(1)-(5) (e.g., First use: The National Aeronautics and Space Act, 51 U.S.C. § 20113 (a) - Second use: 51 U.S.C. § 20113 (a)).

(2) Use the document type, number, and name, but exclude the name, after first use, when citing within the text of directives for citations described in paragraphs 3.3.2c(6)-(14) (e.g., First use: NPR 1400.1, NASA Directives Procedural Requirements - Second use: NPR 1400.1).

e. Exclude the revision letter designation and change numbers when citing or listing NASA directives within NASA directives (see Figure 3-1).

f. Ensure that documents and forms cited in the directive are approved documents that are available to the reader.

g. Include a document’s title and URL in a footnote if it is not a Federal statute or regulation, a NASA directive, or is not available in the NASA Technical Standards System to show readers precisely where to find the cited document.

h. Refer to one or more of the following resources to ensure that citations are current and accurate:

(1) United States Code Citations: http://uscode.house.gov.

(2) Public Laws citations:

http://uscode.house.gov/popularnames/popularnames.htm.

(3) Executive Order citations: https://www.federalregister.gov/presidential-documents.

(4) Federal Register citations: https://www.govinfo.gov/app/collection/FR/.

(5) Code of Federal Regulations citations: https://ecfr.gov.

(6) NASA Directives Library: http://nodis3.gsfc.nasa.gov/.

(7) NASA Standards: https://standards.nasa.gov/.

(8) NASA Forms: https://nef.nasa.gov/.

i. Use the following abbreviations for citations described in paragraphs 3.3.2b(1)-(5):

(1) United States Code - U.S.C.

(2) Federal Register - FR.

(3) Code of Federal Regulations - CFR.

(4) Part - pt., Parts - pts.

(5) Subpart - subpt., Subparts - subpts.

(6) Appendix - app.

(7) Chapter - ch., Chapters - chs.

(8) Subchapter - subch. Subchapters - subchs.

(9) Section - §, Sections - §§

(10) Section - sec.

(11) Executive Orders – E.O.

(12) Public Law – Pub. L.

Note: The word “section” instead of the symbol is used when it is the first word in a sentence. The word is also used in the text of the body and footnotes of law reviews and other documents except when referring to the U.S. Code. Otherwise, the symbol is used. (e.g., The National Aeronautics and Space Act, 51 U.S.C. § 20113 (a)).

a. Format Styles:

(1) Use page numbers (e.g., 1, 2, 3) in NPRs, but exclude page numbers from the table of contents.

(2) Number/letter all paragraphs. If there is not a second paragraph immediately following at the same level or no subparagraphs, do not number/letter the paragraph. Exclude periods behind numbered paragraphs (e.g., use 3.5.1 or 3.5.1h, not 3.5.1. or 3.5.1.h.), but include periods behind lettered paragraphs (e.g., use i., not i).

(3) Align all text along the left margin (i.e., left justify or flush left).

(4) Indent and italicize notes.

(5) Bold chapter, appendix, second-level paragraph section, figure and table headings and include a period after each chapter number, appendix letter, and figure and table numbers and letters as follows:

(a) For NPDs:

(i) 1. [Title].

(ii) Attachment A. [Title].

(iii) Figure 1. [Title] or Table 1. [Title] in Sections.

(iv) Figure A. [Title] or Table A. [Title] in Attachments.

(6) Center figures and tables.

(a) Number all figures and tables (e.g., Figure 1. or Table 1.) placed in chapters using the number of the chapter. Add the figure number and title at the bottom of the figure and add the table number and title at the top of the table. If there is more than one figure or table in a chapter, add a dash and an additional number to indicate that it is the first, second, or third figure or table (e.g., Figure 1-1, 1-2, 1-3, or Table 1-1, 1-2, 1-3, etc.).

(b) Letter all figures and tables (e.g., Figure A. or Table A.) placed in appendices using the letter of the appendix. Add the figure letter and title at the bottom of the figure and add the table letter and title at the top of the table. If there is more than one figure or table in the appendix, add a dash and a number to indicate that it is the first, second, or third table (e.g., Figure A-1, A-2, A-3 or Table A-1, A-2, A-3, etc.).

Note: Adherence to paragraphs 3.5.1a(1)-(6) is under the discretion of the Center official responsible for the format styles for Center-level directives.

b. Writing Styles:

(1) Use NPR 1450.10 to supplement the style requirements in this directive.

(2) Exclude caveat phrases, ambiguous terms, and vague terms (e.g., “as applicable,” “as appropriate,” “whenever possible,” “as soon as possible,” “in a timely manner,” “etc.”) within requirements statements.

(3) Use the correct term (e.g., “shall,” “may or can,” “should,” “will,” and “are/is”) to denote action or other forms of action. See paragraph P.2b.

b. Change Log. (Not used in revisions to Agency-level directives.)

c. Preface titles, chapter titles, second-level paragraph titles, and appendix titles.

Note: Figures and tables may be listed in the NPR's table of contents.

Note: Use Figure 3-2 below if paragraphs go beyond the 4th level. (Right click to download figure)

P.1 Purpose

P.2 Applicability

P.3 Authority

P.4 Applicable Documents and Forms

P.5 Measurement/Verification

P.6 Cancellation

[From 3.6.2c(2)(a)-(f)]

(a) “This directive is applicable to NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers.”

(b) If the directive applies to Jet Propulsion Laboratory (JPL), a Federally Funded Research and Development Center (FFRDC), include this statement, "This directive is applicable to the Jet Propulsion Laboratory, a Federally Funded Research and Development Center (FFRDC), only to the extent specified in the NASA/Caltech Prime Contract." If the directive does not apply to JPL, an FFRDC, remove the applicability statement referencing JPL, an FFRDC, if mentioned.

Note 1: A directive does not apply to JPL, an FFRDC, unless it is on the Listing of the NASA Directives and Standards in the NASA/FFRDC Prime Contract and has been incorporated into the NASA/Caltech Prime Contract.

Note 2: JPL, an FFRDC, may review new and revised directives even if they are not in the NASA/FFRDC Prime Contract and provide comments or no comments as deemed necessary. However, inherently Governmental directives are usually not reviewed by JPL since they only apply to the Government.

(c) If the directive applies to other contractors, recipients of grants or cooperative agreements, or parties to other agreements, include this statement, "This directive is applicable to other contractors, recipients of grants or cooperative agreements, or parties to other agreements only to the extent specified in contracts, grants or cooperative agreements, or other agreements."

Note 1: Only list the type of document (i.e., contract, grant, or agreement) to which the directive applies. For example, if the directive is not applicable to a "grant," only list "contract or agreement" to indicate the directive's applicability.

Note 2: This statement alone is not sufficient to stipulate requirements for the contractor or recipient of the grant. Requirements can be delineated by adding a note after the requirements' paragraph. See paragraphs 2.6.1b and 2.19.6 note for examples of delineating requirements between civil servants and contractors or recipients of grants.

(d) For CPRs, include a statement to ensure applicability at the Center and associated facilities.

(e) “In this directive, all mandatory actions (i.e., requirements) are denoted by statements containing the term “shall.” The terms: “may” or “can” denote discretionary privilege or permission, “should” denoted a good practice, and is recommended, but not required, “will” denotes expected outcome, and “are/is” denotes descriptive material.”

(f) “In this directive, all document citations are assumed to be the latest version unless otherwise noted.”

a. Identify all requirements statements by using the term “shall” to denote mandatory compliance.

b. Designate at least one official (by position title) or organization or office title as responsible and accountable for development, implementation, maintenance, and/or verification of the requirement set forth in the “shall” statement.

c. Identify what action should be accomplished or what product should be provided to demonstrate compliance with the requirement.

d. Identify specific requirements, not general responsibilities with broad application.

e. Provide a description of how requirements will be measured/verified in the measurement/verification section of the directive.

f. Separately state each individual requirement statement (i.e., one “shall” statement per single paragraph and one “shall” statement per paragraph with subparagraphs).

g. Exclude replication of existing internal or external policy statements, procedural requirements, responsibilities, or text from other documents. However, paraphrasing or cross-referencing may be used to summarize information in a way that is significantly different from the original text (i.e., responsible office’s own words). NASA directives may supplement, clarify, or make more stringent external requirements or designate who is responsible for implementation of external requirements.

h. Exclude technical requirements in NASA directives. Technical requirements may be included in NASA technical standards, then cited in NASA directives.

a. Authority document citations list the higher-level document(s) that authorize establishing the policy or requirements contained in the directive. Authority documents can be cited in the text of directives to provide the context, as determined by the Responsible Office.

b. Applicable documents and forms citations consist of documents and forms incorporated by reference in the text of the directive, contain provisions or other pertinent requirements directly related to and necessary for the performance of the activities specified by the directive, and use only controlled and current forms.

(1) Cite all applicable documents and forms listed in P.4 at least once within the text of the NPR/CPR. Use statements to introduce applicable documents and forms (e.g., as required by, according to, under, or per).

(2) Conversely, list all applicable documents and forms cited within the text of the NPR/CPR in P.4.

c. References are documents that may be cited in the text of the directive, but do not constitute requirements to perform activities in the directive. These documents may consist of internal and external requirements and other resources considered to be useful as background information for the reader (to help in understanding the subject matter).

(1) If citing reference documents listed in an NPR's/CPR’s appendix, cite at least once in the text of the directive. Use statements to introduce reference documents (e.g., additional information on this subject is available at/in..., for additional information, see...).

(2) Conversely, list reference documents cited in the text of the NPR in the appendix.

a. List documents in the following order: United States Code, Public Law, Executive Orders, Code of Federal Regulations, Federal Register Notices, Office of Management and Budget Circulars, NPDs, NPRs, NIDs, NPSs, NPIs, NCs, CPDs, CPRs, CIDs, NASA Technical Standards, NASA Forms, non-NASA Government standards, and other documents.

b. List numbered documents in numerical order first and non-numbered documents list in alphabetical order second within each category.

c. List document and form citations using the following format:

(1) National Aeronautics and Space Act, 51 U.S.C. § 20113 (a).

(2) White House Conference on the Arts Act of 1990, Pub. L. 101-509, 104 Stat. 1427 (1990).

(3) Regulatory Planning and Review, E. O. 12866, 3 CFR 638 (1993).

(4) National Space Grant College and Fellowship Program, 14 CFR pt. 1259.

(5) Environmental statements or availability, 71 FR 67389 (Nov. 21, 2006).

(6) OMB Circular A-19, Legislative Coordination and Clearance (09/20/1979).

(7) NPD 1400.1, Documentation and Promulgation of NASA Internal Requirements.

(8) NPR 1400.1, NASA Directives Procedural Requirements.

(9) NID 8000.104, Acquisition of Administrative Office Space.

(10) NC 1000.33, Partnership Council.

(11) NPS 3713.101, Policy Statement on Diversity, Equity, Inclusion, and Accessibility for NASA’s Workforce and Workplaces.

(12) NPI 1000.99, Role of Jet Propulsion Laboratory in NASA Decision-Making Processes.

(13) NASA-STD-8709.2, NASA Safety and Mission Assurance Roles and Responsibilities for Expendable Launch Vehicle Services.

(14) NHQ Form 184, NASA Directive Request Summary.

Note: For documents listed in paragraphs 3.3.2c(1)-(5), the name appears first and the citation location appears second. For documents listed in paragraphs 3.3.2c(6)-(12), the document type and number appear first and the name appears second.

d. Cite documents and forms within the text of directives as follows:

(1) Use the document name and citation location and exclude the name, after first use, when citing within the text of directives for documents described in paragraphs 3.3.2c(1)-(5) (e.g., First use: The National Aeronautics and Space Act, 51 U.S.C. § 20113 (a) - Second use: 51 U.S.C. § 20113 (a)).

(2) Use the document type, number, and name, but exclude the name, after first use, when citing within the text of directives for citations described in paragraphs 3.3.2c(6)-(14) (e.g., First use: NPR 1400.1, NASA Directives Procedural Requirements - Second use: NPR 1400.1).

e. Exclude the revision letter designation and change numbers when citing or listing NASA directives within NASA directives (see Figure 3-1).

f. Ensure that documents and forms cited in the directive are approved documents that are available to the reader.

g. Include a document’s title and URL in a footnote if it is not a Federal statute or regulation, a NASA directive, or is not available in the NASA Technical Standards System to show readers precisely where to find the cited document.

h. Refer to one or more of the following resources to ensure that citations are current and accurate:

(1) United States Code Citations: http://uscode.house.gov.

(2) Public Laws citations:

http://uscode.house.gov/popularnames/popularnames.htm.

(3) Executive Order citations: https://www.federalregister.gov/presidential-documents.

(4) Federal Register citations: https://www.govinfo.gov/app/collection/FR/.

(5) Code of Federal Regulations citations: https://ecfr.gov.

(6) NASA Directives: http://nodis3.gsfc.nasa.gov/.

(7) NASA Standards: https://standards.nasa.gov/.

(8) NASA Forms: https://nef.nasa.gov/.

i. Use the following abbreviations for citations described in paragraphs 3.3.2b(1)-(5):

(1) United States Code - U.S.C.

(2) Federal Register - FR.

(3) Code of Federal Regulations - CFR.

(4) Part - pt., Parts - pts.

(5) Subpart - subpt., Subparts - subpts.

(6) Appendix - app.

(7) Chapter - ch., Chapters - chs.

(8) Subchapter - subch. Subchapters - subchs.

(9) Section - §, Sections - §§

(10) Section - sec.

(11) Executive Orders – E.O.

(12) Public Law – Pub. L.

Note: The word “section” instead of the symbol is used when it is the first word in a sentence. The word is also used in the text of the body and footnotes of law reviews and other documents except when referring to the U.S. Code. Otherwise, the symbol is used. (e.g., The National Aeronautics and Space Act, 51 U.S.C. § 20113 (a)).

a. Format Styles:

(1) Use page numbers (e.g., 1, 2, 3) in NPRs, but exclude page numbers from the table of contents.

(2) Number/letter all paragraphs. If there is not a second paragraph immediately following at the same level or no subparagraphs, do not number/letter the paragraph. Exclude periods behind numbered paragraphs (e.g., use 3.5.1 or 3.5.1h, not 3.5.1. or 3.5.1.h.), but include periods behind lettered paragraphs (e.g., use i., not i).

(3) Align all text along the left margin (i.e., left justify or flush left).

(4) Indent and italicize notes.

(5) Bold chapter, appendix, second-level paragraph section, figure and table headings and include a period after each chapter number, appendix letter, and figure and table numbers and letters as follows:

(b) For NPRs:

(i) Chapter 1. [Title].

(ii) Appendix A. [Title].

(iii) 1.1 [Title].

(iv) Figure 1. [Title] or Table 1. [Title] in Chapters.

(v) Figure A. [Title] or Table A. [Title] in Appendices.

(6) Center figures and tables.

(a) Number all figures and tables (e.g., Figure 1. or Table 1.) placed in chapters using the number of the chapter. Add the figure number and title at the bottom of the figure and add the table number and title at the top of the table. If there is more than one figure or table in a chapter, add a dash and an additional number to indicate that it is the first, second, or third figure or table (e.g., Figure 1-1, 1-2, 1-3, or Table 1-1, 1-2, 1-3, etc.).

(b) Letter all figures and tables (e.g., Figure A. or Table A.) placed in appendices using the letter of the appendix. Add the figure letter and title at the bottom of the figure and add the table letter and title at the top of the table. If there is more than one figure or table in the appendix, add a dash and a number to indicate that it is the first, second, or third table (e.g., Figure A-1, A-2, A-3 or Table A-1, A-2, A-3, etc.).

Note: Adherence to paragraphs 3.5.1a(1)-(6) is under the discretion of the Center official responsible for the format styles for Center-level directives.

b. Writing Styles:

(1) Use NPR 1450.10 to supplement the style requirements in this directive.

(2) Exclude caveat phrases, ambiguous terms, and vague terms (e.g., “as applicable,” “as appropriate,” “whenever possible,” “as soon as possible,” “in a timely manner,” “etc.”) within requirements statements.

(3) Use the correct term (e.g., “shall,” “may or can,” “should,” “will,” and “are/is”) to denote action or other forms of action. See paragraph P.2b.

(i) List the definitions in alphabetical order.

(ii) Provide only definitions for terms used in the NPR and only if the definitions are different than those used in dictionaries or other standard usage.

(iii) Use bullets (e.g., “•”) for definitions with extended explanations.

Note: To avoid blank appendices, if there are no definitions placed in Appendix A or acronyms placed in Appendix B, a measurement/ verification matrix can be placed in either of these appendices only if there are no other appendices that can be placed before the matrices.