Retainers, maintenance, compliance, training, support, facilities. All real work, all owned by someone, none of it heading toward a finish line. Almost every project tool is built on the assumption that a project is a thing that ends — and that single assumption is why your delivery numbers do not survive contact with reality.
The first is whose work it is: a customer's, or your own. The second is whether it ends. Almost every tool models the first and treats the second as a given.
Because the two are independent, all four combinations occur, and each one is ordinary. A client implementation with a go-live. An internal migration with an owner and a date. A managed-service retainer. A standing internal capability like training or compliance that has no end and never should.
Both rows are ordinary work. Only the top row fits a conventional project tool, which is why the bottom row ends up in a spreadsheet, or nowhere at all.
When a tool offers only the top row, the bottom row does not disappear. It gets forced into the available shape — usually a project or task that is opened once and never closed — and from that moment it is quietly corrupting everything the tool reports.
This is easier to see as arithmetic than as an argument. Four items, one of which is a retainer.
A worked example, not a claim about your business. The point is the shape: the same four items produce meaningless figures in one arrangement and answerable ones in the other.
Notice what went wrong on the left. Nobody entered bad data. Nobody was lazy. The retainer is at ninety per cent because somebody had to put a number in a field that should not have existed, and it is overdue because a date was required for something that has no end. The distortion is created by the model, not by the people using it.
And it compounds. Every additional standing item drags the average further from the truth and adds another permanent line to the overdue list. Once the overdue list contains things that will never not be overdue, people stop reading the overdue list — which is how a company ends up unable to see the projects that are genuinely late.
A metric that includes something which can never satisfy it is not a strict metric. It is a broken one, and everyone quietly learns to ignore it.
Teams do find ways around this. They are all worse than they look.
Someone quietly pushes the retainer's end date out each month so it stops showing as overdue. It works, and it also teaches everyone that dates in the system are decorative. Once that lesson is learned it applies to the real deadlines too.
The retainer moves to a spreadsheet and the dashboard becomes clean again. The cost is that a meaningful share of the company's effort is now invisible to the company, including to whoever is deciding where to put people next quarter.
"Support — September", closed at month end, recreated in October. The numbers work. What you lose is continuity: no thread runs through the work, so nobody can see what has been happening on that account across a year, which is precisely the question a renewal conversation asks.
Each workaround trades a real property away to satisfy a model that was wrong to begin with. The alternative is to fix the model.
Set independently of who the work belongs to, because the two questions are independent.
Has an end and a definition of done.
Has no end, and is not pretending to.
Standing work is not second-class. It is fully tracked, fully logged against, and appears in the manager rollup and each person's timeline exactly like anything else. What it does not do is appear in a figure that assumes a finish line.
The reporting question changes with the mode, which is the whole point. For timeboxed work you ask how far along it is and whether it will land. For standing work you ask whether it is being attended to — worked on, on the days it should have been, by whom, and what was done. Both are answerable. Neither is answerable if you insist on asking the first question about the second kind of work.
The test is not how long it runs. Some timeboxed projects run for two years; some standing arrangements last three months.
Not a date — a condition. "The plant is commissioned." "The system is live." If nobody can state one, it is standing work, however firmly a date has been written down.
Completing an implementation is a success. Completing your compliance function is not a thing that happens. If the end would be an ending rather than an achievement, it is standing.
Timeboxed work has a shape — ramp, peak, close. Standing work has a rhythm that looks the same in month two and month twenty.
A timeboxed project slips. A standing arrangement degrades quietly and nobody notices until a customer does. That difference is exactly why attendance is the right measure for one and progress for the other.
Treating a retainer as timeboxed because it has a contract end date. The contract ends; the work has no internal finish line. It is standing work with a renewal date attached.
Treating an internal project as standing because it has no customer. An internal migration with an owner and a date is timeboxed delivery and should count as such, not disappear into overhead.
It happens — an implementation that turns into an ongoing managed service is the usual case. The honest handling is to close the timeboxed project against its baseline and start the standing arrangement, so the delivery record of the first stays intact.
By attendance rather than progress: whether work was recorded against it on the working days it should have been, by whom, and what was done. That is a real measure, just not a completion one.
Yes, on their day exactly like anything else. The distinction is a reporting one, not an experience one.
That is timeboxed work with drift, and the frozen baseline is what makes the extension visible instead of absorbed. If it extends indefinitely with no definition of done, it was standing work that nobody named.
Most offer a recurring task, which is a different thing — a repeated finite item rather than a continuous arrangement. The tell is whether the tool can report on something without asking how complete it is.
Tracking mode is set on the project, independently of whether it belongs to a customer, and it governs which statistics the project appears in. See the product →
Open whatever you track delivery in and find the things that have been at ninety per cent for a year. Bring that list to a twenty-minute walkthrough and we will show you what the numbers look like once they are counted separately.