Handyman Change Orders: Track Added Work

When a customer adds work to a handyman job, keep the extra request separate from the original scope. Record the added work, its price, the customer's decision and whether the amount is already included in the estimate or invoice. Those four facts stop a small extra from becoming an unexplained final total.

The key check is simple: an approved extra should appear once in the document you intend to send. A request still awaiting a decision should remain distinguishable from that approved amount.

This guide follows the records from a new request to the document total. It does not supply contract terms or determine the approvals, tax treatment or right to charge that apply to a particular job. Use the requirements appropriate to your business and location.

Tie the change to one job and one version

Start with the original estimate or invoice reference and the specific work being changed. An address and a customer name may cover several jobs. Give the extra request a reference you can find in the conversation and on the document later.

Write down:

• The original document and the relevant scope or version.
• The extra work requested, including its location and quantity.
• What the added price covers and any unresolved details.
• Any effect on timing, materials or a return visit.
• The decision still needed and the person who can make it.

Describe the change itself rather than copying the entire original job into a second charge. If the customer wants a replacement for something already included, reconcile what comes out as well as what goes in before presenting a revised amount.

For work still at the proposal stage, the contractor estimate guide covers scope and optional choices. Here, the task is narrower: keep a later change connected to the document it affects.

Keep the added amount and revised total separate

Consider a fictional handyman job with an original subtotal of $150. The customer asks for two additional doorstops, priced in this example at $25 each. They also ask about a separate $35 pantry-latch adjustment.

These invented amounts demonstrate the records, not recommended rates. The example has no tax, discount, deposit or previous payment, so the arithmetic stays visible.

The working subtotal is $150 + $50 = $200. The change is $50, not $200. The pending $35 does not belong in that included total merely because someone asked about the work.

Two quick checks catch different mistakes. A $235 subtotal would include the still-pending request. A $250 subtotal could mean the applied $50 was entered a second time. Compare the lines and references, not only the number at the bottom.

If CO-02 is declined, record that decision and keep it distinguishable from the accepted extra. If the customer later requests a different version, identify the revised request and decision instead of silently treating the old one as accepted.

Understand what the software status actually tells you

In ThePocketBoss's web app, a change order can be attached to an estimate or invoice. The workflow is part of core invoicing available from Solo, with the relevant invoice permissions. It keeps a separate change-order record; applying that change also adds its line items to the parent document.

Customer approval is an option in this workflow. Check the approval setting for the particular change rather than assuming every draft requires customer sign-off.

There is a particularly useful distinction in the current customer-portal flow: a successful customer approval also applies the change-order items to the linked estimate or invoice and marks the change order Applied. Check the parent document before adding the extra yourself.

The business can also apply an eligible draft directly when customer approval is not required. That is why the Applied label and the customer's approval record are different facts. Use the approval process required for the actual job; a software setting does not decide that requirement for you.

If you compare contractor invoicing software, check how it handles this transition. Ask whether customer approval changes the document total automatically or leaves a separate apply step. The answer matters more than whether both products use the same status name.

Give the customer one clear decision

Present the added scope, the added amount and the resulting total together. Explain any scheduling condition before making the extra sound like a confirmed addition to today's visit.

For the same fictional extra, the request before approval could read:

I have recorded CO-01 against document H-24: two additional doorstops at $25 each. The added amount is $50, which would bring the subtotal from $150 to $200. The separate $35 pantry-latch request is still pending and is not included. Please review CO-01 through the approval process we are using. I will confirm when the added work can fit before treating it as scheduled.

Replace the references and amounts with the actual record. If the scope, price or timing changes while the customer is deciding, make the revision clear and obtain the decision appropriate to that revision.

If the customer cannot find the approval request, check the contact details and delivery outcome before assuming silence means acceptance. The customer-communication guide has examples for keeping an outstanding decision and the next update clear.

Reconcile the document before you send it

Before sending the revised estimate or invoice, compare it with the change-order list:

1. Find the original document reference and check that it is the one the customer expects.
2. Identify the extra items already present, using their descriptions and change-order references.
3. Reconcile the customer's recorded decisions with the work and amounts included.
4. Check that pending, rejected or superseded requests have not become unexplained charges.
5. Recalculate the subtotal and review the document's actual tax, discount and payment treatment.
6. Preview the customer-facing document and confirm that the added work is understandable.

For the example, finding CO-01's doorstop entry with quantity two already present means its $50 is already included. It is not a reason to type another $50 line. Check the actual result after an action succeeds or fails rather than using repeated clicks or manual lines to force the total you expected.

The resulting document total is also separate from the payment record. An invoice showing $200 does not mean $200 has been collected.

Hand over the current record, not just a bigger number

Keep the current scope reference, decision and document together when someone else takes over the job or its administration. A useful handoff says which extra is included, which request is still open and what happens next.

Preserve the version the customer considered. If an applied change later needs correction, make the revised scope and amount explicit and follow the appropriate review process. Do not assume a saved or applied record is an immutable copy of an earlier agreement.

After handover, a report about previously completed work is a different decision from a newly requested extra. The handyman callback log helps keep that concern and any return visit separate from its billing outcome.

For your next added-work request, start with one reference and one clear description. Then check the customer's decision and the parent document before sending the revised total. That keeps the record useful from the first conversation through invoicing.