Scope-Creep Detector: Catch Out-of-Baseline Work Before It Eats Your Project

The problem this kills

A project starts with a clean, signed-off scope. Then the drift begins. A stakeholder asks for "just one small thing" in a hallway. A developer adds a sub-task that quietly expands a deliverable. A new line item appears on the board that nobody can trace back to a decision. None of it goes through change control, none of it gets re-estimated, and none of it moves the deadline — until the project is suddenly weeks over and everyone is asking how it happened.

Scope creep is rarely one big betrayal. It's a hundred unapproved additions that each looked harmless. The maddening part is that it's completely catchable: you have a baseline that everyone agreed to, you have the current list of work, and you have a log of the changes that were approved. The only thing missing is something that compares the three and asks the obvious question — "this item is in the work but it's not in the baseline and there's no approved change request for it, so who said yes?" You do not need to be a developer to build that something.

What you'll build

A simple internal web tool for PMs, BAs, and PMO leads. You import three files: your scope baseline (the signed-off list of in-scope items), your current work list (tasks/deliverables as they stand today), and your approved change-request log (the changes that legitimately got the green light). The tool diffs them — matching items by ID and by fuzzy title so a renamed item doesn't slip through — and flags every current item that is not in the baseline and is not backed by an approved CR. Each flag explains why it's out of baseline. Your PM reviews each flagged item and chooses a disposition: raise a CR, remove it, or accept with a note. Only after the PM decides does the tool update the scope record and export a clean updated baseline CSV plus a scope-creep report CSV for your steering committee.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how your projects actually track scope, the tools you use (Jira, Azure DevOps, Asana, Smartsheet, or a spreadsheet), the exact IDs and naming your items use, your typical and peak item counts, and your real rule for what counts as an approved change. It reads a short spec back to you for a thumbs-up, then builds the tool around your answers instead of a generic template. From there it walks the agent through the data model, the three CSV imports, the diff-and-match engine (ID plus fuzzy title), the review-and-disposition screen, the human approval gate, and the updated-baseline and creep-report exports. Every step ends with a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a real PMO needs: login so only your team can use it, row-level security so people only see their own organization's projects, a complete audit trail of every disposition and override (who, what, when, and why), a hard human-approval gate so the scope record is never updated until a person decides every flag, and duplicate guards so the same import can't be processed twice and the same item can't be counted twice. The whole tool exists to make a careful human decision easy — the AI raises the creep, a person makes the call.

Who it's for

Project managers, business analysts, PMO governance leads, and account managers who own scope and are tired of discovering creep at the post-mortem. If you can describe what "in scope" and "an approved change" mean in your world, you can build this.

You've got this — open the plan, paste the first prompt, and you'll be catching your first real scope creep this afternoon.