THE MEMBERSHIP OPERATIONS FIELD GUIDE
Manage membership across regional branches.
Give local officers a useful view of their members, with a clear route to central review and a record of the decision.
By VeritableRoll · Updated · Product screenshots use fictional records.
Separate the person from their memberships
A member can belong to the national body and a regional branch, or to more than one branch. Model the person once, then keep the membership number, grade, dates and status with each membership. That preserves the difference between “Fellow nationally” and “Member of the Glasgow branch”.
During migration from Excel, keep a stable person reference across those rows and a distinct reference for each membership. Decide whether an external number is unique nationally or only within its issuing branch before importing.
Give each role the access its job needs
Start with responsibilities, then configure access. In VeritableRoll, access follows the organisation or branch scope assigned to the user. Seeing a person in one branch must not reveal their memberships in other branches.
| Role | Day-to-day work | Boundary to test |
|---|---|---|
| Branch officer | Review local members, prepare evidence and submit cases | Cannot browse another branch through search, exports or direct record links |
| Central reviewer | Review submissions, return incomplete cases and approve eligible renewals | Cannot approve a case they submitted themselves |
| Read-only staff | Inspect records within their assigned scope | Cannot change evidence or approve a case |
This table is a workflow to configure and test, not a claim that every organisation must use the same job titles. Give cross-branch access only where the role needs it, and remove it when an officer leaves.

Make the handover a reviewable case
Consider a Glasgow member whose CPD evidence is complete but whose cover reference is missing. The local officer resolves the missing reference, checks the effective dates and submits the assessment for central review. The submission should identify the member, policy version, evidence, submitter and time.
The central reviewer needs a queue of submitted cases, not a second spreadsheet of names. In the case, they should be able to explain every requirement: met, missing, unmet or excepted. Returning a case needs a reason that tells the branch what to correct.
If evidence changes after submission, reassess and resubmit the updated case. Approval must refer to the information actually reviewed. A newer, unreviewed value should not quietly replace the old decision record.
Keep exceptions inside the agreed authority
“Head office said yes” is not enough to explain a renewal six months later. Record which requirement was excepted, the policy provision, the reviewer’s authority and the reason. A permitted exception to 25 CPD hours does not turn 18 recorded hours into 25.
Allow exceptions only where your policy permits them. If a condition is mandatory with no exception route, the action is to obtain the missing evidence or decline the renewal. See the worked CPD assessment.
Distinguish an assessment, approval and issued renewal
An assessment explains whether the requirements are accounted for. Submission asks another person to review that result. Approval records their decision. Issuance creates the membership term. Keep those actions distinct so a branch does not mistake a green assessment for a completed renewal.
Before the first cycle, rehearse one ordinary case and one returned case using separate branch and central accounts. Confirm that the submitter cannot approve their own work, that a changed case requires review, and that the issued term and export agree on dates and member number.
For organisations with many branches, start with one agreed policy and a few representative branches. Use the same handover and reconciliation across the network; accommodate differences in data and permissions explicitly.