PNH logo
Software5 min read

What a written scope is actually for

It is not paperwork and it is not protection against the client. It is the document that makes an estimate mean something.

Two colleagues working through notes together beside a laptop

Most software projects that go wrong did not go wrong during the build. They went wrong in the week before it, when somebody gave a number for work nobody had written down. The number was honest when it was said. It just described a different project from the one that got built.

An estimate is a claim about a scope

A price quoted before the scope exists is not an estimate — it is a bid to win the conversation. Both sides know roughly what is meant, and "roughly" is exactly where the disagreement lives. Does "customer management" include importing five years of history from the old system? Does "reporting" mean four fixed reports or a report builder? Neither answer is wrong; they are simply different amounts of work, and only one of them was priced.

What we write down before quoting

  • What the software has to do, in the words of the people who do that work today
  • What is explicitly OUT of scope — usually the more useful half
  • The assumptions the price depends on, each one named
  • What we need from you, and by when, for the plan to hold
  • What "finished" means, so it is a date rather than an opinion

The out-of-scope list is the part clients are most surprised by and the part that saves the project. Writing "this does not include integrating with the accounting system" costs one line. Discovering it in week six costs a renegotiation, and the trust that goes with it.

Assumptions are the price

Every estimate rests on assumptions: that the data can be exported, that one person can make decisions, that the existing system has an API. Written beside the number, an assumption that turns out to be wrong becomes a conversation about which line moved. Left unwritten, the same fact becomes an argument about whether we should have known.

A scope is not there to hold the client to something. It is there so that both sides are talking about the same piece of work.
How we run engagements

It costs less than it looks

Writing a scope takes days, not weeks, and most of that is time spent watching how the work is done now. That time is not overhead — it is the part of the project where the cheapest changes are still possible. A process fixed on paper costs nothing; the same fix after the build costs a rewrite.

If you are holding a quotation from anyone — us included — and cannot find the scope it was priced against, that is the question to ask before signing anything.

Next step

Have a requirement this touches on?

If something here is relevant to what you are buying, the fastest route is to describe your case rather than read three more articles.

We reply to every enquiry within one working day.