How should a Submittal Log be managed to support quality control?

How should a Submittal Log be managed to support quality control?

• A. Maintain a controlled log with submittal type, date sent/returned, status, disposition, and revision history; ensure only approved versions are used.
• B. Use a loose notebook with random entries.
• C. Only track submittal dates.
• D. Submittals are not tracked.

Answer: (A)

A Submittal Log should be a controlled, auditable record that tracks each submittal from submission through disposition and use, with a clear history of revisions. This approach keeps all information in one place and ties it to concrete dates, statuses, and decisions. By storing submittal type, date sent and date returned, current status, disposition (approved, approved with comments, revise and resubmit, rejected), and a revision history, you create a traceable path showing when items were reviewed, what changes were required, and which version is actually in use. This ensures the team always works from the latest, approved information, which reduces rework and the risk of field installation using unapproved or superseded data. Having a single, controlled log also improves communication and accountability. It makes it easy to see outstanding items, track response times, and provide evidence for QA/QC reviews or audits. In short, this method supports effective quality control by ensuring submittals are properly reviewed, approved, and consistently applied on site. The other approaches fall short because they lack control and traceability. A loose notebook with random entries can’t verify current versions or complete disposition history. Tracking only submittal dates omits important status and revision information needed to enforce proper use of approved data. Not tracking submittals at all leaves no record of approvals, dates, or changes, which undermines quality control and project accountability.

A Submittal Log should be a controlled, auditable record that tracks each submittal from submission through disposition and use, with a clear history of revisions. This approach keeps all information in one place and ties it to concrete dates, statuses, and decisions. By storing submittal type, date sent and date returned, current status, disposition (approved, approved with comments, revise and resubmit, rejected), and a revision history, you create a traceable path showing when items were reviewed, what changes were required, and which version is actually in use. This ensures the team always works from the latest, approved information, which reduces rework and the risk of field installation using unapproved or superseded data.

Having a single, controlled log also improves communication and accountability. It makes it easy to see outstanding items, track response times, and provide evidence for QA/QC reviews or audits. In short, this method supports effective quality control by ensuring submittals are properly reviewed, approved, and consistently applied on site.

The other approaches fall short because they lack control and traceability. A loose notebook with random entries can’t verify current versions or complete disposition history. Tracking only submittal dates omits important status and revision information needed to enforce proper use of approved data. Not tracking submittals at all leaves no record of approvals, dates, or changes, which undermines quality control and project accountability.