Overview
After you generate requirements in a project, Glossa automatically compares each requirement against your organization's Library. Capability Review is where you verify these matches, handle ambiguous cases, and decide what to do with requirements that don't match anything in the Library.
This is a key step in understanding what's "standard" about a project versus what's new or custom — which directly impacts scoping, estimation, and delivery planning.
Accessing Capability Review
Navigate to your project
Go to the Dashboard
Click Capability Review
The Capability Review Interface
At the top of the page, you'll see:
A summary bar showing total Requirements, Pending (awaiting action), and Matched counts
Status definitions explaining the four match types
Filter tabs to view requirements by status: Needs Review, Unmatched, High Match, Resolved, and All
Each requirement is shown as an expandable row. Click to expand and see the side-by-side comparison: the Library Definition (or suggested match) on the left, and the Discovery Requirement on the right. At the bottom of each expanded row, Glossa provides an AI explanation of why this match was suggested (or why it wasn't matched), plus action buttons.
Match Statuses
High Match (green)
Glossa automatically matched this requirement to a library capability with high confidence (typically 90%+). The match is shown side-by-side: the library capability's description, scope items, assumptions, and complexity drivers on the left, and your discovery requirement on the right.
What to do: Review the match. If it looks correct, no action is needed — it's already matched. If the match is wrong, click Unmatch to remove it and move the requirement to Unmatched.
Needs Review (amber)
Glossa found a potential match but isn't confident enough to auto-match (typically 70–89% confidence). The suggested library capability is shown on the left with a confidence percentage.
Actions available:
Skip — The requirement is valid but represents scope unique to this project, not something that belongs in the Library. The requirement stays in the project but is not associated with any library category. It will not appear in the project's Categories tab; it will appear in the Resolved tab of the Capability Review.
Create New Capability — This requirement represents something not yet in the Library. Glossa proposes a new capability entry from this requirement, which you can edit before saving to the Library. You can review the proposed entry and click Save to Library, Edit, or Discard.
Update Library Capability — The match is close, but the library capability needs updating to fully cover what this requirement describes. Glossa proposes specific changes: an updated description, new scope items, and/or new assumptions to add to the existing library capability. You can review the proposed changes and click Apply Changes, Edit, or Discard.
Adjust Requirement — The library capability is correct, but the requirement is too broad or includes scope outside the capability's boundaries. Glossa proposes an updated version of the requirement that aligns with the library capability, showing the current and proposed text side-by-side. You can click Apply Changes or Discard.
Unmatched (blue)
No matching capability exists in the Library for this requirement.
Actions available:
Cancel Requirement — The requirement isn't needed. The requirement's status is updated to Canceled.
Keep as Project-Specific — The requirement is valid but represents scope unique to this project, not something that belongs in the Library. The requirement stays in the project but is not associated with any library category. It will not appear in the project's Categories tab; it will appear in the Resolved tab of the Capability Review.
Manually Match — You know this matches an existing library capability even though Glossa didn't detect it. Search for and select the correct capability.
Add to Library — This requirement represents a new capability that should exist in the Library for future projects. Glossa generates a proposed library entry with a name, description, scope items, assumptions, and complexity drivers based on the requirement. You can review and click Save to Library, Edit, or Discard.
Resolved (green)
You've already taken action on this requirement. Each resolved row shows what action was taken (e.g., "Action taken: Adjusted requirement," "Action taken: Kept as project-specific").
The Resolved tab serves as an audit trail for all Capability Review decisions in the project.
What Happens After Matching
When a requirement is matched to a library capability (whether through High Match, Needs Review resolution, or Manual Match):
The capability's parent category appears in the project's Categories tab
Clicking on the category in the project shows: associated requirements, Score Insights, and the library capability details (scope items, assumptions, complexity drivers)
The Library's "Projects Using" count and "Referencing Requirements" count are updated
Recommended Workflow
When to Use Capability Review
Check Capability Review after your first batch of requirements is generated from uploaded files. You don't need to wait until all files are uploaded — you can review in batches and come back as more requirements are generated.
Suggested Review Order
High Match tab first — Quickly scan auto-matches to catch any obvious errors. Most should be correct; just unmatch any mistakes.
Needs Review tab — These need your judgment. Read the AI explanation and decide whether to adjust the requirement, update the library, create something new, or skip for now.
Unmatched tab — Decide whether each unmatched requirement is project-specific scope, something that should be added to the Library, or something that should be manually matched to an existing capability.
Tips
Don't rush Unmatched items. If you're early in building your Library, many requirements will be unmatched simply because the Library isn't populated yet. Use "Add to Library" generously in your first few projects to build up the Library.
Use "Update Library Capability" to enrich over time. If a Needs Review match is close but the library entry is incomplete, updating it makes the Library better for future projects.
"Keep as Project-Specific" is perfectly fine. Not every requirement belongs in the Library. One-off client customizations, unique integrations, or highly specific business logic are often project-specific.
Review the AI explanation. The yellow/green explanation bar at the bottom of each match tells you exactly why Glossa matched (or didn't match) a requirement. This context helps you make faster, better decisions.
How Capability Review Relates to the Library
Capability Review is a two-way street:
Library → Project: Your Library provides the canonical capabilities that requirements are matched against.
Project → Library: Through "Add to Library" and "Update Library Capability" actions, each project's Capability Review enriches and grows the Library.
Over time, this feedback loop means the Library becomes more comprehensive and matches become more accurate.
Troubleshooting
Most of my requirements are Unmatched
This is expected if your Library is new or has few entries. Import more historical SOWs to build up the Library, or use "Add to Library" during Capability Review to create entries from your current project's requirements.
A High Match looks wrong
Click Unmatch to remove the automatic match. The requirement will move to Unmatched, where you can take the correct action.
I want to redo a Resolved item
Currently, resolved items cannot be undone from the Capability Review interface. If you need to change a match, you can update the requirement's category assignment from the Requirements tab, or edit the library capability directly from the Library.
Capability Review isn't showing any requirements
Make sure requirements have been generated from uploaded files. Capability Review compares requirements against the Library — if there are no requirements yet, there's nothing to review.