Live delivery change control
Assess incoming requests against the signed scope in minutes so decisions are not deferred to the next steering meeting.
— Operations & Process
Assesses a change request against the current SOW, quantifies scope, cost, timeline and risk deltas, scores materiality, and produces the matching assessment or approval note.
2–3 days → ~15 minutes
For one complete, review-ready pass
No coding required
— USE CASES
Assess incoming requests against the signed scope in minutes so decisions are not deferred to the next steering meeting.
Quantify cost and timeline deltas before agreeing to something that quietly erodes the fee.
Produce the same approval wording and rationale every time, ready for the client's governance process.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Each process step is assessed against criteria you control and weight, so the same standard applies to every process step in the end-to-end process.
Thin cases and strong cases among your process steps are handled differently by design, based on what the analysis actually found.
Findings on the end-to-end process are written up as a document that reads like professional output, with each claim tied back to a process step.
Not every change request deserves a formal impact assessment, but deciding which do is where scope creep hides. In practice it shows up as live delivery change control: assess incoming requests against the signed scope in minutes so decisions are not deferred to the next steering meeting. The value sits in the rigour, not the typing — yet the rigour is exactly what gets traded away when there is only 2–3 days of capacity for it.
Here the same job runs as a Skill. Your material goes in; scope, cost, timeline and risk deltas made explicit comes out, alongside a materiality score that decides the depth of assessment. What sits between input and output is the codified method: thresholds, sequencing and the points where a human confirms a call — all of it visible and editable in the Skill. Net effect: 2–3 days down to ~15 minutes, no drift between runs, and every conclusion traceable back to the evidence behind it.
Change-request impact assessment exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Identifies where adoption of a new system, process or way of working stalls after go-live, with an evidence-backed report on barriers, workarounds and differences between functions.
Assesses AI readiness through anonymous staff evidence, identifying where AI can improve day-to-day work and the practical barriers that could prevent those gains.
Maps how an organisation actually operates using anonymous accounts from its people, producing an evidence-backed diagnostic of responsibilities, decisions, handoffs and duplicated effort.
Reads a set of weekly status notes for progress, blockers and RAG, charts the trend, and writes an executive digest focused on trajectory.
Reviews a proposed change against your change policy and returns a governed advisory decision — approve, approve with conditions, defer to the change board or reject — weighing risk, blast radius and rollback, with a change manager sign-off required before anything reaches production.
Assesses a refund or compensation request against the contract terms and refund policy that govern it, then returns a decision on approving it in full, in part, offering a goodwill gesture or declining, with every element of the remedy traced to the clause that allows it and anything beyond an agent's authority routed for review.