Where the Week Actually Goes

What this is for

You own a business with a handful of employees, and you are still the one who answers the new inquiry, builds the quote, moves the schedule, sends the invoice, and chases the person who did not pay. Everyone tells you to automate something. Nobody can tell you what, because nobody knows where your week actually goes, including you.

This is a one-week log and two prompts that turn it into a map of where work stops and waits for you. It does not recommend software and it does not hand you a number. What it gives you is the list of moments your business cannot move without you, ranked by how often they happen.

Before you start

• One week. A normal one, not a quiet one and not the worst one you have had this year.
• A notes app or a paper pad at your desk. This log is short enough to keep on paper.
• Nothing to install, nothing to sign up for, no tool to pick. Picking tools before you know the answer is the mistake this document exists to prevent.

One rule carries the whole exercise: log where the work waits, not how long tasks take. Time tracking tells you that quoting takes 40 minutes. That is not useful, because quoting has to take 40 minutes. What is useful is that a quote sat for two days because it needed your pricing call, and the customer called twice in the meantime. The waiting is the problem. The task is just work.

The five jobs

Almost every service business runs the same five jobs, over and over, whatever the industry:

1. A new inquiry arrives. Someone calls, emails, fills in a form, or walks in.
2. A quote or estimate goes out. Somebody prices the work and sends it.
3. The work gets scheduled. A person, a van, a room, or a slot gets committed.
4. An invoice goes out. The work is done and somebody bills for it.
5. Somebody chases. The quote nobody answered, the invoice nobody paid.

You may call them different things, and one may not apply. Use your names. The point is that these five repeat every week, which means every delay in them repeats every week too.

The log

For one week, every time one of the five jobs moves, write one line. That is the whole method.

Four fields, one line, ten seconds. If you write more than that you will stop by Wednesday.

Two things to be strict about. Record the wait even when the wait was reasonable, because "reasonable" is doing a lot of work in that sentence and you want to see how often it happens. And record the second and third touches, not just the first. A job that comes back to you three times is the one worth knowing about, and it is invisible if you only log where things start.

By Friday you will have somewhere between 20 and 60 lines. That is enough.

The prompts

Prompt 1: Turn the log into a handoff map

Use either ChatGPT or Claude. Strip customer names to initials before you paste; your own staff's first names are fine. Your log is a description of how your business runs, so if any line carries a real price, a margin, or a customer's financial situation, either take it out or run this in a business-tier account that is contractually confirmed not to train on your data. The One-Page AI Policy has the tier distinction in full.

ROLE: You are an operations analyst who maps how work moves through
small service businesses. You are looking for handoffs and waiting,
not for tasks to speed up.

CONTEXT: I own a business with [NUMBER] employees doing [WHAT YOU DO,
e.g. residential HVAC service and installation]. Below is one week of
log lines. Each line records a job moving, who touched it, and where
it waited.

MY LOG: [PASTE YOUR LINES]

CONSTRAINTS:
- Do not recommend any software, tool, app or vendor. Not one.
- Do not score, grade, rate or rank my business on any scale.
- Group the lines by which of the five jobs they belong to: new
  inquiry, quote, schedule, invoice, chase.
- For each job, describe the path the work took in plain sentences,
  naming each handoff.
- Mark every point where the work waited on me specifically, and
  say how many times that happened during the week.
- Where my log is ambiguous, say so rather than guessing.

OUTPUT FORMAT: One short section per job. Each section has the path
in two or three sentences, then a bulleted list of the waiting points
with a count. End with a plain list titled "Places this week stopped
and waited for you", ordered by how often each occurred.

Prompt 2: Separate the decisions from the tasks

Run this on the output of Prompt 1, in the same conversation.

ROLE: Same analyst. Now you are sorting the waiting points you just
found.

CONTEXT: Use the list of waiting points from your previous answer.

CONSTRAINTS: For each waiting point, sort it into exactly one of
three kinds and say which in one line:
- A DECISION only I can make (a pricing call, bending a rule for a
  long-standing customer, whether to take on a difficult job).
- A DECISION I could hand over if someone knew the rule I use, but
  the rule has never been written down.
- A TASK that waits for me for no real reason other than habit,
  access, or nobody else having been shown how.

Do not tell me to delegate anything. Do not suggest tools. If you
cannot tell which kind something is from my log, say that, and tell
me what you would need to know.

OUTPUT FORMAT: Three lists under those three headings. Under the
second heading only, add one sentence per item naming the rule that
would have to be written down for someone else to make that call.

What the map tells you, and what it does not

The second list from Prompt 2 is the interesting one. Those are the decisions that feel like judgment but are actually a rule you have never said out loud. They are the largest single source of you being in the middle of your own business, and they are the cheapest thing to fix, because writing the rule down costs you an afternoon and no money. Write Down How It Actually Works is the next step for exactly that.

The third list is the one that will annoy you, because most of it exists for no reason at all. Someone does not have the login. The customer only has your cell number. The paperwork lives in your truck.

The first list is the good news. Those are the decisions you should be making. A business where the owner makes the pricing calls and nothing else waits on him is a well-run business, not a broken one.

What this map does not do is tell you what to buy. It cannot, and neither can anyone who has not seen your week. Anything that reads your business and hands back a readiness percentage or a maturity grade is selling you something, and the number is the packaging. You now have something better than a number: a list of specific moments, with counts, in your own words.

Where this goes wrong

• You log a quiet week because it is the comfortable choice. A quiet week has no waiting in it, which is exactly the data you need. Log the normal week even though it is the week you least want to be writing things down.
• You start fixing things on Tuesday. The log stops being a record of your business and becomes a record of you behaving well for four days. Change nothing until Friday.
• You log tasks instead of waits. "Did quotes, 2 hours" tells you nothing. "Jen's quote waited until Thursday because I had not called back about the access issue" tells you everything.
• You treat every wait as a failure. Some waiting is you doing the job you should be doing. The point is to see which is which, not to drive the number to zero.
• You skip the second and third touches. The job that bounces back to you twice is the expensive one, and it only shows up if you log every time it moves.

The 2-minute version

Write four fields on a pad for one week: which job, what moved it, who touched it, where it waited. Cover new inquiry, quote, schedule, invoice, chase. Do not change anything until Friday. Then run the two prompts and read the middle list, the decisions you could hand over if the rule were written down. That list is where your week is going.

---

More where this came from. The resource library has 23 free guides like this one, written for people with real careers rather than developers.

Weekly, on Tuesdays. The GenXcelerate newsletter: practical AI intelligence for people who already know how to do the job. Subscribe free.

Experience Is the API. GenXcelerate