A ceiling grid crew cannot work reliably from a reflected ceiling plan that still leaves sprinkler heads, lights and access panels unresolved. The programme may put both tasks in the same week, but the dates do not make the installation ready. Architects help keep construction moving by identifying the decisions each trade needs before it starts and making unresolved items visible to the team.
The architect does not control the whole schedule. The owner sets priorities; the contractor plans means and methods; consultants provide specialist designs; and authorities control approvals. The architect’s role is to provide coordinated information when it is needed, review submissions within agreed periods and flag design issues that threaten the sequence. That work begins well before construction starts.
Build the timeline around decisions, not just drawing dates
Work backward from construction activities when setting the design programme. Façade fabrication, for example, may depend on completed design, contractor pricing, technical submissions, architect and engineer review, corrections and approved shop drawings before fabrication and delivery can begin. A drawing issue date captures only one step. Structural openings, plant rooms, medical equipment interfaces and long-lead electrical equipment need the same scrutiny.
At the outset, agree a milestone schedule with the owner, consultants and contractor, if one has been appointed. It should identify:
- Owner approvals for scope, budget, materials and operational requirements.
- Planning, permit and inspection submissions, with time for review cycles rather than an assumption of first-pass approval.
- Design packages and the construction activities that depend on them.
- Procurement decisions for products with extended fabrication or delivery periods.
- Dates for verifying existing conditions and supplying specialist information.
Give each milestone an accountable party and a clear completion requirement. “Approve façade” is vague; “owner confirms the façade system and performance criteria before procurement documents are issued” states both the decision and its consequence. Where construction documents are issued in phases, define the areas and systems covered by each package. An early foundation package still depends on settled column loads, below-grade services and other interfaces.
Separate the baseline from the live forecast
The baseline programme records the agreed sequence and dates at a defined point. The live forecast records what the team now expects. Keep both: otherwise, a delay can disappear when someone moves a bar on the chart. Ask the contractor to identify critical-path activities—the sequence currently determining completion—and near-critical work with little float. Float is the time an activity can slip without delaying a later milestone, and it changes as work progresses.
Read the programme for design dependencies rather than trying to direct the contractor’s workforce. In regular reviews, compare planned and actual dates for submissions, approvals, procurement and site work. Ask what the next two to six weeks of work will need, whether that information has been approved and who can close any gaps. A rolling look-ahead gives the team more to act on than a distant completion date.
Make unresolved items measurable
Keep a short constraint log beside the programme. For each item, record the affected activity, the missing decision or information, its owner, the date it is needed and what happens if it remains open. “Kitchen equipment layout awaiting operator confirmation; affects drainage rough-in” tells the team more than “kitchen design ongoing.” Close an item only after the decision has been recorded and sent to those who will build from it.
On an occupied site, a booked date is not necessarily a work-ready date. A hospital refurbishment may have a short, agreed shutdown window for services; if isolation points have not been verified, the team is not ready to use it. The constraint log should make that distinction visible.
Plan review time without turning it into a rubber stamp
Submittals, samples and requests for information can form a queue that quietly uses up schedule float. Agree on routing before the first submission: who receives it, which disciplines comment, how responses are consolidated and what makes a package complete. Review periods should follow the contract and project requirements. An incomplete submission is not ready for a technical decision.
Prioritise reviews by their effect on procurement and site work. A fabricated stair needed months from now may need review before a readily available finish due to be installed next week. Consider, too, whether a response will lead to resubmission. If several disciplines review one assembly, reconcile their comments before returning it so the contractor does not receive conflicting instructions.
Respond to requests for information in proportion to the issue. If the answer is already in the documents, cite the relevant detail. If it changes the design, identify the drawing revisions and consultant input needed. Record decisions made at site meetings promptly, or a trade may build to an interpretation the formal documents do not support. The scheduling value of making design work ready through lean construction practices lies in resolving these prerequisites before crews reach them.
Control changes by tracing their schedule effects
A change in room use may look minor on a plan but affect ventilation, power, fire protection, accessibility, finishes and permitting. Before accepting it, identify the drawings, approvals, purchased items and completed work it touches. The contractor can assess sequencing and procurement; the architect and consultants can assess design and compliance. The owner then has a clearer basis for weighing time, cost and operational trade-offs.
Not every change delays completion. Some fit within available float or affect an area the contractor has not reached. Others hit the critical path despite involving little physical work—relocating an opening after structural steel has been fabricated, for instance. Record the approval date, affected documents and agreed schedule treatment. Do not call a target date recovered simply because acceleration is planned; recovery needs a feasible revised sequence with resources and dependencies checked.
Watch the handoffs at completion
Substantial completion is not just the date construction activity stops. Testing, commissioning, inspections, corrections, training and handover documents may overlap, but they have dependencies. Equipment cannot be meaningfully commissioned until power, controls and connected systems are ready. A public building may also need authority sign-off before occupants can enter, however finished the interiors appear.
Work backward from the intended occupancy date to plan system demonstrations, consultant observations, deficiency correction and owner training. Establish who compiles operating manuals, record drawings and warranties, and when the owner needs them. For phased occupation, set out the requirements for each handover area, including access, fire safety and services shared with unfinished zones.
At the next schedule meeting, pick one upcoming installation, such as the first air-handling unit, and trace it back through approved equipment data, structural support, access clearances, controls coordination and delivery. Give each missing prerequisite a named owner and a resolution date in the constraint log before scheduling the installation crew.