Referral programme coordination: verifiable acceptance criteria

Editorial illustration of Referral programme · Acceptance criteria

This guide focuses on agreeing on an acceptable outcome before production begins. The worked example follows three units: “referral request”, “contact follow-up” and “status closure”.

Reference input: programme rules and touchpoints. Expected output: a referral operations register. Before assigning work, confirm the current input version and who will review the result.

Write requirements that can be observed

An acceptance criterion for the referral programme coordination describes a checkable property of the outcome. “Make it professional” expresses an expectation but does not resolve a review. For referral request, specify required content, reference version, destination and evidence of compliance. When a criterion involves editorial judgment, define who applies it and show a commented example. Agreeing before production exposes different interpretations while they are still inexpensive to resolve. Do not introduce new criteria at the end without recognizing their effect on the work already committed. A usable criterion supports a decision rather than simply expressing a preference.

Show a passing example and a failing example

Compare two versions of contact follow-up. One retains the required information, uses current material and supports the next stage. The other may look finished but leaves an important condition unchecked. In this process, watch the failure of leaving a duplicate referral with two different owners. Document the specific difference instead of applying a broad quality label. A useful comparison explains which observation would change the decision. If no evidence can resolve the disagreement, the criterion still needs refinement or an authorized person to interpret the case. The comparison should reveal an actionable difference, not just a subjective ranking.

Worked example

The fictional programme receives two referrals for one contact through different touchpoints. The register prevents duplicate follow-up and preserves authorized origin. Each state describes a verifiable action without treating a received referral as a completed sale.

The example involves Valeria, Camila and Nora. Names, situations and numbers are illustrative and do not represent customer results. The three units let you test the proposed approach before extending it to other work.

UnitObservable requirementFailure conditionAcceptance
referral requestCurrent input and defined outcomeMissing version or destinationCamila checks the requirement
contact follow-upConsistent with approved materialAn unresolved difference remainsValeria obtains a resolution
status closureReceiver can use the outcomeFinal check has not runNora retains evidence
Worked-example diagram: Referral programme · Acceptance criteria
Diagram of the illustrative example. The table and text explain the complete records and their conditions.

Define who accepts and what evidence remains

The person accepting status closure needs the criteria, access to the reviewed version and time to decide. Record acceptance, return or conditional acceptance with reasons. Conditional acceptance needs an explicit outstanding item and clear boundary; it must not be mistaken for full closure. Retain evidence another reviewer would need to understand the decision. Comment volume does not determine acceptance. A traceable decision about the correct version and agreed requirements does. This distinction helps teams avoid reopening finished work merely because someone discovers an old discussion after the delivery has moved on.

Resolve ambiguity before closure

To validate a referral operations register, the proposed check is to check the identifier and latest authorized follow-up. If applying a criterion to a real case exposes ambiguity, record it and resolve it with the approver. Distinguish clarifying an unclear instruction from changing the requested outcome. The first explains how to check the existing agreement; the second may require capacity and a new decision. Check whether the defect affects other units as well. At closure, leave an identified version and enough explanation that the next review does not need to renegotiate from the beginning what compliance means.

What to check before closure

The risk to control in this case is leaving a duplicate referral with two different owners. A completed label needs a supporting observation. Keep the following beside the decision so the receiver can establish what was checked:

  • Input and version used: programme rules and touchpoints.
  • Case check: check the identifier and latest authorized follow-up.
  • Outcome under review: a referral operations register.

Your privacy on this blog

Choose our own statistics, Google Analytics, Cloudflare, and Google Signals with personalized advertising. The last option allows audiences for GGyess ads and combines your activity with Google data; it also requires permission for Google Analytics. Accept all allows the available options, including advertising when available; it does not subscribe you to the newsletter. Necessary only rejects every option. Permissions last up to 180 days; we remember advertising refusals for 12 months.

Necessary preferences

Remember your language, display theme and privacy choice. These preferences are not used to measure your reading.

Privacy notice · Privacy requests: myprivacy@gloadi.com