Date Plan Sanity Check: Four Tests Any Plan Has to Pass

You already have a plan, or the beginning of one. These four tests say whether it has a structure behind it — and the whole check takes about a minute.

What the four tests are, and why they catch almost every plan that fails

A date plan is not judged by the places in it. It is judged by whether it survives the evening.

The four tests look at structure, not taste. Anchor: one decision is clearly the point of the night, with everything else arranged around it. Timing: there is visible slack between stops, not a minute-by-minute schedule. Booking: the plan says what to book first and how far ahead. Failure logic: it says what to cut first and what to protect.

None of the four is about which place you picked, and that is the point. Taste is personal; structure is checkable in about a minute, and structure is what breaks. A plan can name the perfect table and still fall apart at 7:40pm, because nothing in it said what to do when the table is not ready.

They catch almost everything because they are the four decisions a plan has to make before the night starts: where the weight goes, how much room there is, what has to be secured, and what happens when a piece fails. Answering all four is not a good night — nothing can promise that — but it is a plan. Answering none of them is a list of stops with times attached.

All four also fail quietly. Nothing announces that a plan has no cut list; you find out at the moment you need it, standing on a sidewalk, with someone waiting for you to decide.

Why a plan that is only a list of venues fails all four

Most plans people write for themselves look like a list: three or four good places, roughly in order, with an idea of when to start. It reads well, and it feels like planning. Run it through the four tests and it fails every one.

Anchor fails because a list has no ranking: four equally good options are four decisions deferred to the street corner.

Timing fails because a list has no clock. Venue names do not carry travel time, and the distance between two pins on a map is not the distance between two moments in an evening. Someone pays for the walk, the wait and the extra round, and in an unplanned evening that payment comes out of the next stop.

Booking fails because a list does not say which line matters. If everything is weighted equally, everything gets booked the same way: whenever you get around to it, in whatever order the phone happens to be in your hand.

Failure logic fails because a list assumes the list happens. There is no version of it where the first place is closed, the second is packed, the weather turns, or the person you are with is tired at nine. When one of those happens, the list has nothing to say, and the evening gets improvised at the exact moment nobody has the energy to improvise well.

What “visible slack” actually means in practice

Slack is not spare time, and it is not leaving earlier. Visible slack means the plan shows the room in writing, where you can point at it. Stops at 6:15 and 7:45 is visible slack: ninety minutes for one drink, generous enough that a slow start does not threaten the reservation. Stops at 6:15 and 6:45 with a fifteen-minute walk between them is not slack; it is a schedule wearing a margin as a disguise.

Three things make slack real. The travel time between stops is a written number rather than an assumption, and it is the number you got by checking. Each move carries a buffer on top of that travel time, so a late table or a slow check has somewhere to go other than into the next stop. And at least one stretch of the evening is deliberately unbooked.

That last one is the piece people resist, because an unbooked stretch looks like a gap in the plan. It is the opposite: an unbooked stretch is where the night gets to be better than the plan — the second round, the walk that turns out to be the best part, the dessert nobody intended to order. Book every minute and you have a schedule, not a plan.

One question tests it. If the first stop runs thirty minutes long, what breaks? If the answer is the next stop and everything after it, there is no slack, whatever the timeline looks like. If the answer is nothing much, the room is built in.

Why failure logic is the part everyone skips

Anchor, timing and booking all describe the night going well. Failure logic is the only one that describes it going otherwise, which is exactly why it gets left out. Nobody enjoys writing the sentence about what to cut.

There is a subtler reason too. A fallback is an admission that the plan might not work, and a plan you are excited about does not want that admission. So the fallback stays unwritten, and its absence stays invisible right up until the moment it is expensive.

Failure logic has two halves, and both are short. The first is a cut order: what goes first when the night runs short on time or energy. The second is a protection: the one stop the rest of the plan exists to defend. Written down, those two lines take a minute. Improvised at nine at night, they cost more.

The test is whether you can answer both without stopping to think. If you have to reason it out on the night, you are deciding under pressure, in public, with someone watching you do it. “Skip the first stop, protect the anchor” is a sentence you write in daylight, and it is the whole of Plan B.

How to fix a plan that fails two or more tests

Failing two tests is normal for a first draft, and it is fixable in about twenty minutes if you work in the right order. Patch the gaps separately and you end up with a plan that has four repairs in it.

Start with the anchor, because everything else sits downstream of it. Name one stop as the point of the night and demote the rest. If two stops both feel essential, cut one — not because it is bad, but because a night with two priorities has no priority when the first thing goes wrong. Every other stop can then be judged against a question it could not answer before: does this help the anchor, or compete with it?

Then fix the timing around that anchor. Write the travel time between each pair of stops, add a buffer to each move, and leave one stretch of the evening unbooked. If a stop no longer fits, cut the stop rather than shortening the buffers you just added — the buffers are the part doing the work.

Then fix the booking order. The stop that is hardest to replace gets booked first, whatever else is convenient, and it gets a day to be booked by.

Then write the two lines of failure logic: what gets cut first, and what is protected. If a stop is exposed to weather, a queue or a closed door, name the alternative in the same line.

If three or more of the four tests fail, treat it as a rewrite rather than a patch — adding a buffer to a plan with no point of the night does not fix much. Write the anchor line first, then the timing, then the booking order, then the fallback. Structural fixes are cheap at the start and impossible at the end.

FAQ

What does the sanity check actually test?

Four structural tests: whether one decision is clearly the anchor, whether there is visible slack in the timing, whether the plan says what to book first and how far ahead, and whether it says what to cut and what to protect. It does not test taste, budget, venue quality or whether the two of you are suited to each other.

How is the score calculated?

Ten questions, two or three per test. Each answer scores 2, 1 or 0. A test passes when it earns at least two thirds of the points available to it: 3 of 4 for Anchor and Booking, 4 of 6 for Timing and Failure logic. A question left unanswered scores 0 and marks its test incomplete rather than failed.

Does the check store or send my answers?

No. Your answers stay in your browser and are not sent to us. Pinterest visits may contribute anonymous page and tool-use counts; campaign labels are kept in session storage for 30 minutes of inactivity. See our Privacy page for details. Close the tab and your answers are gone.

Can a plan pass all four tests and still be a bad night?

Yes. The check reads the structure of a plan and nothing else. It cannot know the two people, the city, the budget, the occasion or how the evening feels, and it makes no promise about how a night will go. Passing four tests means the plan has a shape to follow, not that the evening will work.

Related reading

• What a date plan looks like: a full sample, annotated against the four tests
• What a Date Night Plan Should Include: A Practical Checklist
• What a Date Night Should Actually Cost (and Where the Money Really Goes)
• Last-Minute Anniversary Plans: What to Do in the 72 Hours Before
• The Date Plan service: what you get for the fee