Requirements Specification & Business Requirements – Requirements Matrix, Acceptance Criteria and Excel | Word/PDF

Requirements specification and business requirements – editable Word templates, searchable PDFs and an Excel requirements register. For Swedish companies planning an IT system, updating business processes or needing clear, prioritized and testable requirements for an internal project or B2B purchase. The package helps you document needs, requirements, changes and decisions. It is not a binding supplier agreement, a public procurement template or a guarantee of legal or technical compliance.

When should you use a requirements specification?

Use it before a solution is ordered, developed or procured within a private company: define the problem, select the scope, formulate functional and non-functional requirements, determine acceptance criteria and track any changes. For legally binding delivery and liability issues, the correct agreement must be drawn up separately.

File by file – content and use

Excel – requirements matrix and traceability

The workbook contains Dashboard, Read me, Requirements register, Stakeholders, Decisions, Changes, Verification, Risks and Lists. The register tabs have status options for requirements, decisions, change requests and tests. The Dashboard counts the number of registered requirements, priority, documented decisions, test items, changes and risk notes. The registered status is not an actual decision, legal check or completed acceptance testing.

How to use the package

1. Describe the actual business problem, impact goals and scope in the needs analysis.
2. Formulate requirements and give each requirement a permanent unique REQ-ID.
3. Define testable acceptance criteria with prerequisites and observable result.
4. Register requirements, priority, responsibility and change request in Excel.
5. Review and decide on a specific requirements version. Include the specification as a correctly identified appendix in the agreement when necessary.
6. Perform separate testing and delivery approval when a solution has actually been delivered.

Legal prerequisites and boundaries

Agreement: an internal requirements document does not automatically become a supplier agreement. If the requirements specification is to be binding, the correct parties and an exact version must be incorporated under relevant agreement terms. Read the Swedish Consumer Agency's general information on entering into agreements; it does not apply as complete B2B agreement advice.

Data protection: if the IT solution processes personal data, data protection by design and by default according to GDPR may need to be assessed. IMY describes data protection by design. The templates do not automatically perform a consequence assessment or legal security review.

Public sector and regulated industries: this is not a complete public procurement document. Special rules and binding requirements must be assessed in the concrete project.

Questions and answers

What is the difference between business requirements and system requirements?

Business requirements describe which business problem is to be solved and what benefits are sought. System requirements specify what the system should be able to do and how this can be verified.

How do you write acceptance criteria?

Describe the starting condition, event and observable result. A good criterion can be tested with a defined test case and a documented outcome.

Can Excel automatically approve requirements?

No. Excel compiles register items and status markings. An approval presupposes an actual decision by an authorized person.

Is the requirements specification an agreement?

Not in itself. It can become part of an agreement if the agreement clearly refers to the correct version and meets relevant prerequisites.

Are all main templates in English?

No. The five working documents are in Swedish. The English User Guide provides instructions for the Swedish files and does not imply adaptation to foreign law.

Can the product be used in public procurement?

Not as a complete procurement basis. Public procurements and regulated activities may require special documents and assessments.

Related templates

For earlier needs mapping, see Process Mapping & Process Description. For supplier selection, Request for Quote & Supplier Comparison may be relevant. When a completed IT delivery is to be checked, see Acceptance Testing & IT Delivery Approval.

Version, source and delivery

Product version 1.0. AI-assisted legal source check of mentioned official sources on October 29, 2026. No external legal review and no certification. Intended for internal requirements processes and private B2B projects with Swedish prerequisites. Delivered as a digital ZIP after the seller has linked the file to the correct variant and activated the product; the product is under preparation.