St. Louis NDT Reports for Navigation-Gate Handover

A navigation-gate repair can generate records in several places: the river site, a fabrication shop, an examination contractor and the owner’s document system. A report that is clear to the shop may become ambiguous when a field team receives a large segment in a different orientation. The practical reporting task is to preserve the component identity, location convention and examination stage through that handover. A familiar project name or photograph is helpful context, but it cannot carry all of those relationships alone.

The St. Louis District’s Melvin Price Locks and Dam overview describes a regional navigation asset near Alton, Illinois. Its September 2023 navigation information paper provides dated context for regional gate-related work. Melvin Price is not inside St. Louis city, and a historical project reference does not prove that a particular repair is currently underway. The example in this guide is fictional and has no claimed connection to a Corps contract.

The free editor on this page helps you prepare an understandable examination document from information supplied by the responsible team. Supported DOCX and XLSX tables can be previewed and edited before a PDF is generated in the browser. A free verified account can retain private drafts, sequential report numbers and issued revisions. The software does not inspect a gate, approve a repair design or determine whether navigation operations may resume.

Begin with the facility and asset reference, then identify the specific gate, segment or removable component covered by the report. Use the owner’s controlled identifiers where available. A fabrication mark can be added to connect the shop records, but it should not replace the installation identity without a clear cross-reference. The recipient needs to distinguish a particular segment from another built to the same drawing or stored alongside it for the same project.

Carry the hierarchy into the result rows where necessary. If a report covers several segments, a feature number on its own may repeat across them. Add the segment identity to the feature reference so a row remains meaningful when it is copied into an open-item list or printed on a separate page. Avoid relying on spreadsheet position as the only connection between an observation and the physical part it describes.

Treat missing or conflicting marks as a documentation question that requires resolution. Record what was visible and which source was used to establish identity. If the shop receiving label differs from the owner’s drawing callout, retain both and state the confirmed relationship. Do not assume the most legible label is authoritative. Resolving that relationship before issue is more useful than creating a polished report whose results cannot be confidently assigned at the river site.

Location descriptions need a stable reference that survives lifting, transport and reassembly. Use the applicable drawing convention for upstream and downstream faces, reference edges and other orientation labels. Where the project uses different terminology, record the agreed convention explicitly. A shop-side left or right can reverse when a segment is turned over. The reporting table should not require the field team to guess which direction the examiner was facing.

A sketch or drawing reference can establish the wider geometry, while each result row identifies the relevant feature and position. Preserve the distinction between a drawing coordinate and a measurement actually taken during the examination. If the field record gives an approximate region, do not convert it into a precise-looking coordinate merely to populate a table. Obtain clarification where the uncertainty affects the recipient’s ability to locate the feature.

Review orientation again before shipment. Temporary markings may be covered, removed or replaced during finishing and handling. The report should retain an intelligible location convention even if the receiving team cannot see the shop’s original paint marks. A controlled cross-reference to the final component identification is more dependable than expecting a photograph taken during fabrication to establish the installed position on its own.

A gate segment can be examined before a repair, after preparation, after an authorized repair operation or at a later delivery stage. Identify the actual condition presented for each event. An examination date is useful, but it may not distinguish several stages completed on the same day. Link the event to the relevant work order or repair reference so the reader understands which physical state the observations describe.

Preserve earlier observations when later work changes the surface or configuration. A follow-up record should connect to the original concern and the authorized repair action without replacing the history. The report can then show what prompted further work, what reference governed that work and what the later examination covered. Do not make a later evaluation appear to be the result of the original examination by overwriting the first row or removing its date.

Keep repair design and examination evidence separate. The NDT report may reference a repair document, but it does not create or approve the engineering solution. If the repair configuration changes from the one originally requested, obtain the appropriate technical direction and record the new basis. The reporting author should preserve the relationship between the changed part and its examination rather than treating every revision as a cosmetic document edit.

A navigation application does not establish a universal method, acceptance threshold or examination extent. Enter the procedure, revision and evaluation requirements supplied for the assignment. If the governing documents are unclear, identify the unresolved question and retain the report as a draft until the responsible technical authority provides direction. A familiar civil-infrastructure title is not a substitute for the actual examination instructions applicable to the material, feature and work scope.

Describe the specific areas examined and the restrictions recorded by the examiner. Access may differ between a loose component and an installed assembly, but the report should describe the actual condition rather than assume every face was available. An unexamined region needs an explicit status or limitation. A blank table cell should not be left to mean either no relevant finding or no examination, because those statements have very different implications for the receiving reviewer.

Make the evaluation traceable to the relevant observation and requirement. If additional review is required before a disposition is made, record that state without forcing the result into a broad pass/fail category. The owner may need other evidence before deciding what happens next. An NDT report can remain accurate and useful while an engineering or operational decision is pending, provided the document makes the boundary clear.

A project workbook may list all gate segments, while a contractor’s examination sheet covers only selected features. Before importing the XLSX table, determine which rows belong in the report and how their component references map to the owner’s register. Preview the selected sheet and heading row. Do not assume that rows beneath a repeated project heading share the same segment identity when the source file uses merged cells or informal grouping.

A DOCX examination form can also be imported as editable table content. Review each column after import and enter necessary scope or identification information that sat outside the source table. The editor does not promise identical Word-page layout. Reorganize the information so the result, location, condition and limitation remain connected in the exported PDF. A compact layout is only useful if it preserves the distinctions the receiving team needs.

Check unit labels, identifiers and transferred values against the source record. Keep nominal drawing information distinguishable from measured data and from examination results. If a source workbook contains calculations, verify the values being transferred rather than assuming the editor repeats the workbook’s logic. Retain the original file in the approved document system and provide a retrievable reference for any supporting evidence that is not included in the report itself.

A component can leave the shop with its defined examination complete while field installation work remains outstanding. The report should make that stage clear. Do not imply that the installed gate has been examined or functionally checked if the evidence concerns a loose segment before shipment. A delivery-stage statement should identify the physical condition and scope it describes, allowing the field team to combine it with later records without changing the meaning of the original report.

When a field adjustment or repair occurs, retain a reference to the new work and the examination event that follows it where required. The same component identifier can connect the records, but it should not hide the change in condition or scope. The owner’s document controller can then reconcile shop and field evidence into a handover index. The report editor does not automatically integrate those external systems or determine which operating hold points have been satisfied.

Include a clear recipient and open-item owner in the project’s delivery process. A report saved privately in a verified account is not automatically submitted to the facility owner, a government agency or a construction-management platform. Confirm where the reviewed PDF and supporting references need to go. Good technical content still needs a deliberate handover so the people responsible for the next decision actually receive the correct version.

Consider fictional segment STL-EX-G07, received by a shop under reference SHOP-EX-18 for work on a regional navigation gate. The supplied drawing identifies upstream and downstream faces, but the field note uses the phrase bench left. During draft preparation, the author notices that the component was rotated after the initial photograph. They ask the examiner to resolve the location reference instead of transferring bench left into the issued report as though it were an installation coordinate.

The confirmed feature becomes STL-EX-G07/F03 under the stated drawing convention. An earlier observation is retained with its examination date and condition. Authorized repair record REP-EX-05 is linked to the later examination event, and a restricted region remains identified separately. The report does not turn that restriction into an acceptable result. The owner’s reviewer receives a clear description of the evidence and the question that still needs attention.

At shipment, the final component marking differs from the temporary receiving label. The author adds the confirmed cross-reference and checks the actual PDF against the delivery list. The field team can now find the segment, locate the feature and distinguish shop examination from later installation work. The fictional example supplies no gate-design instruction, repair threshold or operating authorization. Its benefit is an evidence chain that remains understandable after the hardware changes location and orientation.

Identify the examination and review personnel according to the requirements of the job. The certificate manager can organize user-entered qualification documents, but it does not establish the individual’s authorization for this particular scope. The responsible organization must confirm the applicable method, qualification conditions and review responsibilities. Keep those supporting references connected to the examination event rather than relying on a general statement that a contractor employs qualified personnel.

The equipment tracker and calibration reminder can help retain instrument identities and user-supplied dates. The report should still describe the equipment and setup information required by the governing procedure for the actual work. A current reminder or register entry does not prove past status. If the original record is incomplete, preserve the missing-information question for resolution instead of filling it from the latest equipment profile.

Maintain retrievable references for photographs and original examination files. A useful filename or repository reference should distinguish the segment, feature and event from other similar project records. The editor does not analyze native instrument data or infer findings from a table import. The author’s role is to present reviewed information accurately and preserve the path to the evidence the technical reviewer may need.

Large components may be delivered in separate shipments, or a project may send a replacement segment under a revised delivery note. Compare the actual shipment identity with the report index before closing the package. A complete report set for an earlier delivery is not automatically complete for the revised one. Identify any component whose evidence is missing or still awaiting review, and give the receiving team a clear explanation of that status.

Keep reports for removed or superseded components identifiable in the archive. They may still explain earlier findings or project decisions, but they should not be mistaken for evidence covering the final installed configuration. Use descriptive fields and controlled cross-references to show the relationship. A report number should remain stable, while the handover index explains which documents apply to the current delivery and which are retained for historical context.

This reconciliation is especially useful when different contractors use their own numbering systems. Preserve the supplier reference and the owner’s corresponding identifier rather than renaming one without explanation. The final package can then retain the source record while giving the recipient a practical route through it. The reporting workspace supports that presentation, but the confirmed mapping comes from the project team responsible for the physical components.

Review the browser-generated PDF as the field recipient will see it. Confirm gate and segment identities, orientation labels, procedure references, result rows and limitations. Check that long feature descriptions and table page breaks do not separate an observation from its condition or evaluation. PNG or JPEG company and client logos can identify the reporting parties, but they should not look like an approval from an owner or agency that has not authorized that representation.

A free verified account supports private draft saves, search and pattern-based sequential numbering. Issued versions remain immutable, and later changes use revisions with a clear explanation. Say whether the change resolves an identification error, clarifies a location or adds a new examination event after field work. The fictional worksheet below helps assign the remaining evidence questions. It is a planning aid, not an approved inspection procedure or a navigation-readiness checklist.