top of page
Search

Coordination Between Architect, Engineer & Manufacturer

Updated: Aug 14

Coordination Between Architect, Engineer & Manufacturer

Coordination Between Architect, Engineer & Manufacturer

Stage 2 of this pillar established the structural coordination framework — who engineers what, which artefacts bind the parties, where the freeze sits. This closing article of Stage 3 descends from framework to workflow: how the three-party relationship actually runs week to week, through shop drawing cycles, RFIs, clash avoidance and the communication protocols that determine whether design intent arrives at handover intact. If the earlier article was the constitution, this one is the daily operating manual.

In This Guide You'll Learn:

Introduction: Coordination as a Weekly Practice

Frameworks fail quietly when nobody operates them weekly. A responsibility map that sits unread, a query answered on a phone call and never logged, a shop drawing package returned late because the review 'was almost done' — each is small, and their accumulation is how well-structured projects still drift into trouble. The workflow this article describes is deliberately lightweight: a handful of documents, two standing rhythms, and a set of habits that together take a project architect perhaps two hours a week to operate on a typical residential project. Its purpose is single: that the design the client approved is the building the client receives, with every deviation along the way deliberate, priced and recorded.

1. The Shop Drawing Cycle: A Managed Process

Shop drawings arrive not as one event but as a flow of packages — panel layouts, floor cassettes, roof framing, openings schedules, services integration — and managing the flow is the workflow's largest single component. The disciplines: agree the package sequence and dates at production kickoff, so the architect's review capacity is scheduled rather than ambushed; review each package within the contractual period using the systematic pass from the drawings article — dimensions from grid, openings against schedules, services against frozen layouts, signature junctions against agreed markups; return one of three verdicts, approved, approved-with-comments or revise-and-resubmit, with comments referenced to drawing and clause so the resubmission can be checked mechanically; and log every package's status on the drawing register, because on multi-package projects the question 'what is released for production?' must always have a one-glance answer. The architect's review is for intent, never re-engineering — the boundary Stage 2 fixed — and a manufacturer's deviation schedule accompanying each package, listing departures from the architectural set, converts the whole cycle from search to decision.

The Resubmission Trap

One cycle pathology deserves naming: the partial resubmission, where a revised package returns with the commented items fixed and uncommented items silently changed. The protection is procedural — resubmissions carry clouded revisions and a change note, and the architect's re-review checks the clouds first and spot-checks beyond them. Manufacturers with mature drawing offices do this unasked; requiring it in the specification's production clauses makes it universal.

2. RFI Discipline: Questions That Resolve in Days

Requests for information are the workflow's circulatory system, flowing in both directions — the manufacturer querying the architect's set, the site querying both. Healthy RFI practice is a format and a log. The format: one question per RFI; the referenced drawing, schedule or clause attached; the asker's proposed answer where they have one, because 'we intend to do X unless directed otherwise' resolves twice as fast as an open question; and a needed-by date tied to the production or site activity waiting on it. The log: a single numbered register — shared, current, owned by one named person — recording each RFI's question, answer, date and any drawing revision it triggered, because an unlogged answer is a future dispute and a logged one is contract administration. The architect's own discipline is answer latency: production RFIs age in days, not weeks, and the standing weekly call exists partly so that no query waits for a meeting. On well-run Loom Crafts projects the full-project RFI count for a residential build runs in the low teens, and the log's final page reads as what it is — the quiet minutes of a project that stayed coordinated.

3. Clash Avoidance: Won at the Desk, Not Discovered on Site

Conventional projects discover clashes during construction because that is when systems first physically meet; prefab projects cannot afford the discovery, because the systems meet inside finished panels. Clash avoidance therefore concentrates at two design-stage gates. The architect's gate is the frozen coordination set: services drawn to position over the structural layout, interior elevations proving that fittings, tiles and fixings agree, and the interface album resolving where site-built work meets the factory system — the instruments the previous articles built, doing their clash-prevention duty. The manufacturer's gate is the panelisation review: as the engineering team decomposes the design into panels, every conduit route, penetration and blocking position is placed within real framing, and the conflicts that survive the architect's set surface here — as drawing queries, while they cost minutes. Projects working in BIM formalise both gates through model coordination, as Stage 8 will detail, but the logic is tool-independent: two gates, both before production, after which the assemblies close and the answer to every clash becomes expensive. The residual site clashes on a disciplined project are interface ones — site services meeting factory terminations — which is exactly why the interface meeting walks the album with every trade before assembly begins.

💡 Loom Crafts Expert Insight: On the Sonar Bangla project in Taki, West Bengal, the phased delivery ran through three package cycles and a fifteen-line RFI log — and the project team's retrospective credited one habit above all: every RFI carried a proposed answer. The manufacturer's drawing office and the architect's studio were, in effect, always voting on a solution rather than composing one from scratch, and average resolution time stayed under three days across the project. Coordination speed is mostly answer-shaped question-writing.

4. Protecting Design Intent Under Commercial Pressure

Between approval and delivery, every project passes through substitution pressure — procurement seeking alternates, value engineering hunting savings, site convenience proposing simplifications — and design intent survives it through explicitness rather than resistance. The architect's instruments: the specification's substitution gate, requiring written equivalence approval; the signature junction list, which names the handful of conditions where no simplification is acceptable because the design's character lives there; and intent pricing — responding to each proposed substitution not with yes or no but with a statement of what it preserves and loses ('the alternate cladding matches on cost and weathering, reads flatter in raking light; the entrance bay should keep the specified board'), so the client trades knowingly. This posture also keeps the relationship collaborative: manufacturers respect architects who distinguish the negotiable from the essential, and a practice known for defending five junctions fiercely and flexing everywhere else gets its five junctions built exactly, project after project.

5. Assembly, Inspection and Closeout: The Workflow's Last Mile

Once assembly begins the workflow narrows deliberately: one query channel to the manufacturer's engineering desk, the weekly site call while erection runs, and the architect's presence concentrated at the hold points the specification named — the pre-pour release before it all, envelope closure when the weathering line completes, and the pre-handover inspection against the retained finish samples and signed schedules. Snagging follows the same written discipline as everything else: one list, referenced to rooms and drawings, statused to closure. Closeout then assembles the records the earlier articles specified — as-built drawings, warranties, the finish record, the RFI and instruction logs — into the handover package, and the final coordination act is the project review: thirty minutes, all three parties, capturing what the next project should repeat and change. That review is where coordination fluency compounds into the relationship asset Stage 2 described — and where the workflow this article describes stops being a checklist and becomes, quietly, the way the practice simply works.

6. The Communication Protocol: Channels, Rhythms and Escalation

Underneath the documents runs the human protocol, and its rules are few enough to state completely. Channels: one named coordinator per party — the project architect, the manufacturer's project engineer, the client's representative — with all decisions flowing through the written channel even when they originate in calls; the WhatsApp reality of Indian project communication is accommodated, not fought, by the one-line habit of confirming every chat decision into the RFI log or an instruction the same day. Rhythms: the standing weekly call during design and production phases, agenda fixed — package status, open RFIs, decisions due, lookahead — and rarely longer than thirty minutes; plus the stage-gate meetings the earlier articles named, from concept review to the interface walk. Escalation: a two-step ladder agreed at kickoff, coordinator-to-coordinator first, principals within a week if unresolved — which, by existing, is almost never used, because named escalation converts simmering issues into scheduled conversations. The protocol's whole character is unglamorous regularity: the projects that stay coordinated are the ones where the Tuesday call happens every Tuesday, including the weeks when there is 'nothing to discuss' — because that is precisely the meeting where the small drifting item surfaces while it is still small.

Keeping the Client Inside the Loop

The client occupies a designed place in the protocol, not an ad hoc one: they receive the decision points — substitutions priced with intent statements, freeze confirmation, hold-point results — and are shielded from the working traffic of packages and RFIs, which would otherwise read as alarming volume. A monthly one-page status note (production state, decisions taken, decisions due, programme position) keeps the client informed at the altitude they can act on; clients managed at this altitude approve faster, trust deeper and interfere less, which every party on the project experiences as the same benefit.

7. A Working Week in the Workflow

To make the operating manual concrete, here is the project architect's coordination week during peak production on a typical residential project. Monday: forty minutes on the register and logs — package statuses updated, two RFIs aged past three days flagged for the call. Tuesday: the standing call, twenty-five minutes — one package moves to approved-with-comments, the flagged RFIs resolve on the manufacturer's proposed answers, next week's roof framing package confirmed for Thursday delivery. Wednesday: an hour on a substitution request — the alternate window hardware priced with an intent statement and sent to the client, approved by evening. Thursday: the roof package arrives; ninety minutes of systematic review books Friday morning for completion. Friday: review completes, verdict returned inside the period, clouds checked on the resubmitted wall package from last week, register updated, done. Total: roughly four hours in the project's busiest documentation week, two in an ordinary one — the workload the workflow's design intends, and the reason a small practice can run three prefab projects in parallel where conventional supervision arithmetic would allow one. The efficiency is not the architect working less; it is the coordination happening on paper at desk speed instead of on site at crisis speed.

  • Peak-week coordination: about four desk hours, structured around the register, the call and the review periods

  • Every decision that week left a written trace the same day it was made

  • Nothing in the week required a site visit: the drawings, logs and call carried it all

💡 Loom Crafts Expert Insight: Our project engineers keep an informal metric they call the Tuesday test: on projects where the weekly call has run unbroken since kickoff, assembly-phase surprises are rare enough to be memorable; on projects where the call lapsed 'because things were quiet', the lapse period is almost always where the eventual surprise was quietly forming. The Chail project ran forty-one consecutive weekly calls from concept to handover, several of them under ten minutes — and its site phase closed with a snag list of eleven items, every one cosmetic. Regularity is the cheapest quality instrument the industry has.

8. Adapting the Workflow to Project Scale

The workflow scales in both directions without changing shape. Downward, on a single cottage: the register may be one sheet, the call fortnightly, the packages three — but the format, the log and the review periods persist, because as the mistakes article established, coordination failures do not scale down with project size. Upward, on phased resorts and institutional work: packages multiply into a formal submittal schedule, the RFI log gains category codes, the weekly call splits into design and production tracks, and a project management consultancy may hold the register — with the architect's intent-review role unchanged at any scale. The one genuine addition large projects demand is interface management across parallel contractors, where the coordination matrix from Stage 2 extends to name every boundary's owner, and the interface meetings recur per phase rather than once. What never changes is the underlying grammar this stage has taught: written decisions, single channels, scheduled rhythms, intent reviewed and deviations logged — the grammar itself is the transferable skill, and an architect fluent in it can walk onto any factory-built project, at any scale, and know within a day exactly which instruments are present, which are missing and what to install first.

9. Stage 3 in One Page: The Documentation System Complete

With this article, the stage's five instruments stand assembled, and their joint operation deserves a closing statement because they were designed as one system. The specification states requirements, boundaries and evidence; the assembly knowledge lets the architect write and review it with authority; the drawing set defines the building with production precision and divides labour cleanly with the shop drawings; the finish schedules clothe the assemblies on substrates the panels were built to carry; and this workflow moves information between all of it and three parties without loss. An architect operating the full system holds, at any moment of the project, a complete written answer to the four questions that decide delivery quality: what was promised, what is being made, what has changed, and who agreed. That completeness — not any individual document — is what clients experience as a project that simply worked, and what manufacturers experience as an architect worth prioritising.

  • Specification: what is required, from whom, evidenced how

  • Assembly fluency: the knowledge behind every review verdict

  • Drawing system: the definitive set and the shop-drawing handshake

  • Finish record: every surface decided, scheduled and sampled

  • Workflow: the weekly mechanism that keeps all four alive

Stage 4 changes register entirely: from the disciplines that make prefab buildable to the design inspiration that makes it desirable — modern homes, luxury resorts, farmhouse architecture and the interior trends shaping factory-built spaces. The rigour of Stages 2 and 3 is what earns that creative freedom; the next five articles show what it looks like when it is spent well.

One final habit binds the workflow to the practice's long-term interest: archive the coordination record per project — register, RFI log, deviation schedules, review returns — in a retrievable structure, not scattered inboxes. Beyond its contractual value, the archive is the practice's own training corpus: the next junior architect learns shop-drawing review fastest by reading three completed projects' review returns, and the practice's template documents improve each cycle by harvesting what the last project's log revealed. Coordination competence, like the DfMA culture of Stage 2, compounds only where it is recorded — and the practices that treat their project archives as an asset rather than an obligation are, not coincidentally, the ones whose third prefab project runs in half the coordination hours of their first.

Frequently Asked Questions

How long should a shop drawing review cycle take?

The review period should be contractual — commonly one to two weeks per package — because it sits on the production critical path. The architect's discipline is returning within it; the manufacturer's is submitting complete packages that don't force serial resubmission.

What makes a good RFI?

One question, one referenced drawing or clause, one proposed answer where the asker has one, and a needed-by date. RFIs written this way turn around in days; multi-question narrative RFIs stall in everyone's inbox.

Who runs clash avoidance on a prefab project?

Prevention is shared: the architect's frozen services layouts and interface details remove most clash sources at design stage, and the manufacturer's panelisation review catches the remainder before production — clash detection on prefab projects is a design-stage activity, not a site discovery.

How does the architect protect design intent during value engineering?

By pricing intent explicitly: when substitutions are proposed, the architect states what each alternative preserves or loses against the signature junctions and prescribed finishes, so the client trades knowingly rather than discovering losses at delivery.

What does coordination look like after assembly starts?

It narrows to one channel and two rhythms: a weekly site call while assembly runs, the query log as the single written track, and the architect's staged inspections at the hold points the specification named — plinth release, envelope closure and pre-handover.

Conclusion

The daily coordination workflow is small enough to hold in one hand: scheduled shop drawing packages reviewed for intent within their periods, RFIs written to resolve and logged to endure, clashes retired at two design-stage gates, intent defended by explicit pricing, and a last mile run on one channel and three inspections. Operated weekly, it is the mechanism by which everything this stage built — specification, assemblies, drawings, finishes — arrives at handover as the building the client approved. With Stage 3 complete, the pillar turns from rigour to inspiration: Stage 4 explores the architectural styles and design ideas that show what all this discipline makes possible.

Continue Reading

Stage 3: Technical Drawings & Specifications

Explore All Knowledge Center Pillars

Specify Loom Crafts on Your Next Project

Loom Crafts Prefab has delivered 600+ factory-built structures across 50+ cities in India, from an ISO 9001:2015-certified facility in Ghaziabad, with a 20-year structural warranty. Our engineering desk runs structured shop-drawing packages, deviation schedules, shared RFI logs and defined review cycles on every architect-led project.

📲 Contact our Technical Team: +91 98711 22239 | rahul@loomcrafts.com

📅 Prefer a live walkthrough? Book a free online demo at a time that suits you — our team will take you through designs, 2026 pricing and the complete build process on a video call: Book Your Online Demo

Important Disclaimer: This article is intended for general architectural and educational guidance. Structural design, code compliance and site-specific engineering must always be verified with a licensed structural engineer and the relevant local building authority before finalising any project.

Comments

bottom of page