The anniversary workflow is the automation layer underneath the anniversary milestone SOP. The SOP defines what happens at each tier; the workflow defines how the system fires and what the VA executes weekly.

A clean workflow lets a Fitness VA cover 100 percent of member anniversaries with under 2 hours of weekly time. A messy one means missed milestones and frustrated members. The difference is in the trigger, the branching, and the gift logistics.

For where this workflow fits in the broader role, our Fitness VA tasks list maps the responsibility split.

Workflow trigger

The workflow fires daily at 6am, looking 7 days ahead at member start dates.

For each member with a year-mark anniversary in the next 7 days, the system:

  1. Determines the tier (1, 3, 5, or 10 years).
  2. Routes to the correct sub-workflow.
  3. Schedules the touchpoints.
  4. Logs the upcoming milestone in the Airtable Members base.
  5. Sends the VA a Monday digest of the week's anniversaries.

Built in GoHighLevel, ActiveCampaign, or Make + Airtable, depending on your stack.

Tier branching

Four branches, each with distinct touchpoint logic:

  • 1-year branch. 3 automated touches + 1 manual (gift coordination).
  • 3-year branch. 2 automated touches + 2 manual (call + handwritten note).
  • 5-year branch. 1 automated touch + 3 manual (founder call + premium gift + featured story).
  • 10-year branch. 0 automated touches + full manual orchestration.

The pattern: as the milestone scales, automation drops and human craft increases. This is on purpose.

Touchpoint scheduling

Each branch schedules touchpoints relative to the anniversary date:

For 1-year anniversaries:

  • Day -7: email "Almost a year"
  • Day 0: branded social post + personal text
  • Day +3: testimonial Typeform link

For 3-year anniversaries:

  • Day -14: founder-name email
  • Day -7: VA phone call task created in Asana
  • Day 0: handwritten note + branded gift task created
  • Day +7: testimonial + referral invite

For 5-year anniversaries:

  • Day -30: founder calendar block created
  • Day -14: founder phone call task
  • Day 0: premium gift task
  • Day +30: featured member story task

For 10-year anniversaries:

  • Day -60: founder calendar block + planning task
  • Day -30: founder personal call task
  • Day 0: in-person or video celebration task
  • Day +30: featured story + studio event task

The system creates tasks; the VA and founder execute.

Gift coordination automation

Gift tasks include three pre-populated fields:

  • Member name and shipping address (pulled from Members base).
  • Tier-specific gift menu (linked from Inventory base).
  • Notes on past gifts (so you do not repeat).

The VA picks from the menu, marks the task complete, and the system logs the gift in the member's record. After 12 months, you have a clean history of what each member received.

Testimonial ask logic

The testimonial ask only fires if the member has not given one in the last 12 months. This prevents annual surveys from feeling like spam.

Mechanics:

  • Day +3 (or +7 for 3-year+): trigger Typeform send.
  • 7 days later: if no response, soft reminder.
  • 21 days later: if still no response, route to "next year" queue.

Aim for 30 to 50 percent response rate. Track lift in published testimonial volume monthly.

Manual override paths

Three opt-out flags:

  • Privacy flag. Member opted out of public recognition. All public touchpoints (social post, featured story) are skipped automatically; private touchpoints continue.
  • Recent issue flag. If a member had a complaint or churn-risk event in the last 30 days, the anniversary workflow pauses. The VA escalates to founder before any anniversary outreach.
  • Geography flag. Remote-only members get adjusted shipping logic; in-studio celebration tasks are converted to video equivalents.

These flags live on the member record. Set on day one of any new member who needs them.

Reporting

The Monday digest covers:

  • Anniversaries this week (count and tier).
  • Last week's completion rate (target: 100 percent).
  • Testimonials collected last week.
  • Featured stories scheduled for publication.

Three minutes to read; flags any execution gaps.

Performance targets

After 90 days running, expect:

  • 100 percent of 1-year anniversaries acknowledged within 24 hours of the date.
  • 90+ percent of 3-year anniversaries acknowledged with a personal touch.
  • 100 percent of 5 and 10-year anniversaries planned 30+ days ahead.
  • 30+ percent testimonial response rate across tiers.

If targets miss for two consecutive months, audit the workflow for a broken trigger or a stale data source.

Common workflow failures

Three patterns to watch:

  • Stale start dates. Members migrated from a prior system sometimes have wrong start dates. Audit on day one of workflow setup.
  • Time zone misfires. If the trigger fires in the wrong time zone, anniversaries slip by a day. Test the trigger in the first week.
  • Inventory gaps. Gift tasks fail when stock is empty. Build inventory monitoring into the workflow (auto-reorder when below 10).

When to evolve the workflow

Three triggers to revisit:

  • Member volume crosses 500 active. Consider adding 7-year and 15-year tiers.
  • Founder time on 5 and 10-year tiers becomes unsustainable. Add a senior VA tier between founder and primary VA.
  • Brand voice or visual identity changes. Refresh all automated copy and visual assets.

For pricing on a VA running this workflow, see our Fitness VA cost guide. For the broader hire, our hiring playbook covers the candidate fit.

Frequently asked questions

Do I need GoHighLevel or can I do this in Mailchimp?

Mailchimp can fire the email touchpoints; it cannot create the manual tasks. For the full workflow you need GoHighLevel, ActiveCampaign with Tasks, or Make + Airtable.

How long to set up?

Two to three days for a VA familiar with the toolset. A week if they are learning the platform from scratch.

What if my member roster is in MindBody only?

Pipe the data to Airtable via Zapier or a native integration. The workflow runs from Airtable, not from MindBody.

Should I run a test anniversary first?

Yes. Use a member with consent (a friend or yourself) to verify timing and content before going live. Catch errors in test, not on a real member.

How does the workflow handle leap years and date weirdness?

Every modern automation tool handles this correctly. Verify in test once; trust thereafter.

For the SOP version of this with the touchpoint copy specifics, see our anniversary milestone SOP.

#anniversary workflow fitness VA#fitness anniversary automation#gym member anniversary#fitness va workflows