Nexus Aero
Follow us
Stay updated

NEXUS AVIATION RESOURCES

Service milestone and evidence-handover checklist

Separate physical delivery, technical certification, customer acknowledgement and commercial closure.

English & PersianSource-aware reference

TPL-10 · BLANK SAMPLE

Read the structure. Keep the evidence separate.

Required/when-applicable are Nexus worksheet-completion rules for a stated stage, not assertions of a universal legal requirement. Draft capture can retain unknowns. A critical unknown blocks only the decisions/actions that depend on it; it must not be fabricated to submit a form.

Evidence received, identity matched, issuer checked, purpose reviewed and operationally accepted are separate results. A positive result must name its purpose, scope, actor, time and limitations.

Before sharing

Use only information you are authorized to disclose. These downloads contain no real records or protected manuals. A tracking ID, hash, payment or customer consent does not create aviation authority.

Shared record controls · 14 fields
C-01Record fieldRequired for the stated submission stage

Record identifier

Use a stable identifier; a tracking number does not certify technical status.

Applies when: Required when the worksheet is submitted for the stated purpose; drafts may retain explicit unknowns.

C-02Record fieldRequired for the stated submission stage

Record revision and superseded record

Preserve previous revisions; link reason, affected scope and revalidation instead of overwriting consent/history.

Applies when: Required when the worksheet is submitted for the stated purpose; drafts may retain explicit unknowns.

C-03Record fieldRequired for the stated submission stage

Created/changed timestamps and time zone

Separate actual events from planned dates; retain a clear time-zone/offset convention.

Applies when: Required when the worksheet is submitted for the stated purpose; drafts may retain explicit unknowns.

C-04Record fieldRequired for the stated submission stage

Acting entity, site and capacity

Name the acting organization/site or explicitly record individual capacity; no organizational mandate is inferred.

Applies when: Required when the worksheet is submitted for the stated purpose; drafts may retain explicit unknowns.

C-05Record fieldRequired for the stated submission stage

Prepared by and source of information

Identify preparer and whether each material statement is declared, observed or document-supported.

Applies when: Required when the worksheet is submitted for the stated purpose; drafts may retain explicit unknowns.

C-06ChoiceRequired for the stated submission stage

Information classification

Use public summary, controlled counterparty information or restricted internal evidence; choose minimum necessary disclosure.

Applies when: Required when the worksheet is submitted for the stated purpose; drafts may retain explicit unknowns.

Choices: public summary / controlled counterparty / restricted internal

C-07Record fieldWhen applicable

Linked case/order/article identifiers

Bind related worksheets to the same case and exact article/scope; record the absence of an issued order honestly.

Applies when: Another case, order, worksheet or exact article is linked.

C-08Record fieldRequired for the stated submission stage

Worksheet status and permitted next step

Distinguish draft, evidence pending, held, reviewed for purpose, superseded and administratively closed; these are not airworthiness states.

Applies when: Required when the worksheet is submitted for the stated purpose; drafts may retain explicit unknowns.

C-09ChoiceRequired for the stated submission stage

Real/synthetic/example record designation

Clearly label fictional/demo content. Never present synthetic evidence as approved data or real qualification.

Applies when: Required when the worksheet is submitted for the stated purpose; drafts may retain explicit unknowns.

Choices: real / synthetic demo / blank example / unknown

C-10Repeatable tableWhen applicable

Controlled evidence manifest

Use evidence ID, issuer/title, date/revision, source, article/scope link, review status, custodian and access limit.

Applies when: Evidence is claimed, reviewed or needed for a subsequent decision.

Controlled evidence manifest
Evidence IDIssuer/title/identifierRevision/dateSource/original/copyArticle/scope linkReview result/limitationsCustodianAccess/disclosure limit
Blank sample—no real evidence entered.
C-11Repeatable tableWhen applicable

Review/decision event record

Record actor, actual authority reference/scope, action/outcome, revision, timestamp, evidence and restrictions.

Applies when: A review, approval, rejection, hold or clearance-of-hold decision is recorded.

Review/decision event record
Event IDActor identityActual authority and scopeRecord/action/revisionOutcome and restrictionsTimestamp/time zoneDecision evidence ID
Blank sample—no real evidence entered.
C-12Repeatable tableWhen applicable

Revision/change and affected-consent history

Retain previous decisions; identify changed lines, technical impact and whether fresh commercial consent is required.

Applies when: Any baseline, evidence, scope or decision changes.

Revision/change and affected-consent history
Change IDPrevious/new revisionAffected lines/evidenceChange reasonTechnical/commercial impactRequired review/consent revalidationStatus/actor/time
Blank sample—no real evidence entered.
C-13Record fieldWhen applicable

Disclosure recipient, purpose and restrictions

Record authorized recipient/use, redactions and agreed duration/onward-sharing controls; masking alone is not access control.

Applies when: Any information is disclosed, published or exported.

C-14Record fieldWhen applicable

Record custodian and retention/disposal basis

Reference the actual jurisdiction/organizational/contractual retention rule and any hold; do not set one global retention duration.

Applies when: The worksheet/evidence is retained or disposed of for actual business use.

Controlled service baseline
transactionRecord fieldRequired for the stated submission stage

Transaction/WO, parties, article identity and agreed scope revision

Link transaction/WO, parties, exact article and accepted scope revision; tracking IDs are administrative, not technical release.

Applies when: Required before this worksheet's purpose-limited submission/review; a draft may retain explicit unknowns.

termsRecord fieldRequired for the stated submission stage

Governing terms, consent version and named representatives

Record actual terms/revision, representative authority and evidence of acceptance; no implied consent from receipt or silence.

Applies when: Required before this worksheet's purpose-limited submission/review; a draft may retain explicit unknowns.

planRepeatable tableRequired for the stated submission stage

Milestone plan with responsible party and evidence needed

Identify each stage owner, prerequisite, evidence and planned milestone; a project plan is not authorization to execute.

Applies when: Required before this worksheet's purpose-limited submission/review; a draft may retain explicit unknowns.

Milestone plan with responsible party and evidence needed
Milestone ID/typeResponsible partyPrerequisite/evidence IDsPlanned event/timeCompletion evidence needed
Blank sample—no real evidence entered.

Use stable row identifiers and link supporting evidence; unknown is not zero or verified.

Repeatable milestone rows
stageRepeatable tableRequired for the stated submission stage

Milestone, prerequisites and permitted next action

Name the milestone and permitted next action; retain hold, exception and cancellation branches.

Applies when: Required before this worksheet's purpose-limited submission/review; a draft may retain explicit unknowns.

Milestone, prerequisites and permitted next action
Milestone IDStage/statusMet/unmet prerequisitesPermitted next actionRestriction and owner
Blank sample—no real evidence entered.

Use stable row identifiers and link supporting evidence; unknown is not zero or verified.

planned-actualRepeatable tableRequired for the stated submission stage

Planned/actual dates, time zones and delay reasons

Keep planned and actual events distinct; record time zone, pauses and factual reasons rather than overwriting baseline.

Applies when: Required before this worksheet's purpose-limited submission/review; a draft may retain explicit unknowns.

Planned/actual dates, time zones and delay reasons
Milestone IDBaseline planned timestampActual timestamp or not yet occurredTime zonePause/delay reason and evidence
Blank sample—no real evidence entered.

Use stable row identifiers and link supporting evidence; unknown is not zero or verified.

evidenceRepeatable tableRequired for the stated submission stage

Evidence IDs, issuer, revision and controlled access

Use exact evidence/issuer/revision and article/scope linkage; a document hash alone is not issuer authentication.

Applies when: Required before this worksheet's purpose-limited submission/review; a draft may retain explicit unknowns.

Evidence IDs, issuer, revision and controlled access
Milestone IDEvidence IDIssuer/date/revisionMatched article/scopeReview result/restrictionCustodian/access reference
Blank sample—no real evidence entered.

Use stable row identifiers and link supporting evidence; unknown is not zero or verified.

decisionRepeatable tableRequired for the stated submission stage

Decision, decision-maker authority and open exceptions

Record the decision-maker's actual scoped authority, outcome and open exceptions; no automatic all-stages-complete result.

Applies when: Required before this worksheet's purpose-limited submission/review; a draft may retain explicit unknowns.

Decision, decision-maker authority and open exceptions
Milestone IDDecision/statusDecision-maker and scoped authorityDecision timestampDecision evidence/revisionOpen exception/owner
Blank sample—no real evidence entered.

Use stable row identifiers and link supporting evidence; unknown is not zero or verified.

Handover and closure evidence
technical-releaseRecord fieldWhen applicable

Technical/release record reference and authenticity-review status, where required

Identify the actual required maintenance/release record and stated work. Record authenticity/issuer checks, signer authority, article/scope match, result and limitations separately. Receipt alone is not authenticity or acceptance. Do not generate or simulate a certificate here.

Applies when: The work, article, jurisdiction and governing procedure require release/certification evidence.

life-configRecord fieldWhen applicable

Updated configuration/life and completed-scope records

Record completed scope and updated PN/configuration/life information with source and date; retain previous baseline.

Applies when: Work changes configuration/life records or such handover evidence is required.

shipment-receiptRecord fieldWhen applicable

Shipment and recipient acknowledgement, with discrepancies

Link shipment and physical receipt with identity/quantity and discrepancies; receiving is not installation approval.

Applies when: A physical shipment or delivery occurs.

financialRecord fieldWhen applicable

Agreed invoice/payment status, separately from technical acceptance

Separate invoice, credit, payment evidence, disputed sums and reconciliation; a declared payment is not verified settlement.

Applies when: The agreement includes invoices, credits or payment obligations.

remainingRecord fieldWhen applicable

Remaining warranty, return, storage and record duties

Assign warranty, core/loan return, retention, storage and unresolved-duty owners and deadlines as applicable.

Applies when: Any obligation continues after handover or partial commercial closure.

closureRecord fieldWhen applicable

Commercial closure basis and unresolved technical/legal issues

State exactly which commercial obligations are closed and which technical/legal issues remain; closure cannot create release authority.

Applies when: Full or partial commercial closure is proposed.

Additional decision and evidence controls
release-limitationsRecord fieldWhen applicable

Completed-work scope, exclusions and release limitations

Reconcile completed work with actual certification and restrictions; customer receipt does not certify the whole aircraft.

Applies when: Any maintenance release/certification is part of handover.

records-handoverRepeatable tableRequired for the stated submission stage

Record-set handover, recipient and retention basis

Identify exact documents delivered, controlled access, receipt, retained custodian and applicable retention basis; no universal period is assumed.

Applies when: Required before this worksheet's purpose-limited submission/review; a draft may retain explicit unknowns.

Record-set handover, recipient and retention basis
Delivered document ID/revisionArticle/work scope coveredAuthorized recipient/roleDelivery/access and receipt evidenceRetaining custodianJurisdiction/contract retention basisRights/disclosure limits
Blank sample—no real evidence entered.

Use stable row identifiers and link supporting evidence; unknown is not zero or verified.

post-close-reopenRecord fieldRequired for the stated submission stage

Post-handover claim, defect and reopening route

Record how later discrepancies, warranty issues and corrected records are linked without erasing the original closure.

Applies when: Required before this worksheet's purpose-limited submission/review; a draft may retain explicit unknowns.

Completion checks

  • A tracking ID, payment or receipt cannot substitute for actual required maintenance certification.
  • Match records to work actually performed and authorized, including exclusions and limitations.
  • Record specific recipients and retention basis; do not impose one global record package or period.
  • Commercial closure preserves open claims, continuing duties and traceable reopening.

Suggested content journey

These stages describe how to organize the record. They are not evidence of implemented platform controls or authorization to perform maintenance.

  1. 1. Confirm agreed service baselineResponsible role: Authorized parties

    Article, scope/revision, terms and consent links match.

  2. 2. Record each milestone against its own gateResponsible role: Named stage owners

    Actual evidence/authority recorded; no automatic progression from elapsed time/payment.

  3. 3. Handover article and required records separatelyResponsible role: Technical records and logistics custodians

    Completed scope, actual release where required, receipt and document access reconciled.

  4. 4. Close only fulfilled commercial scopeResponsible role: Authorized commercial/finance representatives

    Open technical/legal/financial duties, warranty and retention/reopening remain explicit.

Technical, authority and privacy boundaries

  • Keep quantity, unit, identity and as-of date together; do not sum incompatible units or infer globally unique serial numbers.
  • Life remainders require the governing basis, matching identity/unit and evidenced inputs. Unknown is not zero and overhaul does not reset total-life limits.
  • Name currency and distinguish IRR from IRT when used; no automatic conversion, tax treatment, penalty or settlement is implied.
  • Pool capacity is restricted by actual eligible compatible controlled units, reservations and holds in the specified interval; do not count the same unavailable unit twice.
  • Do not supply generic task limits, test pressures, torques, retirement limits or inspection tolerances; these come from applicable controlled data.
  • Platform account role, job title or Super Admin status is not proof of aviation qualification or task authorization.
  • Record individual and organization/site/capability scope and validity at the time of the relevant action.
  • Qualified proposal review and required physical critical-task independent inspection are separate controls; no universal second-person rule is invented.
  • Customer scope/price consent, technical execution authority, release-to-service and payment are separate events.
  • Existing governed organization controls must not be weakened to complete these worksheets; resolve missing procedure/authority before affected work.
  • Public library blank templates contain no live identity, customer data, credentials, uploaded manuals or approved signatures.
  • Only authorized minimum information is disclosed; a public/private label or blur is not an implemented access-control mechanism.
  • Capture references to lawful sources; do not mirror licensed OEM, ATA or other protected manuals without permission.
  • Evidence hashes can help integrity checking but do not establish issuer authenticity, legal validity or airworthiness.

Reference reading

Connected worksheets

About this collection

Original Nexus explanations and sample worksheets, with official-source links. Not an exhaustive world library, approved maintenance data or regulatory approval.

Content review: 15 October 2026Report a correction Include the item ID and an official source. Do not send confidential records.