Quotes waiting on a yes. Invoices waiting on payment. Signatures, documents, vendors, candidates. This guide covers what the chasing costs, why it fails without a sound, and five rules for follow-up that runs on its own.
Free · about 8 minutes · no signup
The same five open loops, tracked two ways. In A the only tracker is a person, so a stall produces nothing. In B every loop has an owner and a clock, so the stall raises the alarm.
01Chasing is a hidden job
A maintenance coordinator at a property management company described the real day like this.
“I genuinely feel like 80% of my job is just chasing people.”Maintenance coordinator, posted on Reddit
VendorChasing the certificate of insurance.
CustomerChasing the signed quote.
CandidateChasing the candidate who went quiet.
Your own teamChasing the status update you need before you can chase the customer.
None of this is on a job description. It grows with every customer you add. And it lives in someone’s head: a flagged email, a sticky note, a feeling that you should hear back by Thursday.
That is why follow-up never fails loudly. It just stops, and nobody is assigned to notice.
Example math. Hours already being spent, times a rate you already pay, times 52 weeks. Put in your own numbers with the calculator below.
02The five rules of follow-up that runs itself
The five rules work as one system. R1 sets the owner and the deadline. R3 caps the reminders. R2 hands the conversation to a person when there is a reply. R4 sets what a reminder says. R5 watches the whole thing.
R1
Every open loop gets an owner and a clock.
A quote sent, an invoice issued, a document requested: each one is an open loop. The moment it opens, the system should know who owns it and when it is overdue. If the answer lives in an inbox, you do not have follow-up. You have hope.
R2
The system chases, people close.
Automate the reminders: the day 3 nudge, the day 7 note that points to the paperwork. The moment the other side replies, a person takes over.
R3
Cap the reminders, then change the state.
Endless reminders teach people to ignore you. Send two or three, then the loop changes state: escalate to a phone call, park it with a revisit date, or close it and say so.
R4
Chase with the facts.
A good reminder names the quote or invoice number, the date, and the last email, and asks for one specific thing by one specific date. Keep it under 120 words.
R5
A stalled chase must announce itself.
This is the one everyone skips. If the reminders stop because an email address changed or a link between two tools broke, someone needs an alert that says “this loop should have moved and did not.”
03Run your own chase audit
One page, about twenty minutes. Tick each step as you go.
04What chasing costs you
Use your own numbers. The result stays on this page.
Tool · chase cost calculator
Which loops are worst?
05What it looks like when the chasing stops
Two loops running on their own clocks. A person steps in twice: once to start it, once when the other side answers. The owner reads one line a week.
A quote goes out. On day 3 the system sends a reminder with the quote attached. On day 7 it names the quote number and asks for a yes, a no, or a date. The rep only steps back in when the customer replies.
A vendor’s insurance certificate expires in 30 days. The vendor gets the request with the policy number and a date. At 14 days it goes to a person, because now it is a risk, not a reminder.
The point
None of this needs new staff or a new platform. It needs open loops treated as records with owners and clocks, not memories in someone’s head.
Want one loop running on its own?
Pick the loop your audit flagged. I will map its clock, cap and escalation with you and tell you what it takes to build on the tools you already use.
