Two vendors estimate the same "corporate website with a catalog" and quote prices that differ several times over. Neither is wrong: each simply pictured a different website. A website requirements document removes that uncertainty. It describes exactly what will be built, how it should work and how the work will be accepted.
Below we cover why you need a website specification, how it differs from a brief and a prototype, which sections it should include, who writes it and what to do when requirements change mid-project.
Why you need a requirements document
A specification has three practical jobs, and all three are about money and stress.
- Estimating cost and timeline. Without a list of pages, features and integrations, a vendor either builds risk into the price or quotes the minimum and bills extras later. With a specification, estimates from different web development agencies can be compared side by side.
- Acceptance. When the site is ready, you need to know whether what was agreed has been delivered. The specification answers that point by point, not by gut feeling.
- Disputes. If the parties understood the task differently, the specification is the document both go back to. It is usually attached to the contract, which gives it legal weight.
There is a fourth, less obvious benefit. While the specification is being written, the client often puts their needs into words for the first time, drops some features or discovers things they had not thought of.
Brief, specification and prototype: what is the difference
These three documents are often confused, or one is used in place of another. In fact they answer different questions and appear in the project one after another.
| Brief | Specification | Prototype | |
|---|---|---|---|
| Answers the question | What the business needs | What the site does and how | How it looks on screen |
| Who fills it in | The client | Usually the vendor with the client | The vendor |
| Length | A few pages of questions | From a few to dozens of pages | Wireframes of key screens |
| What it is for | Initial estimate and conversation | Precise estimate, contract, acceptance | Testing the logic before design |
A website design brief is the starting point: what the company does, who its customers are, why it needs a site, what examples and constraints exist. A brief is enough for a price range, not a precise quote. The specification turns the task into requirements. The prototype shows those requirements visually and is often part of the specification or sits next to it: the same inquiry form is easier to agree on as a wireframe than in three paragraphs of text.
Specification structure: what the document should include
There is no single official standard for commercial websites, and that is fine. The structure depends on the project, but most sites share a similar set of sections. Use it as a checklist when you write the document yourself or review one from a vendor.
- Goals and audience. Why the business needs the site, what visitors should do, who they are and which devices they mostly use.
- Structure and pages. A sitemap, page types and what goes on each: home, catalog, product page, service page, contact, blog.
- Features. Forms, filters, search, cart, payments, customer account, each with a scenario description.
- Roles and admin panel. Who manages the site, who has which permissions, what can be changed without a developer.
- Integrations. CRM, ERP, warehouse, payment providers, shipping services, email platforms: what data is sent, in which direction and how often.
- Content. Who prepares copy, photos and video, who migrates data from the old site, and in what format everything is delivered.
- Design requirements. Brand identity, brand book, references, what you like and what definitely does not fit, how many concept options.
- Responsive design. Which devices and browsers are supported, what changes in the mobile version.
- SEO and analytics. URL structure, meta tags, migration of old URLs and redirects, conversion events in Google Analytics.
- Performance and security. Expected load speed, traffic, protection for forms and the admin panel, backups.
- Hosting and domain. Where the site will live, who owns the domain and server, who pays for them.
- Acceptance criteria. How each feature is tested and what counts as done.
The last item is the most important and the one most often skipped. A feature without acceptance criteria is a dispute waiting to happen, not a requirement. "Convenient search" cannot be tested. "Search finds products by name and SKU, corrects typos and shows suggestions after the third character" can.
Specification for an online store
A store adds its own items to the general list. The document describes the catalog structure and filters, the source of products and inventory, pricing and discount logic, payment and shipping options, order statuses and customer notifications. Separately, it covers what happens to an order after checkout: where it goes, who processes it, how it syncs with the accounting system. These scenarios drive most of the work, and without them a store estimate is almost always off.
Level of detail: short or detailed
Writing forty pages for a landing page makes no sense, and describing a customer account in one paragraph is dangerous. The level of detail depends on complexity and the cost of a mistake.
A short specification is enough when the site is mostly informational: a landing page, a business card site, a small corporate site without integrations. Goals, a list of pages with their blocks, forms and where submissions go, design and responsive requirements, and a plan for content and analytics will do.
A detailed specification is needed when there is logic that is easy to read in different ways: an online store, a customer account, ERP and CRM integrations, multiple user roles, calculations and calculators. Here every feature is described as a scenario: who does what, what they see, what happens on error.
Describe in detail wherever a mistake is expensive: integrations, payments, customer accounts and roles.
A handy rule: the more data the site sends somewhere, the more detailed the specification. Copy on the About page can be fixed in an hour, while a misunderstood order exchange with the accounting system can take weeks to redo.
Who writes the specification: client or vendor
In practice, the question of who writes the specification is settled like this: the client knows the business, and the vendor knows how to turn it into website requirements. That is why a good requirements document is almost always written together.
A client can write it alone if they have experience or a technical specialist on staff. Such a document is useful for comparing vendors, but it usually still needs work: it describes "what we want" well and "how it will work" less so.
More often, the specification is produced by the web development agency during a separate discovery stage. At Sphere, the first stage of every project is research, structure and meaning: we study the market, audience and competitors and plan every screen. The result of that stage becomes the basis for the site requirements. You can see how we work stage by stage on our About page.
How to write a website specification for the first time
- State the goal. In one sentence: what the site should deliver for the business, whether leads, sales or less load on the sales team.
- Describe visitors and their scenarios. Who comes, what they are looking for, what action you expect from them.
- List pages and features. Start with the must-haves and mark separately what can wait.
- List the systems the site must work with. CRM, ERP, warehouse, payments, shipping.
- Decide who prepares content. Copy, photos, catalog migration.
- Review the document with your vendor. Their questions will show where requirements are not fully clear.
Common mistakes in a requirements document
Most specification problems repeat from project to project. They are easier to spot early than to fix at acceptance.
Two more mistakes are rarer but expensive. The first is not specifying who is responsible for content: the site is ready, and there is nothing to put on it. The second is forgetting the old site: without a plan for migrating pages and setting up redirects, the new site loses the search traffic it had built up.
How the specification changes during the project
A requirements document that never changes is rare. During design it turns out a scenario works better another way. After the first tests the client realizes a filter needs a different attribute. That is normal: requirements can change, as long as there are rules.
The change process is worth defining up front, in the specification or the contract:
- How a change is submitted. A written request describing what changes and why.
- How it is estimated. The vendor states how much time and money the change takes and how it shifts the timeline.
- Who approves it. A single point of contact on the client side, so changes do not arrive from three departments with contradictions.
- Where it is recorded. A new version of the specification or an addendum, so acceptance checks the current requirements.
Big ideas that come up during the work are best kept out of the current scope and moved to a second phase. That way the first release ships on time, and the new features are built after launch, with data on how visitors actually use the site. You can see how such decisions play out in finished work in our projects.
FAQ
Does a small website need a specification?
You do not need a long document, but a short specification is worth writing even for a landing page: the goal, a list of blocks, forms and where submissions go, responsive and analytics requirements. It protects both sides at acceptance.
Can I write a specification from a template I found online?
A sample specification is useful as a list of sections so you do not forget anything. But the content still has to be written for your business: someone else's requirements describe someone else's processes.
Who writes the website specification?
Most often the vendor, during discovery, together with the client. The client brings knowledge of the business, customers and processes, and the vendor turns them into requirements, scenarios and acceptance criteria.
Can the specification change after development starts?
Yes, if changes follow the rules: a written request, an estimate of the impact on cost and timeline, approval and a new version of the document. Big ideas are better moved to a second phase after launch.
How is a brief different from a specification?
A brief describes the business goal and is used for the first conversation and a rough estimate. A specification describes the requirements for the site and is used for a precise estimate, the contract and acceptance.




