Demo on fictional data
RFP requirements to a compliance matrix
This is a demo on fictional data that shows the requirements in a short RFP pulled out into a compliance matrix, with every row marked Unknown until a person sets its status, owner and evidence.
Requests since you opened this page: 0
Works offline: not installed
The browser policy on this page forbids network requests (connect-src 'none'). The count is here so you can see it hold. How the demos work.
The RFP
A short made-up request for proposals from Sample Coast Credit Union (fictional). The extractor is a keyword rule: it keeps sentences containing "shall", "must" or "required to", and nothing else.
Compliance matrix
Every row starts as Unknown. A person sets the status, names an owner and points to the evidence. Nothing is marked compliant by software.
| ID | Section | Requirement | Status | Owner | Evidence |
|---|
What this shows, and what it does not
What this shows
- Sentences with shall, must or required to become numbered rows with their section.
- Unknown is the default status, so nothing is marked compliant by accident.
- The matrix exports as CSV for your own tracker.
What it does not show
- The extractor is a keyword rule, not a model. It misses requirements phrased another way.
- No status on this page was decided by software.
- The RFP and the credit union are made up.
How it would run for you
This is the shape of a Architecture Sprint: the agent drafts, a named person approves, the log stays with you.
Answers the question on the AZ or RFPs tile in the Fridays campaign.
Related services: Architecture Sprint, Production Readiness Review.