Make a steel-detail observation relocatable
An NDT observation on a steel bridge is useful only if the responsible team can locate the same detail and understand the examination context. A close-up photograph or a short note such as crack at connection may be insufficient when several similar connections exist. Begin with the bridge identity, structural element and precise detail reference. Preserve the distinction between the observation reported by the examination and any engineering conclusion about its significance. This guide focuses on building a location-and-evidence map that supports the bridge owner's review and follow-up process without claiming to assess the structure automatically.
The free digital NDT reporting workspace can organize entered observations, location descriptions and source references into a PDF. It does not assign an official bridge condition rating, calculate load capacity or determine whether a bridge should remain open. Those decisions follow the owner's applicable inspection and engineering process. Use the downloadable worksheet to connect each finding to a defined element, surface, examination event and responsible action. The fictional examples illustrate documentation only; they do not provide acceptance thresholds, repair instructions or universal notification requirements.
Use the owner's bridge and element identifiers
Record the bridge identifier used by the owner and confirm that it matches the structure examined. Similar route names, parallel structures or separate carriageways can create ambiguity if the report relies only on a local nickname. Include the project reference needed to distinguish the work package, but keep the physical structure identity clear. Where a contractor's job number differs from the owner's asset number, retain both with their relationship. A report should remain retrievable after the contractor's temporary job folder or site shorthand is no longer available.
Use the owner's approved element identification and orientation convention. FHWA's archived LTBP element identification protocol, published in 2016, provides an example of a structured system for identifying bridge elements. It is a reference example, not a requirement to renumber an owner's bridge. If historical reports use different labels, establish a supported cross-reference. Preserve the original labels where needed to retrieve earlier evidence, and do not assume that a matching girder letter identifies the same physical element under every convention.
Identify the detail within the structural element
Describe the particular connection, attachment, weld or other detail associated with the observation. A girder reference alone may still leave many possible locations. Use the approved drawing or detail map and identify the relevant surface or component relationship. Where the detail has repeated features, distinguish the individual item using a stable reference. Avoid a location description that depends only on a temporary access platform or the direction the inspector happened to face. The goal is to make the observation understandable to another qualified person who was not present during the examination.
Keep the observed feature separate from nearby features shown in the same photograph. A result associated with a weld toe should not be attributed casually to an entire connection or member. If the actual location is uncertain, describe the uncertainty and obtain clarification rather than assigning a precise detail label without evidence. The report can preserve a general area while a location question remains open. That is more useful than a falsely exact map that sends the follow-up team to the wrong surface or causes unrelated observations to be combined as one finding.
Define the surface, datum and direction
State the surface and viewing direction needed to interpret the location. Terms such as inside, outside, left and right can change meaning when the observer moves to another side of a member. Use the owner's convention and explain it in the referenced sketch or report. If distances are measured from a datum, identify the datum and direction of measurement. A numerical offset without an origin can look authoritative while remaining impossible to reproduce. Preserve units and distinguish a location offset from the dimensions of the reported indication itself.
When comparing older records, check whether the same surface and orientation were used. A mirrored photograph can make an indication appear to have moved or changed direction. Do not reconcile such differences by visual intuition alone. Record the evidence supporting any mapping between conventions and ask the responsible reviewer to resolve uncertainty. The worksheet can carry both the original source description and the current interpreted location. Keeping those separate allows a future reviewer to understand the transformation rather than seeing only a rewritten label whose basis has been lost.
Preserve the method and the meaning of its indication
Identify the examination method, procedure reference and event associated with the observation. FHWA's dye penetrant testing overview describes surface indications produced by that method and its use on steel bridge details. A surface indication should not be described automatically as a measured subsurface depth or as a complete structural assessment. Record what the method and reviewed evidence actually support. Where another method provides additional information, keep its event and interpretation identifiable rather than blending separate observations into one unsupported statement.
Avoid replacing technical review with a label chosen to fit a report column. The author should preserve the responsible interpretation and its limits, including any need for further examination. If the source record describes a suspect indication, do not promote it to a confirmed crack or downgrade it to a cosmetic mark without the appropriate evidence. The reporting tool displays the entered wording; it does not interpret signals, classify defects or determine structural significance. A clear report distinguishes the observed feature, the technical interpretation and any subsequent engineering decision.
Give each finding a stable reference
Assign a finding reference according to the project's record system and keep it stable across photographs, sketches, examination results and follow-up actions. The reference should identify the observation being tracked without implying a particular severity. If a later examination determines that two entries concern the same physical feature, document that relationship rather than deleting one without explanation. If one broad initial observation is later resolved into several distinct findings, preserve the connection between the original entry and the more detailed records.
Do not use a report revision number as a substitute for a finding identifier. A report may contain several findings, and one finding may appear in several examination events or revisions. Keep those relationships explicit. The same principle applies to repair references: a repair event may address a defined area that includes one or more findings, but it is not automatically identical to the finding record. A stable identifier allows the owner to follow the evidence and action history without assuming that document sequence, physical condition and maintenance work all share the same numbering system.
Link images and sketches to the location map
Use images to support the location description, with enough context to identify the element and detail. A close-up may show the indication clearly but omit the landmarks needed to relocate it. Reference an overview image or drawing where appropriate, and identify the relationship between the views. Keep the original image files in the approved evidence system. The reporting workspace can reference them in a table or narrative, but its logo upload controls are not an inspection-image archive and should not be used to imply that all examination photographs are embedded in the PDF.
Record image identifiers, examination date and the stage represented. If the surface is cleaned, marked, repaired or otherwise changed between images, make that sequence understandable. Do not present an image from a later condition as if it documented the initial finding. Avoid relying solely on a camera's automatic filename or timestamp when the project requires a stronger identification record. The report should let an authorized reviewer retrieve the intended evidence and understand why it belongs to the mapped finding, even after files have been transferred between teams or storage systems.
Keep coverage limits visible beside the finding
Describe the actual area examined and any limitations that affect interpretation. A finding on one accessible surface does not establish the condition of every side of the detail. If another surface could not be assessed, identify that boundary using the project's terminology. Keep an unexamined area distinct from an examined area with no reportable indication. These states have different meanings and should not collapse into a blank cell or a broad satisfactory statement. The responsible process determines what additional evidence or action is required.
Where follow-up examination expands the scope, record the new event and its relationship to the earlier one. Do not rewrite the original report to imply that the expanded coverage was available at the first visit. If a supplementary method addresses a specific question, identify its actual scope and reviewed conclusion. The software does not determine whether the combined examination is sufficient. The location map supports that decision by showing where each piece of evidence applies and where a gap remains, allowing the owner and technical reviewers to work from a consistent physical reference.
Connect the observation to the owner's response process
Follow the bridge owner's established communication and escalation process for findings that require attention. Do not treat completion of a PDF as the only possible notification event. Record the actual communication reference, responsible recipient and subsequent decision where required by the project. This guide does not define a universal urgency threshold or decide an operating response. The reporting task is to preserve accurate information and a clear action trail so that the people with the appropriate authority can assess the finding promptly within their process.
Keep the response record separate from the observation itself. A decision to perform another examination, obtain engineering analysis or carry out maintenance should identify its authority and scope. If an action remains open, record the specific next step and owner rather than using a vague pending label. Do not infer closure from silence or from a favorable result on an adjacent detail. The free tools can organize entered references and planning questions, but they do not notify an owner automatically from a finding row or replace the owner's inspection-management system.
Follow a fictional connection-detail map
Consider a fictional bridge with repeated diaphragm connections along one girder line. An initial field note identifies a linear indication at a connection, but the photograph shows only a close-up of the surface. The author compares the examination notes, overview image and approved element map to establish the correct connection reference. The finding is then assigned a stable identifier and linked to the actual surface and viewing direction. The report preserves the method-specific observation without making a structural severity claim that the source evidence does not support.
At a later visit in the same fictional example, another team records a similar observation on the opposite face of a nearby connection. The author does not merge the entries merely because their photographs look alike. The location evidence shows that they concern different physical references, so the ledger keeps them separate and identifies the required review for each. No crack-size threshold or service recommendation is supplied here. The example demonstrates how element, detail and surface references prevent unrelated findings from being mistaken for growth or repetition of one previously documented condition.
| Layer | Evidence to preserve | Common ambiguity |
|---|---|---|
| Bridge identity | Owner asset reference and work package | Parallel or similarly named structures |
| Element | Approved span and member convention | Repeated girder labels under different origins |
| Detail and surface | Drawing, orientation and local reference | Similar connections or mirrored views |
| Finding event | Method, date and stable observation identifier | Separate events mistaken for one condition |
| Owner action | Actual communication and decision reference | Silence or issued status mistaken for closure |
Prepare a report that supports retrieval and review
Build a result table with finding identifier, bridge element, detail, surface, location reference, examination event, observation and action reference. Keep long explanatory notes tied to the relevant row through clear note identifiers. If the table becomes too wide, separate the physical location map from the examination history while retaining the stable finding reference in both. This lets the recipient follow the information without shrinking important qualifications into unreadable text. The report should explain what was observed and where the supporting evidence can be found.
Use the equipment tracker and certificate manager to organize the supporting instrument and personnel records, then verify and transfer the relevant references manually. A current account entry does not automatically establish the equipment or authorization context of an earlier examination. The free procedure generator can help structure inputs for a draft, but it does not approve a bridge examination technique. Keep the actual procedure and review evidence identifiable. The software's value is organized reporting and retrieval, while the responsible professionals supply the technical interpretation and the owner determines the required response.
Proof and preserve the finding history
Download a draft PDF and test whether another authorized person can locate one finding using the report and its references. Check orientation language, units, image identifiers and the distinction between observation and disposition. Remove obsolete example values or copied location labels from imported templates. Review the conclusion for claims broader than the examined detail. After corrections, save the intended draft and create a fresh proof. Issuing preserves a report version; it does not assign an official bridge rating or provide engineering approval.
At handover, retain the location map, source evidence index and action references with the report. For later examinations, add events to the finding history without overwriting the original observations. If a report error is discovered, preserve the issued version and use a draft revision with the owner's document-correction process. The worksheet should remain useful even when staff change because it explains the physical reference and the evidence relationship explicitly. A successful map allows the next team to find the same detail, understand what was actually examined and identify which decisions or actions remain outstanding.
Steel bridge finding location and evidence map
Download this editable CSV for the task described above. Replace illustrative prompts with your own supported facts. The worksheet is a planning aid; it does not establish inspection acceptance or approval.
Download the free workflow worksheetQuestions about this workflow
Does a surface indication establish crack depth?
Do not assign a depth or structural significance unless the actual method, evidence and responsible interpretation support it. Preserve the scope of the reported observation.
Should I replace the owner’s identifiers with the FHWA example?
No. Use the owner’s approved convention. The archived FHWA protocol is a reference example of structured identification, not a requirement to renumber the bridge.
Does the tool assign an official bridge rating?
No. It organizes entered report information. Condition ratings, structural assessment and operating responses remain with the applicable owner and engineering process.
Can similar photographs be merged into one finding history?
Only when the physical relationship is supported. Similar-looking details may be different elements or surfaces; preserve separate records until the location evidence is resolved.
Sources and editorial scope
Primary references support the specific context cited in the guide. Worked examples and suggested workflows are NDT Connect editorial guidance. Confirm the documents and authority applicable to the actual assignment.
More guides: industry closeout workflows
- Create a Casting Radiography View and Zone Map
Make each delivered radiographic view traceable to the casting zone and examination event it represents, including repair and replacement records.
- Trace Concrete Impact-Echo Results to Validation Evidence
Keep measured response, processed interpretation and verification evidence identifiable. Build a review ledger that exposes missing points and unsupported conclusions before issuing a report.
- Preserve Corrosion Monitoring History When Locations Are Renamed
Separate a naming change from a moved point or replaced component. Build an evidence-backed crosswalk that preserves original observations and makes unresolved mappings visible.
- Separate Crane Hook NDT Findings from Service Release
Connect the reported hook findings to the right component and follow-up process. Preserve the examination scope and actual decision references without implying that a PDF authorizes equipment use.
