How GuardScope
Works
A simple solution to a complex problem: turning vague conversations into clear approvals.
The problem with informal approvals
Most agency projects don't fail because of one big mistake. They bleed money through dozens of small scope changes that get approved in casual conversations.
The Slack message: "Can we add export functionality?"
You reply: "Sure, we can do that."
Two weeks later: "I don't remember approving that. We thought it was in scope."
Why ambiguity causes scope creep
Decisions get lost in the noise
Important approvals are buried in long email threads or Slack channels. When you need to reference them later, finding them takes time and sometimes they're gone.
Stakeholders have selective memory
People remember what they want to remember. Without a clear record, it's your word against theirs—and you usually lose.
Small changes add up
Each "quick tweak" seems harmless. But over the course of a project, these small additions can easily add up to 20-30% more work with zero additional revenue.
How GuardScope fits into real agency workflows
GuardScope doesn't replace your existing tools. It sits on top of them, capturing the final decision after your conversations happen in Slack, email, or meetings.
Conversation happens
You discuss scope changes with your client in Slack, email, or a meeting.
You create a decision in GuardScope
Once you've verbally agreed, you write the decision in plain English and generate an approval link.
Client approves with one click
They click the link (no login needed), see the decision clearly written out, and approve it.
You have permanent proof
The approval is timestamped and stored. When billing time comes, you reference it confidently.
Step-by-step: Creating a decision
Write the decision clearly
In GuardScope, you write out the decision or change request in plain English. Be specific:
"Add CSV export functionality to the dashboard. This is outside the original scope as defined in the project brief. Estimated additional time: 6 hours."
Send the approval link
GuardScope generates a simple approval link. You send it to your client via email, Slack, or any channel you prefer.
The client doesn't need an account or login. They just click the link and see the decision clearly presented.
Client approves
The client sees the decision, clicks "Approve," and you immediately receive a notification.
What an approval record looks like
Decision
Add CSV export to the dashboard — outside original scope, estimated +6 hours.
Status
Approved On
12 Jan 2026 at 14:32
Client
Acme Corp (Sarah Johnson)
How approvals help with billing and scope discussions
When you have clear approval records, every billing conversation becomes straightforward:
Billing for scope changes
Instead of negotiating or discounting, you can show the client exactly when they approved the change. The timestamp removes any ambiguity.
Project retrospectives
Review all decisions made during a project to understand scope evolution and improve your initial estimates.
Setting boundaries
When you have a history of approvals, it's easier to say "This is a new request—let me send you an approval link" without it feeling confrontational.