Create requirements and functional specs with AI
Describe your initiative in a few sentences. PathHub writes a structured document with numbered, testable requirements, acceptance criteria and open points — as a Word file to keep editing.
What the document contains
Not an empty template, but a written draft for your initiative.
Numbered requirements
Functional (F-01 …) and non-functional requirements (N-01 …), each stated on its own and unambiguously.
Priorities
MUST, SHOULD, COULD — so vendors know what is negotiable and what is not.
Acceptance criteria
A testable criterion for every requirement, used for sign-off.
Interfaces and migration
Which systems are connected and which data has to be migrated.
Data protection and works council
GDPR, data processing agreements and co-determination where the system can track performance or behaviour.
Open points
Assumptions are marked; everything still to be clarified is collected at the end.
What a result looks like
Excerpt from a requirements specification for an ERP rollout:
Material requirements planning
The system calculates material requirements per site from customer orders and bills of materials and proposes purchase orders.
Acceptance: Planning run for 500 orders in under 5 minutes; proposals match the manual calculation in the test.
Accounting export
Posting-relevant documents are handed over to financial accounting daily in the agreed format.
Acceptance: The export is imported by accounting without rework.
Roles and permissions
Access is controlled by roles per site and department.
Acceptance: Test users only see the data of their role.
How it works
Describe your initiative
A few sentences are enough: what is introduced, for whom, current systems, key requirements.
Document in about a minute
Requirements or functional specification with chapters, requirement tables and open points.
Keep editing in Word
Download it, complete it with your team — or turn it into a project plan with one click.
Requirements or functional specification?
Requirements specification
Written by the client. Describes WHAT is needed and WHY — goals, requirements, constraints. The basis for proposals and vendor selection.
Functional specification
Written by the contractor. Describes HOW the requirements are implemented — architecture, solution per requirement, testing and acceptance.
Examples and templates
Frequently asked questions
From requirements to project plan
PathHub also turns your initiative into a complete project plan — with schedule, budget, risks and compliance.
Create project plan →