Freelance Scope Guard

The Problem

Clients often assume new features or extra revision rounds are included in the original price. Without a clear audit trail, freelancers lose money on unbilled hours and miss deadlines due to uncontrolled scope creep.

What It Does Analyzes contracts, SOWs, and Slack logs to distinguish between original deliverables and new requests. Identifies unapproved work that lacks formal written authorization. Quantifies commercial impact by calculating additional fees and timeline delays based on project evidence. Generates structured Change Requests and professional email drafts to handle scope discussions without damaging relationships. Calculates a Scope Risk Score to flag projects prone to budget or schedule overruns. Why This Beats Prompting It Yourself

General LLMs tend to be too agreeable, often missing subtle scope expansions or hallucinating client approvals. This skill enforces strict evidence integrity, requiring high-confidence documentation before classifying work as approved, helping you protect your commercial position.

Use Cases Reviewing a "quick" client email request against a signed Master Services Agreement. Generating formal Change Orders for mid-project feature requests. Auditing a project at risk of overrunning its budget due to excessive revision rounds. Drafting firm but professional responses to push back on out-of-scope tasks. Known Limitations

Requires uploaded documentation such as an SOW, contract, or client messages to function effectively. It cannot invent project terms, approvals, or pricing when they are not present in the provided evidence.