An out-of-scope request turned into a priced, dated change order before the awkwardness sets in. Describe what the client asked for and a Taskade Genesis app returns the addendum: what is being added, why it sits outside the original scope, the effort and price, the impact on the timeline, and the approval line, written in a tone that keeps the relationship warm.
The Project Portal is a live Taskade Genesis app embedded on this page. It holds the scope and the deliverables you agreed to, which is the record a change order has to argue against, so start there rather than from a blank document. Use it here, then click "Use this app" to clone it in about ten seconds and describe your own engagement so every change order drafts from your actual scope.
Most unpaid consulting work is not extorted, it is drifted into. A request arrives, it seems small, saying no feels disproportionate, and three of those add up to a week. A change order system makes the boundary routine instead of confrontational, because the answer is never no, it is here is what that costs and when it lands. Workspace DNA supplies the evidence. Memory holds the original scope, exclusions, and every prior change. Intelligence, backed by 15+ frontier models from OpenAI, Anthropic, Google, and open-weight providers, checks the request against the signed scope, estimates the effort, and drafts the note. Execution tracks the addendum through approval and folds it into the plan once signed.
Every change order lives in the layouts you need:
- List view for the readable addendum the client approves
- Table view for the change log with value, status, and cumulative scope added
- Board view for moving requests from raised to priced to approved to delivered
- Calendar view for the revised dates each approved change produces
- Plus the rest of the 7 project views
Automations catch requests before they become assumptions. Wire Taskade automations so a request arriving by email or in the portal is checked against scope and, if it falls outside, opens a change order record and notifies you. With 100+ bidirectional integrations, Gmail and forms pull requests in while Slack and Gmail push the priced addendum and the approval reminder out.
The AI agents inside the app carry 34 built-in tools including persistent memory, file analysis, web search, custom slash commands, and multi-agent collaboration. Ask the agent for three versions of the same change order, firm, neutral, and generous, and pick the one that fits the relationship rather than your mood on the day.
Clone it, share it with anyone who talks to clients, and the change history is yours. A clean log of what was added and when is worth having on the day someone asks why the project cost more than the proposal.
Build your own version in Taskade Genesis, see live client apps in the Community Gallery, or learn approval flows in Learn. Set a scope worth defending using Build a Statement of Work With Acceptance Criteria, and keep recurring work inside its limits with Run a Monthly Retainer Without Scope Creep.
Frequently Asked Questions
When is a request big enough to need a change order?
Set a threshold and let the system apply it consistently. Many consultants use a small allowance per phase for genuinely minor requests and raise a change order above it. Consistency matters more than the exact number, because the damage comes from deciding case by case under social pressure.
How do I raise this without sounding difficult?
By making it procedural and fast. A change order that arrives within a day, priced and with a date, reads as professionalism. The same conversation held awkwardly three weeks later reads as a complaint. The agent drafts in a warm, matter-of-fact register by default.
Can a change order reduce scope as well as add it?
Yes, and offering that is often the move that saves a relationship. If the budget is fixed, the agent can propose what comes out to make room for what is going in, which turns a difficult no into a shared decision about priorities.
Does it show the cumulative effect of many small changes?
Yes. The change log carries a running total of added value and added days, so you can show a client that six small requests have moved the end date by two weeks. That number is far more persuasive than any individual request was.
Who needs to approve it?
Whoever you name on the record. The app tracks the approver, the date, and the method, which is exactly what you want if the sponsor changes halfway through the engagement and the new one asks why the scope looks different from the contract.
What if the client refuses to pay for the change?
You still have a documented decision. Record it as declined with the reason, and the original scope stands unchanged. The value of the record is that the request cannot quietly reappear as an expectation later in the project.
Can approved changes flow into delivery automatically?
Yes. An approved change order can create the new deliverables in your tracker with dates and owners already set, so the work starts from an accurate plan. Track Deliverables Across Every Client Engagement picks it up from there.
Should small requests always be charged?
Not always, and choosing deliberately is the difference between generosity and leakage. Decide in advance what you will absorb, whether that is an hour a week or one small favour per phase, and log it as goodwill rather than pretending it did not happen. Logged goodwill is visible at renewal and is one of the more persuasive arguments for a rate increase, because you can show the client what they received beyond the contract. Unlogged goodwill is simply free work that nobody remembers by the time it matters.
