Overview
Every implementation project has a Statement of Work, and every project has requirements that get created during discovery. At some point in the project, you need to compare the two — that's the only way to identify scope creep, which is by definition the gap between what was sold and what's being built.
Doing this manually is slow and error-prone, and most teams either skip it on smaller projects or only do it once at the end of a big one. SOW Checker compares your project's requirements against your SOW automatically and lets you re-run the comparison anytime requirements change.
Accessing SOW Checker
Navigate to your project
Click SOW Checker in the left navigation
Upload your signed SOW (PDF, DOCX, or DOC)
Once the SOW is processed, Glossa compares every requirement in the project against every line item in the SOW and presents the results.
Important: Don't upload your project SOW as an Input File for requirements generation. Upload it directly here in SOW Checker instead. The SOW is the contract you're comparing requirements against — it's not a source of new requirements.
The SOW Checker Interface
At the top of the page, you'll see:
The active SOW with version, file size, upload date, and a Preview link
A summary bar showing counts for Unmatched SOW Line Items, Unmatched Requirements, Matched Requirements, and Resolved
Replace SOW to upload a new version, and Re-run Comparison to refresh the results against the current set of requirements
Below the summary bar, filter tabs let you view items by status: Unmatched SOW Line Items, Unmatched Requirements, Matched Requirements, Resolved, and All.
Each row shows the relevant content (SOW line item, requirement, or matched pair) with action buttons specific to that status.
Match Statuses
Matched Requirements
Glossa has paired a requirement with a SOW line item. Each match shows the SOW line item on the left, the matched requirement on the right with a confidence percentage, and an AI reasoning explanation below describing why the two correspond.
Actions available:
Confirm Match — The match is correct. The pair moves to Resolved.
Reject Match — The match is wrong. The requirement returns to Unmatched Requirements and the SOW line item returns to Unmatched SOW Line Items.
Unmatched Requirements
A requirement exists in your project but has no corresponding line item in the SOW. This is the most common indicator of scope creep — work that emerged from discovery but isn't backed by what the client signed for.
Actions available:
Manually Match — You know this requirement is covered somewhere in the SOW even though Glossa didn't detect it. Search for and select the correct SOW line item.
Flag for Client — Surface this requirement for a scope conversation with the client. Use this when something needs to be discussed before delivery proceeds. When you choose this option, the Status of the requirement is changed to Flagged.
Ignore — The requirement doesn't correspond to anything in the SOW, but you're not worried about it. The requirement moves to Resolved, and the status on the requirement is unchanged.
Unmatched SOW Line Items
A line item in the SOW has no corresponding requirement in the project. This usually means a contractual commitment hasn't yet been captured in discovery.
Actions available:
Create Requirement — Generate a new draft requirement in the project directly from the SOW line item. The requirement is created and the pair moves to Resolved.
Manually Match — You know this SOW line item is already covered by an existing requirement. Search for and select the correct requirement.
Dismiss — The line item is boilerplate (legal language, payment terms, etc.) that doesn't need to be tracked as a requirement.
Resolved
Every decision you've made in SOW Checker is logged here. Each resolved row shows the action that was taken (e.g., "Matched Record → Confirmed," "Unmatched Requirement → Ignored").
You can click Un-resolve on any item to return it to its previous state and reconsider the decision.
The Resolved tab serves as an audit trail for all SOW Checker decisions in the project.
Recommended Workflow
When to Use SOW Checker
Run SOW Checker as soon as you have a meaningful set of requirements captured from discovery, and re-run it any time the requirements list (or SOW) changes substantively. The whole point of automating this comparison is that you can do it as often as you need to — not just once at the end of the project.
Common triggers to re-run:
A significant change has been made to the SOW (in which case, use Replace SOW to upload the new version)
You're approaching a project milestone or phase gate
Suggested Review Order
Matched Requirements first — Quickly scan the auto-matches and confirm the ones that look right. This grounds you in what's already covered.
Unmatched Requirements next — This is where the highest-value scope conversations happen. Decide whether each item should be flagged for the client, manually matched to an existing SOW line item, or ignored.
Unmatched SOW Line Items last — Catch anything in the contract that hasn't been turned into a requirement. Create requirements directly from these items, or dismiss boilerplate.
Tips
Run it often. The value of SOW Checker compounds the earlier and more frequently you use it. Catching a scope conversation in week two is much easier than catching it in week ten.
Use Flag for Client deliberately. Flagging is a signal that a real conversation needs to happen — not a way to defer a decision indefinitely. Pair flags with actual outreach to the client.
Read the AI reasoning on matches. The reasoning explanation tells you exactly why Glossa matched two items. This context helps you make faster, more confident decisions on Confirm vs. Reject.
Troubleshooting
Most of my requirements are unmatched
This is normal early in a project, especially if your discovery has surfaced significantly more scope than what was originally sold. Work through the Unmatched Requirements tab and decide which items need to be flagged for the client.
If the volume seems unusually high, double-check that you've uploaded the correct version of the SOW and that it includes the full scope of work (not just the cover page or executive summary).
A match looks wrong
Click Reject Match. The requirement will move back to Unmatched Requirements and the SOW line item will move back to Unmatched SOW Line Items, where you can take the correct action.
I want to redo a Resolved item
Click Un-resolve on the row. The item returns to its previous status and is ready to be acted on again.
SOW Checker isn't showing any results
Make sure both the SOW has been uploaded and processed (status: Ready) and that requirements have been generated in the project. SOW Checker compares the two — if either is empty, there's nothing to compare. If your SOW is stuck processing, try Replace SOW with the same file or contact support.
I uploaded the wrong SOW
Click Replace SOW at the top right and upload the correct version. The comparison will re-run automatically against the new SOW.