Why This Matters
Scope creep is, by definition, the gap between what was sold in the SOW and what's actually being built based on requirements. On every project, that gap exists — discovery surfaces things the SOW didn't anticipate, and delivery teams add scope as they get closer to the client's real needs. The question isn't whether scope will drift. It's whether you'll catch it early enough to do something about it.
SOW Checker exists to make that comparison fast, repeatable, and routine. The best teams aren't the ones who avoid scope changes — they're the ones who see them coming and have the conversation early, while everyone still has options.
Decide Who Owns the Review
SOW Checker is most effective when one person on the project is clearly accountable for running it and acting on the results. Without an owner, it tends to get skipped — same as the manual comparison process it's replacing.
In most engagements, this is the project manager or engagement lead. On smaller projects, it might be the lead BA. The exact role matters less than the clarity: someone owns it, and they own it for the duration of the project.
Use "Flag for Client" as a Signal, Not a Filing Cabinet
Flagging an unmatched requirement for the client is meaningful only if the conversation actually happens. When you flag something, think about:
A specific person on the client side who needs to weigh in
A target date for the conversation
A clear decision: in scope, out of scope, or change order
If a flag has been sitting for more than a week or two, that's a sign to escalate — either the conversation isn't happening, or the requirement isn't actually as material as the flag suggested.
Don't Let "Ignore" Become "Absorb"
Ignoring an unmatched requirement is a legitimate option — sometimes a requirement really is valid and not in the SOW. But ignoring should be a deliberate decision, not a way to avoid a hard conversation.
Before clicking Ignore, ask:
Should this be a change order?
Does the client know this isn't in the SOW?
If the answer to either of those is yes, the right action is Flag for Client — not Ignore. Otherwise you're committing to delivering scope that isn't in the contract, which is the exact problem SOW Checker exists to surface.
Treat Unmatched SOW Line Items as a Discovery Gap
When SOW Checker flags a line item from the SOW that has no corresponding requirement, it usually means one of three things:
Discovery missed it. The team didn't ask the right questions, or the right stakeholder wasn't in the room. Use Create Requirement to generate the draft requirement and continue discovery on that area.
It's already covered, but Glossa didn't catch the match. Use Manually Match to pair it with the existing requirement.
It's boilerplate. Legal language, payment terms, or standard contract clauses that don't translate into deliverable requirements. Use Dismiss.
If you're seeing a high volume of unmatched SOW line items, it's worth pausing to ask whether discovery has actually covered the full scope of work, or whether there are areas the team hasn't dug into yet.
Use the Audit Trail
Every action you take in SOW Checker is logged in the Resolved tab. This isn't just for your records — it's a defensible record of how scope decisions were made on the project.
When a question comes up months later about why something was or wasn't built, the Resolved tab tells the story: what was matched, what was flagged, what was ignored, and when each decision was made. This is especially valuable on long engagements where the team turns over, or in client relationships where scope disputes are likely.
Pair SOW Checker with Client Portal
For requirements you flag for the client, the Client Portal gives you a structured way to surface them for review and approval. The combination is powerful: SOW Checker tells you what needs a conversation, and Client Portal facilitates the conversation itself.
This is how you turn scope creep from a defensive end-of-project problem into a collaborative early-project workflow.
Common Pitfalls
Running SOW Checker once and forgetting about it. The value compounds with frequency.
Confusing "matched" with "delivered." A matched requirement means the requirement aligns with the SOW. It doesn't mean the work is done. SOW Checker is a scope tool, not a delivery tracker.
Skipping the AI reasoning on matches. The reasoning explanation tells you exactly why two items were matched. Reading it takes seconds and makes the difference between confidently confirming a match and rubber-stamping something that's actually wrong.
Treating Flag for Client as the destination. Flagging is the start of a conversation, not the end of one. If you're not also driving the conversation, the flag isn't doing anything for you.