New York City Digital NDT Reports for Steel Inspection

A New York City steel project can involve an owner, design team, fabricator, erector, inspection agency and specialist NDT provider. Each may use different references for the same connection. The report should make the examined detail and the issuer’s role clear before it enters that chain. A professional format is useful only when the reader can identify what was actually examined and how it relates to the project.

The free editor on this page imports supported DOCX and XLSX tables for preview and editing. You can adjust columns and rows, enter the supplied inspection basis and findings, add company and client PNG or JPEG logos and download a browser-generated PDF. A free verified account supports private saving, sequential numbering patterns, search and issued versions with revisions.

These functions organize NDT information; they do not register an inspection agency, determine building-code compliance or file a technical report with the city. The NYC Buildings special-inspection page describes the city’s distinct agency and inspector framework. Use your actual project roles and requirements rather than treating the reporting workspace as a substitute for that framework.

A building address is not enough to locate a steel examination. The report may also need the floor, grid, member mark, connection reference, face and drawing revision. Choose the convention used by the project and retain enough context for another inspector or engineer to locate the same detail. An isolated photograph or a short weld number may be ambiguous when similar connections repeat across several levels.

Use separate fields for the wider job identity and the examined connection. If the fabricator’s piece mark differs from the erected-location reference, preserve their relationship in the table. A report should not force the recipient to reconstruct that mapping from unrelated emails. Resolve conflicting references through the project’s document process before representing the item as unambiguously identified.

For a revised drawing, record which version governed the examination and whether the change affects the reported detail. A newer drawing date does not automatically invalidate an earlier observation, but the relationship requires explanation. The responsible project team decides its significance; the report author should preserve the information needed for that decision.

A specialist examination may cover only a selected weld or region within a broader steel inspection assignment. State that scope explicitly. Do not title the document in a way that implies the author completed every special inspection associated with the project. Identify the responsible client and the purpose for which the NDT evidence was requested.

The NYC 2022 Building Code Chapter 17 publication addresses special inspections and tests within that code edition. The actual project team must determine its applicable code and approved documents. This page does not reproduce a complete requirement list or decide which inspection categories apply to a particular job.

The editor’s method and conclusion fields remain user supplied. It cannot expand an examination into a statutory certification or infer that an entire connection is acceptable from an incomplete row. Enter the actual scope, limitations and reviewed findings, and leave the wider project disposition to the party authorized to make it.

An XLSX fabrication log may organize welds by assembly and shop sequence, while a field team works by floor and erection area. Preview the imported table and add the project references needed for the recipient. Preserve the original weld identity rather than replacing it with a convenient row number. The most useful report makes both the originating record and the installed location understandable.

Check repeated headers, merged descriptions, units and rows containing notes rather than results. A blank may mean not supplied, not applicable or not examined; those states need explicit treatment. The importer extracts supported table content for editing. It does not reproduce every Word layout, carry all spreadsheet behavior or determine which interpretation of a blank is correct.

Compare several imported rows with the source, including an exception and a long location description. If the source uses a legend or another sheet to explain abbreviations, bring the necessary meaning into the report. A client reading the PDF should not need access to an unreferenced workbook simply to understand the status of a listed connection.

Use the actual project specification, procedure, document edition and acceptance criteria provided through the responsible technical process. Avoid a general phrase such as city code compliant in place of those references. The reader needs to understand the basis for the particular examination and the evaluated conclusion, not a broad claim whose supporting scope is unclear.

If a drawing note conflicts with another supplied instruction, keep the report in draft while the authorized party resolves the question. The reporting software does not select the controlling document or approve an alternative. Record the clarification through the project’s normal process and identify the resulting basis accurately in the final document.

The method-selection guide and construction industry guide can help prepare questions. They do not establish project-specific acceptance or substitute for the responsible design and inspection authorities. The author should enter only technical conclusions supported by the actual examination and its required review.

Construction sequencing can change access to a connection. The report should identify which planned regions were examined and which remained unavailable under the actual conditions. Do not let the progress of other trades erase an examination limitation from the final record. A later reviewer needs to distinguish completed evidence from an unresolved scope item.

Use a clear limitation description tied to the connection identity, along with the responsible role and requested next action where appropriate. This is a documentation workflow, not an instruction to stop or release construction. The project’s authorized parties determine what the limitation means for sequencing, further access or another examination.

The worksheet below includes fictional location and review items that illustrate this distinction. Replace them with the current project references and assigned responsibilities. Its purpose is to expose missing information before issue, not to prescribe a special-inspection program or suggest that a report author can independently approve concealed work.

A supporting NDT report and a city technical filing serve different functions. NYC Buildings’ forms page describes forms including TR1 and their administrative purposes. The appropriate form and filing route depend on the actual job. A PDF created in this editor is not automatically a TR1 submission, a substitute city form or an accepted filing.

DOB NOW: Build is the city’s platform for relevant job submissions and document activities. NDT Connect’s reporting workspace does not submit documents to DOB NOW or report completion to the Department of Buildings. The responsible project party must use the required city process and determine which supporting evidence belongs with it.

Keep the report’s own identity and the project filing references in separate fields. If a client requests a supporting document reference, enter the actual reference provided rather than inventing an application number. This prevents a useful examination record from implying that an administrative step has already occurred when it remains outstanding.

Record the actual examiner, reviewer and reporting organization. If the work forms part of another agency’s assignment, identify the relationship accurately without presenting the subcontractor as the registered agency by default. A logo, account name or typed qualification does not create a registration or verify the authority of the person issuing a technical statement.

The certificate manager can organize user-entered qualification records, and the qualification planner helps prepare evidence questions. Neither tool determines whether a person or company meets a city or project-specific requirement. Verify current evidence through the responsible sources and follow the actual assignment and review process.

Keep roles stable across report revisions. If the reviewer changes, record the actual review information rather than retaining an earlier name for appearance. The recipient should be able to understand who is responsible for the present issue and which supporting examination records remain associated with the original work.

Enter the equipment and relevant configuration actually used. If multiple setups apply to different connections, show that relationship in the table or supporting reference. A generic instrument description repeated across a large project can become difficult to interpret when a later question concerns one particular examination item.

Use the equipment tracker and calibration reminder for administrative organization around supplied records. Those tools do not validate calibration evidence or establish suitability for an examination. Check the underlying information and preserve its relevance to the work date and configuration recorded in the report.

Review units and abbreviations after import and again in the browser-generated PDF. A compact column heading should still state what a value means. Do not silently convert dimensions or overwrite the source representation during cleanup. If the project requires an additional unit display, preserve the original basis and have the responsible reviewer confirm the intended presentation.

A free verified account can save reports privately and apply supported pattern-based sequential report numbers. Keep the report number separate from the building job number, connection identity and drawing reference. Each identifies a different part of the record. Consistent naming helps the author retrieve the right draft or issue without relying on a long filename alone.

Saved-report search supports retrieval, but check the actual status and revision before distributing a result. Draft content may look complete while still awaiting technical or administrative review. Establish who can authorize issue in your organization and how that authorization is recorded. The software does not make the decision simply because the fields are populated.

Issued versions are immutable, with later changes handled through revisions. That preserves what was issued rather than silently replacing the client’s earlier record. Explain whether a revision corrects a reference, changes an interpretation or incorporates new examination evidence. The reason should remain intelligible alongside the project’s wider document-control history.

Company and client PNG or JPEG logos can make a report recognizable, but the organization names and responsibilities must remain explicit. Do not use a project participant’s branding to imply approval or a city affiliation that has not been given. The author is responsible for the accuracy of those representations as well as the inspection table.

Review the downloaded PDF for long floor and grid references, connection descriptions and exception notes. Page breaks should not make a limitation appear unrelated to its row. If a table is too dense, revise the column structure or separate concepts rather than shrinking everything until the evidence becomes difficult to read.

Retain the draft while resolving layout and content questions. Browser PDF generation does not mean the document has been filed with the city or approved by the design team. Treat the output as the report you must review and distribute through the actual project process, with the correct status and revision clearly understood.

A single building address can appear on several construction packages or assignments. Keep the relevant project reference and scope visible so the report is not mistaken for evidence covering every activity at that address. Where a client supplies a filing or package identifier, reproduce the actual reference accurately and confirm its relationship to the examined connections.

Before delivery, ask the recipient to identify the intended package from the report alone. If the answer depends on an email subject or an unwritten assumption, add the necessary context. This administrative check does not establish filing acceptance; it simply helps the supporting NDT record reach the correct project file.

Consider a hypothetical steel project where a subcontractor’s NDT table refers to a fabrication mark and the field coordinator needs the erected floor-and-grid location. The author imports the table, preserves the original mark and adds the confirmed project location. One row remains unresolved because the drawing revision and field description do not agree, so the report stays in draft for clarification.

The responsible project party supplies the corrected reference, while the technical reviewer confirms the actual examination scope and result. The author checks the PDF, saves the record privately and issues it under the organization’s procedure. The special-inspection agency separately determines how the NDT evidence supports its assignment and any required filing. The software does not perform those external actions.

A later administrative correction is preserved as a revision rather than rewriting the original issue. This scenario is fictional and does not claim a real building, inspection agency or city acceptance. It illustrates the distinction between a clear supporting record and the broader statutory and engineering responsibilities surrounding a construction project.

At handover, reconcile the report with the assigned connection list and its authorized changes. Explain removed scope, missing evidence and unresolved access separately from completed results. A recipient should not have to decide whether an absent connection was intentionally excluded or accidentally omitted during import. Resolve that administrative ambiguity while the original team can still clarify it.

Use the report buyer-review guide and New York City planning guide to prepare review questions. The generated PDF may be one part of a package containing drawings, field records and other professional decisions. Identify those relationships without claiming the reporting workspace verifies every external document.

Begin with a representative connection and an exception row, agree the table with the intended recipient and then extend the format across the assignment. Clear identity, supplied criteria and preserved limitations make the report useful. The benefit is a traceable NDT record within the project’s real process, not an automatic declaration that the entire construction work complies.