
A supplier-neutral scoping document is a written plan that any supplier could pick up and build from. It should describe the problem, what the software must do, which rules it must meet, where it will run and who will run it, and how the finished work will be accepted. It should end with a clear go or no-go decision.
Many custom software projects go wrong before anyone writes code. The plan lives in meeting notes, emails and the head of one project lead. Then the build starts, and nobody can say for sure what "done" looks like.
A proper scoping document fixes that. Many documents fall short on one test: whether a different supplier could use them.
Why the document should work without the supplier who wrote it
Some scoping documents only make sense to the team that wrote them. They use the supplier's own terms, point to its own tools and leave gaps that only its developers can fill. In practice that ties you to one supplier before you have decided anything.
A supplier-neutral document gives you a real choice. You can take it to the supplier who wrote it, to another agency or to your own IT team. You can also put it in a drawer if the answer is no. If you are still weighing up suppliers, this comparison of Upward Technologies and Dutch custom software agencies sets out the main differences.
What a scoping document should contain
These are the parts that make a scoping document usable, whoever builds the software:
- The process as it works today. Who does what, where the data comes from and where people work around the tools they have now.
- Requirements, written down. What the software must do. Security and accessibility should sit in the same list as the features, not in a note at the end.
- Statutory and regulatory requirements. The laws and rules the software has to respect, checked before any design work starts.
- The hosting boundary. Where the software will run and who is responsible for running it. This decides who handles backups, monitoring and fixes after go-live.
- Planned stages. Each stage of the build needs defined inputs and outputs, so progress can be checked against something concrete.
- How acceptance will work. The finished software is measured against the recorded requirements. If something does not meet a requirement, the document should say how that gets handled.
- A go or no-go decision. A clear answer on whether to build and on what basis.
One thing does not belong in a scoping phase: a prototype or a working AI agent. Scoping decides what to build. Building comes after. If you are scoping an AI agent, this article on when to build a custom AI agent and when to use an off-the-shelf tool can help you frame that part of the document.
How a go or no-go decision is reached
A go or no-go is only useful if "no" is a real option. The decision should follow from what the scoping work found. It should not follow from how much time has already gone into talks.
A no-go can take several forms:
- An off-the-shelf package fits well enough. If a standard tool covers the process, buying it is often the better choice. A fair scoping phase says so plainly.
- The supplier is the wrong fit. The work might need skills, hosting or a setup the supplier does not offer. The supplier should say this early. Week one is better than week three.
- The rules make the plan unworkable as written. Legal or regulatory limits can mean the idea has to change before it can be built.
A go means the requirements are clear enough to build against. It also means the way the result will be accepted is agreed.
Questions to ask any supplier before scoping starts
- Will the document be written so another supplier could build from it?
- Is scoping paid and fixed in length, and what exactly do I get at the end?
- Will you tell me if an off-the-shelf tool fits better, or if you are the wrong supplier?
- Are security and accessibility listed as requirements next to the features?
- Does the document say where the software will run and who runs it after go-live?
- How will the finished work be accepted, and what happens when something does not meet a requirement?
For a wider view of choosing a builder, see how to choose custom software development.
How Upward Technologies handles scoping
Every Upward Technologies project starts with a three-week paid scoping phase before any code is written. It ends with a document the client could take to another supplier, along with a go or no-go decision. Feasibility is checked first. That includes statutory and regulatory requirements and which side of the hosting boundary the work sits on. "Wrong supplier" is a valid outcome, and Upward Technologies says so in week one.
If the answer is go, the build starts from the scoping document.
Upward Technologies builds what it delivers and also offers hosting and support.
FAQ
What makes a scoping document supplier-neutral?
It is written so that any supplier, or your own IT team, could build from it. It avoids one supplier's internal terms and tools, and it leaves no gaps that only the original author can fill.
Should a scoping phase include a prototype?
No. Scoping decides what to build and whether to build it. Prototypes and working software come after the go decision.
Is a no-go a failed scoping phase?
No. A no-go can save money and time. It might show that an off-the-shelf tool fits, that the supplier is the wrong fit, or that the plan has to change to meet the rules.
Why does the hosting boundary belong in a scoping document?
Because it settles where the software will run and who is responsible after go-live. Without it, tasks like backups, monitoring and fixes can fall between parties.



