How to write a meeting purpose in one line

The one-line meeting purpose test works like this: before you send the invite, write one sentence saying what will be true when the meeting ends. If that sentence will not come, the meeting is not ready to book.

The line is not the agenda. It comes before the agenda, it is shorter, and its only job is to decide whether the agenda ever needs writing.

What a line that passes looks like

A passing line names one outcome, in plain words, so that someone who was not in the room could check afterwards whether it happened.

"By the end, we know which of the two suppliers we are signing with." Or: "By the end, the launch date is on the calendar, or we know what is blocking it."

Read those again and notice the property they share. Each one is checkable. That is the whole mechanism, and it is why the test bites hardest on the meetings you would rather not examine.

• It names one outcome instead of a subject area.
• It is written as though the meeting has already happened.
• An outsider could tell whether the outcome arrived.
• It fits on one line, with no comma quietly stapling two meetings together.

That last point catches more meetings than people expect. If your sentence needs an "and" in the middle, you have booked two meetings and you will run out of time inside the first one.

The lines that fail, and what each failure tells you

A sentence that refuses to arrive is information, and the shape of the failure usually points straight at the real problem.

• "Sync on the roadmap" contains no outcome, which normally means you have reading to send rather than a meeting to hold.
• "Discuss the pricing changes" describes the method and skips the result.
• "Align on the goals" is a feeling wearing a verb, and nobody can check a feeling.
• "Touch base" means you want contact with a person, which is a fine thing to want and a strange thing to disguise.

I think "discuss" should be barred from invite titles. Discussion is how a group gets somewhere. It is never the somewhere, and putting it in the purpose line is how an hour goes missing with everyone behaving impeccably.

The failure is not always yours. Sometimes the sentence will not come because the decision genuinely is not available yet: two numbers are missing, and the meeting was booked to make their absence feel productive.

Where the line goes once you have it

Put the line in the first line of the invite description, always, and in the title whenever it fits.

Titles have room for more than a subject. "Pick the supplier (30 min)" tells people more than "Supplier discussion" and costs fewer characters. The description then opens with the full sentence, before the video link and before anything about logistics.

The line has a second job that pays for itself immediately. When someone replies asking what the meeting is about, you paste the line, and you are done, which beats writing an explanatory paragraph at eleven at night to a person who wanted six words.

My own first attempt at the line is usually a mumble: two clauses of throat-clearing and no outcome anywhere. I write it in the invite box and fix it before sending, and taking the Direct rewrite from Unvent in that box is what stops the mumble from shipping just because it was already typed.

The line also decides who gets invited

Once the sentence exists, the invite list writes itself: you invite the people who can change whether that sentence comes true.

• Whoever will be held to the outcome needs to be in the room.
• Whoever holds a piece of information that cannot survive being written down needs to be there too.
• Everyone else gets the result afterwards, in two lines, whenever they open it.

Adding someone "for visibility" is a request that they spend an hour learning something you could have told them in a message. It looks generous and it is expensive. If you want a person informed, inform them.

When the line will not come

If the sentence still refuses after two honest attempts, take one of three moves instead of booking the room.

Send what you have in writing and name the single thing you are missing. Plenty of the meetings I have wanted to call while building Unvent turned into a message with one question at the bottom, and the answer came back before the slot I was about to block out. A written ask that ends in a decision beats a meeting that ends in "let's regroup".

Wait. Some meetings are early rather than wrong, and the question has not formed yet. A week of the work forming it is worth more than an hour of six people watching it fail to form on a call.

Or state the real reason out loud. "I want twenty minutes to talk through how the project has been going" passes the test, because anyone can tell afterwards whether the talking happened. The test allows conversation. What it refuses is vagueness dressed up as an outcome.

Read the line again at the end

The same sentence closes the meeting: read it out, answer it, and let the answer decide whether the meeting continues.

If the answer is yes with fifteen minutes left, stop there. Handing people back their time is the only reward this format offers, and a group that receives it once starts writing sharper lines without being asked.

If the answer is no, say what blocked it and who owns clearing the block, then think hard before rebooking the same line for next week. The same purpose line surviving three weeks in a row means you are running a status broadcast in a meeting costume, and status is cheaper written down and read on everyone's own schedule.

Asking other people for their line

You can run the test on meetings you did not call, and it comes across better than you expect.

"Happy to join. What should be settled by the end?" is a normal question in a normal tone, and it produces one of two useful results. Either you get a line and can prepare for something real, or the organiser discovers they do not have one while there is still time to build it, which they will not thank you for out loud.

Some people will read the question as a challenge to their authority. That risk is real, and it is still worth taking, because the alternative is sitting through the meeting composing the same question silently and getting nothing for it.

What surprised me was how few of my own sentences survived the test in the first week of using it, and how much of the week opened up once I stopped rescuing the ones that failed.