Assign the role responsible for final decision and evidence across the development lifecycle. Contributors support; accountability remains visible.
Role framework - not appointment. Selecting a role does not appoint a person, define contractual liability or replace project-specific professional scopes.
It is a planning framework covering 32 critical deliverables with suggested accountability and contributors. It is not legal, engineering, safety, financial or project-management certification.
No. It helps structure ownership and questions. Qualified professionals remain responsible for defining, verifying and signing their work.
No. They are starting prompts. The actual site, contracts, design, procurement, community, environment and operations require project-specific risks.
No. Scores reflect user selections and can never replace investigation, evidence, controls, monitoring or professional judgement.
Yes, but one accountable role should normally own the final decision and evidence while contributors support it.
They stay in local storage in this browser unless the user deliberately copies a summary or submits an enquiry.
The tools do not ask for personal contact data. Contact details are only entered in the separate enquiry form when the user chooses.
Review it at every decision gate and whenever land, design, cost, contract, programme, approval, operator or opening assumptions change.
The project should define authority, evidence requirements and review frequency. A browser selection alone is not formal project approval.
It identifies the single role expected to own the decision and final evidence, not necessarily the person performing every task.
Yes, after adapting the risks and deliverables to live operations, asset condition, current contracts and actual performance evidence.
The enquiry provides context for a human scope discussion. It creates no appointment, approval, quotation, contract or payment.