SOPs for design studios: standardising without killing the craft
Seven one-page SOPs worth having, why they must be written from what already happens, and how to separate what must not vary from the design itself.
Blueprint OS Blog
Practical writing on running an architecture or interior design studio — pricing, phases, approvals, snagging, profitability and team structure.
Seven one-page SOPs worth having, why they must be written from what already happens, and how to separate what must not vary from the design itself.
Three to twelve people is where most design studios break. Where the real bottleneck is, what changes at each size, and what the principal must stop doing.
A visit should produce progress variance, decisions taken on site, and items with owners. The one-screen structure, and how to photograph deliberately.
Projects fail in week three, not at handover. The four causes, the one number that predicts the outcome, and how to cost your team properly.
Designers resist timesheets because they are usually surveillance. Scoped to pricing rather than performance, they are the only way to quote accurately.
Approval delay is rarely client indecision. It is bundled decisions, too many options, and the wrong person in the room. What to change.
A snag list structure that gets defects fixed and holds up in a dispute - six fields, three states, severity definitions and a room-by-room route.
Discovery, design, procurement, execution, handover - and the specific failure mode at each phase boundary, with the gate that prevents it.
Per square foot, percentage of project value, or fixed fee - each breaks differently. A practical comparison with the hourly cost arithmetic.
Generic PM tools assume software teams. Design studios run on phases, client approvals and site reality. What to look for, and what to ignore.