Certification plan evidence review for quality teams

When this review is needed

• A certification plan is heading to the authority for concurrence and quality wants its commitments checked against reality first.
• A design change has redrawn the affected areas and the plan has not caught up to the new footprint.
• The plan was written months ahead of the evidence and quality needs to know which promises the data now backs.
• A prior plan drew a finding for a commitment the program could not later meet, and quality wants that avoided.

The problem

A certification plan is written early, when the change is still being scoped and the evidence is a promise rather than a fact. It commits to a basis, a set of affected areas, and a review approach, then the design shifts and the plan does not move with it. Quality ends up holding a document that reads confident and complete while the data package underneath it has grown a different shape, and the mismatch only shows when the authority reads both.

What gets reviewed

• The stated certification basis checked against the change so the plan neither over-claims nor omits an applicable requirement
• Affected areas in the plan compared to the change's real footprint on the design
• Compliance methods the plan commits to matched against the evidence types the program will actually produce
• Review and involvement commitments to the authority checked for deliverability within the schedule
• Roles, delegations, and responsibilities in the plan reconciled with who will actually generate and sign the evidence

What gets validated

• Every basis requirement the change triggers appears in the plan, and every requirement the plan names is actually triggered
• Each affected area the plan claims corresponds to a real design impact, with no unlisted area left out
• The compliance method committed per requirement is one the evidence path can deliver, not one chosen for convenience
• Authority involvement points named in the plan are consistent with the finding path the program will use
• Named delegations and roles match the people and authorizations the program actually holds

Evidence normally required

• The certification plan at its current draft revision
• The change definition or project scope that the plan responds to
• The certification basis, issue papers, and any special conditions in play
• The compliance approach or means-of-compliance agreement the plan relies on
• Any prior plan for the product and the findings it drew

Common discrepancies

• An affected area the change actually touches that the plan never lists
• A compliance method committed in the plan that the evidence path will not support
• A basis requirement carried over from a template that this particular change does not trigger
• An authority involvement commitment the schedule cannot realistically meet

What is at stake

A plan that overcommits sets the program up to miss its own promises in front of the authority. The reviewer holds the team to a compliance method the plan named but the evidence never followed, or to an affected area the change actually left out, and the concurrence that looked routine turns into a renegotiation. Correcting a plan after concurrence costs more credibility than getting it right before.

How the work runs

What the buyer receives

• A gap list naming each plan commitment the evidence cannot yet meet and each affected area the plan missed
• A commitment-to-evidence map tying every promise in the plan to the artifact meant to satisfy it
• A closure sequence ordering the corrections so basis and scope are settled before methods are locked

Who uses the output

• Quality leadership deciding whether the plan is safe to submit for concurrence
• Certification engineers who need to know which commitments to revise before they harden
• Program leads reconciling the schedule against the involvement points the plan promises

How the work fits into the transaction or program

The certification plan is the contract the rest of the effort is measured against, so a plan that overcommits distorts every downstream deliverable. This review runs before concurrence, while commitments are still adjustable, so quality corrects the promises on their own terms rather than after the authority holds the program to a plan it can no longer meet.

Jurisdiction-specific considerations

FAA and EASA structure the plan differently: an FAA certification project follows a project-specific plan and delegated findings, while an EASA project turns on a certification programme, review items, and panel involvement. A plan meant to serve both has to name the finding path each authority expects, so the review reads the commitments against whichever framework the program is filing under.

Regulatory limits

This review reads your certification plan and reports where its commitments are deliverable and where they outrun the evidence. It does not concur with the plan, does not accept the proposed basis or methods, and does not stand in for the authority's or the delegate's review of the plan itself.

What this review does not cover

• Writing or rewriting the certification plan for the program
• Negotiating the basis or affected areas with the authority
• Granting concurrence, which the authority reserves

Specific to this review

• A plan drafted from a template carries requirements the current change does not trigger, and dropping them is as important as adding the ones it missed.
• The affected-areas section fails more often by omission than by error, because a late design change adds a footprint no one folded back into the plan.
• Committing to test where analysis would do, or the reverse, locks the program into an evidence path the schedule cannot afford.
• The plan's involvement commitments are read literally by a reviewer, so a promise the schedule cannot keep becomes a finding rather than a courtesy.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits