Loyalty software: a weekly operating workflow

What to take away

Why the workflow needs a named owner

A loyalty scheme fails quietly when nobody owns the join journey. Points post late, a referral link breaks, and the first person to notice is a customer. Assign one owner to each of four areas: member data, campaign build, reward fulfilment and reporting.

Ownership means a name in a rota, not a team inbox. When the owner changes, the handover note becomes the audit trail. Keep it short: what changed, what was tested, what is still open.

For email and text marketing, check PECR (Privacy and Electronic Communications Regulations 2003) as well as UK GDPR: PECR sets rules for electronic marketing, including when consent is needed and when the limited soft opt-in may apply. Under UK GDPR Article 6, record which lawful basis applies: consent, contract, legal obligation, vital interests, public task or legitimate interests. Follow the ICO's guidance on choosing your lawful basis for direct marketing and its direct marketing guidance and checklist. For live marketing calls, screen against the Telephone Preference Service (TPS) or Corporate Telephone Preference Service (CTPS), as appropriate.

Record the basis next to the audience definition. A dated consent record might read: 14 May 2025, member 4821 opted in to email at sign-up, source website, basis consent. Check whether the controller must pay the ICO data protection fee or is exempt, and keep its registration status on file.

Build the weekly cadence

A weekly rhythm beats a quarterly overhaul. Four checks, run on a consistent schedule each week, keep the scheme honest.

A typical weekly timetable looks like this:

The longest section of the workflow is usually campaign build, so it earns a closer look.

What the campaign build step covers

Campaign build starts with the audience definition and ends with a signed-off test. In between, you set the reward, write the message, and check the terms that apply. For referral campaigns, test attribution from invitation through the qualifying action to reward fulfilment, and make the eligibility, exclusions and reward terms clear. Where referral incentives are promoted, check the CAP Code, especially Section 8 on sales promotions and their material conditions.

For paid membership terms, check Part 2 of the Consumer Rights Act 2015, which addresses unfair terms in consumer contracts. The Act's Schedule 7 is a list of repeals, not the operative rules for current terms.

What the reporting step covers

Reporting should answer three questions: did the campaign run, did members respond, and what will change next week. Include delivery, reward redemptions and referral conversions, with each figure's source and date; compare results with the programme's own targets rather than an assumed industry benchmark.

How to size the workflow to your market

Workflow design depends on how your members actually buy. If most sales happen in store, your digital cadence still matters, but reward fulfilment carries more risk.

Workflow design depends on how your members actually buy. If sales are online, test the sign-up and redemption journeys on the website or app; if they are in-store, trace transactions through to reward posting. Match the checks and reporting to the channels your scheme uses rather than to a generic template.

Examples of loyalty and referral-marketing platforms include LoyaltyLion, Yotpo, Smile.io, Open Loyalty, Antavo, Talon.One and Mention Me. This is not a comparison: ask shortlisted suppliers to demonstrate how their platform supports your owners' checks for member data, consent, campaign testing, reward fulfilment, referral attribution and reporting.

Where handovers go wrong

Most failures sit at the join between two owners. Reward fulfilment hands back to data, and nobody updates the suppression list. Campaign build hands to reporting, and the test evidence stays in a chat thread.

Fix this with a two-line handover note at each boundary: what was done, and what the next owner must check. For referral handovers, include unresolved attribution issues or rewards still to be fulfilled. Store notes in one place so a later review can follow the chain.

A two-line handover note could read: Data check done 14 May. Suppression list updated, no failed posts. Next owner must confirm reward post times for the 20 May send.

Before launch, run the data, consent, campaign and reporting checks above, and confirm that referral attribution and reward terms have been tested.

Common questions

How often should the workflow run?

Weekly is the practical minimum for a live scheme with active rewards. Run the four checks at consistent points in the weekly cycle so the evidence is comparable week to week.

Who should own the consent record?

One named person, usually in marketing operations, not the agency running the send. That person confirms the lawful basis before each campaign and logs any change.

Does the workflow need a tool?

No. A shared document and a dated log will do for a small scheme. Loyalty software can help as activity grows, but the cadence and ownership still matter; assess platforms against the checks and handovers your team needs.