The title block on an engineering drawing is easy to skip during quality review, but it is one of the first places quality teams should look before ballooning. A revision mismatch or missing reference document caught upfront costs a few minutes to resolve. Caught later, it can mean a rejected First Article Inspection Report (FAIR), re-inspection, a resubmission cycle, and supplier scorecard issues.
Before ballooning a drawing, confirm the revision, referenced documents, tolerance notes, approval status, revision history, part identity, and drawing scale. These checks establish whether you are inspecting against the right design data before a single balloon goes on the page.
Key takeaways
- A title block review takes minutes and can prevent days of FAIR rework or resubmission.
- AS9102 FAIRs depend on the right design document, revision level, requirements, approvals, and traceability.
- Revision mismatches between the drawing, PO, work order, and customer portal are common preventable rejection triggers.
- Every document referenced in the title block or general notes should be treated as an inspection requirement.
- Title block errors are not just administrative issues. They can point to configuration control and document control problems under AS9100.
What is a title block?
An engineering drawing title block is the standardized information panel, usually found in the lower right corner of a drawing. It identifies the document and commonly includes the part name, part number, revision level, drawing number, scale, material, general tolerances, approval signatures, and revision history references.
For an AS9102 First Article Inspection, the title block is the administrative foundation of the drawing. It tells the quality team what document they are inspecting against and whether that document appears complete, controlled, and released.
Why title block review matters for AS9102 FAIRs
AS9102 requires a FAIR to demonstrate conformance to design documentation. That means the part must be inspected against the correct document, at the correct revision, with the correct requirements in scope.
The title block is where that certainty starts. If you balloon the wrong drawing revision, the error can flow into your measurement plan, Form 3, supporting evidence, and customer submission. By the time the issue is caught, the problem is no longer just clerical. It can affect shipment timing, customer confidence, and audit readiness.
This applies whether you are working from a 2D drawing, a model-based definition (MBD) package, or a hybrid drawing and CAD model. The format may change, but the principle does not: if the design data is wrong, incomplete, or uncontrolled, the FAIR built from it is exposed to rejection.
Pre-ballooning title block checklist
1. Revision mismatch between drawing, PO, and customer system
Your drawing has a revision level. Your purchase order references one. Your customer's portal or contract may reference a third.
When these do not match, you may be ballooning the wrong revision, inspecting to superseded tolerances, or missing requirements added in a later change. The resulting FAIR may be rejected because it does not match the customer's system of record, even if every measurement is accurate.
Check: Confirm the drawing revision against the PO, work order, and any customer portal reference before opening your ballooning tool. If they conflict, get written clarification. Under AS9100, configuration control is a core requirement. Revision alignment is an audit item, not a clerical detail.
2. Referenced documents you do not have
Most aerospace drawings do not stand alone. The title block and general notes often reference supplemental documents: material specifications, process specifications, customer quality requirements, surface treatment standards, drawing notes, parts lists, and special process requirements.
Each reference is a requirement. If you do not have the document, you cannot inspect to it. An incomplete FAIR package, regardless of how well the parts were inspected, may not satisfy the customer's AS9102 documentation expectations.
This matters especially on defense and aerospace programs where customer-specific quality notes, flow-down requirements, or supplemental inspection criteria may live outside the drawing itself.
Check: List every document referenced in the title block and general notes before you start. Confirm you have the correct revision of each document. Request missing documents from the customer before proceeding, and document the request.
3. General tolerance notes that conflict with feature-level callouts
Almost every drawing carries a general tolerance note, such as "unless otherwise specified" linear and angular tolerances. These tolerances apply to dimensions that do not have their own explicit tolerance.
Problems arise when a feature-level callout, feature control frame, or tighter bilateral tolerance appears to conflict with the general tolerance block. The same risk appears when a general profile, flatness, or surface requirement overlaps with a specific GD&T callout.
Under AS9102, each design characteristic must be accounted for and traceable to inspection results. If the applicable tolerance is unclear, the characteristic cannot be documented cleanly.
Check: Read the general tolerance block before ballooning. Flag any characteristic where the relationship between the general note and a specific callout is ambiguous. Document which tolerance you applied and why, or request customer clarification.
4. Missing or undated approval signatures
A released engineering drawing should carry evidence of formal approval, including engineer and checker signatures with dates. In an AS9100-certified environment, document control requires review and approval of documented information. Using an unapproved or informally released drawing as the basis for a FAIR creates a traceability gap.
This shows up more often than expected: drawings revised under time pressure, documents shared outside a customer's PDM system, or legacy drawings that were never formally re-released after a change.
Check: If approval signatures or dates are missing, do not assume the document is released. Request confirmation from the customer in writing, and include that confirmation in your FAIR package.
5. Revision history that does not add up
The revision block is a trail of how the drawing has evolved. Red flags include skipped revision letters, vague or missing change descriptions, out-of-sequence dates, or a current revision level that does not appear in the history table.
Any of these can indicate that a drawing changed outside formal change control, which raises questions about whether all requirements are current and whether earlier changes introduced anything that was not formally resolved.
For suppliers working on long-running programs, this is especially common with legacy drawings that have accumulated informal redlines, verbal change directives, or customer-approved deviations that were never incorporated into the formal release.
Check: If the revision history looks inconsistent, document the issue and ask the customer to clarify before ballooning.
6. Part number and nomenclature mismatch
Part number, dash number, and part name in the title block should match what appears on the purchase order, material certifications, work order, ballooned drawing, and all AS9102 FAIR forms.
Small discrepancies, such as a transposed digit, missing dash number, or legacy part name, can cause a customer to return a FAIR package as administratively incomplete. The measurements may be correct, but the traceability chain is broken.
Check: Confirm that part number, dash number, revision, and nomenclature match across the title block, PO, and FAIR forms before ballooning. Flag discrepancies and get written clarification before proceeding.
7. Drawing scale and detail view scale
The drawing scale noted in the title block is easy to overlook, but it can affect inspection planning. This is especially true when optical or vision-based measurement systems are used, or when features are small enough that their drawing representation can be misleading.
Detail views, section views, and auxiliary views may also use a different scale than the overall drawing. Applying the wrong scale to an inspection plan can create avoidable confusion during review.
Check: Note the drawing scale in the title block and the scale of every detail or section view. Confirm your inspection method is appropriate for the true feature size, not just the represented size.
Seven questions before ballooning
- Does my drawing revision match my PO and customer system of record?
- Do I have every document referenced in the title block and general notes, at the correct revision?
- Do the general tolerance notes and feature-level callouts align?
- Is the drawing formally approved with signatures and dates?
- Does the revision history make sense, with no gaps or inconsistencies?
- Do the part number, dash number, revision, and nomenclature match across the full FAIR package?
- Have I checked the drawing scale and any detail view scales that affect inspection planning?
If all seven are green, proceed. If any are red, resolve the issue before you start ballooning.
Frequently asked questions
Does AS9102 require title block review before ballooning?
AS9102 does not prescribe a pre-ballooning title block review by name. It does require the FAIR to demonstrate conformance to design documentation, which is only possible when the quality team has confirmed the right document, revision, requirements, and approvals are in scope.
Title block review is the practical step that establishes that foundation before inspection planning begins.
What happens if I submit a FAIR on the wrong drawing revision?
A FAIR submitted against the wrong drawing revision is likely to be rejected or returned for correction. The supplier may need to re-balloon the drawing, re-inspect affected characteristics, update AS9102 forms, and resubmit the package.
The underlying parts may still be conforming, but the FAIR no longer proves conformance to the customer's current system of record.
Who is responsible for providing referenced documents?
The customer typically provides the released design package, including drawings, models, specifications, and referenced requirements. The supplier is responsible for identifying missing documents before inspection starts and requesting clarification.
Proceeding without referenced documents creates risk because requirements may be missed before they are ever ballooned or measured.
How does this apply to MBD models instead of 2D drawings?
The same checks apply to Model-Based Definition (MBD), but the information may be distributed differently. Dimensions and product manufacturing information may live in the model, while notes, material requirements, special processes, and approvals may live in supporting documents or the product data package.
Before inspection planning, confirm the model revision, related specifications, approval status, part identity, and any customer-specific MBD instructions.
What is the fastest way to prevent title block-related FAIR rejections?
Use a repeatable pre-ballooning checklist. Confirm revision alignment, referenced documents, tolerances, approvals, revision history, part identity, and scale before creating balloons.
For teams managing many FAIRs, centralized quality reporting software can help keep drawing review, ballooning, AS9102 forms, and supporting evidence in one controlled workflow.
The bottom line
A FAIR does not just prove the part is good. It proves you understood what was required and verified it traceably and completely. That proof starts with the document you inspect against.
The title block is the first five minutes of every inspection job. Done properly, it is also the five minutes most likely to protect everything that follows.
Looking for a faster way to manage drawing review, ballooning, and FAIR documentation in one place? See how GroundControl works.
