Scope Creep Detection

Omako automatically scans client feedback you log on the Revisions tab and flags anything that looks like it falls outside the agreed project scope.

How It Works

When you log a piece of client feedback, Omako checks the text against a list of scope-change keywords you configure in Settings → Workspace → SCR Keywords. Common examples: "add a new section", "we also need", "can you also build", "change the entire layout".

If a match is found, an SCR alert appears on the Revisions tab showing the matched keywords and the text excerpt that triggered the match.

You can customise the keyword list at any time. Keywords are workspace-level — they apply across all your projects.

Reading an SCR Alert

Each alert shows:

• Matched keywords — which words from your list appeared in the feedback
• Excerpt — the ~120-character passage from the feedback around the first match

Acting on an Alert

Dismiss

If you believe the request is within scope (or you've decided to absorb it), click Dismiss. The alert is marked as reviewed and moves out of the active view.

Draft SCR

If this is genuine scope creep, click Draft SCR. This opens the Scope Change Request editor pre-linked to this detection, so you can turn it into a formal request to send to the client for sign-off.

See Revisions & Feedback → Scope Change Requests for the full SCR flow.

Alert History

All SCR alerts — including dismissed ones — are kept in the project record. Even if you dismiss an alert, the original feedback text, the detection result, and your response are preserved. This gives you a paper trail if a billing conversation arises later.

INFO

Scope creep detection requires at least one keyword to be configured in Settings → Workspace → SCR Keywords. If your keyword list is empty, no alerts will be generated.