Most studios that lose money on a project blame the project. The client changed their mind, the builder was slow, the third round of revisions came out of nowhere. Look at the proposal that started it and the problem is usually already there, written down and signed by both parties.

Here is a line from a real interior design proposal: "Concept design phase includes development of the design direction and presentation to client." That sentence commits the studio to an unknown number of concepts, an unknown number of presentations, and an unknown definition of when the phase ends. The client who asks for a fourth layout option in week nine is not being difficult. They are asking for something the proposal never excluded.

Compare it to this: "Concept design includes two layout options for the ground floor. Once you've reviewed both and confirmed a direction, we'll develop it into a full set of drawings." Same phase, same work, but now there is a number, a decision point, and a clear end. The fourth layout option becomes a variation you can price, because the proposal established that the base fee covers two.

The pattern repeats across spatial work.

Architecture proposals say "design development" without stating how many coordination meetings, which consultants the fee covers, or whether council amendments after lodgement are included. The client who treats a planning setback as your problem to absorb is reading the document the way it was written.

Landscape proposals include "planting plan" without saying whether plant procurement and site supervision are in or out, and the gap between those two readings is measured in site visits.

None of this requires legal language or a longer document. It requires the proposal to state three things per phase: what is produced, how many of it, and what the client needs to do before the next phase starts. A client sign-off requirement is worth more than most terms and conditions clauses, because it converts an open-ended process into a sequence of gates. If the client has not confirmed the schematic set, the construction documents have not started, and neither has the scope creep.

The reason studios keep writing vague scope is not laziness. It is that the proposal gets written at the moment of least information, usually late, usually the night before it is due, usually by adapting whichever old document is closest. Vagueness is what happens when you write scope from scratch under time pressure. The fix is not to try harder at 11pm. The fix is to settle the counts, the deliverables, and the sign-off points once, on a quiet afternoon, so that when the next proposal is due your job is adjusting them for the project rather than remembering to include them at all.

You will still have projects that go sideways. But there is a difference between a project that goes sideways with a document that says exactly where the base scope ended, and one where you re-read your own proposal mid-dispute and realize it could mean anything.