Gap Analysis
A gap is the difference between where the client is and where the framework says they should be. Gaps turn what we found in Diagnose into the recommended workstreams we act on.
Who can access
Members of the engagement team.
How gaps are produced
- An assessment produces per-dimension answers with confidence and citations.
- You accept the answers you trust.
- Celeredge surfaces the gaps from those findings.
- You review the gaps in Diagnose, where each gap comes with AI-suggested workstreams to close it.
Two kinds of "gap" you'll see
- Findings gaps — the substantive gaps between current and target state that drive planning.
- Evidence gaps — where a question had no supporting evidence. These aren't conclusions; they're a prompt to collect more evidence (often via an AI interview) and re-run. They show up as Not grounded with a no-evidence state.
Step by step
- Review and accept answers in Diagnose section 5.
- Review the resulting gaps in Diagnose.
- For each gap, review its AI-suggested workstreams.
- Accept workstreams — each carries a lineage link back to its gap — and carry the work into Deliver.
Best practices
- Close evidence gaps before committing. An evidence gap means you don't yet know — fill it, don't plan around a guess.
- Let lineage do the work. Because workstreams link back to gaps, you can always justify the plan.