Submittal readiness
Authority-submittal readiness review before you file
An authority-submittal readiness review checks whether a certification data package is internally consistent and complete enough to file, taking the reviewer's seat before the authority does. It is used by avionics, equipment, and modification teams at the point of submitting an STC, TSO, or change application. It reviews the package contents against the plan, the cross-references between documents, the compliance reports, and the open items the submission still carries. You receive a submittal readiness assessment, a defect list ordered by likely review impact, and a recommendation on what to resolve before filing.
When this review is needed
- A submission is days from filing and the team wants an independent read before it leaves the building.
- The package was assembled from artifacts authored by several groups and nobody has read it cover to cover as one document.
- A prior submission drew avoidable questions and the team wants to file cleaner this time.
- Leadership needs a go or no-go call on filing supported by a concrete defect list.
The problem
A package can be technically sound and still file badly. Documents reference each other by titles that have since changed, the cover compliance report points at sections that moved, and open items are buried instead of declared. A reviewer who hits a dead reference on the first page reads the whole submission more skeptically.
What gets reviewed
- The package contents checked against the certification plan and submittal list
- Cross-references between documents and whether they resolve to the right place
- The cover compliance report and its alignment with the underlying evidence
- Open items, deviations, and assumptions and whether they are clearly declared
- Document control, revision marks, and approval signatures across the set
- The narrative that walks a reviewer from the basis to the evidence
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Identify what is missing against the means of compliance.
What gets validated
- Every artifact the plan lists is present in the package and current
- Cross-document references resolve to the correct, current section or document
- The compliance report aligns with the evidence it summarizes
- Open items and assumptions are declared in the submission rather than hidden
- Revision identifiers and approval status are consistent across the set
- A reviewer can navigate from the certification basis to the substantiation without gaps
- The submittal matches the application type and its expected content
Evidence normally required
- The assembled data package or its index
- The certification plan and the agreed submittal list
- The cover compliance report or summary
- The open-item, deviation, and assumption logs
- Document control and approval status for the included artifacts
Common discrepancies
- References to documents or sections that have since been renamed or moved
- A compliance report that summarizes evidence the package does not actually contain
- Open items present in the engineering records but absent from the submission
- Mixed revisions of the same artifact included in one package
- Artifacts listed in the plan that never made it into the assembled set
- Approval signatures missing on documents the submittal depends on
What is at stake
Avoidable defects in the package convert into authority questions, and questions add review rounds that the program did not schedule. Each round delays the issuance the business is waiting on and pulls engineers off the next program to answer items that a final read would have caught.
How the work runs
Check against the plan
Confirm every artifact the certification plan calls for is present and current.
Read as a reviewer
Walk the package front to back, resolving cross-references and testing navigation.
Reconcile the cover
Align the compliance report with the evidence and surface any undeclared open items.
Call the decision
Issue a go or no-go recommendation with a prioritized fix list.
What the buyer receives
- A submittal readiness assessment with a go or no-go recommendation
- A defect list ordered by likely review impact
- A short list of items to resolve before filing
Who uses the output
- Certification leads making the filing decision
- Program management closing the pre-filing defects
How the work fits into the transaction or program
The review is the last gate before a package leaves for the authority, focused on whether the assembled submission holds together as one document. It follows deeper evidence and traceability work and turns their outputs into a clean filing decision.
Start with a single asset
Reduce finding cycles by checking the package first.
Regulatory limits
Endeavor Elements reviews the applicant's submission for completeness and consistency. It does not file on the applicant's behalf, make compliance findings, or guarantee the authority will accept the package. The applicant files and the authority decides.
What this review does not cover
- Filing the application or corresponding with the authority
- Making compliance findings or issuing any approval
- Authoring the missing artifacts the defect list identifies
Specific to this review
- The review reads the package the way an examiner would, front to back, so navigation defects surface the way they will during review rather than after.
- First-page dead references carry outsized cost, because an early broken link sets a skeptical tone for the rest of the read.
- Declared open items read better than discovered ones; submissions that hide open work tend to draw more questions than those that state it plainly.
- Mixed revisions inside one package are a recurring filing defect when artifacts are pulled from tools at different moments during assembly.
Sources
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
SAE International. Development assurance process at aircraft and system level, including requirements capture and validation.
Frequently asked questions
Will you tell us whether the authority will accept the package?
No. We assess whether the package is complete, consistent, and ready to file. Acceptance is the authority's decision. A cleaner filing reduces avoidable questions but does not guarantee an outcome.
Does this replace a full evidence review?
No. This is a final readiness gate on the assembled submission. It assumes the deeper evidence and traceability work is done and checks that the package files well.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Walk through your situation with an engineer who has done this work.