Operations
Put tasks beside the customer
A personal to-do list cannot tell you who the work is for. Tasks belong on the record, with an owner and a date, so covering leave is not guesswork.
6 min read
When tasks live in a private list, covering leave is guesswork. When they live on the customer, anyone can see what is still open, what is waiting on them, and what is waiting on you.
Personal to-do apps are fine for buying milk. They are a poor system for 'call Jane about the quote' because Jane is not in the app, and neither is the quote.
Personal to-do apps are fine for buying milk. They are a poor system for 'call Jane about the quote' because Jane is not in the app, and neither is the quote.
When tasks live on the customer, covering leave is not guesswork. Anyone can see what is still open, what is waiting on them, and what is waiting on you.
If covering leave still needs a verbal list, the tasks are still private. The record should be the list.
A task needs a person and a date
Call Jane Tuesday about the quote. That is a task. 'Admin' is not. 'Follow up' is not, until you say who, when, and why.
If you cannot name the customer, it may not belong in the CRM. If you can name the customer, it does not belong only in your head.
Open the customer, see the work
Before you ring, you should see open tasks with the history. That is how you sound like one business, not a series of strangers. You also avoid calling about a quote that was already accepted this morning.
The customer record is the briefing. The task is the prompt to open it.
- ✓What is due
- ✓What is waiting on them
- ✓What is waiting on you
- ✓What was already done this week
“When I was off, my to-do list was off with me. Customers still needed the callbacks. Once tasks sat on the customer, the person covering just worked the list. I came back to completed work, not a pile of guilt.”
Close tasks when the fact changes
Done means done on the record. Leaving completed tasks open trains everyone to ignore the list. Then the list is as useless as the notebook you abandoned.
If the work moved (they asked for Friday instead of Tuesday), change the date. Do not leave Tuesday overdue as a monument.
Team tasks versus private noise
If only you can see it, it is not a team task. Put it on the customer or it will vanish when you are out. Recurring private rituals (your own Friday admin) can stay private. Customer promises cannot.
Make that distinction explicit. New staff should never have to guess which list is real.
A day run from the customer list
Morning: overdue and due today, by customer. Each one opened with the notes. Each one closed or moved. Afternoon: new promises from calls become tasks before you pick up the next job.
That rhythm is enough. You do not need a project methodology. You need the work next to the person it is for.
Name the customer, the reason, and the day
Call Jane Tuesday about the quote. That is a task. Admin is not. Follow up is not, until you say who, when, and why.
If you cannot name the customer, it may not belong in the CRM. If you can name the customer, it does not belong only in your head.
Write the reason in the same breath. Future you, and the person covering you, will not remember the vibe of the call. They will remember a date if you give them one.
Open the customer before you ring
Before you ring, you should see open tasks with the history. That is how you sound like one business, not a series of strangers. You also avoid calling about a quote that was already accepted this morning.
The customer record is the briefing. The task is the prompt to open it.
If you dial from a private list, you will skip the briefing. Then you will invent the conversation again.
- ✓What is due
- ✓What is waiting on them
- ✓What is waiting on you
- ✓What was already done this week
Close it when the fact changes
Done means done on the record. Leaving completed tasks open trains everyone to ignore the list. Then the list is as useless as the notebook you abandoned.
If the work moved, they asked for Friday instead of Tuesday, change the date. Do not leave Tuesday overdue as a monument.
Overdue that is not real is how people stop believing overdue. Then the real late work hides in the pile.
Start the morning from due work
Morning: overdue and due today, by customer. Each one opened with the notes. Each one closed or moved. Afternoon: new promises from calls become tasks before you pick up the next job.
That rhythm is enough. You do not need a project methodology. You need the work next to the person it is for.
Team tasks versus private noise should be explicit. Recurring private rituals can stay private. Customer promises cannot. New staff should never have to guess which list is real.
Promises become tasks before the next ring
The dangerous gap is the ten minutes after a call. You mean to write the next step. The phone rings. The step stays in the air.
Write it before you pick up again. That is the whole discipline. Tools cannot do that part for you.
Shared ownership without shared shrugs
A task can move to another person. It should not sit on 'the office'. Named people get things done. Named rooms do not.
If two people own it, neither does. Pick one. Add a note for the other.
Foxtra keeps tasks on the customer so follow-up is part of the record, not a side notebook. Write the next step when you make the promise. Close it when the fact changes.
Write the next step when you make the promise. Close it when the fact changes. If only you can see it, it is not a team task.
Put it on the customer or it will vanish when you are out. A date, an owner, and a reason are the whole requirement.
Milk can stay on your phone. Customer promises stay on the customer. That split is how leave stops being a risk.