Where the time actually goes
The architect's review window is only the middle leg. A typical door-to-door timeline looks like: sub finishes package → GC reviews and stamps (1-5 days) → architect logs and routes to consultants (structural, MEP) → consultant review (the 10-14 day window, often run in series with the architect's own review) → architect consolidates and returns → GC logs and distributes back (1-3 days). That is how a 'two-week review' becomes a four-week round trip without anyone missing a deadline.
What makes review run long
The predictable extenders:
- Resubmittals: 'Revise and Resubmit' restarts the clock in full — plan for at least one cycle on controls, curtain wall, and shop-drawing-heavy scopes
- AHJ review on fire protection and deferred submittals: add two to six weeks, usually sequential
- Owner or consultant layers: lighting designers, IT/security departments, FM Global
- Incomplete packages: reviewers return them without review, costing a full cycle for a missing battery calc
- Submittal surges: dumping 40 packages on the architect in week two produces a queue, not approvals — sequence by procurement priority
How to shorten the cycle
You cannot compress the contractual window, but you control everything around it. Submit complete, marked-up, one-section packages — the quality of the package is the single biggest lever on review speed. Sequence the register by lead time so reviewers see long-lead gear first. Flag genuinely urgent items on the transmittal and follow up through the GC at the one-week mark. For substitutions, file the substitution request before the submittal rather than bundling them and losing a cycle to procedure.
And keep your own side honest: measure how long packages sit in your court between award and first submission. On many projects, sub-side preparation time exceeds architect-side review time.
What the contract actually says
Check two places: Division 01 (Section 01 33 00) for the stated review duration and resubmittal rules, and the general conditions for what happens when the window lapses. Most contracts do not make silence an approval — a lapsed review window gives you a schedule-delay argument, not permission to install. Document late reviews in the log contemporaneously; they matter for time extensions later.
Tracking it without a spreadsheet
Submittal.App timestamps every package automatically — submitted, opened, returned — and shows the aging register at a glance, so the follow-up email cites dates instead of vibes. Packages assemble in minutes rather than days, which quietly removes the largest self-inflicted delay in the whole pipeline: the gap between award and first submission, the only part of the review timeline that was ever fully yours to control.