Record and bill job variations in AxiomBlue

Record the extra scope in AxiomBlue Professional

1. Open the original job and its Variations record. Describe the requested addition or omission, the reason and the priced difference from the accepted scope. Keep the requester and the effect on time or materials in the supporting record.
2. Review the change with the customer through the approval process. Check that the variation is Approved before treating it as agreed revenue or instructing the crew to proceed. A draft request or note is not an approval.
3. Inspect the revised contract value and the invoice or claim preview. In the worked example, reconcile the original $1,000 and approved $200 addition with earlier invoices. Put the approved change into the job’s Description or Tasks for the field team; do not make them infer scope from a changed total.

Separate a request from an agreed change

Record the request against the original job, including who asked and what they want changed. Describe the difference from the existing scope. A note saying “extra work” leaves too much for the next person to infer.

Check whether the work is already included before pricing it again. If it is a correction to something you were already responsible for, that is a different situation from a newly requested addition. Resolve that distinction before preparing a revised amount.

Make the effect on price and timing visible

Illustrative example: the original scope is $1,000 and a requested addition is priced at $200. Once that addition is approved, the revised service amount is $1,200 before applicable tax. Record the original reference, the $200 change and the approval together.

If the addition needs another visit, different materials or a later completion date, record that too. The new price alone does not explain what the scheduler or crew should do. The downloadable record includes a blank worksheet and a filled example.

• Original job and scope reference
• Requested addition or omission
• Change in amount and revised total
• Effect on work, materials or timing
• Approval status and supporting reference

Give the crew an unambiguous instruction

Make it easy to tell whether a change is requested, awaiting an answer or approved. The person on site should not have to guess from an old message. If the request changes again, update the current instruction and keep the earlier record understandable.

A recorded signature, message or approval has context. Preserve the description that the customer was responding to rather than keeping an isolated “yes”. Your agreement and normal approval process determine what you need before proceeding.

Trace the approved change into billing

Before invoicing, check whether the approved amount is included and whether any part has already been billed. For progress billing, review previous claims as well as the revised value. Approval of a change and payment of an invoice are separate events.

AxiomBlue’s contract variations, approval states and revised contract values require Professional. Inspect a sample fixed-price change and its billing result in the demo or on that plan. Your agreement and approval process determine what authorisation is needed.