TL;DR: All three PSAs record a change order once someone decides to file one. Rocketlane adds a budget inside the project, Kantata proposes a budget change the client can approve, Certinia raises a change request that becomes a Salesforce opportunity. None of them tells you the scope moved before the form exists, and none helps you stop selling hours. That gap gets expensive when project overrun sits at 10.7%, above the 10% line SPI Research flags. Aircall paired an account brain with its existing stack and cut time from contract to cutover 30%.

If you run an implementation team, the change order is where your margin is decided, and most of the time it is decided by not filing one. The customer asks for two more integrations on a Tuesday call, the implementation manager says "we'll look at it", and forty hours later nobody can point to the moment scope changed. Your PSA will record the change order. It will not tell you that you needed one.

The buffer is thin. SPI Research's 2026 report, summarized by Deltek, puts project margin at 37.7% and billable utilization at 66.4%, the lowest in SPI Research's survey history. PMI's 2018 Pulse of the Profession found that 52 percent of projects experienced scope creep or uncontrolled changes to scope, up from 43 percent five years earlier.

A professional-services leader at a compliance software vendor put the root cause plainly: "Any miss in presales comes back and bites us during implementation. That's when you start uncovering what you missed." The change order is usually born in the CRM handoff, and the PSA meets it months later. Each vendor section below answers four questions from the vendor's own documentation: what the object is, who approves it, what it does to financials, and what triggers it. The pillar on scope creep in implementations covers the wider problem.

How does Rocketlane handle change requests?

Rocketlane treats a change order as an additional budget inside the same project. Its May 2026 billing post states that Rocketlane supports multiple budgets within a single project, each with its own billing model, and that change orders become separate budgets rather than separate project records. Each budget carries its own fixed-fee, T&M, retainer, or milestone terms.

The object: a budget you edit in place

Rocketlane's help center explains that you click the pencil icon near the project budget, budgeted hours, or currency to edit the fields directly, choose whether the change applies going forward or from the start, and review changes through a history icon. That is an audit trail, not an approval workflow. The article documents no customer sign-off.

What triggers it: Nitro Signals, and what it costs

Rocketlane is the only one of the three that claims to detect scope moving. Its Nitro page says the platform continuously monitors customer conversations across emails and meetings to surface early delivery risks, and the billing post adds that the Signals Agent monitors client calls and emails for scope expansion language. The detection only sees conversations captured inside Rocketlane's own workspace, and it belongs to the Nitro layer, not the base budget feature. Base pricing is public: Standard at $49 and Premium at $69 per team member per month billed annually, with a minimum of 5 team members, Enterprise quote-based. Our Rocketlane pricing breakdown covers the costs that appear after the contract.

How do Kantata change orders work?

Kantata models a change order as a proposed budget change on the project's Budget tab. You select Propose Budget Change, enter a positive or negative price change as a whole number, add an optional message, and the proposal appears in the budget activity. Kantata's docs call these entries change orders.

The approval setting

Approval is real in Kantata but optional. The project setting Schedule and budget changes must be approved requires every schedule and budget change to be approved by a client with View Financials or higher, or by a provider-side Project Administrator. When it is off, a budget change is just an edit, so whether your Kantata instance has a change order process is a configuration question. An approved change updates the project budget, and tasks bill in Fixed Fee or Time and Materials mode. Nothing in the documented flow detects that scope has changed.

Implementation reality, in Kantata's own words

Kantata is candid about the rollout. Its July 2026 post says implementation takes "6-8 weeks for mid-size orgs and 3-6 months for enterprise-scale, multi-entity rollouts". Per G2 reviews, the learning curve is the second most cited dislike with 15 mentions. Pricing is tailored to company size and goals, with no public number. The Kantata alternatives guide compares the options for implementation teams.

How does Certinia handle change requests?

Certinia turns a change request into a Salesforce opportunity. The PSA help states that you raise a change request from your project, which creates a change request opportunity, used when a change falls outside the originally agreed scope. Of the three, this is the one a finance team would recognize: a change order as new revenue with its own record.

Budget types and the Approved checkbox

Certinia documents budget types including Customer PO Change Request, Internal Budget Change Request, Vendor PO Change Request, and Work Order Change Request. An "Approved" checkbox together with "Include in Financials" controls whether a budget appears in project financials, and Customer PO budgets add to bookings actuals. Approval rides on Salesforce, fast if your approvers live there and slow if they do not.

Admin configuration and the Salesforce commitment

The workflow is configured, not switched on. Certinia's change request settings expose a budget-name suffix, default budget status, default budget type, and an opportunity-name suffix that an admin sets first. Certinia is also explicit that it is "100% coded on Salesforce" and uses 100% Salesforce objects, so every user needs a paid subscription and your change order process inherits your Salesforce admin capacity. Per G2 reviews, "Steep Learning Curve" is the second most cited dislike. Certinia does not publish an implementation duration.

Change orders compared: spreadsheets + Slack, Rocketlane, Kantata, Certinia

Start with what most teams actually run, a SOW tracker in a spreadsheet and a Slack channel per customer. Every vendor in the table beats that on record keeping. The trigger column is where the differences narrow, and none of the columns shows the 45 hours that never reached any of these systems. A change order process only earns its keep if the ask is caught while it is still an ask, and the spoke on scope creep vs discovery is the judgment call that sits right before that moment.

  • Spreadsheets + Slack. What a change order is: An email thread and a new row in the SOW tracker. Who approves: Whoever replies first. Financial effect: None until finance re-keys it. What triggers it: Someone notices. Price: "Free" until the first unbilled 45 hours.
  • Rocketlane. What a change order is: An additional budget inside the same project, edits logged in a history icon. Who approves: No approval step documented. Financial effect: Per-budget invoicing. What triggers it: Budget alerts, plus Nitro Signals on Rocketlane's own captures. Price: $49 / $69 per team member per month, 5-seat minimum, Enterprise quote-based.
  • Kantata. What a change order is: Propose Budget Change on the Budget tab. Who approves: Client with View Financials or provider-side Project Administrator, if the setting is on. Financial effect: Updates project budget, Fixed Fee or T&M billing. What triggers it: Nothing documented, a human proposes. Price: Quote-only.
  • Certinia. What a change order is: Create Change Request creates a Salesforce opportunity and a Change Request budget. Who approves: Salesforce approval, "Approved" checkbox. Financial effect: Customer PO Change Request adds to bookings actuals. What triggers it: Nothing documented, a human raises it. Price: Quote-only, every user licensed.
  • Tandem (not a PSA). What a change order is: Not processed here. Surfaces scope drift as a red, amber, or green risk with evidence, drafts the SOW addendum for human approval. Who approves: Your PSA or contract tool still approves and invoices. Financial effect: Keeps the account state the change order is measured against. What triggers it: The ask appearing in Slack, email, CRM, tickets, or a call. Price: Varies by team.

The T&M-to-packaged shift none of them cover

All three PSAs bill both time and materials and fixed fee, and none of them helps you move from one to the other. That move is the real margin lever for implementation and FDE teams, and the PSA can only record it after you have made it.

What FAR says about who carries the risk

The clearest non-vendor source on the economics is the US Federal Acquisition Regulation. FAR 16.601 states that a time-and-materials contract "provides no positive profit incentive to the contractor for cost control or labor efficiency", which is why it carries a ceiling price the contractor exceeds at its own risk. The firm-fixed-price clause says that model places upon the contractor maximum risk and full responsibility for all costs. Under fixed scope the change order is the only thing between you and unpaid work.

Why packaged scope matters for FDE teams

The FDE playbook on this blog puts it in one line: time and materials is the honest default when effort is unknown, and it is also a margin ceiling. Mature FDE programs stop selling hours and start selling packages, a defined outcome with a time-box and milestones. A forward deployed engineer is an engineer who spends roughly half their time with customers understanding the problem and half building the solution for that specific customer. That split is what makes scope hard to count.

The head of a forward-deployed team at a Series A AI startup described the exposure (translated from French): "Because we have forward-deployed engineers, sales tends to say yes to everything. What was actually sold or promised doesn't always make it into the contract." A PSA can bill a package once you have defined it. It cannot tell you the average effort per engagement when nobody logged the informal scope.

Where Tandem sits: the signal before the change order

Tandem does not process change orders. It is the AI workspace for implementation and deployment teams, and its job here is to surface the moment scope moved, with evidence, so the change order gets filed in your PSA while it is still worth filing.

Scope drift with the evidence attached

The account brain holds the account state, meaning what was promised, what was decided, and what is at risk, sourced from Slack, email, CRM, tickets, and calls. Risk detection reads that state and flags scope drift as a red, amber, or green risk with the evidence: the Slack thread where the customer asked for two more integrations, the call where an engineer said yes. The spoke on the scope baseline as account state explains why a change order needs that baseline. Without one, the conversation with the customer is memory against memory.

When a scope drift risk is confirmed, a Tandem agent drafts the SOW addendum from the evidence. The action is named (draft SOW addendum), a human on your team approves it before anything leaves the workspace, and the draft carries a visible marker with the source thread or call attached. Aircall paired the account brain with its existing stack and cut time from contract to cutover 30%, with 3x rollouts per engineer (5 to 15).

From signal to signed change order

  • Set the baseline. Load the SOW and kickoff commitments into the account state.
  • Catch the ask where it appears. Risk detection flags scope drift in the Slack thread, call, or email, with the source attached.
  • Decide: change order, goodwill, or discovery. A human makes this call.
  • Draft the addendum with approval. A Tandem agent drafts the SOW addendum, your lead approves it, and the marker and source stay on the record.
  • File it in the PSA. Add the budget in Rocketlane, propose the budget change in Kantata, or create the change request in Certinia.

What stays manual

Tandem does not decide whether a request is a change order or goodwill, price the change, get the customer to sign, enter the approved budget in the PSA, or invoice it. All five steps stay with your team and your PSA or contract tool. Tandem pairs with a PSA or tracker rather than replacing resourcing and invoicing, needs your playbooks configured first, and has a thin review base as a new category. A human approves every agent action, and the approval and the source stay visible on the record.

Choose the PSA for the workflow, add the signal for the trigger

Rocketlane has the lightest change order model and the only detection layer, limited to its own workspace. Kantata has a real client approval step, if you turn it on. Certinia ties most tightly to finance, at the cost of living entirely in Salesforce. The PSA buyer guide for 2026 weighs those trade-offs beyond change orders. See Tandem flag scope drift on one of your live implementations, with the evidence attached, before the change order is overdue.

FAQs

Does Rocketlane have a change order feature?

Rocketlane handles change orders as additional budgets inside the same project, each with its own billing model. Edits are made in place and logged in a history view. There is no documented approval step.

How do you approve a change order in Kantata?

Turn on the project setting that requires schedule and budget changes to be approved. A client with View Financials or a provider-side Project Administrator then approves or declines each proposed budget change. Without that setting, a budget change is a plain edit.

Which PSA detects scope creep automatically?

Rocketlane states that its Nitro Signals layer monitors emails and meetings captured in Rocketlane for scope expansion language. Kantata and Certinia document no detection step, their flows begin when a person proposes a budget change or raises a request. Tandem's risk detection reads the account state sourced from Slack, email, CRM, tickets, and calls.

Does Tandem replace a PSA for change orders?

No. Tandem surfaces the scope drift that should trigger a change order and drafts the SOW addendum for human approval. Pricing, signature, budget entry, and invoicing stay in Rocketlane, Kantata, Certinia, or your contract tool.

Key terms

Change order: A signed agreement to change a project's scope, budget, timeline, or all three. In a PSA it becomes a new budget, a proposed budget change, or a change request record.

Scope creep: Work delivered beyond the agreed statement of work without a change order.

Scope baseline: The recorded promises and decisions a project is measured against, usually the SOW plus kickoff commitments.

Time and materials (T&M): Billing by hours worked at agreed rates. The customer carries cost risk and the vendor carries a margin ceiling.

Professional services automation (PSA): Software for projects, resourcing, time, budgets, and invoicing in services teams. Rocketlane, Kantata, and Certinia are PSAs.

Account brain: Tandem's product block that holds the account state, meaning what was promised, decided, and at risk, sourced from Slack, email, CRM, tickets, and calls.