"Send the same CSV as the June AGM mailing, but add the new members and drop anyone who has lapsed. Ready for Thursday's reminder about the autumn apiary visit."
That reads like a rerun you can start from the old query. It isn't. June's export had exclusions this email never repeats, and two households who asked to be taken off in August will come back out if you only press that query again.
Say you're a freelance developer who looks after a county beekeepers' association membership list in a few invoiced hours a month. This is a labelled hypothetical, not a client story. I build Maildoer, and the hold sheet below is the page I would fill in before I generated a single row. You can use it with a text file. The useful part is the refusal to treat "same CSV" as a send instruction, not the tool.
What the June card actually locked in
The earlier export note usually holds three kinds of fact, and Email 2 repeats none of them.
Who must not appear, even if they are still paid-up. The trustees' private working group is a separate list. The press and honey-show media list is a separate list. In April a 'no-newsletter' flag was added for members who pay dues but opted out of mailings; that flag still applies. In August, after a mistaken mail-merge, two households asked to be removed from mailings until they opt in again. They were still in the June file. They must not go out in this one.
Columns that must stay out of a mailing file. Do not include phone numbers or apiary addresses. Those belong in the members-only yearbook, not in a reminder CSV. Use the preferred-name field, not the legal name on the standing-order form.
Paper rules that only bite later. BCC the membership secretary. Do not send from the developer's address. Invoice the association, not the secretary personally.
"Same CSV as the June AGM mailing" is meant to carry all of this. If you treat this week as a new export, you can keep Thursday and put back the two August households, or keep the June exclusions and still add a phone-number column because the reminder is about a visit.
What "add the new members" cannot decide
Write this down before you accept a send date:
June: paid-up members, minus the working group, the press list, and the April opt-outs, with no phone numbers or apiary addresses. August: two households still paid-up, but off the mailing list until they opt in. This week's email: "the same CSV," add the new members, drop anyone who has lapsed, ready for Thursday. The first instruction only holds if June's exclusions and August's removals are still on the page. "New members" and "lapsed" are not filters until someone defines the dates. Thursday is a request, not a send you have already accepted.
Until that paragraph exists, you do not have an export plan. You have an accepted date and an undefined query.
"New members" might mean anyone who joined after the June mailing, anyone who joined after the 31 March renewal, or a list of names the secretary has not attached. June already excluded members unpaid on 31 March. Have any more lapsed since? Has anyone paid and come back? If you only rerun June's query, you will not know.
The two August households are the easy mistake. They were in the June file. A clean rerun of June, plus "new members," puts them back in. Their later request only exists in the August note.
A pre-send hold sheet
One page per mailing. Three blocks, plus a hold line you do not fill in yourself.
PRE-SEND EXPORT HOLD SHEET — DO NOT GENERATE THE CSV YET Mailing: autumn apiary-visit reminder Send date requested: Thursday (requested, not yet accepted) Source request: "same CSV as the June AGM mailing, add new members, drop lapsed" 1. STANDING RULES THAT STILL APPLY (from the June card, plus August) - Exclude the trustees' private working group (separate list) - Exclude the press / honey-show media list (separate list) - Honour the April 'no-newsletter' flag (paid-up, opted out) - August removals: two households off mailings until they opt in (they were still in the June file; a rerun will put them back) - No phone numbers, no apiary addresses (yearbook only) - Preferred-name field, not the legal name on the standing-order form - BCC the membership secretary; do not send from the developer's address - Invoice the association, not the secretary personally 2. WHAT THIS WEEK STILL LEAVES BLANK - "New members": after June mailing, after 31 March, or a named list? undefined - "Lapsed": still the 31 March cut-off, or has anyone lapsed or paid since June? unknown - Have the two August households opted back in? not stated - Will this reminder be sent as BCC from the secretary's address? not confirmed 3. HOLDS — DO NOT START - Do not generate the CSV until the two filters above are written as dates or a named list - Do not rerun the June query and "add a few rows" — that restores the August removals - Do not add phone or apiary columns because the reminder is about a visit - Do not accept Thursday until the query, the August names, and the send path are on this sheet The sheet stops you treating "add the new members" as a small variation on an export you have already agreed to reuse.
The confirmation I would send
A useful reply restates the standing rules, names what is still undefined, and leaves the date unaccepted.
I'll work from the June AGM mailing card: no working-group or press-list rows, honour the April opt-outs, preferred names only, and no phone numbers or apiary addresses. I'll also keep the two August households off the file until they opt in — they were still in the June export, so a straight rerun would put them back. I'll BCC you, and invoice the association.
"The same CSV as June" only works once "new members" and "lapsed" are dates or a named list, not phrases. I haven't generated the file, and I won't accept Thursday until those two filters are written down and the August removals are acknowledged. If you can tell me whether "new" means after the June mailing or after 31 March, and whether anyone has lapsed or paid since June, I'll put that on the sheet and write back with a row count before anyone is sent a reminder.
If you only confirm "yes, same CSV, ready for Thursday," you have accepted a date and invented a query for a list you have not defined.
Mistakes that drop the earlier card
- Treating the newest email as the whole brief. "Add the new members" does not replace the working-group exclusion, the April opt-outs, the column rules, or the August removals.
- Accepting Thursday first and defining the query later. Once the visit is in members' diaries, you will be the person who mailed the people who asked to be left off, even if you only reran June.
- Rerunning June and appending rows. The two August households were in that file. Their later request lives in a different note.
- Adding apiary addresses because the reminder is about a visit. The June card already said those stay in the yearbook.
The later email is only usable if it is read with the June card and the August note, not as a fresh request. If you use a tool on the two messages, that is the test: the August removals and the June exclusions still have to be on the page after the new wording arrives.
If you want to try that kind of follow-up on a real file, email the file and your ask to do@maildoer.com, then send a second message that assumes the first one is still in view — that's the point. 100 credits come with your first email. https://maildoer.com
When a later request says "same export, just add the new people," do you write the old exclusions on the page first, or do you rerun last time's query and check the diff afterwards?

