Spot Scope Creep in Recent Requests

Act as a project manager checking whether scope has been creeping without anyone noticing.

Approved scope statement or requirements baseline: {{SCOPE_BASELINE}}
Requests, tickets, emails and "small asks" from the last few weeks: {{RECENT_REQUESTS}}
Change requests approved so far: {{APPROVED_CHANGES}}

Do this:
1. Compare each request with the baseline and the approved changes. Classify it as in scope, a clarification of existing scope, out of scope (new work), or gold-plating (extras the team added that nobody asked for).
2. Show a table: request | who asked | date | classification | baseline reference or "none" | status (done, in progress or not started).
3. Highlight out-of-scope work already done or in progress without an approved change, because that is the real exposure.
4. Group the out-of-scope items into themes that reveal a pattern, such as one stakeholder or one area of the product.
5. Recommend how to handle each: raise a change request, bundle it into the next phase, decline politely, or accept it as a clarification.

Rules: base every classification on the baseline text and quote the line you relied on. If the baseline is too vague to judge, say "baseline unclear" and suggest tighter wording. Don't estimate effort; mark the items that need sizing.