CSA Farm Shares: Sign-Ups, Pickup Reminders and Swaps With AI

A CSA farm can run share management with three linked pieces: a sign-up form that writes to a members sheet, a weekly reminder email merged from that sheet, and a written rule for skipped weeks and swaps. AI drafts the form wording, reminders and box notes and checks the sheet for gaps; it never needs your members' details.

The growers who struggle with CSA admin are rarely short of software. They are short of rules written down before the season starts: what a skip is, who can swap, when the pickup list is final. Once the rules exist, an assistant can turn them into form questions, email text and a weekly checklist in an afternoon. Without the rules, it will happily draft whatever you ask for and the arguments arrive in week six.

Follow me on Instagram@sagnikteaches

The flow from form to reminder in one picture

1. Sign-up form. Collects the member's choices and agreement to your rules.
2. Members sheet. One row per member per season, filled by the form.
3. Changes sheet. One row per skip, swap or pickup change, each with a date, filled by a second short form.
4. Weekly summary. A formula or filter that shows who is collecting this week, where, and what size.
5. Reminder email. Merged from the weekly summary and sent a day or two before pickup.
6. Box note. A short note on what is in the box, sent with the reminder or at the pickup.

That is all of it. It needs a form tool, a spreadsheet and your email provider's mail merge or a simple automation. If you already use a form and sheet combination, you have the first two. For how to move form answers into a sheet with an automation tool, the n8n data-entry tutorial walks the steps.

Connect on LinkedInSagnik Bhattacharya

Step 1: the sign-up form, written from your rules

Start by writing your rules as plain statements. Here is an illustrative set for a 20-week vegetable share:

Subscribe on YouTube@sagnikteaches

• Full share feeds two people for a week; half share feeds one or a couple who cook little.
• Pickup is on one of two days at one of two sites; members choose at sign-up.
• Members may skip up to two weeks in the season, with at least five days' notice. Skipped boxes are credited to the end of the season or donated; the member chooses.
• Uncollected boxes are donated after the pickup window and are not credited.
• Swaps: members may swap named items in the box if they tell us by the swap deadline, subject to what is available.

Then ask the assistant to turn the rules into form questions and a short agreement. Tell it what it may not add.

Turn these CSA rules into a sign-up form. For each question give: the question text, the answer type (short text, single choice, checkbox, date), whether it is required, and the exact choices. End with an agreement checkbox whose wording restates the rules in under 120 words. Use only the rules given. Do not invent fees, refund terms, dates, or health claims. Flag any rule that is ambiguous and ask me a question about it instead of guessing.

RULES:
[paste the rules above]

Illustrative output: questions for name, email, phone for pickup problems (optional), share size (full or half), pickup day (Tuesday or Saturday), pickup site (A or B), dietary dislikes (optional text), skip-credit preference (credit or donate), and an agreement checkbox. The assistant would flag questions such as "Is the deposit refundable if a member moves away?" because your rules do not say. Answer those yourself; they are the arguments you would otherwise have mid-season.

Two form details are worth the trouble. Add a unique member number, a simple counter you assign, so the merge never has to depend on matching names. And use choices, not free text, wherever the answer feeds a filter: a pickup site typed freehand arrives as "Site a", "A site" and "the farm", and none of those groups together.

Step 2: the members sheet and a weekly view

The members sheet has one row per member per season: member number, first name, email, share size, pickup day, site, skip preference, paid (yes or no), start week, end week and any notes. Protect the original rows from editing; changes go in the changes sheet.

The changes sheet has: date logged, member number, change type (skip, swap, move, cancel), week affected, details. Because every change is dated, you can reconstruct any week.

The weekly view is a filter on both. For week 9: all members whose start week is 9 or earlier and end week 9 or later, minus any member with a skip logged for week 9. If you do not write spreadsheet formulas, an assistant can write one for your layout; give it the column letters and the rule. Always test it on a small made-up table before trusting it on real data.

I have two Google Sheets tabs. MEMBERS has columns A member number, B first name, C email, D share size, E pickup day, F site, G start week, H end week. CHANGES has A date logged, B member number, C change type, D week affected, E details. Write one formula for a third tab that lists, for the week number typed in cell B1, the member numbers from MEMBERS who are active that week and have no row in CHANGES with change type "skip" for that week. Explain each part in one line. Then give me a test table of six made-up members and three changes so I can check the answer by eye.

The "test table" request is the safety net. An assistant can produce a plausible formula that fails on edge cases such as a member with two skips. Check the outcome against the made-up table by hand before running it on the real sheet. If you use Excel rather than Google Sheets, say so, because some functions differ between the two; the ChatGPT Excel guide covers the general habit.

Week 9 at a 48-member farm

Take an illustrative farm with 48 members: 30 full shares and 18 half shares across two pickup days. In week 9 the changes sheet shows three skips and one move from Tuesday to Saturday. The weekly view returns 45 active members. The summary for the packing team reads:

28 full plus 17 half is 45, matching the active count, which is the cross-check to make every week: the summary total must equal the number of active members. If the farm has 30 full shares and two are skipped, 28 remain. The packing team now has a number for each site and nobody has to re-read the inbox.

Step 3: the weekly pickup reminder

A good reminder says four things: what day and where, what time window, what to bring, and what to do if you cannot come. Keep it short; a member reads it on a phone.

Write a reminder email for CSA members. Use merge placeholders exactly as written: [first name], [pickup day], [site], [window]. Under 90 words. Plain and friendly, no emojis. Include: pickup day and site, the collection window, bring your own bag, uncollected boxes are donated after the window closes, and a line saying to reply or use the changes link before Wednesday noon if they want to skip next week. Do not invent anything else. Provide a subject line under 50 characters.

Illustrative output: subject "Your box is ready on [pickup day]"; body "Hello [first name], your share is ready for collection on [pickup day] at [site], between [window]. Please bring a bag. Boxes not collected by the end of the window are donated. If you need to skip next week, tell us by Wednesday noon using the link below." A sound draft. Two things to check: that the deadline in the email is the deadline in your rules, and that the link is the changes form link, not the sign-up form link.

Send a test merge to yourself with two made-up rows before the real one. Check that a placeholder has not come through as raw text, which is the commonest failure. The mail-merge tutorial covers the mechanics and the points that keep messages out of spam folders. A reminder sent the day before suits most schemes; a second, shorter one on the morning suits members who forget.

Step 4: box notes that members read

A box note tells members what is in the box and what to do with the unfamiliar parts. It is also where you explain a swap or a shortage. Take the contents from your packing sheet, not from memory.

Write a box note for this week's CSA share, under 120 words. Use only the contents listed. For any item flagged UNFAMILIAR, add one sentence on a simple way to cook it. Do not claim health benefits, do not give storage times I have not provided, and do not mention any item not listed. Tone: plain, friendly, specific.

CONTENTS (full share): kale bunch, salad mix 200 g, carrots 1 kg, beetroot 500 g, kohlrabi x2 (UNFAMILIAR), garlic x3 bulbs, parsley bunch
NOTE FROM THE FARM: the first beetroot of the year; peas not ready, expected next week

Illustrative output: a short paragraph naming the items, a line suggesting kohlrabi peeled, sliced and eaten raw with salt or roasted in wedges, and a line about peas next week. Common errors to fix: the assistant adds "perfect for a hearty soup" for kale when you never said so, or quotes a quantity for the kohlrabi that is not in your list. Check against the list, and delete any extra claim. If you plan the contents for several weeks ahead, veg box planning with AI covers it.

Skip weeks, swaps and the rules that make them painless

The skip-week rule has four parts: a deadline, a limit, an outcome and a way to claim. Write all four. The deadline lets you pack to the real number. The limit stops a member skipping half the season. The outcome (credit, donation or extension) must be chosen once. The way to claim is one link.

Handling a skip then takes one row: date, member number, "skip", week. A formula checks the member has not used their limit. Say a member asks to skip a third week when the rule allows two, you can reply with a draft from the assistant that is kind and clear:

Draft a reply to a CSA member who wants to skip a third week. Our rule: two skips a season with five days' notice. Be kind and brief, under 70 words. Offer exactly one alternative: a friend or neighbour can collect their box using their member number. Do not offer a refund or credit. Sign off [your name].

The restriction on offers is deliberate. Left alone, an assistant will cheerfully promise a credit you have not agreed to give. Swaps follow the same logic: allow named swaps (skip the beetroot, take extra carrots) only when you can honour them from the harvest, state the swap deadline, and log each swap in the changes sheet. If a swap list gets long, ask the assistant to count requests per item, so you can see that 14 of 45 members asked to avoid beetroot and decide whether to put less of it in.

Awkward weeks the sheet has to handle

The member who gives the wrong site

A member signs up for Saturday site A but always turns up at site B. The sheet shows the member's pickup record; the packing sheet shows a box left at A. Add a "collected at" tick to the weekly view and ask the assistant to list members whose boxes were left uncollected two weeks running. Then ask them, kindly, if the site is wrong.

Before and after: a clearer deadline

Before: "Let us know in good time if you want to skip." After: "Tell us by Wednesday noon if you want to skip next week's box." The after version removes a dispute before it starts. If you find vague phrases in your own emails, paste the email and ask for every sentence that contains a vague time or amount, then replace each one yourself.

A flood destroys a crop

Some weeks the box is thin. A member who has paid for the season should hear about it early and honestly. Give the assistant the facts: what failed, what will replace it, when the box returns to normal. Ask for a short, direct note without drama. Do not let it promise compensation or invent a cause; keep to what you know.

Mistake: the reminder that went to cancelled members

An illustrative grower cancelled three members' shares in the changes sheet, but the reminder merge ran from the original members sheet and still included them. The three received "your box is ready". One turned up. The fix was to merge only from the weekly view, which already subtracted cancellations, and never from the raw members sheet. The check is easy: the number of rows in the merge file must equal the number of boxes on the packing sheet.

Money matters

Payment sits outside the flow described here. If you take payments, record only whether a member has paid, not card details, and use a payment provider's own pages. For retention, cancel reasons and save offers, see subscription box churn; the same patterns apply to a seasonal share.

A Monday routine that takes forty minutes

Once the pieces exist, the week runs on a fixed order. Settling the order matters more than any single tool, because it is what stops a Thursday scramble.

1. Monday morning: check the changes sheet. Look for rows logged since last Monday and read any that carry free-text details. Answer anything that needs a person. Ten minutes.
2. Monday midday: open the weekly view. Confirm the total equals active members for the week. If it does not, find the row that breaks it before you do anything else. Five minutes.
3. Tuesday: write the box note. Take the contents from the harvest plan, draft with the assistant, check each line against the list. Ten minutes.
4. Wednesday noon: skip deadline passes. Freeze the weekly view and send the packing sheet to whoever packs.
5. Day before pickup: send the reminder. Send a test to yourself first. Five minutes.
6. Pickup day: tick off collections. Tick as members arrive, or at the end of the window from the list left over. Ten minutes.

The ticking at the end is what feeds the uncollected-box number. Without it you have no way to tell whether the reminders work.

Closing the season and inviting members back

Renewals are where a sheet pays off a second time. Because every member has a row with their share size, pickup site and skip use, you can write a renewal email that mentions only what is true for each group, using merge fields. Make two or three versions rather than one for everyone: members who collected nearly every week, members who skipped the maximum, and members who left boxes uncollected.

Write three short renewal email drafts for a CSA farm, each under 100 words, for these groups. Use the placeholders [first name], [share size] and [site]. Do not promise a price, a date or a share contents list that I have not given. Do not mention any other member. Ask the member to confirm their place by [date to be added].

GROUP 1: collected at least 18 of 20 weeks
GROUP 2: skipped the maximum two weeks and collected the rest
GROUP 3: three or more boxes left uncollected; ask gently whether a different pickup day or site would suit them better

FACTS I CAN STATE: next season starts in spring; same two pickup sites; I will confirm price and dates in a separate message.

Illustrative output for group 3: "Hello [first name], thank you for being part of the share this year. A few of your boxes were not collected, and I would like to make it easier for you next season. Would a different pickup day or site suit you better? Reply with your preference and I will keep your [share size] place at [site] or move you." Check that it does not apologise for you or promise a change you cannot make. Then send a reply form that logs the answer in the sheet, so the preference sets next season's row.

At season's end, ask the assistant to summarise the changes sheet into counts: skips by week, swaps by item, moves by site. The pattern often shows a week where half the skips landed, usually a holiday, and you can plan a lighter harvest or a "double box" the week after. It is evidence for next year's rules, and it costs a few minutes with data you already hold.

Testing the whole chain before week one

Run a dress rehearsal two weeks before the season. Invent six members with names like "Test One", enter them through the real form, log one skip and one pickup move through the changes form, and then run the weekly view, the reminder merge to your own address and the box note. You are looking for three faults: a form answer that lands in the wrong column, a filter that miscounts the skip, and a placeholder that arrives as raw text. Fixing them with six invented rows is a quiet afternoon; fixing them with 48 real members is an apology email. Delete the test rows afterwards and keep a copy of the working layout as your template for next year.

Privacy and what to keep out of the assistant

Members trust you with names, emails, phone numbers and addresses. The assistant never needs them. Use placeholders for drafting, a handful of invented rows for formula testing, and the merge in your own email tool for real sending. Allergy and dietary notes should stay in your sheet and be handled by you. If a member writes about a health condition, reply personally.

Check also who can open your sheet. Share it with the people who pack and no one else, and remove access when volunteers leave. If the sign-up form is a Google Form, note that Google gives the form's collaborators access to a newly created response spreadsheet automatically, so tidy the form's collaborator list as well as the sheet's. If some members live under different privacy rules from you, take advice from a qualified adviser on data-protection duties, since they differ by place.

Signs the form-to-reminder chain is working

Look at four numbers over the first six weeks: the hours you spend on admin each week, the count of "where is my box?" messages, the number of uncollected boxes, and the number of skips logged against the number of skips emailed in. If the hours fall below two a week, uncollected boxes fall below one in twenty and nobody emails a skip instead of using the form, the system works. If the form is ignored, move the link to the top of the reminder and put it on the pickup table as a printed code. Farm shop weekly boxes and labels has more on the packing side.

Questions from CSA growers about the weekly admin

Do I need CSA software or is a form and sheet enough?

As a rough rule of thumb, for up to 60 to 80 members, a form, a sheet and a mail merge is usually enough. Dedicated CSA software earns its keep when you need online payments, member self-service swaps and add-ons. Decide by counting the hours the admin takes you each week.

Should the AI see my members' details?

It does not need to. Reminders can be built with placeholders such as [first name] and merged by your email tool. For drafting and checking, use a small sample of made-up rows. Keep the real list in your own sheet.

How do I handle skip weeks fairly?

Set a written rule: a deadline before the pick, a limit on skips per season, and what happens to the skipped box (credit, donation or extension). Put it in the sign-up form so every member agrees once. Then every skip is a row in the sheet, not a negotiation.

What if a member's pickup details change?

Give them one route to change it, such as a link to a short form that adds a dated row for the change. The reminder merge reads the latest row for that member. Never edit the original sign-up row, or you lose the history.

Can AI write the weekly box notes?

Yes, from the list you give it of what is in the box and a note of anything unusual. It should not invent recipes' health claims or quantities. Check the contents list against the packing sheet before sending, since a wrong item in the note is an obvious error to the member.

Further reads

• Subscription Box Pricing: Build a Margin Model With AI — Price shares from costs and margin.
• Is AI Worth It for a Small Subscription Box? Five Jobs First — Which five jobs to hand to AI first in a box business.
• Farmers Market Stock Planning: How Much to Pack Each Week With AI — Plan how much to harvest and pack each week.
• How to Reduce No-Shows With AI Reminders and Automatic Rebooking — Reduce missed collections with timed reminders.
• Can Farmers Use AI for Farm Records and Paperwork? — Farm records and paperwork with AI, beyond the member list.
• How to Use AI in a Bakery Business: Wholesale and Standing Orders — Standing orders handled in a similar weekly rhythm.
• Selling Beef Boxes Direct: Hanging Weight, Cut Sheets and Pricing With AI — Convert hanging weight to retail cuts, price a quarter, half or box, and build the order form and deposit steps with AI checking your sums.
• Organic Certification Records: Prepare the Paperwork With AI — Use AI to tidy field logs, input records and draft plan text, then see exactly what a certification body will still inspect.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: general practice for community-supported agriculture schemes; Google Docs Editors Help on saving form responses to a spreadsheet (checked November 2026); standard sheet and mail-merge features; all member numbers and figures in the examples are illustrations.