Turn a signed T&M tag into a change order

Back in the office, I open TM-001. Wednesday, Serrano's crew framed a kitchenette bulkhead that isn't in the drawings, and the GC's super signed the tag the same day: eight hours, described, dated. That signature is evidence, not money. Money comes from a chain — tag to change event to PCO to CO — and the Changes tab holds every link. Here's how a signed tag becomes a change order.

Flag the tag and make it a change event

1. Open the job → Changes → T&M Tickets. TM-001 is there with its work date and description, and a Change Candidate column that's empty until you decide.
2. Flag as Change. The row picks up a Flagged chip: the PM saying this wasn't base scope. (Directed work gets flagged; an open question would have been an RFI instead.)
3. Convert → CE. The chip becomes CE Created, and on Change Events the new event carries the ticket as its Source. The link runs both ways, so the hours, the signature, and the date travel with the event.

Price it as a PCO

1. PCOs → + New PCO, then Build → on the draft. The builder has a Scope of Work, the Linked Change Events (pick the bulkhead), and Line Items.
2. One line: the labor, Qty and Unit Cost, with OH% and Margin% set to what the subcontract allows, 15% here. The totals block shows subtotal, Markup, and the sell price: $1,860. A number the GC can say yes to without a meeting.
3. Submit. That locks the PCO — what you sent is what you sent. Print gives you the priced package with the ticket behind it.
4. When the GC answers, Approve or Reject puts their answer on the record, not in a hallway.

Execute the CO

1. Change Orders → + Record CO: a Title, the Amount, and the Source PCO. Picking the PCO is what keeps the chain unbroken.
2. Execute on the row. The Execute Change Order dialog asks for the Executed Date and the SOV Impact: Add new SOV line, Amend existing SOV line (pick the line, enter the delta), or No SOV impact. The bulkhead gets its own line.
3. Execute CO. It fires exactly once; if the CO carried days, the contract's completion dates move with it.
4. When the GC's paper comes back, record GC Executed and their SCO # on the row.

What flipped underneath

The top of Changes now shows Revised Contract Value carrying the $1,860 and Executed CO Impact counting it. The SOV has a new line, and if a pay app is already open the line is on it at zero previously billed, ready for the 25th. Finance gets the CO in their Inbox the same minute — "CO-001 executed — $1,860 added to the SOV" — so the billing side hears about the money before the pay app does. Contract value and the schedule of values moved together, same day. A claim never had a chain like this: a signed tag, an event, a priced ask, a recorded yes, an executed amendment, each pointing at the one before it.

Common mistakes

• Pricing before the event exists. A PCO with no linked change event is a number with no story. Convert the ticket first.
• Recording the CO without the Source PCO. It still executes, but the chain breaks right where a dispute would look.
• Choosing No SOV impact to "sort it out later." Later is the pay app, and the CO isn't billable until it's on the SOV. Add the line or amend one when you execute.

See also

• E13 · Daily log and photos
• E15 · Friday, 4:30
• PCO vs CO — the change path
• T&M tag — why the owner signature is everything