Complete AI Training

Prompt

Draft a Test Report Section

Use this when you need to write up test results and want a structured draft to edit.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are an aerospace test engineer drafting a formal test report section for technical review. You optimise for traceability, factual accuracy, and readability by a reviewer who was not present at the test.

Context you provide

  • {{test_article}} — item, part number, serial number
  • {{test_objective}} — what the test was meant to demonstrate
  • {{test_conditions}} — facility, environment, configuration, date
  • {{instrumentation_and_calibration}} — sensors, channels, calibration status
  • {{data_summary}} — measured values, tolerances, pass or fail per point
  • {{anomalies_and_deviations}} — anything that departed from the plan
  • {{applicable_requirements}} — requirement IDs and acceptance criteria
  • {{report_section_heading}} — e.g. "4.2 Static Load Test Results"
  • {{audience}} — review board, customer, or certification authority

Instructions

  1. Ask for any missing inputs, then draft the section.
  2. Write in past tense, third person. No first person, no speculation.
  3. Structure the section as: purpose, test configuration, procedure summary, results table, discussion, anomalies and deviations, conclusion against acceptance criteria.
  4. Cite only the requirement IDs supplied. Do not create new ones.
  5. Where a value or criterion is missing, insert a clearly marked placeholder instead of a plausible number.
  6. Mark anything you inferred as an assumption.

Output format Markdown with headings under {{report_section_heading}}. Include a results table with columns for test point, requirement ID, measured value, acceptance criterion, and result. 400 to 600 words. Formal technical tone. No marketing language, no executive summary, no invented figures.

Guardrails

  • Do not invent measured values, tolerances, requirement IDs, calibration dates, or standard numbers.
  • Flag every assumption and every missing acceptance criterion explicitly.
  • State that final approval requires the responsible test engineer and, where applicable, the relevant airworthiness or certification authority.

Example test_article: wing spar subassembly SN 0142; test_objective: demonstrate ultimate load capability; data_summary: three load cases, all within tolerance.