The dates you chose, and the dates you were given

Look at a full week and the first useful question isn’t what’s due. It’s what can move.

You set some of those dates yourself. You said Thursday because Thursday was reasonable, and if Thursday stops being reasonable you can pick up the phone. Others arrived from a filing window, a tender close, a court, a board that meets when it meets. Those have no give in them, and no phone call changes them.

Draw both kinds the same way and you hide the one thing a crowded week needs. You look at 9 deadlines, you know 6 of them could shuffle, and you cannot remember which 6. You rebuild that from memory every time, which is the work you brought a tool in to take off you. Or you plan as though nothing moves, which means planning for a harder week than the one you actually have. Every date that shifts makes you re-read the whole list, and this is the reading you cannot do at all.

One switch, on the date itself

Deadlinewatch gives you a padlock, and it sits directly in front of the due date on the card. Open and grey when you can move the date. Closed and red when you can’t.

You see it in both states on purpose. A control that only appears once it is on is a control nobody finds, and the padlock is not really the point. The question is. Every deadline gets asked whether its date is yours, and most of the time the answer is yes, the padlock stays open and grey, and you stop noticing it within a day.

The red is deliberate. Deadlinewatch uses 3 colors and each one means something: red for urgency, amber for priority, green for finished. A locked date is neither urgent nor important, so by that rule it should have been grey. I made it red because red is what your eye finds first, and you need this fact before you start rearranging anything. Red then came out of the palette streams draw from, so that a red dot can never mean both “the Filings stream” and “this one cannot move.”

It refuses out loud

The obvious way to build a lock is to make the drag fail. You pick a locked deadline up on the Forecast, drop it 3 days later, and it springs back. The date is protected, nothing is damaged.

That reads as a broken app, not a protected date. Everyone has used software that swallowed a gesture and said nothing, and nobody’s first thought is that it must have been deliberate. A locked deadline refuses in words instead. It tells you the date is locked and tells you to unlock it on the deadline first, and then you can move it if you meant to.

Which sets a rule I would keep in any tool. Advice that points at a control the reader cannot find is worse than no advice. The message says unlock it on the deadline, so the switch on the deadline shipped in the same pass.

That rule earned itself during this same stretch of work. The tests found a control for marking a day back on that worked correctly and had no way to reach it from the screen, which would have made marking a day off a one-way door. It was caught the day it appeared and fixed in the same pass, before it could reach anyone. That is exactly the class of thing the testing is built to find, because it is invisible to the person who wrote it and obvious to the person using it.

What the padlock is not

Two assumptions come free with a padlock, and both are wrong.

It is not a permission system. You unlock it in one click, no confirmation, no ceremony, because you own it and there is nobody else here. It stops an accidental drag on a Tuesday afternoon. It does not stop you.

It is not a record. Nothing logs that you locked it, or when, or that a move was refused. Deadlinewatch keeps no change history, and I would rather tell you that than let a padlock imply a paper trail. If you need to prove what a date was on a given day, this is not the thing that proves it.

What it is, is a note to yourself that survives the week. You write it once, at the only moment you reliably know the answer, which is while you are entering the deadline and the notice is still in front of you.

What it changes about the Forecast

The payoff is not on the card. It is on the view where you decide what to move.

The Forecast draws a heavy stretch as a shape, and a heavy stretch has always had 2 readings hiding inside it. 12 deadlines in 9 days is a scheduling problem if 9 of them can shift. It is a staffing problem, or a decline-the-work problem, if none of them can. Same picture, 2 completely different weeks, and nothing on screen told you which one you were looking at.

Now a locked date draws as a square instead of a circle, on the Curve and the Heatmap both. Squares don’t move. Look at a cluster and you can see how much of it is genuinely negotiable without opening a single deadline, and the morning briefing says the same thing in a sentence on the weeks it is worth saying.

Everything else carries on unchanged. Status, snooze, priority, and reminders each answer a different question, and this touches none of them. The lock concerns one field.

A padlock, one click, and a crowded week that finally tells you how much of itself you are allowed to move.

Common questions

What does locking a deadline do? It refuses any change to that date from every direction: a drag on the Forecast, the inline date editor on the card, or a suggested move in the reconciliation list. Rather than springing back in silence, it tells you the date is locked and says to unlock it first. Everything else about the deadline stays editable.

Why lock a date instead of remembering it’s fixed? Because remembering it is the work you brought the tool in to take on. The payoff shows on the Forecast, where a locked date draws as a square. A crowded stretch of movable dates is a scheduling problem. A crowded stretch of fixed ones is something else entirely, and you can tell which at a glance rather than opening deadlines one at a time.

Can someone else unlock it? There is no one else. Deadlinewatch is a single-seat tool, and unlocking takes one click with no confirmation. The lock guards against a mis-drag, not against a person.

Does Deadlinewatch record when I locked or unlocked something? No. It keeps no change history, so nothing logs who locked a date, when, or that a move was refused. The padlock is a working marker, not an audit trail, and that is worth knowing before anyone leans on it as evidence.

Does locking a date change reminders or anything else? No. Reminders, priority, snooze, streams, and status all behave exactly as before. The lock concerns one field, the due date.