Why this tool has a ceiling

Deadlinewatch holds up to 1,000 active deadlines. It says so on the pricing page, in the FAQ, and in the machine-readable file the AI assistants read. That number is a decision, and I want to explain why I would rather publish a ceiling than claim there isn’t one.

Start with what 1,000 actually means. This is a single-seat tool for one person’s working life, and the rest of the site describes carrying a dozen deadlines at a time. 1,000 live commitments in front of one person is an enormous number. It is the true scope of the tool, stated honestly, and it sits far enough above real use that you should read it as headroom rather than a budget.

Testing found the edge, so the edge became a feature

Every product has a point where its scope ends. Most never find theirs, and their users find it instead.

Pre-launch testing pushed Deadlinewatch well past any realistic load to see what happened at the far end, and that is where the number came from. Past a certain volume the underlying data layer would return a full page of deadlines and stop, and the ones it stopped at were the furthest in the future.

Picture what that does to a chart. You open the Forecast to read the year ahead, and the far end of it is thin. Not empty. Just light. Which is exactly what a genuinely quiet stretch looks like. Nothing on screen separates “April is clear” from “April is past where the view reaches”, and the second one would be a chart quietly misleading you in the one view built to show what’s coming.

Finding that in testing is what turned it into a feature instead of a support ticket.

The limit belongs where you add, not where you read

Deadlinewatch counts your active deadlines when you add one. If the next one won’t fit, it tells you, and it doesn’t add it.

Refusing a deadline is a real cost and I won’t pretend otherwise. But look at the 2 outcomes side by side. One is a sentence at the moment you are doing the thing, telling you where you stand and what frees up room. The other is a chart that leaves things out and looks composed doing it. That second one is the failure this product exists not to have.

Checking at the door buys something a bigger number never could. Because writes are capped at or below what a single read returns, a view with rows missing became impossible rather than unlikely, for every screen in the tool today and every one I build later. That is a stronger guarantee than a promise to be careful, and it holds without anybody having to remember it.

What counts, and what doesn’t

1,000 is your working set, not a lifetime total.

Completed deadlines don’t count. Anything On Hold doesn’t count. Those live on their own surfaces with their own paging, so years of finished work never touch your capacity. Finish something and the room comes back the moment you click. Set something aside and the same thing happens.

That is what makes the number honest enough to publish. A lifetime cap on a tool you use for years is a countdown, and a countdown is one more thing to manage. Deadlinewatch has no business handing you one of those.

Nothing shows you a counter until you pass 800. Below that a usage meter would be anxiety with no purpose, on a product whose whole pitch is less of it. Deadlinewatch states what is true and stops there, and a number you cannot act on is not worth stating.

Repeating deadlines run 2 years out

The second limit measures time rather than count.

Repeating series in Deadlinewatch are created up front, every occurrence a real date on the calendar from the start, because that is what makes them dependable. But “create 60 of them” means wildly different things depending on cadence. 60 weekly occurrences is a bit over a year. 60 yearly ones reach into 2086.

Dates in 2086 are not generosity, and the reason has nothing to do with storage. Annual obligations move. A filing date that falls on the 15th this year is not reliably the 15th in 9 years, because those dates roll for reasons that have nothing to do with you. Generating a decade of them means generating 10 future dates that are probably wrong and presenting them as facts.

A series builds 2 years ahead at a time, which is past the furthest view in the tool, and the card tells you when the set is running low so you can extend it. A short horizon you renew on purpose beats a long one you have to take on trust.

Streams cap for a different reason

Streams stop at 100, and that number comes from somewhere else entirely.

The deadline cap is about what a query returns. The stream cap is about what a person can pick from. Every stream you haven’t archived appears as a chip in the picker, and well short of 1,000 that stops being a picker and becomes a scroll.

100 is roughly 5 times what a heavy user keeps, and past the point where organizing this way works at all. Streams are categories, not a row per client. Archive one you’ve finished with and the slot comes back, with nothing inside it lost.

Naming a ceiling is the same discipline as taking things out until only the necessary remains. A stated scope is a finished decision. An open one is a decision nobody has made yet.

Saying where you stop

There’s a line I keep returning to. If we say something works, it needs to work, or we put a limit on it.

“Unlimited” is the easy claim, and it costs nothing to write. It also stays true right until the day it doesn’t, and the person who finds out is your user, and the way they find out is that something they trusted was quietly incomplete. A stated ceiling is the smaller promise and the better one. You can check it. I can test against it. And everything underneath it becomes dependable rather than merely untested.

The number is not really the point. The point is that Deadlinewatch knows where it stops and tells you, rather than working it out on your behalf at the far end of a chart.

Common questions

How many deadlines can one account hold? Up to 1,000 active deadlines. Completed deadlines and anything On Hold sit outside that number, so it limits what you are working on at once rather than the life of the account. Marking something complete or setting it aside frees room immediately.

Is 1,000 enough? For one person, comfortably. Deadlinewatch is a single-seat tool and the rest of the site describes carrying about a dozen deadlines at a time, so 1,000 live commitments is far above real use. It is the true scope of the tool, and it is stated rather than implied.

What happens if I reach the limit? Adding a deadline is refused, with a message telling you where you stand and what frees up room. Nothing is deleted and nothing is hidden. Past 800, Add dates shows your usage, so the ceiling is never something you meet at the door.

What happens if I import a spreadsheet that’s too big? It imports nothing and gives you both numbers, how many rows you are adding and how much room is left. Filling to the brim and leaving the rest behind would mean you couldn’t tell which rows landed without auditing the file by hand.

How far ahead do repeating deadlines get created? 2 years at a time, and the series tells you when it is running low so you can extend it. That is past the furthest view in the tool, and it avoids building a decade of annual dates that were always likely to shift first.

How many streams can I have? Up to 100 active streams at once. That ceiling is about usability rather than storage, because every stream appears in the picker when you assign one. Archived streams don’t count toward it and nothing inside them is lost.