The problem with spreadsheets between organisations
On most programmes the requirements live in a spreadsheet that gets emailed between the client, the head contractor and a dozen suppliers. Each copy drifts. Nobody is sure which version the supplier priced against, who owns a requirement that sits on an interface, or whether the evidence a subcontractor sent last month was ever filed. The result is version control arguments, "that wasn't in my scope" disputes and problems that surface at acceptance instead of at design.
Reqi replaces the emailed spreadsheet with a single live register that everyone works in.
One shared space, unlimited users
Internal teams, contractors and suppliers see the same real-time information. Responsibilities are tracked per requirement and per system, dependencies between teams are visualised, and a problem is caught where it starts rather than after it has cascaded into a delay.
Because every plan has unlimited users, the question of whether a supplier's engineer gets a licence never comes up. Invite them to the project and they are in.
Contract requirements, before and after award
Bulk import the contract requirements from the specification, whether it arrives as Excel, Word or a PDF, with REX extracting a structured requirement list from the PDF. Then track compliance with system-level views across the supply chain, so you can see at a glance which systems are compliant, which are partially compliant and which have no evidence yet.
Reqi manages the requirements pre and post contract award with full traceability from specification through to acceptance. Analyse how different parts of the system interconnect and surface risk before it becomes a problem.
Decide who designs and who signs off
The engineer who designs a system should rarely be the one who signs it off. Reqi ships five roles: Project Manager, System Designer, System Reviewer, System Verifier and View Only. Rename any to your own terminology, then set what each can reach: all systems or only their own, every page Edit, View Only or Hidden, and who may close a requirement. The configuration applies across every project in your organisation.
| Access | Project Manager | System Designer | System Reviewer |
|---|---|---|---|
| System access | All | Assigned | Assigned |
| Requirements | Edit | Edit | View only |
| Systems | Edit | Edit | View only |
| Closure | Approver | View only | Approver |
An example configuration. Every role, page and step is yours to set.
Allocations are reviewed and agreed, not just edited
Who owns a requirement is a contractual question, so Reqi treats allocation as something that is proposed, reviewed and agreed rather than a cell anyone can overwrite.
- A requirement is allocated to one or more systems in the breakdown structure, each with its own designer, reviewer and verifier.
- The allocation moves to Review and then to Agreed, at which point it locks.
- A team member who is not an approver can still ask for a change. The request appears as a pending badge on the requirement until an approver agrees or declines it, so the register shows both what is agreed and what is contested.
- Acceptance criteria are defined against the requirement and the supplier records its verification evidence there. Each requirement carries a comment thread, and every user has an inbox of the open comments addressed to them, so a query about evidence is answered on the requirement rather than in an email.
Built for programmes where a missed requirement is a finding
Reqi is used by project teams, systems engineers and asset owners in defence and aerospace, construction and infrastructure, rail and transport, energy and utilities, mining and resources, healthcare and medical devices, manufacturing and automotive, and IT and telecommunications. Each industry's particular failure mode is described on the about page. The platform runs on Azure with ISO 27001 and SOC 2 compliance in an Australian data centre; see data security.
What it costs
$190 per month, plus GST
Per project, for one to five projects. Unlimited users on every plan, including the free one.
Per project rather than per seat is the whole point for a supply chain: adding a supplier's team to the programme does not change the invoice. A single project is free for three months, up to 500 requirements. Full detail on the pricing page.
Supply chain requirements: frequently asked questions
Do our suppliers need their own licences?
No. Every plan has unlimited users. You invite a supplier's people into the project and the price does not change.
Can one supplier see another supplier's requirements?
Only if you let them. Each role is set to see all systems or only the systems it is assigned to, so a supplier can be limited to the requirements it is answerable for.
How does a supplier submit verification evidence?
Against the requirement itself. Acceptance criteria are defined per requirement, the supplier records the evidence there, and the reviewer or verifier closes it. Questions about the evidence go in the requirement's comment thread.
Can we import the contract specification?
Yes. Requirements import from Excel, CSV and Word, and REX extracts a structured requirement list from a PDF specification, contract or standard.
What happens after contract award?
The same register carries on. Allocations are reviewed and agreed, evidence is recorded against each requirement, and compliance is reported by system through to acceptance, so there is one record from tender to handover.
Bring the chain into one project
Three months free, 500 requirements, unlimited users, no card. Invite a supplier on day one.
Get started free Book a demo