Do not balloon a note just because it is printed on the drawing, and do not ignore it just because it is not a dimension. First decide whether the note defines or governs an acceptance requirement, whether your inspection process must account for it, and what evidence will show that it was addressed.

Classify the note before assigning an ID

General tolerances: identify the rule and the dimensions it governs

A title-block note may say that dimensions without individual tolerances use a stated general rule. That note governs the interpretation of those dimensions; it is not a separate measured value repeated for each line on the drawing.

For example, a synthetic title block might specify different limits for one- and two-decimal-place dimensions. Before using the rule, verify the drawing’s exact note, units, referenced standard and edition, and any exceptions. A local tolerance printed beside a feature may override the general rule. If the note or its scope is ambiguous, ask the responsible engineer rather than inferring a tolerance from decimal places alone.

Do not reproduce a copyrighted tolerance table in a report or article. Record the source and edition that the drawing invokes. If an ISO or ASME tolerance standard is named, use the edition required by the drawing or contract; standards can be revised.

Worked examples: one callout can carry several requirements

Four-hole pattern with position control

“4X Ø8.0 ±0.1 THRU” contains quantity, size, tolerance, and a depth condition. A related position feature-control frame adds geometric control and datum context. An inspection plan may group the size results or list each hole separately; it may record geometric results in a distinct row. Keep the hole count, source region, datum references, and relationship among rows visible.

Thread callout

A callout such as “2X M6 × 1–6H, 10 DEEP” can include quantity, thread size, pitch, class, and depth. The approved check may use a specified gauge or another method. Record the result at the level your procedure requires. Do not reduce the callout to “M6” and discard the remaining conditions.

Surface finish and datum controls

A local roughness symbol applies to a particular surface; a general finish note may have broader scope. A datum label usually supplies context for a feature-control frame rather than acting as a separate acceptance limit by itself. Keep location and control relationships with the evidence.

Basic and reference dimensions

A basic dimension is theoretically exact and used with related geometric controls; it is not an ordinary plus/minus dimension. A reference dimension is generally informational. Do not turn either into a standalone numeric acceptance characteristic without a governing reason.

Deburr, coating, and special process

“Remove burrs” may be verified as an attribute; an edge-break limit may require a defined measurement or inspection method. A coating or heat-treatment note can require a certificate or process record. Those evidence types may be tracked outside the dimensional-results table, with a clear link back to the drawing and job.

Example source-to-evidence path

This synthetic example follows a compound hole callout through interpretation, characteristic identification, verification, and report evidence. The graphic does not prescribe how every company must split the rows.

Choose whether to group or split

Keep elements together when one record preserves the full requirement and produces usable evidence. Split them when separate results or acceptance decisions are needed. If evidence belongs in a certificate or process record, reference that record rather than forcing the requirement into a numeric measurement cell. In every case, follow customer and quality management system (QMS) rules and keep the drawing-to-record connection clear.

A five-question note review

1. Does the note define an acceptance requirement or govern another requirement?
2. Is it in scope for this inspection or first article inspection (FAI)?
3. What method or objective evidence demonstrates it was addressed?
4. Where does the procedure require the result or evidence to be recorded?
5. Does it need a unique characteristic ID, or a reference to another controlled record?

How software can help—and what it cannot decide

BalloonForge can surface note and callout candidates, let a reviewer correct or reject them, rescan a selected region, or add a missed item. It does not determine which customer or QMS requirement applies, nor can detection prove completeness. The reviewer owns classification and release. See the BalloonForge workflow.

Frequently asked questions

Should every general note have a balloon?

No. First identify which notes define requirements for the job and where your procedure records them. Informational and document-control notes are different from acceptance criteria.

Should a general tolerance block get one balloon?

It may need to be reviewed or referenced, but it governs applicable dimensions rather than replacing them. Record the rule source and apply it carefully.

Do all edge-break notes get measured?

The drawing may define an attribute or a numeric limit. Use the stated requirement and approved verification method; do not infer one from generic practice.

Does coating belong in a dimensional report?

It is a product requirement when specified, but its evidence may be a process record or certificate. Use the report structure required by your customer and QMS.

Further reading

• How to decide what is accountable
• AS9102C and customer requirements
• The complete drawing ballooning workflow
• ISO 2768-1 information