Build a Small Text Library With Keep–Slot–Send

The awkward part of reusing an old invitation is finding every detail that no longer belongs. You change the date but miss last month’s location, or leave in a request that applied only once. A small text library can make those changing parts visible before you start.

Plain-text starter library

REUSABLE TEXT LIBRARY
Copy a snippet into a working message before filling its slots.

SITUATION: Potluck — invite guests
Come to our potluck on [DAY], [DATE], at [TIME] in [LOCATION]. Bring a dish to share. Please tell me what you plan to bring by [REPLY DEADLINE].

SITUATION: Club — remind members about a meeting
A reminder that [CLUB] meets on [DAY], [DATE], at [TIME] in [LOCATION]. We’ll discuss [TOPIC]. Please bring [MATERIALS].

SITUATION: Hobby meetup — announce the next gathering
Join our [HOBBY] meetup on [DAY], [DATE], from [START TIME] to [END TIME] at [LOCATION]. This time, we’ll [ACTIVITY]. Bring [MATERIALS].

BEFORE SENDING
Resolve all slots. Confirm current details. Remove requests that do not apply. Read the completed message.

Is this a situation you will write for again?

Use Keep–Slot–Send for a recurring situation with a stable purpose: inviting people to a potluck, reminding a club about a meeting, or announcing a hobby meetup. Start with those three situations, or choose three of your own. A message that depends on a unique personal conversation may be easier to write fresh.

Keep the sentences that would make sense next time. Slot the details that need a new answer, using labels such as [DAY], [DATE], and [LOCATION]. Send only after filling a separate working copy and reading it as a complete message.

Decide sentence by sentence. If the wording stays useful, keep it. If the fact changes, make it a slot. If a sentence belonged only to the previous event, remove it. This keeps the library from becoming a collection of old messages with a few blanks.

Potluck invitation: what stays welcoming?

Hypothetical worked example: A host often types, “Come to our potluck on Sunday, October 11, at noon in the courtyard. Bring a dish to share. Please tell me what you plan to bring by Thursday, October 8.” The invitation and request can stay; the schedule, location, and reply deadline need slots.

The saved version becomes: “Come to our potluck on [DAY], [DATE], at [TIME] in [LOCATION]. Bring a dish to share. Please tell me what you plan to bring by [REPLY DEADLINE].”

For a later gathering, the working copy reads: “Come to our potluck on Saturday, November 14, at 1 p.m. in the community room. Bring a dish to share. Please tell me what you plan to bring by Wednesday, November 11.” Before using it, the host also checks that asking everyone to bring a dish still fits this gathering.

Club reminder: which facts must be explicit?

Hypothetical worked example: A club organizer starts with “See you tomorrow in the usual room to discuss chapter four.” Copying that sentence creates three questions: which date, which room, and which chapter? Keep the reminder’s purpose, but replace assumptions with named details.

The reusable wording is: “A reminder that [CLUB] meets on [DAY], [DATE], at [TIME] in [LOCATION]. We’ll discuss [TOPIC]. Please bring [MATERIALS].” A completed copy might read: “A reminder that the neighborhood reading club meets on Tuesday, November 17, at 7 p.m. in the community room. We’ll discuss chapter five. Please bring your book and one discussion question.”

If no materials are needed, delete the final sentence from the working copy. A slot is a prompt to make a decision; it does not require inventing something to fill it.

Hobby announcement: has the activity changed?

Hypothetical worked example: A sketching group repeats the same meeting arrangement, but changes its activity. Keep the invitation structure and give the activity its own slot instead of leaving last time’s plan in place.

The saved wording is: “Join our [HOBBY] meetup on [DAY], [DATE], from [START TIME] to [END TIME] at [LOCATION]. This time, we’ll [ACTIVITY]. Bring [MATERIALS].” Filled in, it reads: “Join our sketching meetup on Saturday, November 21, from 10 a.m. to noon at the community center. This time, we’ll draw objects arranged on a table. Bring paper and a pencil.”

Use this snippet while the purpose remains a casual meetup announcement. If the occasion becomes an exhibition invitation, write a separate snippet under that situation rather than stretching this one to fit.

Where will you look when you need the wording?

Store snippets under the situation that calls for them: “Potluck — invite guests” is more useful here than “Friendly wording.” Put the plain-text library below in any notes app or text document you already use.

Keep the saved versions unfilled. Copy the relevant text into a working message each time, then replace its slots. Add another snippet when you encounter another recurring need; there is no need to build a large collection in advance.

Is the working copy ready to send?

First look for any remaining square brackets. Then read the whole message for stale facts that might sit outside slots, including phrases such as “tomorrow,” “the usual room,” or an old activity description. Filled slots alone do not make a message current.

Use the check below on the working copy. If you discover a changing detail that the library treated as permanent, turn it into a slot in the saved version too.

Your checklist

• Look for [ and ] and resolve every remaining slot.
• Confirm the day, date, time, location, and any reply deadline for this event.
• Check that the activity and requests still apply; remove any irrelevant sentence.
• Read the complete message once for missing words or awkward phrasing after filling the slots.

The next time you need a familiar message, start with its situation name and supply the facts for this occasion.