Rotary Market Research Program · SOP

For: Chau Phan, Ela Requinto, and the VA who runs the sequence
Built: 2026-09-24 from Tim's plan of the same day
Status: Tim calls this eight tenths done. It gets finished with Chau at the Tuesday call, 2026-09-29. Everything to confirm is in section 9.

One source, many views. This SOP says WHO does each step, WHEN, HOW MANY, and in what ORDER. It never copies the words people say. The words live in exactly two files:

If a section number below does not match the file, find the section by its name. Both files were being revised on 2026-09-24.

Tim's plan, his words, 2026-09-24:

"ask why they stopped going. ask what they need to start going. ask what problems they have in business. ask what goals they have. if the door opens use it. if not just grow the group and trust compounding interest and market data."

"email, follow up email, phone call, text message, last call email. It's the structure."

"the VA's job is to set an appointment with Chau, and it's just market research."

1. PRIORITY

FIRST: this program. It is "the one that compounds the most over time": every call grows Rotary, and every call puts a business owner's own words about their problems into the tracker.

WAITS: the cold emails for the four priority two avatars (optometry and dental, vet, DME and home health, CPA and bookkeeping). They run second, and they are written from the quotes this program collects (the VOC_FEED tab, Step 9).

2. ROLES

Every step, one name

3. EVERY STEP, IN ORDER

Order for the VA inside any one workday, highest first:

1. Replies and callbacks (Step 3.7). A person who wrote back is ready now.
2. Booking, confirmations and reminders (Step 4).
3. Follow ups due today: Email 2, call 1, text, call 2, last call email (Steps 3.2 to 3.6).
4. New starts, Email 1 (Step 3.1).

If the shift runs out, what drops is item 4, never items 1 to 3. Missed new starts get added to the next workdays (Step 9).

STEP 0 · CLEAR THE GATE

• WHAT: Replace every [AWAITING ...] tag in SEQUENCE and CALL SCRIPT, and tick every box in SEQUENCE § 8 BEFORE THE FIRST SEND.
• HOW:
  1. At the Tuesday call, Chau answers every item in section 9 of this SOP, out loud.
  2. Ela types each answer into the file, at the tag, the same day.
  3. Chau confirms the sending address exists, her Fathom recording works, and her two weekly slots are on her calendar.
  4. Ela searches both files for the word AWAITING.
• WHEN AND HOW MANY: Once, before the first Email 1. Every tag, zero left.
• DONE WHEN: Ela's search finds zero AWAITING in both files, and all five boxes in SEQUENCE § 8 are ticked. Nothing sends before this.

STEP 1 · GET THE LIST

• WHAT: The list of former D5170 members Chau may contact as membership chair.
• HOW:
  1. Pull the names from the source Chau confirms in Step 0 ([AWAITING FROM CHAU: source of the contact list, and who is allowed to hold it], the same tag as SEQUENCE § 8).
  2. Keep five fields only: first name, last name, club, email, phone.
  3. Mark the people who left for business obligations Priority 1 (the 2026-09-17 decision: these come first). Everyone else is Priority 2.
  4. ⛔ Never copy the termination reason, the member record, or any other field into the list. Chau's line of 2026-09-17 holds: "I can't export that and use it for my market research." The priority mark is the only trace of the reason, and it says nothing about the person.
  5. Count the rows. That count is N.
  6. Send the file and N to Ela.
• WHEN AND HOW MANY: Once, within 2 workdays after Step 0.
• DONE WHEN: Ela has one file with N rows and six columns (the five fields plus priority), and N is typed into the SETUP tab.

STEP 2 · LOAD THE TRACKER

2A · Ela builds the sheet.

• WHAT: One sheet with four tabs: TRACKER, SETUP, WEEKLY, VOC_FEED (section 6).
• HOW:
  1. Create TRACKER with the 39 columns in section 6, in that order, as row 1.
  2. Create SETUP and fill: N, the window (30 or 90 days), W, daily starts, weekly starts, the booking rate assumption, calls per week, the first start date, every RMB evening date inside the window, Chau's two weekly slots, the VA's name. Use the formulas in section 4.
  3. Create WEEKLY with the columns in section 7, one row per week.
  4. Create VOC_FEED with the columns in section 6.
• WHEN AND HOW MANY: Once, the same day the list arrives.
• DONE WHEN: Four tabs exist, and SETUP shows daily starts as a whole number.

2B · The VA loads the names.

• WHAT: One row per person in TRACKER.
• HOW:
  1. Paste the list into columns B to F (Name, Club, Email, Phone, Priority).
  2. Remove duplicates: same email or same phone means the same person. Keep one row. Type the number removed into SETUP.
  3. Fill column A (Row #, 1 to the last row), column G (Source) with CHAU_LIST, and column H (VA) with your name.
  4. Sort: all Priority 1 rows on top, then Priority 2.
  5. Leave every other column blank.
• WHEN AND HOW MANY: Once, within 1 workday after 2A. All N rows.
• DONE WHEN: TRACKER row count equals N minus the duplicates removed, and every row has Row #, Priority, Source and VA filled.

STEP 3 · RUN THE SEQUENCE, PER PERSON

Rules on every touch: SEQUENCE § 0 RULES THE VA FOLLOWS ON EVERY TOUCH. Read it before your first shift.

The schedule. Day numbers are business days, Mon to Fri, per SEQUENCE § 6 TIMING TABLE. When you finish a touch, type the next touch and its date into columns N (Next step) and O (Next step date). The date comes from this table, or from the formula in section 6.

Time zone. Recipients are Pacific. Manila is 15 hours ahead of Pacific until Sunday 2026-11-01, and 16 hours ahead after that. So 8:00 am Pacific is 11:00 pm Manila now, and midnight Manila after November 1.

3.1 · SEND EMAIL 1

• WHAT: First touch to the next [daily starts] rows with a blank Start date, top down.
• HOW: SEQUENCE § 1 EMAIL 1. One email per person. Fill {first_name} and {club}, and the RMB evening from SETUP (the next date on the list). Send, or schedule it to land 8 to 10 am Pacific. Then log: Start date = today, Last touch E1, Last touch date = today, Outcome SENT, Next step E2, Next step date from the table.
• WHEN AND HOW MANY: Every workday, Monday to Friday, [daily starts] people (section 4), landing 8 to 10 am Pacific.
• DONE WHEN: [daily starts] rows show E1 with today's date.

3.2 · SEND EMAIL 2

• WHAT: Follow up to every row with Next step E2 due today and no reply.
• HOW: SEQUENCE § 2 EMAIL 2 (FOLLOW UP), as a reply in the same thread as Email 1. Log E2, Next step CALL, date from the table.
• WHEN AND HOW MANY: Every workday, every row due today, landing 8 to 10 am Pacific.
• DONE WHEN: Zero rows show Next step E2 with a date of today or earlier.

3.3 · MAKE CALL 1

• WHAT: Phone call to every row with Next step CALL due today and no reply.
• HOW: SEQUENCE § 3.1 Live script. No answer: leave the SEQUENCE § 3.2 Voicemail. For what people say, use SEQUENCE § 3.3 Short answers. Log CALL (they answered) or VM with Outcome NO_ANSWER_VM. Type anything they said into Their words, in quotes. They said yes: go to Step 4 now. No answer: Next step TXT, date from the table.
• WHEN AND HOW MANY: Every workday, every row due today, inside a call window: 8:30 to 10:00 am or 4:00 to 5:30 pm Pacific. Write which window you used in Their words (AM or PM) so call 2 goes in the other one.
• DONE WHEN: Zero rows show Next step CALL with a date of today or earlier.

3.4 · SEND THE TEXT

• WHAT: Text to every row with Next step TXT due today, where call 1 did not connect.
• HOW: SEQUENCE § 4 TEXT MESSAGE. Only after call 1 and the voicemail happened. Never before. Log TXT, Next step CALL2, date from the table.
• WHEN AND HOW MANY: Every workday, every row due today.
• DONE WHEN: Zero rows show Next step TXT with a date of today or earlier.

3.5 · MAKE CALL 2

• WHAT: Second call to every row with Next step CALL2 due today and still no answer, reply or opt out.
• HOW: SEQUENCE § 3.4 Second call attempt, in the other call window from call 1. No voicemail. Log CALL2, Outcome NO_ANSWER if nobody picks up, Next step E3, date from the table.
• WHEN AND HOW MANY: Every workday, every row due today.
• DONE WHEN: Zero rows show Next step CALL2 with a date of today or earlier.

3.6 · SEND THE LAST CALL EMAIL

• WHAT: Last touch to every row with Next step E3 due today and still no reply.
• HOW: SEQUENCE § 5 LAST CALL EMAIL, as a new email, not a reply. Log E3, Outcome SEQUENCE_DONE, Next step none, Next step date blank.
• WHEN AND HOW MANY: Every workday, every row due today, landing 8 to 10 am Pacific.
• DONE WHEN: Zero rows show Next step E3 with a date of today or earlier.

3.7 · ANSWER EVERY REPLY

• WHAT: Every email reply, text reply, returned call and voicemail from a person on the list.
• HOW: SEQUENCE § 0 rule 5. Type their words into Their words, in quotes. The first time they reply or answer live, type today's date into Reached. Then:
  • Yes to a call: Step 4, now.
  • Not now: thank them. Outcome REPLIED_LATER. Next step check back with their date, only if they gave one. On that date, send one short note offering two times (SEQUENCE § 7.1). No date given: Next step none.
  • No, or take me off: Outcome OPT_OUT (or REPLIED_NO), Do not contact Y, Next step none. Never touch the row again.
  • Wants the RMB evening but not the call: Outcome RMB_ONLY, RMB interest Y, Next step RMB invite (Chau), Next step date today. Chau sends it (Step 7).
  • Email bounced: Outcome BOUNCED. Keep going on the phone and text touches on their normal dates. No phone either: Outcome SEQUENCE_DONE.
  • Wrong number: Outcome WRONG_NUMBER. Skip the calls and the text, keep the emails on their normal dates.
• WHEN AND HOW MANY: First thing every shift, before any other touch. All of them.
• DONE WHEN: At the end of the shift, the inbox, the text app and the voicemail have zero unanswered messages from people on the list.

3.8 · ELA'S DAILY CHECK

• WHAT: Proof that today's touches happened and were logged.
• HOW:
  1. Filter TRACKER: Next step date is today or earlier, Next step is not none, Do not contact is blank.
  2. The filter should return only rows waiting on Chau (Chau call, RMB invite (Chau)). Any VA row that shows up is a missed touch. Message the VA with the Row #s.
  3. Count rows with Start date = today. It should equal daily starts.
  4. Type today's date into SETUP, "Last daily check".
• WHEN AND HOW MANY: Every workday, at the end of the VA's shift. Every row.
• DONE WHEN: The filter shows zero VA rows, and SETUP shows today's date as the last daily check.

STEP 4 · BOOK THE CALL WITH CHAU

• WHAT: Turn every yes into a time on Chau's calendar.
• HOW:
  1. SEQUENCE § 7.1 What the VA says to lock a time. Offer two specific times inside Chau's two weekly slots (SETUP tab). Never a calendar link.
  2. Ask phone or Zoom. Confirm the number or email, and their time zone.
  3. Ask the recording question in SEQUENCE § 7.1.
  4. Put the call on Chau's calendar ([AWAITING FROM CHAU: how the VA puts calls on Chau's calendar]). Title: their name and club. Body: Row #, phone number or Zoom link.
  5. Send the confirmation in SEQUENCE § 7.1, within one hour.
  6. Log: Booked (day and time), Booked on (today), Format, Recording OK, Outcome REPLIED_YES or CONNECTED_BOOKED, Next step Chau call, Next step date = the call date.
  7. The workday before the call: send the reminder text in SEQUENCE § 7.1.
  8. No show (SOP default, confirm Tuesday): the same day, send one short email offering two new times. They miss the second one too: Outcome SEQUENCE_DONE, Next step none.
• WHEN AND HOW MANY: Every yes, within one hour of seeing it during the shift. Reminders the workday before each call.
• DONE WHEN: Every yes row has Booked and Booked on filled, a confirmation sent within the hour, and a reminder sent the workday before.

STEP 5 · HOLD THE CALL

• WHAT: A 15 to 20 minute recorded market research call.
• HOW:
  1. Two minutes before: open the row. Read the VA's Their words column so you know what they already said. Start Fathom.
  2. Run CALL SCRIPT Step 1 to Step 11, in order, keeping THE RULES FOR THE WHOLE CALL and Lines Chau never says.
  3. Consent: CALL SCRIPT Step 1, out loud, before the first question (also SEQUENCE § 7.1, the recording consent note). A no means stop Fathom and take notes by hand.
  4. Health, family, a loss or a move: go to CALL SCRIPT THE BRANCH.
  5. Keep to CALL SCRIPT The clock. Running long: protect Steps 6 and 7.
• WHEN AND HOW MANY: Only inside your two weekly slots, [AWAITING FROM CHAU: two open time slots each week for these calls]. Every booked call. The weekly count is in section 4.
• DONE WHEN: A Fathom recording exists (or handwritten notes, if they said no), and Call held has today's date.

STEP 6 · LOG THE ROW

• WHAT: Their words, in the tracker, before the next call.
• HOW:
  1. CALL SCRIPT Step 12 AFTER THE CALL, 5 MINUTES, minute by minute, following The rules for the row.
  2. Fill columns W to AI (section 6), and Next step (column N) using the Step 12 list.
  3. Fill Call held (today) and Avatar: OPT_DENTAL, VET, DME_HH, CPA_BK, or OTHER.
  4. Names they gave you at "who comes to mind": add one new row per name at the bottom of TRACKER. Source = referral: [the person who named them]. Add whatever contact details they gave. The VA starts them like any other row.
• WHEN AND HOW MANY: Within 5 minutes of hanging up, before the next call. Every call.
• DONE WHEN: Columns W to AI have no blank cell for that row (not asked and not said count as filled), and the recording link is pasted.

STEP 7 · SEND THE RMB INVITE

• WHAT: The invitation to the next Rotary Means Business evening.
• HOW:
  1. On the call, at CALL SCRIPT Step 8, send it while you are still on the phone. (Tim's plan names Chau as the sender. The channel is open: [AWAITING FROM CHAU: who sends the mixer details, you or the VA, and by text or email].)
  2. It carries: the date, the time, the place, the format, any cost, that they come as your guest, and how to reply.
  3. Also send one to every row showing Next step RMB invite (Chau). The VA put those there from Step 3.7.
  4. Log Invitation sent as Y [date] or N [reason]. On RMB invite (Chau) rows, change Next step to none.
  5. The workday after each RMB evening, type that evening's date into RMB attended for every person on the tracker who came.
• WHEN AND HOW MANY: During every call, and the same day for every RMB invite (Chau) row. Attendance within one workday after each evening.
• DONE WHEN: Every row with a call held or RMB_ONLY has Invitation sent filled, and every RMB evening has its attendees marked by the next workday.

STEP 8 · HANDLE THE DOOR

• WHAT: Raise the business once, with the out. On a yes, book the separate call before hanging up.
• HOW:
  1. CALL SCRIPT Step 9 THE DOOR, WITH THE OUT. Route A or Route B, never both, following The rules for the door.
  2. Yes: CALL SCRIPT Step 10. Book the one part sales call live, on this call, and put it on your calendar. Fill Sales call booked on (today) and Next step sales call booked [date].
  3. No: CALL SCRIPT Step 11 THE WARM CLOSE.
  4. Heavy call: skip it, per CALL SCRIPT THE BRANCH.
  5. Log Door opened per CALL SCRIPT Step 12, rule 5.
  6. The sales call itself runs outside this SOP. Tim's rule for it: "get their exact number of what they think they need."
• WHEN AND HOW MANY: Once per call, at about minute 17.
• DONE WHEN: Every held call has Door opened filled, and every Y row has a sales call date booked before the call ended.

STEP 9 · WEEKLY REVIEW

• WHAT: The week in seven numbers, and the week's quotes handed to the priority two cold emails.
• HOW:
  1. Ela, Friday: run the 3.8 daily check across the whole week.
  2. Ela: fill one row on WEEKLY with the seven numbers in section 7, using the COUNTIFS in section 6. Add the SEQUENCE § 7.2 Friday totals (emails sent, dials, answers of 2 minutes or longer, calls requested, calls booked, RMB yes), counted from the sent folder and the phone log.
  3. Ela: people started this week fewer than 5 × daily starts? Spread the shortfall across next week's starts and type the new number into SETUP.
  4. Ela, from the end of week 2: replace the booking rate assumption in SETUP with the real one (section 4).
  5. Ela: copy every row whose call was held this week and whose Avatar is not OTHER into VOC_FEED. These rows are the market research for the priority two cold emails.
  6. Ela: message Chau: "WEEKLY is filled", with the seven numbers in the message.
  7. Chau: read the row before Tuesday. For any low number, read its line in section 7. Bring the row to the Tuesday coaching call.
• WHEN AND HOW MANY: Every Friday, by the end of Ela's shift. Chau reads it by Monday. Tim sees it Tuesday.
• DONE WHEN: WEEKLY has this week's row with all seven numbers, VOC_FEED has this week's rows, and Chau has the message.

4. VOLUME MATH

Tim: "If there are hundreds of people, we just divide it. Let's see if we could knock it out in the next 30 days. If there are thousands of people, we divide it over three months."

The formula

Why 10%, and why it is only an assumption. No published booking rate exists for this exact motion (NOT FOUND in the reactivation research). The nearest vendor numbers are 15 to 30% participation in win loss interviews (Clozd) and 32 to 39% engagement from lapsed association members (PropFuel). 10% sits below both on purpose, because these people left.

Replacing it with the real number. At the Friday review of week 2, Ela computes: people from week 1 who booked ÷ people started in week 1. Some week 1 rows are still one to four days short of their last touch, so treat it as a first read. Recompute every Friday using only rows started at least 10 business days ago. Type it into SETUP and every number below it updates.

Capacity check. If calls per slot × 30 minutes is longer than a slot, tell Chau on Tuesday.

Worked examples

How far off the assumption can be. Calls per week for Chau at other booking rates:

5. WEEKLY RHYTHM

The week is Monday to Friday. All times Pacific.

The VA, every workday, in this order: (1) replies, (2) booking, confirmations and reminders, (3) follow ups due today, (4) new starts. Emails land 8 to 10 am. Calls go 8:30 to 10:00 am or 4:00 to 5:30 pm.

The first two weeks ramp. Week 1 has only Email 1, Email 2 and some first calls. Week 2 adds the texts, second calls and last call emails. From week 3 the VA runs every touch type every day, and Chau's calls reach the weekly number in section 4.

6. THE TRACKER

Where it lives: [AWAITING FROM CHAU: where the tracker lives, a Google Sheet or GoHighLevel] (CALL SCRIPT Step 12). The formulas below are written for a Google Sheet.

One row per person. Every column from SEQUENCE § 7.2 and every column from CALL SCRIPT Step 12 The row is here. Name, Club and Next step are shared by both. Columns marked SOP are added so the numbers in section 7 can be counted.

TRACKER tab

Next step date formulas (Start date is column I, row 2 shown):

SETUP tab

N · duplicates removed · window (30 or 90) · W · daily starts · weekly starts · booking rate (marked ASSUMPTION until replaced) · calls per week · first start date · every RMB evening date in the window · Chau's slot 1 and slot 2 · VA name · last daily check.

WEEKLY tab

One row per week. Column A = that Monday's date, column B = that Friday's date. Then the seven numbers in section 7, and the SEQUENCE § 7.2 Friday totals.

Count formula, one per number, changing only the column letter:
=COUNTIFS(TRACKER!I:I,">="&A2,TRACKER!I:I,"<="&B2) counts people started (column I). Use P for reached, S for booked, AJ for calls held, AL for sales calls booked, AM for RMB attendees.
Doors opened: =COUNTIFS(TRACKER!AJ:AJ,">="&A2,TRACKER!AJ:AJ,"<="&B2,TRACKER!AH:AH,"Y*")

VOC_FEED tab

Row # · Avatar · Business type · About the business (their words) · Goals (their words) · Business problems (their words) · Small tasks (their words) · Hours a week (their number) · Recording link · Week.

7. NUMBERS TO WATCH EVERY WEEK

8. DONE CONDITION FOR THE WHOLE PROGRAM

The program is done when every row in TRACKER, including referral rows added along the way, is in one of two states, and Ela's filter proves it.

1. Had a call: Call held (AJ) has a date, and columns W to AI are all filled. A quote, not asked or not said counts as filled.
2. Finished the sequence: Outcome is SEQUENCE_DONE, or the sequence ended early on REPLIED_LATER, REPLIED_NO, CONNECTED_DECLINED, OPT_OUT or RMB_ONLY.

Ela's proof: filter TRACKER for Call held blank AND Outcome not in the list in state 2. The filter returns zero rows. Then filter Booked filled AND Call held blank AND Outcome not SEQUENCE_DONE. That also returns zero.

9. TO CONFIRM WITH CHAU TUESDAY

Every open item from SEQUENCE, CALL SCRIPT and this SOP, in one list. Where two files ask the same thing, it appears once with both sources.

A. The open tags (nothing sends until these are filled)

1. Sender name. SEQUENCE § 1, § 2, § 5.
2. Sender email address. SEQUENCE § 1.
3. VA name. SEQUENCE § 3.1, § 3.2, § 4, § 7.1. Also this SOP, section 2.
4. VA callback number. SEQUENCE § 3.2.
5. Two open time slots each week for these calls, with the day and time of each. SEQUENCE § 7.1. Also this SOP, Step 5 and section 5.
6. Source of the contact list, and who is allowed to hold it. SEQUENCE § 8. Also this SOP, Step 1.
7. The RMB evening: date, place, format. SEQUENCE § 1, § 2, § 3.1, § 5 and CALL SCRIPT Step 8. The starts roll for 30 or 90 days, so this SOP needs every evening date inside the window, not only the next one.
8. Whether former members can attend RMB as guests, the chapter's name, and any cost for them. SEQUENCE § 8 and CALL SCRIPT Step 8.
9. Exactly who hears the recording. CALL SCRIPT Step 1.
10. Who sends the mixer details, Chau or the VA, and by text or email. CALL SCRIPT Step 8. Tim's plan names Chau.
11. Where the tracker lives, a Google Sheet or GoHighLevel. CALL SCRIPT Step 12. Also this SOP, section 6.

B. The decisions CALL SCRIPT already lists

12. The ten items in CALL SCRIPT, TO REFINE WITH CHAU TUESDAY (a no at the invite, route A or B, company name at the door, the name ask, heavy calls, length, the "bring them back" column, and the three tags above).

C. New from this SOP

13. How the VA puts calls on Chau's calendar. Step 4.
14. How many calls fit in each slot. At N = 2,000 and a 10% booking rate, each slot holds 8 calls, about 4 hours. Section 4.
15. Start days. SEQUENCE § 6 says Email 1 goes out Tuesday, Wednesday or Thursday. Tim's plan says the VA starts new people daily. This SOP follows Tim, Monday to Friday. Pick one.
16. Where business comes up. RESOLVED 2026-09-24: SEQUENCE § 0 rule 1 and § 3.3 now match CALL SCRIPT step 9 (version 2). The VA's answer to "Are you selling something?" says Chau is a business owner too and may say so if she can help, and the person is free to say no.
17. The no show rule in Step 4, item 8 (one rebook offer, then close). An SOP default.
18. Referral names go into the same sequence as new rows (Step 6, item 4). An SOP default.
19. The 300 name cutoff between 30 and 90 days. Set in this SOP from Tim's "hundreds" and "thousands". At N = 500 and a 30 day window, daily starts would be 25, not 8.
20. The 10% booking rate and the 14 minutes per person VA time. Both assumptions, both replaced with real numbers after week 2 and week 1.

D. Other open items (not Rotary, listed so nothing is lost)

21. The VOC research slots (software, task and bottleneck, by avatar). This program's VOC_FEED is one of the ways they get filled.
22. The actual bill rate per client.
23. The Corwin Li contradiction, 4 hours written vs 40 hours spoken.
24. The KPI sheet: dials, answers, appointments requested, appointments booked.
25. Scope, rate, SOW and SLA for the Member Minder Pro / DapDB account.

SUGGESTIONS FOR TUESDAY

Not part of the SOP. Ideas only, for Tim and Chau to take or leave.

1. If "knock it out in 30 days" means finished, not started, put every start in the first 11 working days so the last email lands by working day 20. At N = 150, that is 14 starts a day instead of 8.
2. At N = 2,000, split the list across two VAs (16 starts a day each). One VA would be at about 7 hours a day, and Chau at about 8 hours of calls a week. Or stretch the window.
3. Log the first real booking rate when week 2 closes. The references found no published number for this motion, so Chau's will be the first.
4. Give referral names their own first email that says who suggested them. A warm name reads a cold Email 1 as cold. It would be one short variant in SEQUENCE § 1.
5. Pin the Friday WEEKLY row to the Trello board, the live surface, so Tim sees it before the Tuesday call without asking.

Built 2026-09-24 from Tim's plan of 2026-09-24, 2_Rotary_VA_Outreach.md (revised version with call 2 on Day 8) and 1_Rotary_Call_Script.md (version 2).