Submittals and shop drawings: the schedule is decided in week one

Submitting things that get approved

Rejected submittals are the most avoidable delay in construction, and rejection is usually the contractor's fault rather than the reviewer's.

Five practices that raise first-pass approval substantially:

Review before forwarding. A contractor who passes a subcontractor's submittal to the architect without reading it is adding a week of transit time and no value. The contractor's review is a contractual obligation in most agreements and is the step most commonly skipped.

Check it against the specification, section by section. Most rejections are for missing information — a required test report, a finish designation, a code listing — not for the wrong product.

Flag deviations explicitly. If the product differs from what was specified, say so on the cover sheet with a clear explanation and a comparison. A deviation discovered by the reviewer is rejected; a deviation disclosed by the contractor is usually discussed.

Submit complete packages. Partial submittals to appear responsive generate a rejection and restart the clock.

Never submit a substitution as if it were the specified product. It will be caught, and it converts a routine review into a relationship problem that affects everything you submit afterward.

The economics are stark. A first-pass approval costs two weeks of review. A rejection and resubmittal costs five to seven weeks, and on a long-lead item that delay lands directly on the completion date.

Shop drawings and who owns what

Shop drawings are where the boundary between design responsibility and construction responsibility gets tested, and misunderstanding it creates genuine liability.

The conventional division: the design professional is responsible for the design, and reviews shop drawings for general conformance with the design intent. The contractor is responsible for dimensions, quantities, fabrication processes, construction means and methods, and coordination between trades.

Three consequences that contractors regularly get wrong:

An approved shop drawing does not transfer responsibility for field dimensions. If the drawing showed a dimension that was wrong and the fabricator built to it, the approval stamp typically does not make that the architect's problem.

Coordination between trades is yours. Ductwork, piping, structure and lighting all fitting in the same ceiling cavity is a construction coordination task. Submitting each trade's drawings separately and hoping is the origin of a large share of field conflicts.

Delegated design has its own process. Some elements — certain trusses, connections, curtain wall, fire protection layouts — are designed by a specialty engineer engaged by the subcontractor and require sealed drawings. Confirm early who is providing that seal, because assuming the design team covers it is a common and expensive discovery.

One project, two approaches

A general contractor building two similar medical office fit-outs, roughly $4.4 million each, managed submittals differently on each.

Project A, conventional handling: submittal log created in week three, sent to subs without dates, reviewed in the general meeting when it came up. Of 118 submittals, 41 were rejected on first pass — a 65% first-pass approval rate. Four long-lead items were submitted after their required date, the worst by nine weeks. The project finished 34 days late. Acceleration costs, extended general conditions and liquidated damages exposure totaled roughly $186,000.

Project B, managed: submittal register built during buyout from the specifications, submittal due dates written into every subcontract, backward-scheduled deadlines placed on the construction schedule as milestones, contractor review of every package before forwarding, and a fifteen-minute submittal segment in the weekly meeting. Of 124 submittals, 19 were rejected on first pass — an 85% first-pass approval rate. No long-lead item missed its deadline. The project finished 3 days early.

The cost of the difference in management: roughly 90 hours of project engineer time across the job, about $6,800.

The general contractor's own summary was that nothing about project B was harder — the work happened earlier, not faster, and the first six weeks were busier in exchange for the last six weeks being calm.

Closeout submittals, handled early

The final category is the one that delays final payment more than any other: operation and maintenance manuals, warranties, as-built drawings, training records, spare parts and attic stock.

These are treated as end-of-job tasks and should not be. Three changes pull retainage release forward by weeks:

Require closeout documents with the submittal, not after installation. The warranty and the manual exist when the product ships. Collecting them at the end means chasing subcontractors who have already left the site and been paid.

Make final subcontractor payment conditional on closeout delivery. Stated in the subcontract at award, this is the only mechanism that reliably works.

Maintain as-builts continuously. Marking up drawings weekly during construction takes minutes. Reconstructing them at the end takes days and produces documents that are partly fiction.

On a project where retainage is 5% of $4.4 million, pulling release forward by six weeks is $220,000 arriving a month and a half earlier — for administrative work that was going to be done anyway.

RFIs: the other half of the paper schedule

Submittals move information from the contractor to the design team. Requests for information move questions in the same direction, and they follow the same pattern: cheap when handled early, expensive when handled late, and almost always blamed on the wrong party.

Four disciplines keep RFIs from becoming a delay engine:

Ask early, in one batch per area. Reviewing an entire scope of drawings before the trade mobilizes and submitting fifteen coordinated questions is dramatically better than fifteen separate questions arriving as each is discovered in the field. Batched questions get one coordinated answer; scattered ones get inconsistent answers weeks apart.

Propose an answer. An RFI that says "the drawings conflict, please advise" invites a slow response. One that says "the drawings conflict; we propose this resolution at no cost impact, please confirm" frequently comes back approved in days. It also demonstrates competence, which changes how everything else you send is received.

State the schedule impact when there is one. Not as a threat, as information: this response is required by a specific date to hold the fabrication release. A design team that does not know an RFI is on the critical path treats it as routine.

Log them like submittals. Number, date sent, date required, date answered, cost and schedule impact. The log is what turns a pattern of slow responses into a documented condition rather than a general complaint.

One thing worth understanding about volume: an unusually high RFI count is a signal about the documents, not necessarily about the contractor. Incomplete drawings generate questions, and a contractor who records that pattern from week one is in a far better position when the conversation turns to who caused the delay.

Five mistakes with submittals

• Building the log after mobilization. Already late for every long-lead item on the project.
• Forwarding submittals without reviewing them. Adds transit time, adds rejections, and skips a contractual obligation.
• Not giving subcontractors dates at award. Makes their delay unenforceable and therefore likely.
• Hiding a substitution. Converts a routine review into a permanent credibility problem.
• Leaving closeout documents to closeout. Delays the last check by weeks for no reason.

The numbers to watch

• First-pass approval rate, by subcontractor and overall — the clearest measure of submittal quality.
• Days from submittal receipt to forwarding, which is entirely within your control.
• Design team review duration against the contract allowance, documented every time.
• Long-lead items submitted by their backward-scheduled date, as a percentage.
• Resubmittals per package, and the reason for each rejection.
• Closeout documents collected before installation, as a share of the total.

Submittals are administrative work that determines physical outcomes. Nothing about the process is difficult, and almost every element of it happens in the first weeks of a project, long before anyone feels urgency about a delivery scheduled for month nine. That timing mismatch is the entire problem — and a register built during buyout, dates written into subcontracts, and fifteen minutes a week are enough to solve it on nearly every job.

Frequently asked questions

How far in advance should submittals be prepared?

Work backward from the installation date, and the answer is usually much earlier than it feels. The full sequence for a fabricated item runs: award the subcontract, the sub engages a fabricator, the fabricator produces shop drawings in two to four weeks, the package is submitted, the design team reviews in one to three weeks and longer with consultants, a rejection adds two to five weeks for revision and resubmittal, then fabrication takes four to sixteen weeks before delivery and installation. That is three to seven months from award to installation for an item that takes two days to install. The practical exercise is to take the schedule, identify every fabricated or long-lead item, subtract fabrication, approval, review and preparation time, and write the resulting submittal due date on the schedule as a hard milestone — most of them will land in the first six weeks.

What should a submittal log contain?

Nine fields per item: number, specification section, description, responsible subcontractor, date required for fabrication start, date submitted, date returned, status, and the resulting fabrication release date. Three practices make the log function rather than decorate. Build it during buyout rather than after mobilization, since the register comes out of the specifications, which exist before the job starts — building it in week one of construction is already three weeks late for long-lead items. Give every subcontractor their own dates at award, written into the subcontract as contractual obligations, because a sub who learns in month two that something was due in week three will not absorb that delay. And review the log weekly in the same meeting, since fifteen minutes prevents the discovery in month four that nobody submitted the roofing package.

How do you reduce rejected submittals?

With five practices, because rejection is usually the contractor's fault rather than the reviewer's, and the economics are stark: a first-pass approval costs two weeks of review while a rejection and resubmittal costs five to seven. Review before forwarding, since passing a subcontractor's package to the architect unread adds transit time and no value, and the contractor's review is a contractual obligation in most agreements. Check against the specification section by section, because most rejections are for missing information — a test report, a finish designation, a code listing — rather than the wrong product. Flag deviations explicitly on the cover sheet, since a deviation discovered by the reviewer is rejected while one disclosed by the contractor is usually discussed. Submit complete packages rather than partial ones. And never submit a substitution as if it were the specified product.

Who is responsible for errors in shop drawings?

The conventional division is that the design professional is responsible for the design and reviews shop drawings for general conformance with design intent, while the contractor is responsible for dimensions, quantities, fabrication processes, construction means and methods, and coordination between trades. Three consequences are regularly misunderstood. An approved shop drawing does not transfer responsibility for field dimensions — if the drawing showed a wrong dimension and the fabricator built to it, the approval stamp typically does not make that the architect's problem. Coordination between trades is the contractor's, so submitting each trade's drawings separately and hoping they fit in the same ceiling cavity is the origin of many field conflicts. And delegated design elements such as certain trusses, connections, curtain wall and fire protection layouts require a sealed drawing from a specialty engineer, so confirm early who provides that seal.

How can closeout documents be collected earlier?

By treating them as part of the submittal rather than as an end-of-job task, which pulls retainage release forward by weeks. Three changes do it. Require closeout documents with the submittal rather than after installation, since the warranty and the manual exist when the product ships — collecting them at the end means chasing subcontractors who have left the site and been paid. Make final subcontractor payment conditional on closeout delivery, stated in the subcontract at award, which is the only mechanism that reliably works. And maintain as-built drawings continuously, marking them up weekly during construction, because reconstructing them at the end takes days and produces documents that are partly fiction. On a project with 5% retainage on $4.4 million, pulling release forward six weeks means $220,000 arriving a month and a half earlier.