> For the complete documentation index, see [llms.txt](https://docs.range-mate.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.range-mate.co.uk/for-club-admins/membership-workflows.md).

# Membership Workflows

Set out what a member must do before they become a full member, track each member's progress, and keep the record of who signed what off.

A **membership workflow** is your club's journey to full membership: one or more **stages** (usually just **Probation**), each with **requirements** such as an induction, a number of range visits, a safety test or a committee sign-off. The journey always ends at the same place, **Becomes a full member**. You don't build, name or map that end. When everything on the last stage is done, you confirm it, choose the membership type, and the member becomes a full member.

You can also build any number of **separate tracks** (for example, a Range Officer qualification) that don't touch membership.

Find it under **Memberships → Workflows (probation)** in the admin menu.

{% hint style="info" %}
A club has one membership workflow. Every new club starts with a suggested one, **Probation to full member**, saved as a draft with an induction and a committee sign-off. Nobody is affected until you publish it, and you can change anything. An older club with no workflow can create the same draft in one click from the Workflows page.
{% endhint %}

## Building the journey

1. Open **Memberships → Workflows (probation)**. Pick **Start from our suggested workflow**, or **Start from blank** and give it a name. Members see the name on their progress page.
2. Add a **stage** and say who is on it: **On probation** for the usual case, or **Applied**, **Invited to interview** or **On the waiting list** for an earlier step. Each status has one stage.
3. On the stage, add your **requirements** (below). New requirements are **required** by default, so they hold members back until done.
4. **Publish**. The Publish button stays greyed out until the workflow is ready, and the page lists what's missing, naming the stage concerned. Publishing asks you to confirm.

The last stage is followed by the fixed **Becomes a full member** card. There is nothing to add there.

{% hint style="warning" %}
If your club built a workflow before this release with a final **Full member** stage, it still works. That stage now shows as the finish line. If it has requirements on it, move them to an earlier stage, because nothing can be checked once someone is a full member.
{% endhint %}

## Adding members who are already on probation

When you publish, the page tells you how many members are **already** at a stage of the workflow (for example, "5 members are already on probation") and lists them, with where each one's counting starts. Tick the ones to add. **Only the members you tick are added.** Tick nobody to publish without adding anyone.

* **Select all on this page** ticks everyone listed on the page you're looking at.
* When the list runs to more than one page, **Select all N members who can be added, including those on other pages** picks everyone at a stage who isn't in the workflow yet, not just this page.

Before anything changes, you see the exact number and the names (the first ten, then "and N more"), and you confirm.

You can add people later too:

* From the workflow's page, which keeps a card listing anyone at a stage who isn't in the workflow yet. Tick the ones to add, choose **Add ticked members** and confirm.
* From the **Membership** tab of a member's page, with **Add to workflow** in the workflow panel.
* From **People → Users**: tick members in the list (or use **Select all N matching your search and filters**), then choose **Actions → Add ticked to membership workflow** and confirm. Only the ticked members are added. Anyone who doesn't fit is skipped, and you're told how many and why.

{% hint style="info" %}
Adding more than 200 people at once runs in the background so the page doesn't time out. The enrolments page shows them as they're added.
{% endhint %}

Adding someone never changes their membership status, subscriptions, invoices or payments. Their progress counts from the date they were put on probation (shown before you confirm), so a member who has already done nine of ten range visits shows nine of ten, not nought. Adding someone twice changes nothing.

New members are added on their own when they're put on probation or reach another stage.

## Requirement types

* **Manual sign-off.** A club official confirms it. Use it for an induction, a safety test or a committee decision.
* **Declaration signed.** Met when the member signs a declaration you choose. See [Declarations](https://docs.range-mate.co.uk/for-club-admins/declarations.md).
* **Attendance count.** Met when the member has a set number of **checked-in attendances**, optionally limited to specific events, events with a tag, locations or event types. The card shows the target, for example "3 attendances". Bookings don't count, attendance does. See [Attendance & range logs](https://docs.range-mate.co.uk/for-club-admins/attendance-and-range-logs.md).

{% hint style="info" %}
**Picking an event vs tagging events.** The specific-event picker matches one event, which suits a **recurring** event. If you create a **new event each time** you hold, say, a safety day, use **Limit to events tagged** instead and tag every safety day the same. See [Creating & managing events](https://docs.range-mate.co.uk/for-club-admins/managing-events.md#tagging-events).
{% endhint %}

* **Minimum time in stage.** Met once a minimum time has passed since the member reached the stage (for example a three-month probation). It updates on its own.
* **ID approved.** Met once you've approved the member's proof of ID on their profile.
* **Police check cleared.** Met once the member's police check has come back clear. You record the result under **Needs doing** on the member's page. To let someone through without a clear check, **waive** the requirement for them.

### Required vs optional

Required requirements decide when a member can move on. Optional ones are suggestions the member can tick off themselves, and never hold them back.

### Changing the order

Members see the requirements on a stage in the order you set. Drag a requirement by its handle to move it, or use the up and down arrows next to it (handy on a phone or with a keyboard). The order is saved straight away. Changing the order of a live workflow doesn't change anyone's progress.

### Doing one step before another

**Do other steps first?** on a requirement lets you choose other steps on the same stage that must be done before it. For example, set **Committee sign-off** to come after **Induction** and **Safety test**. Until those are done (or waived), the requirement is **locked**:

* You can't **sign it off** or **mark it met**. The panel on the member's **Membership** tab shows it as locked and says which steps come first.
* The member can't tick it off themselves. Their progress page shows a lock and "Do Induction first."
* An **attendance count** (or any other automatic requirement) keeps counting. If the member reaches the target early, it shows **Waiting for the other steps** and is ticked off as soon as they're done.

Only required steps can be chosen. Optional and disabled steps never hold anything up, so if a step you chose is later made optional or disabled, it stops locking anything. If you reset an earlier step, an automatic requirement that depends on it goes back to waiting.

{% hint style="warning" %}
You can still **waive** a locked requirement, for example for someone who did it at another club. The waive form warns you that the earlier steps aren't done and asks you to tick **Waive it before the other steps are done** to confirm.
{% endhint %}

### What counts

By default a count starts from when the member **reached the stage**. You can change it to count **all time**.

## Signing things off

A member's progress shows on the **Membership** tab of their page, under **Membership workflow**, with each requirement's status. Their **Overview** tab has a line for each workflow they're in, which takes you there. For each requirement you can:

* **Sign off** a manual requirement. You're asked for the **date** it happened (today by default), **who signed it off** (you by default, or any club official, or someone else by name) and an optional **note**. The record shows the named person and date, and keeps your name as the person who entered it.
* **Mark met** an automatic requirement by hand, for example a member who did the equivalent at another club. The same details are asked for, and the row says "Marked met by hand". The system won't overwrite your decision.
* **Waive** a requirement so it no longer holds a member back. A **reason** is required and shown on the record.
* **Reset** a requirement back to not done if you made a mistake. This clears who signed it off and when, and can pull a member back below the bar for the stage.

{% hint style="info" %}
These are your club's records of what happened and who vouched for it. Record the person who really did the sign-off, such as the range officer who ran the induction, rather than whoever happens to be logged in.
{% endhint %}

## Making someone a full member

Once every required requirement on the last stage is done, the member's panel says **Everything's done** with a **Confirm and make full member** button. It asks for:

* the **membership type** (chosen for you when your club has only one full membership type);
* whether to ask them to **pay** or to **skip payment**;
* whether to **notify the police**, if your club asks that each time.

It then runs the same change as **Change membership status → Passed probation**: the probation membership ends today, the full membership starts today, and who confirmed it is recorded. If a check fails (for example their ID isn't verified yet, or your club is at its member limit), you see the reason and nothing is changed.

To make someone a full member **before** everything is done, use **Make full member anyway**. You must give a reason, which is kept on the record.

Using **Change membership status → Passed probation** on the profile has the same effect on the workflow: the record is completed, not lost.

Members who've met everything on their current stage appear in your to-do list under **Members ready to move on**, which opens the enrolments list filtered to them.

## The record afterwards

When a member becomes a full member, their workflow record stays on the **Membership** tab of their page, marked **Completed** and read-only: every requirement's outcome, date, note and who signed it off, and when they became a full member and who confirmed it. The member sees the same record under **Your progress**. If a member leaves the club part-way through, their record is kept as withdrawn.

## Editing a live workflow

Editing a **published** workflow affects members part-way through it:

* **Disable, don't delete.** A requirement that members have started against is **disabled** (its history is kept) rather than deleted. A disabled requirement can be **re-enabled** at any time. If you're sure, a disabled requirement also has a **Delete** button that removes it for good, along with every member's history of it.
* **Raising a target moves progress back.** If you raise a count (for example, attendances from 3 to 10), members who'd met it go back to in progress.

When you add, edit, disable or re-enable a requirement on a live workflow, the members already working through it are refreshed automatically.

**Archiving** stops new members being added and stops progress being checked. Members part-way through keep their progress and records. You're asked to confirm, and you can bring the workflow back to draft later.

## Enrolments overview

**Memberships → Enrolments** gives you the whole picture: everyone working through a workflow, the stage they're on, how many of their required conditions are done, and the records of those who've finished. Filter by workflow and by status: **Active**, **Ready to move on**, **Completed** or **Withdrawn**.

From here you can **refresh** progress, which recalculates it against the current setup: **Refresh** on a row updates that member, and **Refresh all** updates everyone in the workflow you're viewing. Refreshing never undoes a sign-off or waiver, and never moves a member's stage.

## Not in this release

* "Supervised" and "on separate days" rules for attendance. Write them in the requirement's guidance text for now.
* Automatic moves. An admin always confirms the move to full membership.
* Qualifications after full membership. Use a separate track for those.
