TR1 inspections: track responsibility through closeout
By DOB Desk · MoLabs LLC · Updated
TR1 is the Technical Report: Statement of Responsibility. It identifies inspection or testing responsibility and reports completion where applicable. The required items and responsible parties must be determined for the actual scope under the applicable instructions and codes.
Start from the proposed work
Do not copy an inspection list from a similar-looking project. The responsible professional needs to review the actual scope, systems, code basis, and applicable technical-report requirements. An automated suggestion is a prompt for that review, not a final determination.
Separate the question 'is this item required?' from 'who has accepted responsibility?' and 'what evidence closes it?' Keeping those questions distinct helps the team spot a missing handoff before it becomes a scheduling problem.
Keep an inspection responsibility register
For internal coordination, maintain one row per inspection item. Include the source of the requirement, the assigned professional or agency, the current status, and a link to the supporting evidence. Clearly label a tentative assignment as tentative.
- Inspection item and its source
- Scope or drawing reference
- Responsible person or agency
- Acceptance or outstanding action
- Evidence needed for completion
- Last checked date and next owner
Do not treat every technical report as TR1
DOB publishes separate technical reports, including reports for concrete testing and energy-code progress inspections. Confirm the applicable form or online section; using 'TR1' as shorthand for the entire inspection package can hide an outstanding item elsewhere.
When the scope changes, revisit both the selections and the assignments. Keep a note of what changed and who reviewed it so the latest package can be distinguished from a superseded working list.
Plan for closeout while preparing the filing
A permit-stage checklist and a closeout checklist serve different purposes. Track the evidence and responsible actions needed at each milestone rather than marking an inspection finished when it has only been assigned.
DOB Desk's matter workspace can hold the team's tasks and evidence links. Verify official completion states in the agency system and keep internal task completion distinct from an official sign-off.
Questions and answers
Can software decide which inspections my project requires?
Software can help organize the review and suggest items to check. The responsible professionals must determine the requirements and take their own required actions for the actual project.
Official sources and scope
This is general preparation guidance, not a determination for a specific project. Agency requirements can change. Use the current source instructions and the responsible professional's review. See our editorial approach or report a correction.