How do I write a short event description that answers people's first questions?

Think of the description as a quick decision aid. A reader should be able to tell, in a few seconds: Is this for me? What will I do? When and where is it? Is there anything I need to bring or do first?

A useful order is:

1. Audience and activity.
2. Date, time, and location or access details.
3. What participation involves, including any known cost or registration step.
4. One practical expectation, such as what to bring or whether newcomers are welcome.

Keep the opening focused on the event itself. Save background, organizer introductions, and extra program details for a longer page if readers need them.

Do not guess or phrase an undecided detail as settled. First decide whether readers need that information before they can plan. If it matters, confirm it with the organizer before publishing. If you cannot confirm it yet, use a clear placeholder in your draft—such as [registration details] or [cost, if any]—and replace it before sharing.

For a detail that is genuinely not decided, say so plainly only if the event description must go out now: “Registration and any fee: [details to be confirmed].” That signals the information is incomplete rather than implying there is no registration or no cost. Avoid adding logistics that do not apply just to fill out the description.

Yes. Here is a copyable draft using explicit placeholders; the example does not claim any real event details:

“Join [audience] for a neighborhood seed swap on [date] from [start time] to [end time] at [venue and address or access details]. Bring [what participants should bring, if applicable] to exchange with others; [briefly describe what happens if someone has nothing to swap]. [Registration or cost details, if applicable].”

The first sentence identifies the activity and audience, then gives the basic logistics. The next part sets expectations about taking part. Keep only instructions the organizer has confirmed. For instance, if bringing seeds is optional, say that; if you do not know, leave the placeholder rather than writing “everyone should bring seeds.”

Describe what a person can expect instead of promising how they will feel. A specific, confirmed welcome is more useful than a broad claim. For example, if accurate, you might write, “New to seed saving? You are welcome to come and ask questions,” or “You can browse before deciding whether to swap.” These lines answer practical concerns about joining in.

Be careful with claims such as “all ages,” “accessible,” or “no experience needed”: include them only when the organizer can confirm what they mean for this event. If a reader may need a particular access detail, name it precisely when known, or provide a placeholder for the organizer to check. A short description can be warm and still stay factual.

Fill in this worksheet before writing the paragraph:

• For: [who the event is intended for]
• Activity: [what participants will do]
• Date and time: [date, start time, end time, and time zone if relevant]
• Place or access: [venue and location, or online access details]
• Participation: [what to bring, how to join in, or whether anything is required]
• Cost and registration: [confirmed details, or a reminder to verify]
• Expectation: [one useful detail, such as whether newcomers are welcome, if confirmed]

Then turn the answers into two or three short sentences. Check that the first sentence names the event and that the logistics are easy to spot. Remove repeated phrases, background readers do not need to decide, and any unverified promise. Before publishing, replace every bracketed note with a confirmed detail or remove it if it is not relevant. If a key fact remains unknown, ask the organizer rather than silently filling it in.