A construction submittal log records the shop drawings, product data, and samples that need review. It tracks deadlines, revisions, and approval status, helping teams coordinate procurement and fabrication. Clear records can prevent avoidable delays—especially when several trades depend on the same materials.

Multiple Choice

What is the primary function of a submittal log on a construction project?

The main function of a submittal log is to serve as the central record of all required submittals—shop drawings, product data, and samples—that must be submitted for review. It tracks each item from submission through review and approval, capturing due dates, status (submitted, in review, approved, rejected), and any revisions. This keeps procurement and fabrication on schedule and helps prevent delays caused by missing or late submittals. It’s different from logs used for other purposes: field observations are tracked separately, as are RFIs and change orders/substitutions, which are managed in their own processes.

Why the Submittal Log Matters on a Construction Project

A construction project runs on many kinds of information: drawings, product details, samples, questions from the field, and decisions about cost or scope. Keeping those records straight isn’t glamorous, but it can make a real difference to the schedule. One tool helps teams manage a specific slice of that information: the submittal log.

At its core, a submittal log is a central record of the items the contractor must send for review. These often include shop drawings, product data, and material samples. The log tracks each item as it moves from preparation to submission, review, and response. Think of it as a project’s shipping tracker—but for information that may need review before a product is ordered, fabricated, or installed.

That role sounds simple. Yet when a log is clear and current, it can help prevent costly confusion. When it’s incomplete, small oversights may ripple through procurement and construction.

What goes into a submittal log?

The log typically lists each required submittal and gives it a distinct name or number. It may also show who is responsible for sending it, when it is due, when it was received, who is reviewing it, and what response was issued. Common status labels include “not submitted,” “in review,” “approved,” “revise and resubmit,” and “rejected.”

A useful log does more than show whether an item has arrived. It helps the team see what needs attention next. For instance, if a custom window system needs a long lead time, the related shop drawings and product data may be time-sensitive. A late review could affect fabrication; a late submission could push the review back before fabrication can even begin.

Submittals vary by project. A roofing system might require product data and color samples. A complex stair may call for detailed shop drawings. A finish sample can help the design team assess appearance in real conditions, where lighting and nearby materials may change how a color reads. The contract documents and project specifications set out what is required.

A log should reflect those requirements rather than become a generic list copied from another job. Each project has its own materials, systems, review needs, and schedule pressures.

Why tracking status is more than paperwork

A submittal often passes through several hands. The contractor may collect information from a subcontractor or manufacturer, check it for completeness, and send it to the architect or another designated reviewer. The reviewer then responds, and the contractor shares that response with the relevant team members.

That path can get tangled. A document may arrive without a required sample. A reviewer may request a revision, but the updated file might not reach the right people. Or a supplier may start fabrication based on an outdated detail. A well-maintained log gives the team a shared view of where each item stands and what action is still needed.

It also helps connect the schedule to the work on site. A submittal that affects a near-term installation deserves close attention. This doesn’t mean every item is equally urgent; it means the team can spot the items that could hold up procurement or field work and respond accordingly.

Clear status tracking is especially useful when a project has many subcontractors and manufacturers. Without it, people may rely on scattered email threads or personal notes. Those can help in the moment, but they’re a poor substitute for a record everyone can check.

A submittal log isn’t a catch-all

Construction projects use several logs, and they serve different purposes. Confusing them can leave important information hard to find.

A request for information, or RFI, records a question about the contract documents or a condition encountered on site. An RFI log tracks questions, responses, and often the dates involved. It is not the main record of shop drawings, product data, or samples.

A field observation record captures observations made during a site visit. It may note visible progress, work that appears inconsistent with the documents, or items that need further attention. It serves a different function from a submittal log, which follows review materials through a defined process.

Change orders and substitutions also have their own documentation and approval paths. A change order records an authorized change to scope, cost, or time. A substitution request seeks permission to use a different product or material from the one specified. A substitution may appear in the submittal process, depending on the project’s procedures, but it should not be mistaken for the submittal log’s main purpose. The log is chiefly a record of required submittals and their review status.

The distinction matters because each record answers a different question: What needs review? What question is unresolved? What was observed? What change was authorized? Keeping those answers in the right place makes project communication easier to follow later.

Review is not the same as taking responsibility

A reviewer’s response needs to be read in context. In many contracts, an architect’s review of a submittal is limited to checking for general conformance with the design intent and the information in the contract documents. It does not usually shift the contractor’s responsibility for construction means and methods, dimensions, coordination, or fabrication details. The exact scope depends on the contract and the project’s procedures.

That distinction can feel subtle, especially when a submittal has a stamp or formal response. But the review process is not a replacement for the contractor’s own checks. The contractor remains responsible for coordinating the work and confirming that the submittal is complete and suitable for its intended use, as set out in the contract.

A log can support this division of responsibility by recording who submitted an item, who reviewed it, and what response was returned. It doesn’t settle every question about responsibility, but it helps preserve a clear history of the process.

What makes a log useful?

A good submittal log is current, consistent, and easy for the project team to read. It should use clear item descriptions and status terms, rather than vague notes that different people may interpret in different ways. Dates matter, too. A log that isn’t updated can create false confidence: an item may look complete even though a revision is still outstanding.

Digital project platforms can make the information easier to share. Tools such as Autodesk Construction Cloud and Procore, along with project-specific systems, allow teams to store files, assign reviewers, and track status in one place. The software doesn’t make the decisions, of course. A tidy platform can still hold messy information if the team doesn’t keep it up to date.

Useful habits include linking each log entry to its current document, recording review responses promptly, and making sure revisions don’t get confused with earlier versions. It also helps to flag items tied to long-lead materials or upcoming work. These small steps make it easier to act before a delay becomes visible on site.

A quiet tool with a real effect

A submittal log may never draw attention when a project is moving smoothly. That’s partly the point. It gives the team a reliable way to track required review materials, follow their status, and see where action is due.

It won’t replace good communication, thoughtful scheduling, or careful review. But it gives those efforts a shared record to work from. And when schedules are tight and many people are coordinating the same building, that simple record can keep a missing sample or unanswered shop drawing from becoming a much bigger problem.