BRD v1.3
The business requirements. Requirements the SDD replaces are left out.
Release 1 Must-haves: — without integrations, — with them.
How much of the BRD and the SDD the application does today, measured against the code on 2 November 2026. Lead capture is the furthest along. The modules from the verification visit to recovery have not started, and no integration is connected to a live system yet.
The business requirements. Requirements the SDD replaces are left out.
Release 1 Must-haves: — without integrations, — with them.
The solution design, which governs the build where it differs from the BRD.
The SDD groups each later module into one feature, where the BRD lists many requirements, so its figure runs higher.
Complete means fully built plus half of what is partly built. With integrations, an exchange with Dynamics 365, Web.HR, payments or SMS counts as done only once it works against the live system.
Share of each workstream's requirements that is done.
Each module's features by status, with the share done at the end of the bar.
Integration features that run against a stand-in count as not started until they are connected live.
— done, — in progress and — not started.
| Ticket | Work | State |
|---|
| Milestone | Dates | State |
|---|
| System | State | Note |
|---|