What the walkthrough tells us
The operator repeatedly combines overlapping inputs, resolves contradictions by judgement, requests client confirmation, moves approved outputs into another specialist project and re-runs gap analysis after remediation. A single giant prompt would preserve none of the necessary authority or stage control.
The eight-stage process
- 1Intake and backstory
Collect entity history, client-portal answers, resumes, qualifications, categories, services, people, evidence, constraints and unresolved questions.
- 2Organisation design
Infer a plausible board and responsible-person structure, allocate service-delivery roles, test workload concentration, then send the proposal to the client.
- 3Source-document construction
Combine the approved organisation chart with Q&A, business information, financial inputs and service selections to produce business, financial, workforce and recruitment plans.
- 4Client confirmation
Separate minor defects Harrison can fix from financial assumptions, role decisions or missing evidence that require the client. Approval controls the next stage.
- 5Policy-pack construction
Select the correct master-pack edition and registration categories; rebrand and populate without leaking residential or otherwise inapplicable material.
- 6Application assembly
Combine approved governance, plans, policy pack, evidence and client answers into the exact current base and category-specific forms.
- 7Gap analysis and remediation
Upload the assembled case to the review lane, classify unsupported or contradictory content, route client blockers and rerun validation after repairs.
- 8Review, declaration and lifecycle
Prepare client review and clean final sets, record approval, operate submission externally, then preserve receipts, Commission requests, audits and outcome.
The information model already implicit in the video
| Object | Examples | Required control |
|---|---|---|
| Case | Entity, categories, status, backstory | Stable ID, tenant boundary, exact form version |
| Person | Role, CV, qualifications, screening | Per-person evidence, restricted PII, approval |
| Claim | Answer to an application question | Evidence, requirement, confidence, review status |
| Gap | Missing, expired or contradictory item | Severity, owner, route and next action |
| Artifact | Org chart, plan, policy, form | Inputs, version, approvals, supersession |
| Decision | Role allocation or conflict resolution | Actor, rationale, timestamp and immutable event |
Where the current process breaks
Project-to-project copying
State is repeatedly uploaded, paraphrased and potentially lost.
Competing sources of truth
Organisation charts, portal answers, models and forms can diverge after revisions.
Reasonable guesses look final
Material inferred facts need proposed status and explicit confirmation.
Category leakage
The 331-row register crosses categories; the wrong tier creates misleading content.
Prompt and regulatory drift
Separate projects and static guides can silently disagree with the current form.
PII crosses AI systems
Identity, screening, qualification, address and financial data require strict tenancy and retention controls.