Task

Finished work that is waiting on something before it can be billed

The waiting pile has no alarm.

Finished work can sit in a waiting pile long after the thing it was waiting on has happened.

Not every business has this problem, and some should leave it alone.

Most of these can be handled better. Whether it's worth doing is a separate question. What follows is one common form of the problem, described in general terms, because your version will differ. These are possible challenges, not a description of your business, and some should be left exactly as they are. If it sounds like your week, that's worth a conversation.

Watch: Owed, but Never Asked For

Sound familiar?

The same jobs have been "waiting on paperwork" for months.
Nobody could say how much finished work is sitting unbilled right now.
The sign-off came in, but the job never moved.
The waiting list only gets looked at when cash is tight.

What it looks like

The work is done, but the bill cannot go out yet. It is waiting on something: a sign-off from the customer, an inspection, a delivery receipt, the next stage of a larger job, or a document from somebody else.

So the job goes on a pile. It might be a folder, a tab in a spreadsheet, or a status that nobody filters on. The pile is meant to be temporary. Jobs arrive in it every week. Leaving it depends on somebody noticing that the thing it was waiting on has happened.

What it costs

The waiting pile has no alarm. When the sign-off or the receipt finally arrives, it goes to whoever asked for it, not to the pile. The job keeps waiting for a reason that no longer exists.

The reason goes stale without anyone saying so. The inspection happened last month. The paperwork is in somebody's truck. The note on the job still says waiting.

Older is harder. Chasing a sign-off months after the work is awkward, and the person who knows the job may have moved on. Some billing arrangements also have a window for submitting a bill. Once it closes, the claim can be harder to make or no longer possible.

Nobody knows how big the pile is. Real holds and forgotten jobs sit together, so the total looks like normal business.

Where it goes wrong

Nobody owns the pile. Everyone adds to it. Nobody is responsible for emptying it.
The reason is not written down. A job marked waiting with no note cannot be chased, because nobody knows what to chase.
The thing it was waiting on goes somewhere else. The receipt, the sign-off, or the inspection result lands in an inbox or a folder with no link back to the job.
The pile is reviewed only in a crisis. It gets worked when cash is short, and then all at once.

What a better version looks like

Each waiting job carries three things: what it is waiting on, who is getting it, and when somebody last checked. The pile is reviewed on a regular schedule, oldest first, and anything past an agreed age is raised.

When the missing item arrives, it is matched to the job that was waiting for it, so the job is raised for somebody to move instead of waiting for somebody to remember.

What still needs a person

A person chases the sign-off and talks to the customer. A person decides whether part of the work can be billed now. And a person decides when a job has waited long enough that it should be written off or escalated, which is a judgment about the customer, not the list.

Questions worth asking about your own operation

Where do finished jobs go when they cannot be billed yet?
Does each one say what it is waiting on?
When the missing item arrives, how does the job find out?
How old is the oldest job on that list today?

If this sounds familiar

Bring me the version you actually have. I'll learn how the process really works before I suggest anything. If it isn't worth changing, or isn't a fit for me, I'll say so. Talk through a problem