What you receive
Examples of a requirements brief, screening, question register and decision pack. They are readable here; sensitive material is shared separately when needed.
Requirements brief
Purpose, role, geography, load definitions, stages, hard requirements, preferences and the next decision. A changed load type requires a fresh review of affected conclusions.
Screening
The buyer’s question, what the evidence can support, sources, open questions and the recommended next decision. The headline is not “feasible” after overview material alone.
Candidate comparison structure
This is a neutral HTML structure for the same questions in each candidate review. It contains no sites or results.
| Field | Example content | Control |
|---|---|---|
| Requirement | Buyer brief | Criterion kept constant |
| Observed | Fact or document | Source and date |
| Evidence state | Stated / reviewed / missing | Not a universal score |
| Next check | Question to resolve | Responsible role |
Question register
Each open question has a meaning, who can answer it, and whether it blocks the next decision. Unknown stays unknown.
Decision pack
The same defined questions for every candidate. End by progressing, changing the brief, looking further or stopping.
Process and responsibility matrix
For each work step, the evidence, responsible role, dependency on other tracks and decision supported by the step are visible.
Process and responsibility example
| Work step | Responsible role | Decision supported |
|---|---|---|
| Define the brief | Buyer + Powered Sites | Next decision |
| Review planning evidence | Agreed planning role | Planning question and dependency |
| Define the grid question | Powered Sites + right specialist | Next technical input |
| Document the handover | Agreed review role | Continue, complement or stop |
Open questions and risk register
Each question gets a meaning, status, owner and proposed action. A risk is written as a question to manage, not as an unsupported probability or score.
Risk register example
| Question | Why it matters | Responsible role | Next action |
|---|---|---|---|
| Land boundary | Scope is not yet evidenced | Buyer + property role | Confirm relevant evidence |
| Planning document stage | Legal effect is unclear | Planning role | Review the document |
| Grid question | Power position is not established | Coordination + grid specialist | Define the technical question |
Dossier and evidence index
A dossier example shows version, access class, reviewed attachments and remaining questions. It organises evidence but does not replace the source documents.
Dossier field structure
| Version | Illustrative version A |
|---|---|
| Access class | Public structure / controlled attachment |
| Evidence index | Source, date and review state |
| Open questions | Question, meaning, owner and next action |
