Nexus Aero
Follow us
Stay updated

NEXUS AVIATION RESOURCES

RFQ and technical enquiry sheet

Make the requested transaction, technical item and evidence needs clear before quotations are compared.

English & PersianSource-aware reference

TPL-02 · 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.

Request and intended use
request-kindChoiceRequired for the stated submission stage

Requested branch: purchase/supply / repair / exchange / loan / lease / pool enquiry

Use buy/supply, repair, exchange, loan, lease or pool enquiry; select only the relevant branch, not every transaction type.

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

Choices: purchase/supply / repair / exchange / loan / lease / pool enquiry

requesting-orgRecord fieldRequired for the stated submission stage

Requesting organization/site and recipient

Identify requesting entity/site, intended counterparty and the representative's mandate.

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

urgencyRecord fieldRequired for the stated submission stage

Required-by date, time zone and AOG context if applicable

Use a specific date/time/time zone and explain any AOG claim; urgency does not waive technical checks.

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

aircraft-appRecord fieldWhen applicable

Aircraft/model/configuration and intended installation context

Record model/variant, configuration and intended installation context; restrict sensitive operator/aircraft details to approved recipients.

Applies when: Installation/application is known or constrains offered compatibility.

Item lines — repeat for each item
item-pnRepeatable tableRequired for the stated submission stage

Description, exact PN, quantity and unit

One stable line ID per requested article/service; preserve exact PN punctuation, quantity and unit. Mark unidentified items explicitly.

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

Description, exact PN, quantity and unit
RFQ line IDArticle/service descriptionManufacturer and exact PNConfiguration/applicabilityQuantityUnit of measureRequested conditionEvidence required/basis
Blank sample—no real evidence entered.

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

sn-conditionRecord fieldWhen applicable

SN if known, requested condition and evidence

State requested condition separately from any seller condition claim; an exact SN may remain unknown before sourcing.

Applies when: A serialized article or specific condition is relevant to the request.

alternatesRecord fieldWhen applicable

Allowed alternatives and technical acceptance route

State whether alternatives may be offered, with qualified evaluation route; no automatic interchangeability from matching descriptions.

Applies when: Any alternate PN/configuration is permitted for consideration.

trace-releaseRecord fieldWhen applicable

Requested traceability, life status and release records

Specify evidence appropriate to the article class and receiving jurisdiction; do not require one universal certificate for all materials.

Applies when: Evidence requirements affect the requested item/service or quotation comparison.

work-scopeRecord fieldWhen applicable

For repair: reported defect and requested initial scope

Describe the reported defect and initial investigation request; do not present the customer report as a confirmed finding.

Applies when: Repair, inspection, test or overhaul is requested.

Commercial response requirements
priceRecord fieldWhen applicable

Currency, price basis, validity and exclusions

Request itemized currency, unit basis, tax/freight treatment, validity and exclusions; no payment authorization is created.

Applies when: Commercial quotations are requested; mark a technical-information-only enquiry as such.

timelineRecord fieldWhen applicable

Lead-time/TAT start, finish and pause assumptions

Define start/end events and pause conditions for lead time or TAT; keep shipping transit time distinct.

Applies when: Any timing commitment or repair turnaround is requested.

deliveryRecord fieldWhen applicable

Delivery location, agreed delivery terms and packaging needs

Name the delivery point, packaging/preservation requirements and agreed terms; identify any trade-rule edition if expressly used.

Applies when: Physical movement or delivery is contemplated.

dgRecord fieldWhen applicable

Dangerous-goods screening and trained-person review required?

Record screening status and referral to a trained responsible party; do not derive shipping classification from this worksheet.

Applies when: Items or packaging may require dangerous-goods assessment, or screening is unresolved.

privacyRecord fieldWhen applicable

Public summary versus controlled technical attachment access

Define public summary, controlled attachment, recipient, purpose and onward-sharing permission; visual blurring is not access control.

Applies when: Any information is published or disclosed to a counterparty.

Additional decision and evidence controls
response-deadlineRecord fieldRequired for the stated submission stage

Quotation-response deadline and clarification channel

Separate response deadline from required delivery date; name the controlled clarification contact.

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

acceptance-basisRecord fieldWhen applicable

Proposed receiving and technical-evaluation basis

State who evaluates offered evidence and any destination-specific acceptance conditions; this is not an evaluation result.

Applies when: An item/service offer requires technical or destination-specific evidence evaluation.

clarification-logRepeatable tableWhen applicable

Controlled RFQ clarification and revision log

Bind each question/answer to line and RFQ revision; circulate changed requirements to affected recipients.

Applies when: Any clarification, correction or revised enquiry is issued.

Controlled RFQ clarification and revision log
Query IDAffected line/RFQ revisionQuestion and agreed answerAuthorized respondent and dateAffected recipient notificationResulting revision/status
Blank sample—no real evidence entered.

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

Completion checks

  • Compare offers only against the same revision, line identity, condition and evidence basis.
  • Select relevant transaction branches; do not demand all branch fields from every requester.
  • An RFQ or clarification does not authorize purchase, work, dispatch or payment.

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. Define transaction branch and exact linesResponsible role: Requester

    Requested scope, identity and unknowns are explicit.

  2. 2. Define evidence, timing and disclosureResponsible role: Requester and relevant technical representative

    Same scope/evidence basis can be sent to authorized recipients.

  3. 3. Issue revision-bound enquiryResponsible role: Authorized requester

    Recipients and revision known; no purchase/execution/payment authorization inferred.

  4. 4. Record clarification/comparison basisResponsible role: Commercial representative with technical referral

    Changed requirements circulated; quotations compared against the correct baseline.

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.