AI-drafted content to close assessment gaps — grounded in your documents, traced to the source.
Assessment tells you what is missing. But knowing the gap exists does not close it.
You run an assessment against IPA gateway criteria, Green Book requirements, or your organisation's own framework. The platform finds 14 RED and AMBER findings. Each one is specific: "No sensitivity analysis found." "Escalation procedures not defined." "Benefits not quantified."
Now what?
Today, you write the missing content from scratch. You open a blank document, look up the expected format, dig through your business case for the relevant figures, and spend two or three hours producing a sensitivity analysis table that should have been in the Financial Case from the start. Multiply that across 14 findings and you are looking at a week of remediation work before the next gateway.
Generate Content produces an 80% complete first draft in minutes. It assembles context from the criterion definition, the evidence requirements, and the data already in your uploaded documents. You get a structured draft with real figures pulled from your business case, citations back to source pages, and clear markers where you need to add information the AI could not find.
You review it, fill in the gaps, and download as Word. The platform already knows what good looks like for each criterion. Generate Content uses that knowledge to write the first draft so you can focus on the 20% that requires human judgement.
Five steps from assessment finding to downloadable first draft.
Not every gap can be addressed with generated content. The system knows the difference.
The key distinction: can the AI produce the structure and populate it with data from your documents, or does it need information that only you possess? Each criterion in the assessment framework has a suitability rating that determines whether the Generate Content button appears and what kind of output you get.
| Tier | Definition | Examples | What You Get |
|---|---|---|---|
| HIGH | Structure is known and data can be extracted from your uploaded documents. The AI produces a populated draft. | Sensitivity analysis tables, escalation procedures, RACI matrices, benefits quantification tables, risk escalation triggers, evidence requirement checklists | 70–90% complete draft with real figures, citations, and source references. You review and refine. |
| MEDIUM | Structure is known but significant data requires human judgement or input the AI cannot infer. | Stakeholder engagement plans, risk appetite statements, change control procedures, lessons learned summaries, benefits realisation plans | Structured template with standard content pre-filled and [ACTION REQUIRED] placeholders where you need to add information. |
| LOW / EXCLUDED | Gap is about missing raw data, decisions not yet made, or content requiring original research. Generating a template would be misleading. | Cost breakdown structures, environmental impact data, financial model outputs (NPV, BCR, IRR), technical specifications | The Generate button does not appear. These gaps require human work that AI cannot shortcut. |
A Green Book business case is assessed. The sensitivity analysis is missing. Here is what Generate Content produces.
The AI assembles context from the Financial Case (capital costs, operating costs, discount rate), Economic Case (benefit estimates, BCR), and HMT Green Book sensitivity analysis template. The generated output:
| Variable | Base Case | OB Adjustment | Source |
|---|---|---|---|
| Capital costs | £340M | +24% (standard infrastructure) | [Source: FBC p.23] |
| Operating costs | £12M/year | +15% (non-novel operations) | [Source: FBC p.31] |
| Demand forecast | [ACTION REQUIRED: Insert base case demand] | [ACTION REQUIRED: Apply OB uplift] | Not found in documents |
| Benefit values | £714M PV (30 years) | -10% to -30% range test | [Source: Economic Appraisal p.18] |
| Discount rate | 3.5% real | Test at 1.5% and 5.0% | [Source: FBC p.24] |
| Variable | Switching Value | Headroom | Confidence |
|---|---|---|---|
| Capital costs | +110% (to £714M) | £374M headroom | HIGH |
| Benefit values | -52% (to £343M PV) | £371M headroom | HIGH |
| Discount rate | [ACTION REQUIRED: Requires full cashflow profile] | — | LOW |
| Scenario | Capital Cost | Benefits | BCR | VfM Rating |
|---|---|---|---|---|
| Base case | £340M | £714M | 2.1 | High |
| Optimistic | £274M (-20%) | £857M (+20%) | 3.1 | High |
| Central with OB | £422M (+24%) | £714M | 1.7 | Medium |
| Pessimistic | £442M (+30%) | £500M (-30%) | 1.1 | Low |
| Worst case | £510M (+50%) | £429M (-40%) | 0.84 | Poor — does not represent VfM |
Sources: Business Case v2.1 (pp. 23, 24, 31), Economic Appraisal (p. 18). OB adjustments from HMT Supplementary Green Book Guidance on Optimism Bias (2022). Confidence: Medium (demand forecast data not found).
A governance framework gap triggers a generated escalation procedure grounded in the project's terms of reference.
The AI draws on the Terms of Reference (governance roles), the Risk Management Strategy (tolerance references), and the project value (£340M) to produce a structured procedure:
| Level | Escalated To | Authority | Response Time |
|---|---|---|---|
| 1 — Project | Programme Director [Source: ToR p.4] | Corrective action within delegated authority | 5 working days |
| 2 — Programme Board | Project Board (Chair: SRO) [Source: ToR p.2] | Budget changes up to [ACTION REQUIRED: Insert limit] | Next board or 10 days (emergency) |
| 3 — Sponsoring Body | [ACTION REQUIRED: Insert sponsor] | Scope changes, budget increases beyond delegated authority | 15 working days |
| 4 — Portfolio / Minister | [ACTION REQUIRED: Insert authority] | Reset or closure decisions | As required |
| Category | Amber Trigger (Level 1–2) | Red Trigger (Level 3–4) |
|---|---|---|
| Cost | Forecast outturn exceeds budget by >5% | Forecast outturn exceeds budget by >10% |
| Schedule | Critical path slippage >4 weeks | Key delivery date at risk or slippage >8 weeks |
| Benefits | Realisation <90% of forecast at review | Realisation <75% or strategic benefit unachievable |
| Risk | New residual rating ≥16 (4×4 matrix) | Risk materialised, impact exceeds contingency |
| Quality | Deliverable rejected at quality gate | Repeated failures indicating systemic capability gap |
Each exception report must include: (1) Exception description, (2) Impact on cost, schedule, benefits, risk, (3) Minimum 3 options including "do nothing", (4) Recommendation with rationale, (5) Specific decision required.
Sources: Terms of Reference (pp. 2, 4), Risk Management Strategy. Confidence: Medium (financial thresholds not specified in source documents — review all triggers against programme risk appetite).
Four of six benefits are not monetised. Generate Content produces a structured table mixing extracted data with clear placeholders.
| # | Benefit | Value (PV) | Methodology | Confidence |
|---|---|---|---|---|
| B1 | Reduced journey times | £412M [Source: Econ. Appraisal p.12] | DfT WebTAG values of time × forecast demand | MED |
| B2 | Construction employment | £302M [Source: Econ. Appraisal p.15] | ONS multiplier applied to construction spend | MED |
| B3 | Improved air quality | [ACTION REQUIRED] | Recommend: DEFRA air quality damage costs (2024 values) | — |
| B4 | Reduced carbon emissions | [ACTION REQUIRED] | Recommend: BEIS traded/non-traded carbon values | — |
| B5 | Community connectivity | Non-monetised | [ACTION REQUIRED: Justify per Green Book para 5.14] | LOW |
| B6 | Skills development | Non-monetised | [ACTION REQUIRED: Consider lifetime earnings uplift] | LOW |
Totals: Monetised: £714M PV (B1 + B2) [Source: Econ. Appraisal p.18]. To be monetised: B3, B4. Non-monetised (justify): B5, B6.
Sources: Economic Appraisal (pp. 12, 15, 18), Strategic Case benefit descriptions. Confidence: Medium.
Notice the pattern: cells with extracted data carry teal citations. Cells requiring your input carry red ACTION REQUIRED markers. The methodology column recommends the appropriate HMT valuation approach even where the value itself must come from you.
Every piece of generated content tells you how much it trusts its own output. Here is how to read the signals.
Each generated section carries an overall confidence rating based on how much source data was available and how reliably it could be extracted.
Data was found in your documents and verified across multiple sources. Figures are directly extracted, not inferred. The structure matches the framework template exactly.
Your action: Verify the figures match your latest version of the source document. Spot-check two or three citations.
Data was found but not independently verified across documents. Some values are extracted from a single source. The structure is correct but some cells rely on a single reference.
Your action: Check each cited value against the source. Confirm the context has not changed since the document was written.
Values are inferred rather than explicitly stated in your documents. The AI has made a reasonable interpretation but it may not reflect your intent.
Your action: Treat these values as suggestions. Replace with verified data before using in any formal submission.
Even within a High-confidence section, individual values can carry uncertainty. These are highlighted in yellow in the generated output. A yellow highlight means the AI found something relevant but is not certain it extracted the right figure.
Common causes of yellow highlights:
Every generation is fully traceable. If content is questioned during an audit, the full chain is reconstructable.
Programme documentation goes through gateway reviews, NAO scrutiny, and public accountability processes. AI-generated content in this context requires a complete audit trail. Programme Insights records every step of the generation process.
| Element | What Is Captured |
|---|---|
| Trigger | Which finding triggered the generation, the criterion code, the RAG rating, and the assessment run ID |
| Context assembled | The exact document chunks retrieved, their source documents and page numbers, the search queries used to find them, and the total token count |
| Prompt sent | The full system prompt including criterion definition, evidence requirements, framework template, and all retrieved context — the complete input to the AI |
| Model version | The specific AI model and version used, with a timestamp of the generation |
| Raw output | The unedited AI output exactly as generated, before any user modifications |
| User's final version | If the user edits and saves the content, the final version is stored alongside the original, with a diff showing what was changed |
If a reviewer or auditor asks "where did this sensitivity analysis come from?", the answer is fully documented:
This is not an afterthought. The provenance system is designed for environments where generated content may be scrutinised by the IPA, the NAO, or a parliamentary committee.
Generated content improves over time because the system learns from your edits.
When you edit a generated draft and save it, the platform captures the difference between the AI's version and yours. This is not abstract machine learning — it is a concrete record of what you changed and why:
If your organisation consistently changes "5 working days" to "3 working days" for Level 1 escalation response times, future generations for your projects will default to 3 working days. If you always add a "Dependencies" column to RACI matrices, future RACI generations will include it.
The learning is scoped to your organisation. Your edits improve your future generations. They do not affect other users.
From assessment findings to first draft in seven steps.
Contact us at support@programmeinsights.co.uk or visit programmeinsights.co.uk/help for documentation, walkthroughs, and framework guidance.
User Guide — Full platform walkthrough
Assessment Guide — Running and interpreting assessments
Custom Criteria Guide — Building your own framework