EVIDENCE & LIMITS

Adapted from my recorded thoughts on cancelled service jobs. The review format below is a suggestion, not a report of measured losses or a named customer.

The visit stops. The preparation already happened.

One thing I recommend to service-business owners is to record cancelled jobs, even when nobody goes out to do the work.

By the time a job is cancelled, someone in the office may already have taken the request, created the job and worked on getting it arranged. The customer sees a cancelled visit. The office still spent time getting to that point.

That was the point I wanted to make in the recording: setting up a job takes time, effort and attention. If the job disappears from the system when it is cancelled, that part of the customer relationship becomes harder to see.

Keep a useful record, without inventing a cost

I am not putting a dollar amount on this. I have not presented a timed study or an account-by-account calculation. The first useful step is to make the work visible.

The five notes below are a simple way I would start. They connect the original request to the cancellation, show what preparation had happened and leave room for the reason. They can live in the job record you already use; this does not need to become another software project.

If nobody tracked the time, leave the time unknown. A short factual note is more useful than a precise-looking estimate nobody can explain. You can map the work from request to closeout to see where preparation happens before a technician arrives.

Review the pattern before deciding what it means

In the recording, I raised the possibility of letting a customer go when the work repeatedly gets set up and then cancelled. That is a decision about whether the relationship works, and I would want the record in front of me before making it.

One cancellation does not answer that question. I would want to see it beside the jobs that went ahead, understand the reasons and check whether our own process contributed. A changed appointment and a job that never happens also need different labels.

The next conversation might be about confirming the scope earlier or how the work is scheduled. It might reveal that the customer needs something we cannot provide well. The useful part is having enough context to make a human decision, instead of asking the office to carry the whole history in memory.

The office work belongs in the picture

This is a small example of why software has to work for the people using it. A clean-looking job list can miss the calls and preparation that happened before a visit.

For me, business leadership includes paying attention to that work. If an owner wants to understand which customer relationships are working, completed jobs are only part of the picture. Keep the cancellations visible, too.

TRY THIS

Five notes to keep when a job is cancelled

A suggested starting point for a private job record. Use facts the team can verify; leave unknown details unknown.

  1. 01 · Original jobWhat work had the customer requested?Keep the original job reference and scope so the cancellation stays connected to the work.
  2. 02 · TimingWhen was the job accepted, scheduled and cancelled?Use actual timestamps when available. Mark a reschedule separately from a final cancellation.
  3. 03 · PreparationWhat had the office already done?Note the calls, setup or coordination that actually happened. Add time only if it was recorded.
  4. 04 · ReasonWhat reason was given, and by whom?Keep the stated reason separate from an assumption. Include an issue on our side if that caused the change.
  5. 05 · Next decisionWhat should the team review or change?Assign a person to review the pattern and record the next action. A cancellation alone does not decide the customer relationship.

What to remember

  • Keep a cancelled job connected to the original request.
  • Record preparation that actually happened; do not invent time or cost.
  • Review the reasons and the wider relationship before choosing a response.