Scope creep, with
the audit trail.
Every scope request is a structured event — raised, debated, accepted or rejected with a reason. New work gets its own task with a permanent link back to where it came from.
Scope, on the record.
Three rules: clients raise it, you decide it, the trail outlives both of you.
Clients raise, you decide.
While a task is in client review, the client can raise a scope request — a structured note saying “I'd like more than this.” The task enters a scope_requested state until you respond.
Conversation before commitment.
The scope request appears as a special note in the Notes tab. Talk it through with the client — is this a small tweak or a new deliverable? Once you're aligned, you accept (creating a new scope task) or reject with a reason the client reads.
Accepted scope tasks show their origin.
Every scope task renders with an orange bar on the timeline and a banner on its detail page pointing back to the original task. A future auditor — or a future you — can always trace where new work came from.
Scope Requests, answered
Built for agencies. Over-engineered for honesty.
Every decision in Progense exists for one reason: to tell the truth about where your projects actually are. Not to make you look good on a Monday morning slide. To show you — and your clients — reality.
Get started
The first month is on us.
