Fit-Gap Analysis

February 2026 · 18 min

What Is Fit-Gap Analysis?

Fit-gap analysis is the structured comparison of 'what the hospital needs' (requirements from BRD) against 'what the system can do' (Bio Ecko's standard features). The output is a comprehensive matrix that classifies every requirement as a Fit (system handles it as-is), Partial Fit (needs configuration or minor adjustment), or Gap (requires customization, workaround, or is out of scope). This exercise is the foundation of every implementation -- it determines project scope, timeline, cost, and risk.

Why it matters:

• Prevents scope creep by documenting what is and isn't included
• Gives the client transparency on system capabilities before go-live
• Creates a clear backlog for the development team
• Protects both vendor and client during disputes

When to Conduct Fit-Gap

Fit-gap analysis happens in the Blueprint phase (Phase 2), after requirements are gathered but before configuration begins.

Timeline:

1. Pre-fit-gap (Week 1-2) -- Complete BRD with signed-off requirements
2. Fit-gap workshops (Week 3-4) -- Module-by-module sessions with hospital SMEs
3. Analysis & scoring (Week 5) -- FC classifies and scores each item
4. Review & sign-off (Week 6) -- Present to steering committee, get approval on gap disposition

Typical effort:

The Fit-Gap Matrix Template

Every FC must use a standardized matrix. Here is the column structure:

Classification Rules

Consistent classification is critical. Different FCs rating the same feature differently creates confusion.

Fit (Green):

• Bio Ecko handles the requirement exactly as described or with minor configuration (toggle, setting, master data entry)
• No code changes needed
• Example: 'System must support male/female/other gender options' → Fit (dropdown already exists)

Partial Fit (Amber):

• The feature exists but doesn't fully meet the requirement
• Configuration or minor customization can bridge the gap
• Example: 'Auto-assign token numbers by department' → Partial Fit (tokens exist but are global, not per-department)

Gap (Red):

• The feature does not exist in Bio Ecko's standard product
• Requires development, third-party integration, or is genuinely out of scope
• Example: 'Integration with state government e-Hospital portal' → Gap (custom integration needed)

Severity ratings:

• Critical -- blocks go-live; hospital cannot operate without this
• Major -- significant impact on daily operations; workaround is painful
• Minor -- nice to have; workaround is acceptable
• Cosmetic -- visual/UI preference; no operational impact

Running a Fit-Gap Workshop

The workshop is where the FC demonstrates the system and the hospital SMEs validate against their requirements.

Workshop format:

1. Module introduction (5 min) -- FC briefly describes what Bio Ecko offers in this module
2. Requirement walkthrough (40 min) -- Go through BRD requirements one by one; FC demonstrates the feature live; SME confirms fit or flags gap
3. Gap deep-dive (10 min) -- For each gap, discuss severity, possible workaround, and disposition
4. Summary (5 min) -- Recap fits and gaps found

Facilitation rules:

• One module per session -- never mix OPD and Lab in the same session
• Right people in the room -- module owner + 1-2 power users from the hospital
• Live system demo -- don't describe features, show them
• Record the session -- video or audio for later reference
• Park scope discussions -- if someone says 'We also need X that isn't in the BRD', note it as a potential CR, don't fit-gap it now

Gap Disposition Strategies

Not every gap needs custom development. The FC's value lies in finding creative dispositions.

Golden rule: Always propose at least one disposition for every gap. Never present a gap without a recommendation.

Prioritization Matrix

With 50-200 gaps on a typical project, prioritization is essential. Use the MoSCoW method combined with effort scoring:

Plot gaps on a 2x2 matrix:

• X-axis: Effort (Low → High)
• Y-axis: Business Impact (Low → High)
• Top-left (High impact, Low effort): Do first -- quick wins
• Top-right (High impact, High effort): Plan carefully -- these define your project timeline
• Bottom-left (Low impact, Low effort): Do if time permits
• Bottom-right (Low impact, High effort): Defer or drop

Presenting Fit-Gap Results

The fit-gap summary is presented to the steering committee for sign-off. This is a critical milestone -- once signed, it becomes the project baseline.

Presentation structure:

1. Summary slide -- total requirements analyzed, % fit, % partial, % gap
2. Module-wise breakdown -- bar chart showing fit/partial/gap per module
3. Critical gaps -- each critical gap with recommended disposition and effort
4. Timeline impact -- how gaps affect the go-live date
5. Cost impact -- customization effort in person-days and estimated cost
6. Decision needed -- which gaps to approve for development vs defer

Key metrics to show:

Notes

Related topics