Back to Send on Tuesday

Issue 1 · Field note · Published 6 October 2026

You collected 70 event leads.Now what?

A practical system for turning hurried notes and half-remembered conversations into useful next steps.

The field note

The event went well. Then momentum disappeared.

The stand was busy, conversations were flowing and the spreadsheet is now full of names. That is the good news. The harder part comes afterwards: every contact looks superficially similar, while the useful context is scattered across badge scans, notebooks, LinkedIn connections and somebody's memory.

It is easy for good intentions to get lost in the gaps. Without a shared way to interpret the information, teams can end up sending the same generic email to everyone or leaving the list untouched until the moment has passed.

Post-event follow-up is not an email-writing exercise. It is a decision-making exercise.

Before anyone writes a follow-up email, the team needs three answers:

  • What was actually learned?
  • What was promised?
  • What is the next useful move - and who owns it?

The complete system

From messy notes to a reviewed follow-up plan.

This issue gives you four connected tools. Use them in order to turn incomplete notes into a clear, owned and appropriate follow-up - without inventing intent or sending the same email to everyone.

  1. 1

    Understand the four routes

    Use a shared framework to decide whether to act now, build context, keep warm or close cleanly.

  2. 2

    Run the complete prompt

    Paste in your notes. It structures the evidence, identifies gaps, suggests a route and prepares a first-draft email.

  3. 3

    Move it into the Excel table

    Put one contact in each row, then add the next action, owner, due date and review status.

  4. 4

    Review, assign and send

    Check the evidence, correct the route and adapt the email. Nothing is sent automatically.

Start withHurried notes and half-remembered promisesFinish withAn owned plan, sensible next steps and reviewed emails

Four follow-up routes

Choose the route that fits the conversation.

Each route gives the team a shared decision and a useful action without pretending that limited event notes can predict a sale.

Act nowA relevant problem, credible timing or a specific next step was discussed.Continue the exact conversation with a personal follow-up.Within 2 working days
Build contextThe contact is relevant but the need, timing or authority is unclear.Ask one useful question or share one directly relevant resource.Within 5 working days
Keep warmThere is a good audience fit but no current issue or agreed action.Add to suitable insight-led nurture, with permission.After immediate follow-up
Close cleanlyThere is no meaningful fit, context or permission to continue.Record the outcome. Do not manufacture a campaign.Immediately

Ready to use

The complete prompt.

Copy the whole prompt, then paste your event notes beneath it using the structure shown at the end.

Remove personal or commercially sensitive information if your organisation has not approved the AI tool for that data.

Event follow-up triage prompt
You are helping a B2B team organise notes from an event. Your job is to structure the supplied information without inventing facts, intent, urgency or familiarity.

For each contact, return one row in a table with these exact columns: Contact; Role; Organisation; Raw notes; Stated need; Timing evidence; Commitment; Missing context; Suggested route; Reason for route; Next useful move; Owner; Due date; Review status; Follow-up draft.

Use only these routes: Act now, Build context, Keep warm, Close cleanly.

Rules:
- Distinguish direct evidence from inference.
- Write “Not recorded” when information is missing.
- Do not use job title as evidence of intent.
- Do not describe someone as a hot lead.
- Do not invent personal details.
- Do not add the contact to ongoing marketing without an appropriate basis.
- Keep follow-up drafts specific, calm and under 120 words.
- Write “Not recorded” when the owner or due date is missing.
- Set Review status to “Needs review”.

Before the output, list any notes that are too ambiguous to classify confidently. After the output, provide three questions the human reviewer should answer before anything is sent.

Paste your event notes below this prompt. Use this structure for each contact:
- Contact name and organisation
- Role
- Raw notes
- Anything promised
- Person responsible for follow-up

The practical tool

Move the output into a working plan.

The Excel table has ready-to-use rows and columns that match the prompt output. Run the prompt, transfer one contact into each row, then review the evidence and assign the action before anything is sent.

Event Follow-up Triage Table

  • One row per contact
  • Four evidence-based routes
  • Owner, due date and review status
  • First-draft follow-up column
  • Instructions included
Download the Excel tableFree to use. Built for human review, not automatic sending.

The worked example

From a rough note to a useful follow-up.

See the essential result at a glance, or open the complete example to inspect every step.

Rough noteSupplier reporting is fragmented
RouteAct now
OutputTemplate plus a useful question
See the complete worked example

The raw note

Priya Shah, Operations Director at Northbridge Components. Supplier performance information sits across separate purchasing and production spreadsheets. The monthly review takes too long to prepare. Trialling a consistent review format next month. I said I would send our supplier review template. Alex to follow up.

The structured review

Stated needSupplier performance information is split across separate spreadsheets, making the monthly review slow to prepare.
Timing evidenceA consistent review format will be trialled next month.
CommitmentSend a supplier review template.
Missing contextWhich measures matter most, who owns the review and whether a replacement system is being considered.
Suggested routeAct now.
ReasonA defined administrative problem, a near-term trial and a specific promised action were all recorded.
Next useful moveSend the promised template and ask which measures the new format needs to make easier to compare.

The first-draft follow-up

Human review before sending

  • Confirm that the template is genuinely relevant to the issue discussed.
  • Check that the wording reflects Alex's memory of the conversation.
  • Make sure the question feels natural and useful.
  • Record the sent date and a sensible follow-up point.
If the same follow-up could be sent to every attendee, it is not a follow-up. It is distribution.

That is the thought worth taking back to the spreadsheet.