Recipes across several work areas
These playbooks show how teams combine recipes for bigger pieces of association work. They are not automation promises. They are guided journeys: gather evidence, review the plan, approve sensitive steps, then verify the outcome.
New member from enquiry to welcome
Section titled “New member from enquiry to welcome”For: Membership team, Member services · Covers: Membership, billing, portal access, communications
| Stage | Powered by | Outcome |
|---|---|---|
| 1. Check the person and possible duplicates | R-01-01, R-10-02 | One clear candidate record and any duplicate concern before onboarding. |
| 2. Prepare the join or renewal action | R-01-02 or R-01-03 | Membership option, price, dates, and approval point are visible. |
| 3. Confirm payment or invoice posture | R-06-01, R-06-07 | Finance knows whether money is due, paid, disputed, or scheduled. |
| 4. Check access and welcome message | R-01-08, R-05-02 | The member can be welcomed with the right portal/access guidance. |
Where you stay in control: Staff approve the member setup, any payment handling, and any outgoing welcome message.
Conference from launch to closeout
Section titled “Conference from launch to closeout”For: Events team, Finance team, CPD administrator · Covers: Events, finance, communications, CPD, reporting
| Stage | Powered by | Outcome |
|---|---|---|
| 1. Check event readiness before opening | R-02-01 | Capacity, prices, sessions, communications, and launch risks are known. |
| 2. Monitor registration and unpaid balances | R-02-09, R-02-06 | Events and finance share one operational view. |
| 3. Handle live desk exceptions | R-02-02, R-02-03, R-02-05 | Walk-ins, waitlist, and cancellations are reviewed before changes. |
| 4. Apply CPD only to eligible attendees | R-04-06 | Attendance and enrolment are matched before credits are recorded. |
Where you stay in control: Roster changes, payments, cancellations, and CPD credits each need their own review point.
Fundraising appeal from plan to acknowledgement
Section titled “Fundraising appeal from plan to acknowledgement”For: Fundraising team, Communications team, Finance team · Covers: Campaigns, gifts, receipts, communications, reporting
| Stage | Powered by | Outcome |
|---|---|---|
| 1. Prepare campaign/source tracking | R-03-07, R-05-07 | Gift and response tracking is ready before outreach. |
| 2. Build the audience and message | R-03-10, R-05-02 | Segments and draft copy are reviewed before export or send. |
| 3. Record gifts and pledges cleanly | R-03-02, R-03-03, R-03-04 | Donor, campaign, payment, and receipt details are correct. |
| 4. Confirm acknowledgement and reporting | R-03-05, R-07-07 | Receipts, thank-yous, and leadership metrics can be evidenced. |
Where you stay in control: No outreach, gift entry, receipt resend, or payment action happens without staff approval.
Renewal season command centre
Section titled “Renewal season command centre”For: Membership team, Finance team, Communications team · Covers: Membership, billing, AutoPay, communications, dashboards
| Stage | Powered by | Outcome |
|---|---|---|
| 1. Understand renewal cohorts and risks | R-07-01, R-06-06 | Staff see who is due, scheduled, or likely to need intervention. |
| 2. Review complex member cases | R-01-09, R-06-07 | Odd statuses and billing disputes are diagnosed before action. |
| 3. Prepare reminders and next actions | R-05-08, R-13-01 | Messages and automation rules are reviewed before sending. |
| 4. Track progress for managers | R-07-06, R-07-07 | KPIs and exception lists support weekly decisions. |
Where you stay in control: Membership changes, payment collection, and reminder sends are separated into confirmed actions.
Certification cohort health check
Section titled “Certification cohort health check”For: CPD administrator, Education team, Communications team · Covers: Certification, events, communications, reporting
| Stage | Powered by | Outcome |
|---|---|---|
| 1. Review programme setup and cohort | R-04-01, R-04-08 | Requirements, enrolled members, and risk categories are clear. |
| 2. Check individual progress | R-04-04 | Member-facing answers are based on transcript evidence. |
| 3. Credit recent attendance where eligible | R-04-06 | Only attended and enrolled people are credited after review. |
| 4. Prepare expiry reminders | R-04-05, R-05-02 | Renewal messages are segmented and reviewed before send. |
Where you stay in control: CPD credits and communications are approved separately, with exception lists reviewed first.
Data cleanup before an import or campaign
Section titled “Data cleanup before an import or campaign”For: Data quality team, Imports team, Communications team · Covers: Duplicates, imports, data quality, reporting
| Stage | Powered by | Outcome |
|---|---|---|
| 1. Triage existing duplicate risk | R-10-01, R-10-02 | Likely duplicates are understood before new data arrives. |
| 2. Check incoming records before import | R-10-07, R-11-03 | File mapping and duplicate matches are reviewed. |
| 3. Validate or post only after approval | R-11-04, R-11-05 | Batch impact and errors are visible before load or rerun. |
| 4. Repair data-quality gaps | R-10-06, R-07-08 | Clean lists support campaigns or downstream systems. |
Where you stay in control: Imports and merges are high-impact actions and require explicit confirmation.
Portal page or form launch
Section titled “Portal page or form launch”For: Digital team, Forms owner, Membership team · Covers: RiSE, forms, custom data, design system
| Stage | Powered by | Outcome |
|---|---|---|
| 1. Audit current pages and forms | R-08-09, R-09-01 | The team knows what already exists and where risks are. |
| 2. Design the new page or form | R-08-06, R-09-02, R-09-03 | Content, fields, access, and owner decisions are agreed. |
| 3. Apply brand and placement rules | R-16-03, R-09-05 | The public experience is consistent and correctly placed. |
| 4. Test, publish, and verify | R-09-06, R-08-07, R-09-08 | Submission, writeback, routing, and page rendering are checked before announcement. |
Where you stay in control: Created assets are not treated as live until publish, permissions, and browser verification are complete.
Leadership pack from operational evidence
Section titled “Leadership pack from operational evidence”For: Leadership team, Reporting team, Department leads · Covers: Reporting, dashboards, membership, finance, events, fundraising
| Stage | Powered by | Outcome |
|---|---|---|
| 1. Agree the questions and definitions | R-07-01, R-07-07 | Metrics are defined before numbers are compared. |
| 2. Build cross-domain evidence | R-07-09, R-06-08, R-03-10 | Membership, money, giving, and engagement sources are connected carefully. |
| 3. Create dashboards or reusable reports | R-07-06, R-07-03 | Approved assets support repeatable management review. |
| 4. Explain caveats and next actions | R-01-10, R-05-08 | Leaders see where action is needed, not just totals. |
Where you stay in control: Each KPI should show source, date range, exclusions, and whether it is ready for board-level use.

