Every extra ask gets an estimate and a signature.
Scope creep is rarely one big change. It is ten small asks that nobody priced. Change Requests gives each one a scope, an estimate, a price and a client sign-off, then puts it on the plan and the invoice.
Change Requests/Logistics App/CR-014Multi-warehouse routing for dispatch
Raised by Kavya S. from client call on 28 Oct · linked to Backend APIs, Dispatcher console
- Scope written and estimated
- Internal review by delivery head
- Sent to client for sign-off
- Added to plan and billing
- Sign-off by link
- Clients approve without a login
- Impact first
- Hours, price and days shown before sign-off
- Straight to billing
- Signed changes land on the next invoice
- Full history
- Who asked, who estimated, who signed
Everything in Change Requests
Write it once
Describe the change, link the affected phases and tasks, and attach the client email or call notes it came from.
Estimate by role
Estimate hours per role. The price is calculated from the project’s rate card, or set as a fixed amount.
Schedule impact
See how many days the change adds to go-live, using the current plan and team load.
Client sign-off
The client receives a clean page with scope, price and date impact, and approves or declines with a typed name.
Unsigned work flagged
If hours are logged on a change that is not yet signed, AI Project Health raises it as scope risk.
Billing rules per change
Bill a change as a fixed amount, as T&M, on the next invoice or as its own invoice.
Budget tracking
Each change keeps its own budget, so overruns on extras do not hide inside the main project.
Linked to the plan
Signed changes create tasks in the right phase, and the Gantt and baseline variance update.
Audit trail
Every version, estimate and approval is kept, so disputes are settled by the record.
A week in Change Requests
- 1The client asksA client wants multi-warehouse routing. The account manager logs it as CR-014 with the call notes attached.
- 2Estimate and priceThe tech lead estimates 120 hours by role. The rate card prices it at ₹4.2 L, with 6 days added to the schedule.
- 3Send for sign-offThe delivery head reviews and sends it. The client sees scope, price and impact, and signs from the link.
- 4Plan and billTasks drop into the plan, the team starts work, and the amount appears on the next invoice.
Client Billing/Invoices/INV-2026-0412| Backend development | 212.0 h | ₹2,000 | ₹4,24,000 |
| Flutter development | 146.5 h | ₹1,800 | ₹2,63,700 |
| QA engineering | 38.0 h | ₹1,200 | ₹45,600 |
| CR-011 Bulk order upload | Fixed | ₹1,80,000 | |
| IGST 18% | ₹1,63,782 | ||
| Total | ₹10,77,082 | ||
Signed changes land on the invoice.
Whether a change is billed fixed or by the hour, it appears on the right invoice with its reference number, so the client recognises what they signed.
- CR number and title on the invoice line
- Partial billing for large changes
- Margin for each change in Profit View
Every plan starts
with a signature.
Sign off on your own kickoff. Import a live project, invite the team, and watch the first timesheets turn into an invoice before the month closes.
- Project
- Your next client project
- Kickoff
- Today
- Workspace
- 30 days free · up to 25 people
- Go-live
- The date you promised the client