Skip to main content

Gap Analysis

A gap is the difference between where the client is and where the framework says they should be. Gaps are the bridge from Diagnose (what we found) to Plan (what we'll do about it).

Who can access​

Members of the engagement team.

How gaps are produced​

  1. An assessment produces per-dimension answers with confidence and citations.
  2. You accept the answers you trust.
  3. Celeredge surfaces the gaps from those findings.
  4. You send gaps to Plan, 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​

  1. Review and accept answers in Diagnose section 5.
  2. Send gaps to Plan.
  3. In Plan, review each gap's AI-suggested workstreams.
  4. Accept workstreams to commit them to Execute — each carries a lineage link back to its gap.

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.