Caseload

One thing arrives. It turns into forty.

A customer emails asking whether you are compliant. Nine weeks later it is fifteen requirements, two government portals, an annual obligation, questions for your IT person and a letter to every supplier. Nobody wrote that down. It accumulated.

Open it

The problem is not the list

It is that the list does not exist yet. Between the thing arriving and the work being doable sits a step nobody owns: working out what it means. That is where this kind of project goes to die.

One thing in, many things out

Three screens

Today

Say how long you have. It tells you what fits, ordered by what it costs to delay rather than by what is due.

5 min  Send Eric the 13 IT questions
        then 14 days of somebody else's time.
        Start by 6 Oct or the end date moves.

Cases

One row per arriving thing, saying how much needs you now rather than how many tasks exist. Seventeen tasks with fifteen blocked reads as urgent and is not.

Timeline

What is coming, then what happened, across every case. Kept apart: a deadline is a debt and a finished thing is a payment.

Four rules it will not break

Your time and other people's time are counted separately

A three minute email with two weeks of waiting behind it beats an hour of writing that waits on nobody. No list sorted by size or due date can show that.

It never claims to have seen something it did not

An email it sent is recorded as observed, with the message id. You saying you sent one is your word, in a different colour. A record that cannot tell evidence from recollection fails an audit.

"Not sure" is a real answer

Ask a colleague fourteen questions and "not sure" is a button of equal weight. Offer only yes and no, and whoever does not know picks the answer that ends the conversation.

It is allowed to tell you it does not fit

If your time cannot reach the deadline it says so, with the number. A planner that always produces a plan is a planner that lies for a living.

What it is not

Not a task manager. You have four of those and the problem was never storage. Nothing to connect: no consent screen, no integration project. Drop a document in, or paste an email. And it never holds regulated material, because a tool built to help with compliance must not become why you fail it.

Where it actually is

One real project end to end, plus a second to prove nothing is shaped around the first.

59things one email became
348minutes of work found
93startable today
643assertions holding it up

Caseload is a working title. And the honest limit: a person or a model still has to read the arriving thing and decide what it means. Nothing here does that. It holds the answer, checks it for holes, and hands back the next five minutes.