Crew must acknowledge new scope before rolling stages

An approved change order has to be acknowledged by the crew lead before they can mark later stages complete.

What it is

AcknowledgeChangeOrder stamps crew_acknowledged_at and crew_acknowledged_by on the change order. It is described as 'a required gate before they can mark subsequent stages complete' and deliberately does not change the change order's own status.

Also called: crew didn't know about the change · acknowledge change order · field team scope change

See it
Crew must acknowledge new scope before rolling stages
CustomerBuildingAmountStatus
Ronan PetschBarndominium$10,510Approved
Sutter KlineHobby Shop$7,850Draft
Sutter KlineEquipment Storage$17,920Open
Ronan PetschHobby Shop$10,320Approved
Ronan PetschEquipment Storage$8,420Approved
The crew view of an approved change order with an 'Acknowledge new scope' action and, after, the name and timestamp of who acknowledged it. Sample data — no customer information appears here.
How it works
  1. 1The customer signs; the change order becomes approved.
  2. 2The crew lead acknowledges the new scope from their surface.
  3. 3The acknowledgment is recorded with a timestamp and the acknowledging person.
  4. 4Until then, subsequent stage completions are gated.
Why we built it

The status lifecycle comment states the sequencing: 'approved → customer signed (signAsCustomer); crew lead must ack before the next phase rolls.' Paperwork the field never reads is paperwork that gets built wrong.

The problem
  • Approved scope changes that never reach the people building
  • Stages completed against superseded scope
Sound familiar?
What you get
The field confirms it has seen the new scope
A recorded acknowledgment with a name and time
Stage progress can't outrun the change

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →