Texts.Analyzer

Checklist

Confirming Plans Over Text: A Five-Line Checklist

A plan agreed in text is not a plan. It is a plan's first draft, and the gap between "yeah let's do thursday" and a Thursday that happens is where most of the interesting information sits.

This is a short checklist for confirming plans over text, written to be used before you send the message rather than after.

The four-part message

A plan that survives contact with two calendars names four things:

  1. A day — not "this week" or "soon".
  2. A time — even approximate, like "after work" with an hour attached.
  3. A place or an activity — something specific enough to be said out loud.
  4. Who confirms last — a real question, not "sounds good".

Compare: "sounds good!" with "great — thursday 7 at the noodle place on 4th? i'll book if you're in". The second one can only fail honestly.

The checklist before you send

  • Is there a day in the message?
  • Is there a time, even an approximate one?
  • Is there a place or a plan?
  • Does it end in a question that requires a yes or a no?
  • Have I avoided the words "sometime", "soon", "we should"?

Five lines, twenty seconds. It converts a warm exchange into a decision.

Reading the reply

Once the message is specific, the reply is informative:

Reply What it tells you
Suggests a different day Interested, and actually checking
Asks a detail ("which one?") Interested, moving toward yes
"yeah for sure" with no follow-up Warm, uncommitted
Changes the subject Not now
Nothing for two days Not now, possibly not ever

None of those is an insult. The point of being specific is that you stop needing to guess.

The follow-up rule

One follow-up, twenty-four hours later, and then stop. One follow-up is normal organising behaviour. Three is a different conversation, the one where you are doing the work of two people.

If a plan needs more than one nudge to become real, the plan is not the issue.

Where the counts come from

If you want to know whether this is a one-off or a pattern, look at the thread over a month: how many plans were agreed, how many happened, and who brought them up. The analyzer cannot tell you what happened in real life — that part sits on your calendar — but it can tell you whether the proposing was one-sided.

That is the honest divide. Text gives you the proposal count; only a Thursday evening gives you the answer.