Suggest standard operating procedures in a design studio and someone will say that design cannot be proceduralised. They are right about the design and wrong about the studio.
Nobody is proposing a procedure for the concept. The proposal is a procedure for naming files, so that a designer at 11pm before a client meeting is not searching three drives for the current revision.
Every studio already has SOPs. In most they are undocumented, inconsistent between people, and re-invented per project. That is not the absence of process; it is process with no quality control.
Write down what is already true
The failure mode is designing an ideal process in a workshop and imposing it. It will not survive a fortnight, because it was never how the work happens.
Start by documenting what your best project actually did. Not what should have happened — what did. That is your first draft, and it has the advantage of being real.
The seven worth having
Ordered by how much pain they remove per page written.
- File naming and folder structure. Dullest, highest return.
ProjectCode_Drawing_Rev_Date, one structure, no exceptions. Studios lose hours a week to this and never count them. - Drawing issue checklist. What must be true before a drawing leaves the studio — title block, scale, revision, north point, the specific things you have been burned by.
- Client onboarding. Brief template, budget conversation, what you collect before design starts, what the client is told about revisions. This one prevents the most expensive failures.
- Revision and variation handling. When a request becomes chargeable, who decides, how it is communicated. Not having this documented is why nobody invokes the clause.
- Handover pack. Exactly what the client receives: drawings, warranties, maintenance notes, vendor contacts. Assemble it as you go, not in a panic at the end.
- Site visit format. Covered in site visit reports that actually get read.
- Snagging. Covered in snag lists for interior projects.
Seven documents. None longer than a page. If yours run to five pages, they are being written for an imaginary auditor.
One page, or it will not be read
The test: can a new joiner read it in two minutes and act correctly?
Checklists beat prose. Prose beats policy. A numbered list of what to do, in order, with the decision points marked, is worth more than a well-written explanation of the philosophy.
Where an SOP needs justification, one line is enough. "Revision number goes in the filename because we have issued the wrong revision twice." People follow rules whose reason they know.
Separate the parts that must not vary
The distinction that makes this palatable to designers:
Must not vary — anything where inconsistency creates risk or waste. File naming, drawing checks, what goes in a handover pack, how a variation is raised, how a snag is verified.
Must vary — the design. Concept, palette, spatial strategy, detailing. No procedure, and saying so explicitly is what makes the first list acceptable.
Most resistance to process in studios comes from a fear that the second list is next. Draw the line loudly.
Owned, dated, revised
An SOP with no owner rots. Every document gets a name and a review date, and a project that exposes a gap in one is the trigger to update it — that afternoon, while the pain is fresh.
The alternative is a folder of documents describing a studio that stopped existing two years ago, which is worse than none, because people learn the documents are fiction and stop reading all of them.
What this buys you
The point of SOPs is not consistency for its own sake. It is that they remove the decisions that were never creative, so attention is available for the ones that are.
A designer who is not deciding where to save a file, what to call a revision, or whether this counts as a variation has more attention for the design. That is the argument, and it is the only one that will land in a room full of designers.
Related: structuring a small design studio team.