Write a verification close-out report

Use this skill

Use Arc Skills to draft a verification close-out report for the supplied baseline.

Inputs:
- Controlled in-scope requirement baseline, configuration, and report cutoff
- Current matrix and Run or report index with exact evidence locators
- Failures, incomplete work, anomalies, deviations, waivers, exit criteria, and sign-off records

Return scope, evidence index, reconciled disposition, open actions, exit assessment, and blank sign-off block.
Do not count an unsigned waiver as accepted or a failed Run as verified

Set up the toolkit · Read the skill instructions

What you provide and what you get

Eight demonstrated, one failed, one incomplete

Illustrative engineering example.

The illustrative cutoff is baseline B on article A-3. Runs E-1 through E-8 demonstrate R-1 through R-8; E-9 records a valve timing failure; R-10 has no Run. Waiver W-1 for R-9 is unsigned.

Baseline B: R-1…R-10, all in scope. Article A-3.
E-1…E-8: current Pass for R-1…R-8.
E-9: R-9 valve closure 2.3 s against ≤2 s.
R-10: Test T-10 planned, not run. W-1: proposed waiver for R-9, unsigned.

The count reconciles: 8 + 1 + 1 = 10 in-scope requirements. The failed observation is not a “covered pass,” and an unsigned waiver has no approved effect on the technical result.

The report excerpt below maps all ten requirements to specific evidence or an unrun Test. It leaves source revision details and exit criteria as placeholders because they were not supplied; a closed campaign can still have open requirement close-out actions.

Close-out report excerpt

Verification close-out report — illustrative excerpt
Scope: Baseline B, R-1 through R-10, article A-3.
Cutoff: after E-9 and before T-10 execution; report date [not supplied].
Disposition: 8 demonstrated; 1 failed; 1 incomplete. Total: 10.

Evidence index (exact report revisions/sections: [not supplied]):
R-1 → E-1 Pass    R-2 → E-2 Pass    R-3 → E-3 Pass    R-4 → E-4 Pass
R-5 → E-5 Pass    R-6 → E-6 Pass    R-7 → E-7 Pass    R-8 → E-8 Pass
R-9 → E-9 Fail, 2.3 s against ≤2 s; W-1 proposed and unsigned
R-10 → T-10 planned; no Run

Plan exit criteria: [controlled plan and criteria not supplied].
Gate assessment: undetermined against the plan; R-9 disposition and R-10 execution open.
Recommendation: do not declare baseline B verified at this cutoff.

Technical reviewer: __________________  Date: __________
Approval authority: _________________  Decision: ______  Date: __________

Reconcile before writing the conclusion

1. Fix report cutoff, requirement baseline, article, and exclusion rules.
2. Map each requirement to current evidence and the applicable acceptance result.
3. Count demonstrated, failed, incomplete, and formally dispositioned exceptions exactly once.
4. State unmet exit criteria and open owner actions; leave approval fields for authorized reviewers.

Questions about this task

Can W-1 make R-9 verified?

An unsigned proposal cannot. Even an approved deviation is a formal disposition, not a retroactive passing measurement.

Why include R-10 if its Test is planned?

Because the baseline includes R-10 and a planned Test has no executed result at the cutoff.

Sources and further reading

• NASA Systems Engineering Handbook: Lifecycle and requirements guidance; the example decisions are illustrative.

Related tasks

• Identify requirements without verification coverage: Prepare the gap register used in the close-out denominator.
• Assess whether test results demonstrate a requirement has been met: Resolve E-9’s technical outcome before final disposition.