Tasks hide commercial decisions
A task title rarely shows whether the work was included, priced, or approved.
Change request workflow
Do not let client change requests jump straight onto the task board.
A change request should pass through a decision layer before it becomes delivery work. EasyScope gives freelancers that layer: capture, estimate, approve, convert, and bill.
Workflow rule
request before task
The project stays healthier when new asks are decided before exécution.
Change request path
Live projectInbox
Client ask loggedSimulation
Impact calculatedApproval
Decision neededConversion
Deliverable or change orderSTEP 01
Ask arrives
STEP 02
Impact calculated
STEP 03
Client approves
STEP 04
Work becomes billable
Why it matters
The board is for work. The inbox is for decisions.
When every client ask becomes a task immediately, the project loses the distinction between agreed scope and new scope.
Clients expect instant acceptance
If the request moves into delivery too quickly, approval becomes assumed.
Billing becomes harder later
It is easier to invoice work that was explicitly approved before delivery.
The EasyScope way
A better path for every incoming ask
EasyScope keeps new requests in a controlled flow until you decide what they are.
01
Capture
Log the request from the client, a call, a message, or a simulation.
02
Classify and estimate
Decide whether it is included, extra, declined, deferred, or needs more context.
03
Convert
Turn the request into a deliverable, change-order draft, quote, or client response.
Proof points
A workflow made for messy client reality
The system is simple because the real work is getting to a clear decision.
Scope Request Inbox
Hold requests before exécution.
Simulation origin
Save impact simulations directly as requests.
Conversion paths
Create deliverables or change-order drafts from requests.
AI Diplomat
Respond professionally when a request is not included.
No awkward surprises
Workflow questions
Is this too much process for small requests?
The process can be lightweight. The point is to avoid invisible acceptance.
Can clients submit requests directly?
Yes. The client portal can collect new requests through a secure link.
Can I still move fast?
Yes. A fast approval path is different from skipping approval.
Give every change request a decision before it gets a deadline.
Protect delivery by separating requests from tasks.
Create a change workflow