Handyman Callback Log: Track Problems After a Job

You finish a job, send the invoice, and move on. Then a customer texts that something is wrong. A second message adds a photo. A third asks when you can come back.

Keep those messages together as one concern linked to the original job. Give it a next action, a person responsible and a time for the next update. Record the visit decision separately from the billing decision. That gives you a useful callback log without treating every return request as a new sale, an admitted mistake or a closed issue.

This guide uses callback to mean a reported concern after handover. It is a working label for your records, not a finding about workmanship or who owes what. You can use the log in a notebook, spreadsheet or job system.

Open a concern record before booking another job

Start with the original job reference, the work area and what the customer says has changed. An address alone may not be enough: you could have worked on several rooms or completed separate jobs for the same customer.

Record the customer's description as a report. “Customer says the shelf moves when touched” tells the next person what to investigate. “Bad installation” reaches a conclusion before that investigation has happened.

Keep the original handover notes and photos available. Add the new report with its own date instead of editing the old note to make it look as though you knew about the concern earlier. Your job notes should let you distinguish what was observed on the visit from what arrived afterward.

Where ThePocketBoss linked notes fit

In the PocketBoss web app, you can link notes to a customer or project. Customer-linked notes are part of the core workflow; the Projects workspace requires Essentials or above. Team members also need the relevant account permissions. A note added from the linked-notes panel also appears on the Notes page. You can use a separate note to record a later customer report, including the original job reference, what was reported and the next action, without rewriting the earlier handover account.

The customer or project link does not identify a particular callback for you. Enter the specific job and concern references in the note and keep the visit, billing and outcome decisions explicit. The example statuses in this guide are manual recordkeeping labels, not a dedicated callback module or an automated resolution workflow. A promised update written in this note is not automatically a scheduled reminder.

You do not need the cause or a finished solution to acknowledge the report. You do need to say what you will check next. If the customer reports an immediate safety concern, do not leave it in a routine admin queue; direct them to the appropriate emergency or qualified service for the situation. This log is not a repair or remote-diagnosis guide.

Separate the concern from the extra work

A customer may mention a problem with the completed work and ask for something new in the same message. Give each a clear reference so one does not quietly become the other.

For example, “the shelf you fitted moves” and “could you put another shelf in the hallway?” need different decisions. Keep the concern linked to the original job. Put the additional shelf through your usual scope and estimate process. Cross-reference them if you plan to discuss both on one visit.

Do the same with unfinished work that was already recorded at handover. It belongs on the existing remaining-work list, even if the customer uses the word callback. Preserve that history rather than making a new record that hides why the first job is still open.

The contractor estimate guide covers describing and agreeing work. The callback log has a narrower job: keep a reported concern visible until someone has assessed it and recorded what happens next.

Make two decisions: the visit and the charge

Booking time to look at a concern does not settle whether the visit is chargeable. A no-charge decision also does not mean the concern has been resolved. Keep those facts in separate fields.

Before confirming a return, identify its purpose: assess the report, complete a specific agreed action, or check a previous action. Confirm access, the responsible person, any information or materials needed, and what remains outside the visit's scope. Use your daily scheduling check to decide whether that work actually fits the day.

For billing, refer to the relevant scope, prior decision and applicable terms. Record who reviewed it and what was communicated. This worksheet does not decide warranty coverage, legal liability, refunds or a right to charge. Get the appropriate advice when those decisions are disputed or unclear.

Avoid copying all the old invoice lines into a new invoice simply because you created another appointment. Reconcile any proposed charges against the original record and the actual decision for this visit. A visit label is not a billing instruction.

Work through a fictional callback example

Consider a fictional solo handyman who handed over a storage job last week. On Monday, the customer sends three messages about one shelf and a fourth requesting an additional shelf elsewhere. A fifth message comes from another customer reporting a different issue with a previous job.

There are five messages but three distinct matters to manage. Two are concerns about previous work; the additional shelf is a new request. The table below is a worked recordkeeping example, not a customer story or a claim about a PocketBoss feature.

On Tuesday, the owner visits C-01 and records an assessment and the action taken. The appointment can be marked completed. If a promised follow-up is still outstanding, keep the concern open with that next action. Do not turn “I went back” into “the issue is closed.”

Suppose the log records 12 minutes reviewing messages, 26 minutes traveling and 34 minutes at the property for C-01. That is 72 minutes of recorded time: 12 + 26 + 34. It is not automatically 72 billable minutes, a cash loss or a profit calculation. Record the billing outcome separately; use your own cost method if you later analyze the expense.

The extra shelf remains N-01 until its scope and approval are addressed. C-02 stays in the open-concern list rather than disappearing because you dealt with C-01 first.

Close the issue with a specific outcome

After a visit or assessment, record what was observed, what was done, what remains and what you told the customer. If the reported problem was not reproduced, write that instead of saying there was no problem. If a further visit or specialist assessment is needed, assign it a next action.

Use an outcome such as “action completed; customer update sent; no further action currently planned” when that is what your records support. Record customer confirmation only if you actually received it. No response is not the same as approval or satisfaction.

Keep any pending billing review visible even if the operational follow-up is complete. Equally, processing a refund or deciding not to charge does not erase an unresolved work concern. The record needs to show both.

Here is a reusable customer update. Replace the brackets with the facts of the case:

I have recorded your concern about [specific item] against [job reference]. My next step is [action]. I will update you by [day and local time]. [The visit is proposed / the visit is confirmed / no visit is arranged yet]. I will explain any proposed charge before asking you to approve additional work.

For a completed assessment:

At today's visit I observed [finding] and completed [action]. [Item] remains open, and [person] will [next action] by [time]. The recorded billing decision is [decision / still under review]. Please let me know if I have misunderstood the concern you reported.

These are communication starters, not warranty or contract terms. Do not make handling the concern conditional on a public review being changed or removed.

Keep a short open-concern list

Keep the detail with the original job and use a small list to find the records needing attention. Avoid copying every private message or photo into a shared overview.

Review overdue promised updates, unanswered questions and proposed visits that have not been confirmed. When several messages describe the same concern, link them to that concern rather than counting each message as another job failure. When a genuinely different issue is reported, preserve its own description and decision trail.

For a weekly review, count concerns, return visits and time separately. In the fictional example, the three C-01 messages describe one concern. A second visit to assess that same concern would increase the visit count, not the count of distinct concerns. A return visit is not, by itself, proof of defective work.

If you evaluate handyman business software, try to find this information in one harmless sample: the original job, a later concern, a separate new request, the next update and the outcome. Ask which steps require manual notes and which the software supports. Do not assume that scheduling, invoicing or a broad CRM label provides a dedicated callback workflow.

Start with the next concern you receive. Link it to the right job, write one next action and keep the promised update visible. That is enough to make the next conversation more concrete.