How to write website requirements: a practical checklist
The terms of reference for the site are not a formality and not an attempt to describe each button in advance. This is a common working document that helps the customer and developer to equally understand the purpose of the project, the scope of work, content requirements and readiness criteria.
A good technical specification reduces the number of controversial interpretations, but should not turn into a hundred pages. For most corporate websites, it is enough to consistently answer seven groups of questions: why the site is needed, who will use it, what pages and functions are needed, where the materials come from, what systems it is connected to, what it should look like and by what criteria the work is considered accepted.
1. Start with a goal and measurable outcome
The first section of the statement of work should explain the business problem. The formulation “we need a modern website” does not give direction: modernity cannot be verified, and different participants understand it differently. It is much more useful to indicate what action the visitor should take and what the company will do with the result.
For example: receive enquiries for specific services, show a portfolio, accept requests for calculations, publish vacancies or give clients access to documents. For each goal, indicate the main indicator – a submitted form, a call, an appointment, a document download, or an account login. Do not promise sales growth in advance: the site affects the result along with traffic, offers and processing requests.
If the project replaces an existing site, separately list the reasons: inconvenient management, slow loading, outdated structure, errors on phones or the inability to connect the necessary services. This will allow you to distinguish mandatory tasks from wishes.
2. Describe the audience and main workflows
Describe two or three main user groups. There is no need for fictional character biographies; enough tasks, context and constraints. One visitor is looking for a service from his phone and wants to quickly get in touch, another is comparing contractors from his computer, the third has already become a client and is opening documents in his client dashboard.
For each group, write down a short path: where the person comes from, what he should see first, what information he needs to make a decision, and what action completes the scenario. This makes it clear where prices, examples of work, answers to questions, a form, a map, a filter or authorization are needed.
Scripts help remove unnecessary functions. If an element does not support any user task and is not needed by employees, it should be removed from the first version. And if an important step depends on a manual response from the manager, this must be indicated immediately – otherwise a beautiful interface will not solve the problem of processing enquiries.
3. Agree the page structure and content
Create a site map: home page, service pages, portfolio, about the company, contacts, blog and service pages. For the catalogue, add categories and cards; For multiple languages, indicate which sections are being translated and who is responsible for the translations. The structure should reflect actual content, not just menu items.
For each page type, list the blocks and data. For example, a service page might include a title, a short sentence, steps, examples, answers to questions, and a form. Project card – task, solution, technology, images and link. Such a list gives the developer an understanding of repeating patterns and helps to more accurately estimate the volume.
Before starting the design, it is useful to prepare materials according to the business owner checklist. If some of the content appears later, note which pages can be filled temporarily and who will replace the materials before publication.
4. Collect functional requirements
Functional requirements describe not the appearance, but the behavior of the system. For the form, specify the fields, mandatory requirements, data verification, message after submission, enquiry recipient and storage location. For search – what data it searches for. For your client dashboard – roles, available sections, statuses, files and user actions.
Write down the conditions and result: “after sending, the enquiry is saved, receives a number and is transferred to the manager; If there is a temporary delivery error, no data is lost.” This is more useful than the phrase “connect CRM.” The path from the form to the manager is discussed in detail in the article about the transfer and control of requests.
Don’t forget about error messages, empty states, file upload restrictions, resubmission protection and access rights. Also indicate what actions the site administrator performs: edits pages, changes statuses, exports data, or manages users.
5. List materials, integrations and access needs
Make a table of content: text, photos, logos, documents, prices, legal information and translations. Next to each item, assign a person responsible and a deadline. If the developer must edit or create materials, this is a separate work that needs to be included in the assessment.
List integrations with the direction of exchange: the site transfers requests to CRM, receives goods from the accounting system, sends notifications to Telegram, or shows availability from an external calendar. Indicate the owner of each system, availability of documentation and test access. Do not transfer permanent passwords in the requirements document itself – access is issued separately and with minimal rights.
Fix in advance who owns the domain, hosting, analytics, mail, repository and third-party accounts. This protects the project from depending on the client dashboard of one employee or contractor.
6. Define design and responsive requirements
Instead of a vague “make it beautiful”, attach two or three examples and write down what exactly fits them: density, navigation, presentation of cases, animation or color. Separately list the elements of your corporate identity – logo, palette, fonts and rules of use.
Define priority screen sizes and behavior of complex blocks on the phone. Responsive – not a scaled-down desktop version: menus, tables, forms, cards and headers should remain usable without horizontal scrolling or unnatural wrapping.
Include requirements for accessibility, contrast, readability, keyboard navigation and image captions if these are important to the project. Animations should support the meaning and not interfere with reading. After implementation, check not only the screenshot, but also the real conditions: long titles, form errors, empty lists and slow network.
7. Agree milestones, review and support
Divide the work into stages: prototype, design, development, content, testing and publication. For each stage, determine the result, the approval format and who is responsible on the part of the customer. Also agree on how changes are recorded after approval – otherwise new wishes will imperceptibly expand the scope of the project.
Acceptance criteria must be verifiable: pages open according to the agreed structure, forms deliver test requests, roles do not see other people’s data, images have captions, and mobile versions do not exceed the width of the screen. Before launching, use site technical checklist.
Separately describe the warranty period and further support: updates, backups, monitoring, corrections and response time. Post-launch support is a separate process, not an unlimited continuation of development.
A checklist before handing over requirements
Before sending to the developer, check the technical specifications against a short list:
- the purpose of the site and the main action of the visitor;
- audiences and key user paths;
- site map and composition of repeating pages;
- forms, accounts, search, notifications and roles;
- content sources and those responsible for materials;
- integrations, account owners and issuance procedure access permissions;
- references, corporate identity and mobile requirements;
- stages, acceptance criteria and rules for changing the volume;
- conditions of publication and further support.
After that, request an assessment by stages and check that it includes all required work. Additional guidelines can be found in the article on transparent assessment of development. Fill out a brief for website development – we will help you turn your initial wishes into a clear project plan.
How to check a finished technical specification
A good way to check how to compose a technical specification for a website is to hand over the document to a person who did not participate in the discussions. If he understands the purpose, scope, roles and acceptance criteria without verbal explanation, the document is suitable for evaluation.
Before agreeing, check the requirements against the W3C Web Accessibility Guidelines. This helps to consider contrast, keyboard navigation, and clear captions up front rather than fixing them after launch. This way, a practical answer to the question how to draw up technical specifications for a website turns into a verifiable plan, and not into a wish list.
Short questions about the technical specifications
How to draw up a technical specification for a website for redesign?
Fix current problems, analytics data, saved materials and measurable results of the new version.
How to draw up a technical specification for a website with a client dashboard?
Describe the roles available to each role, data, statuses, notifications and administrator actions.
How to draw up technical specifications for a site if the content is not ready yet?
Make a table of materials, assign those responsible and indicate what texts or images are being prepared by the contractor.