Lesson 10.1Lesson 10.1 · Delivery, Change & the Future
Delivering a Workplace Project
A beautiful plan is only a promise until it is built - delivery is the long, coordinated work of turning drawings into a workplace that holds its intent
The design is the easy part to love. Delivery is where most of the effort lives - and where most good intentions quietly leak away if nobody guards them.
There is a seductive moment in every project when the concept is signed off: the renders look wonderful, the client is excited, and it feels as if the hard part is done. It is not. Between that approved concept and a workplace that people actually walk into lies a long, demanding stretch of work - detailing every junction, specifying every product, drawing it so a contractor can price and build it, running the tender, and then the months on site where a thousand small decisions are made, some of them by people who have never read the brief. This lesson is about that stretch: how a workplace project is delivered, and what the designer does through all of it.
The single most useful idea to carry in is this: delivery is not a relay race where the designer hands the baton to the builder and walks away. It is a through-line. The concept contains an intent - a reason every setting exists, a logic to the palette of spaces, a feeling the place is meant to have - and that intent is fragile. It gets chipped at by cost cuts, by a contractor substituting a cheaper product, by a services run that was never coordinated, by a client who forgot why the quiet room mattered. The designer's job through delivery is to keep that intent alive and true, while coordinating the many specialists and trades whose work must all land in the same rooms, at the same time, to the same standard. Get delivery right and the idea survives into the built thing. Get it wrong and you hand over a compromised echo of what you promised.
The render is the promise. Delivery is keeping it - line by line, junction by junction, snag by snag.
The stages: concept to handover, and what each is really for
A workplace project moves through a recognised sequence of stages, and although names differ by market and by the contract in use, the logic is universal: each stage resolves the design to a greater level of certainty, and each decision gets more expensive to change the later it is made.
It usually begins with concept design - the big moves settled: the zoning of the floor, the palette of settings, the look and feel, the headline plan. This is where the ideas from the brief (Module 1) and the planning (Module 2) become a coherent proposal. Next comes detailed or developed design, where every part is resolved: the exact dimensions of rooms, the junctions between materials, how the ceiling, lighting and services coordinate, the specification of each finish and piece of furniture. This is unglamorous and decisive work - most of the quality of the finished space is won or lost here, in the details nobody photographs.
Then the design must be documented - turned into the drawings, schedules and specifications a contractor can price and build from. Good documentation is complete, coordinated and unambiguous: it leaves as little as possible to be 'figured out on site', because things figured out on site are figured out by whoever is cheapest and quickest, not by the designer. From documentation the project goes to tender: contractors price the work, the client and team evaluate bids on more than price alone, and a contractor is appointed. Construction and fit-out follow - demolition, services, partitions, finishes, furniture - the longest and most visible phase. It closes with snagging (systematically finding and fixing defects against the design), commissioning (proving systems actually work), and handover, when the keys, the manuals and the responsibility pass to the client.
The exact names and the boundaries between these stages shift with the market and the form of contract - some projects compress concept and detailed design, others split documentation into several packages, and fast-track jobs deliberately overlap stages to save time - but the underlying logic holds everywhere: resolve the big moves, then every detail, then turn it into buildable information, then buy it, then build it, then prove and hand it over. Understanding this spine lets you see where you are, what must be settled before the next stage can start, and why rushing one stage always costs more in a later one. It is also the map you use to manage a client's expectations, because most of the friction on projects comes from decisions arriving late - a finish chosen after the drawings are issued, a layout changed after tender - and the remedy is almost always to make the decision at the stage where it belongs.
Each stage turns a little more of the design from 'about right' into 'exactly this'. Skip a stage and the gap gets filled badly.
The designer's job through delivery: guard the intent
If the stages are the what, the designer's role is the how - and it changes as the project moves along, but it never disappears. Early on, the designer is the author: making the moves, resolving the details, writing the specification. As the project goes to site, the designer becomes something subtler and, frankly, harder - the keeper of the intent and a coordinator among many.
On site, the designer reviews the contractor's shop drawings and samples, answers the constant stream of queries (the 'requests for information' that real construction generates daily), inspects the work as it goes up, and judges the endless small proposals to substitute this product for that one, to simplify this junction, to save a little here. Each of those proposals is a tiny negotiation between cost, time and the design idea, and somebody has to hold the line on the ones that matter while letting go gracefully on the ones that do not. That judgement - knowing which compromises are fatal to the concept and which are harmless - is one of the most valuable things an experienced workplace designer brings.
This is also relentless coordination. A workplace fit-out is built by many parties at once (see the coordination web): the main contractor and their trades, the MEP or services engineers, the structural engineer where the base build is touched, acoustic and fire specialists, the furniture and FF and E suppliers, the client's IT team, and the client's own project manager. Their work physically collides - a duct wants the same ceiling void as a light and a sprinkler and an acoustic baffle - and somebody must make sure it all fits and all lands on time. The designer rarely builds anything directly; the job is to make sure everyone else builds the right thing, in the right place, in the right order. Doing this well is less about drawing flair and more about communication, organisation, and a calm insistence on quality when the pressure is to just get it finished.
Documentation, tender and the traps in between
Two moments in delivery deserve special care because they are where good projects quietly go wrong: documentation and tender.
Documentation is where the design either becomes buildable or becomes a source of disputes. A set of drawings and specifications is a contract as much as a picture: it tells the contractor precisely what to build and what they are being paid for. If it is incomplete or contradictory - a dimension missing here, a finish unspecified there, a detail that does not actually resolve - the gaps do not vanish; they become variations, claims and arguments once someone is on site and the clock is running. The discipline is to resolve decisions *before* they are drawn, to coordinate every drawing against the others (the reflected ceiling plan must agree with the services drawings must agree with the partition plan), and to specify clearly: exact products where they matter, performance standards where a range is acceptable, and honest allowances where a decision genuinely has to wait. For binding technical content - fire-rated construction, egress widths, accessible dimensions, services capacities - the documentation must carry the specialist's input and defer to the current codes, not the designer's guess.
Tender is where the client buys the project - and where the cheapest bid is often the most expensive. Inviting a small field of suitable contractors to price a well-documented design lets the client compare like with like and appoint on value, not just headline cost. The traps are familiar: a bid that is low because the documentation left room to cut corners; a contractor chosen on price who has no feel for fit-out quality; a programme that looks fast on paper and slips the moment reality arrives. A good designer helps the client read tenders critically - interrogating what is and is not included, how realistic the programme is, whether the contractor has done comparable workplace work - so the appointment protects the design rather than undermining it. The aim is not the lowest number; it is the right partner to build the thing well.
A gap in the drawings is not a gap for long. Someone on site will fill it - cheaply, fast, and not the way you meant.
Snagging, commissioning and a handover that actually works
The end of a project is where tired teams cut corners, and it is exactly where care pays off, because this is the part the client lives with from day one.
Snagging is the systematic business of walking the finished space against the design and recording every defect and shortfall - the paint scuff, the misaligned door, the tile that was never grouted, the setting that was built subtly wrong - then tracking each item to a fix. It is unglamorous and detailed, and it is the difference between a space that feels finished and one that feels almost-finished forever, because the small defects never quite get closed out once everyone has moved on. A disciplined snag list, agreed with the contractor and chased to zero, protects the quality the whole project was for.
Commissioning is proving that the systems actually do what they were designed to do - that the air handling delivers the air, that the lighting controls dim and zone as intended, that the booking system and AV in the meeting rooms genuinely work, that acoustic treatments perform. A workplace is full of systems that look complete but are not yet *working*, and commissioning is where that gap closes - usually led by the relevant engineers and specialists, with the designer confirming the experiential intent is met.
Handover then passes the space, and the responsibility for it, to the client. Done well, it is more than handing over keys: it includes the operation and maintenance information, the warranties, the as-built drawings, and - crucially for a workplace - the knowledge the client's facilities team needs to run the place, plus the groundwork for helping people actually use it (the subject of the next lesson). A good handover sets the client up to keep the workplace working long after the designer has gone; a poor one dumps a building on an unprepared team and watches the intent erode within months. Delivery, done properly, does not end at practical completion - it hands over a place that is ready to live.
Fire-rated construction and egress (NBC 2016)
Compartmentation, exit widths, travel distances in the fit-out
Document to the current code with a fire/life-safety specialist; never detail fire-rated or egress elements from memory. See the Fire and Life-Safety course.
MEP and services capacities (IS / NBC 2016)
HVAC, electrical, plumbing, sprinklers feeding the fit-out
Coordinate and document with the MEP engineer; capacities and routes are theirs to confirm, not the designer's to assume.
Accessibility (NBC / Harmonised Guidelines)
Barrier-free routes, doors, sanitary and reach dimensions
Carry an accessibility consultant's input into the documentation; verify dimensions against the current standard. Module 8.
Contract and documentation standards
Drawing conventions, specifications, the building contract
Follow the contract in use (the client's PM or QS usually sets it); documentation is a contract document, so clarity has legal as well as design weight.
Workshop - trace a project from concept to handover
Delivery is best understood by following one thing all the way through. In this workshop you will take a single design decision and trace how it survives - or does not - across every stage of delivery, which is the fastest way to feel why documentation, coordination and snagging matter.
Paper and a pen. No software needed - this is about understanding the flow of a project, not producing drawings.
Goal: see how intent travels through delivery, and where it leaks. Inputs: any workplace setting you can imagine or have designed + this lesson + a sheet of paper Time: ~45 minutes
- 1Pick one specific design element with a clear intent - say, a quiet focus room meant to feel genuinely calm and acoustically private, or a social stair meant to draw people together. Write its intent in one sentence.
- 2Walk it through the stages. For each - detailed design, documentation, tender, construction, snagging, handover - write what must happen for the intent to survive (e.g. acoustic spec written in, coordinated with services, priced properly, built to spec, snagged, explained at handover).
- 3At each stage, name the realistic threat: the cost cut, the missing dimension, the substituted product, the services clash, the corner cut under time pressure. Where is your element most vulnerable?
- 4Identify who must act, and when, to protect it - and what the designer specifically does at that moment (document it clearly, defend it in a value-engineering meeting, inspect it on site, list it as a snag).
- 5Write a short reflection: at which single stage is intent most often lost, and what habit would best protect it? Compare your answer across two different elements if you have time.
You’ll walk away with
A one-page 'delivery trace' for one design element: its intent, what each stage must do to keep it, the threats at each stage, and the designer's protective action - plus a reflection on where intent most often leaks. Keep it; it is a map of where to spend your attention on a real project.
Three altitudes on the same idea
Read the band that fits you — or all three.
On delivery the architect usually owns the base-build and the large moves, and the interface between shell and fit-out is where coordination is won or lost. Core, structure, facade, main services routes and floor-to-floor heights set what the fit-out can do, so your documentation and site decisions ripple through every later trade. Sequence matters: base-build work that lands late or differently from the drawings throws the whole fit-out programme. Hold the interfaces - slab penetrations, riser capacities, facade tie-ins, fire compartmentation - tightly, document them unambiguously, and defer every binding structural, egress and services value to the current codes and the specialist engineers. Your calm coordination at the shell-to-fit-out seam protects the whole delivery.
Delivery is the core of workplace interior practice: most of your hours go into detailing, documenting and then protecting the design on site. You resolve the junctions, write the finishes and FF and E specification, produce the drawing set a contractor can build from, review shop drawings and samples, answer site queries, and judge every proposed substitution against the concept. Your superpower is knowing which compromises are harmless and which quietly kill the idea. Document completely, specify clearly, and chase the snag list to zero - the last ten per cent of finish is where interiors feel either resolved or cheap. Carry the acoustic, fire and accessibility specialists' input into your documentation rather than guessing it.
Delivery is the part of the job schools teach least and practice values most - so learning its shape early gives you a real head start. Memorise the spine: concept, detailed design, documentation, tender, construction, snagging, commissioning, handover, and understand that decisions get dramatically more expensive to change the later they are made. Notice that the designer never simply hands over and leaves; the role shifts from author to keeper-of-the-intent and coordinator. When you get the chance, read a real drawing set and a real snag list - they teach more about how buildings actually happen than any render. The skills that matter here are less about flair and more about rigour, communication and judgement under pressure.
“Once the design is approved and handed to the contractor, the designer's job is basically done - construction is the builder's problem, and the space will come out looking like the renders.”
Do it yourself
No tools needed - reason it through.
- 1List the stages of a workplace project from concept to handover, and say in one line what each is for.
- 2Why do decisions get more expensive to change the later in delivery they are made?
- 3What does it mean to say the designer's job through delivery is to 'guard the intent'?
- 4Why can the cheapest tender be the most expensive choice for the client?
- 5Explain the difference between snagging, commissioning and handover - and why each matters to the finished workplace.
The one line to carry out
Peer-reviewed journals & authoritative standards
- 01Project management — Wikipedia - Project management, 2026.
- 02Procurement — Wikipedia - Procurement, 2026.
- 03Furniture, fixtures and equipment — Wikipedia - Furniture, fixtures and equipment, 2026.
- 04National Building Code of India — Wikipedia - National Building Code of India, 2026.
But a finished, snag-free building is still only an empty stage. The hardest part of a new workplace is not the construction - it is the people who have to change how they work inside it. That is where we go next.
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →