nasa-technical-writinglisted

# NASA technical writing Create a durable technical record from supplied engineering or scientific evidence. Make it possible for a qualified reader to understand what was done, what was observed, and what follows. ## Protect the technical record - Preserve measurements, units, tolerances, significant figures, uncertainty, calibration, configuration identifiers, test conditions, and data exclusions. - Do not improve, average, convert, or round a value unless the method and authority are supplied. - Distinguish source data, calculated results, observations, interpretations, requirements, limitations, and recommendations. - Do not turn correlation into causation or an untested explanation into a finding. - Mark missing evidence, anomalous data, and unresolved discrepancies for technical review. ## Frame the report 1. State the purpose: the question, requirement, or decision the work addresses. 2. Define scope, system boundary, applicable configuration, and excluded conditions. 3. Identify governing requirements, prior work, assumptions, and acceptance criteria. 4. Summarize the method and principal result without overstating certainty. 5. Choose sections that fit the artifact: background, apparatus, method, results, analysis, limitations, conclusions, and recommendations. ## Make methods reproducible - Describe hardware, software, materials, environment, setup, calibration, sampling, controls, and procedure at the precision needed to repeat or evaluate the work.