THE GOLD STANDARD OF INTELLIGENCE · SPECIALIST STUDY
Close a multi-site RDS payment system without closing a participant’s remedy too early
A multi-site respondent-driven sampling study can finish interviews while still owing value. Sites may hold cash floats, vendors may report unsettled cards or transfers, referral rewards may mature later, and unused or expired instruments may be described as breakage even though a participant still has a remedy. Good reconciliation follows each entitlement from approved event to usable value, separates participant identity from research data, and closes finance, vendors and field sites only after outstanding liabilities and dispute routes are resolved.
This guide belongs to the Intelligence subject root, the Gold Standard of Education, and the How X Works hub. It begins with a concrete decision, then tests whether the method still holds when the context changes.
Choose a reading route
Define entitlements and ledgers · chapters 1, 2, 3
Reconcile sites and vendors · chapters 4, 5
Control floats and liabilities · chapters 6, 7, 8
Close safely and measure harm · chapters 9, 10, 11
Govern retention and transfer · chapters 12, 13
The whole problem at a glance
| Question | Evidence | Unsafe shortcut |
|---|---|---|
| What is owed? | Consent/payment terms, eligible event, amount, timing and policy version | Using issued value as paid value |
| Where is the value? | Site, vendor, instrument, custody and status lineage | Netting all channels into one total |
| May an item close? | Usable delivery, expiry, dispute and reissue evidence | Writing off provider breakage |
| Did finance and participant views agree? | Entitlement-to-settlement reconciliation with exceptions | Balancing the bank account only |
Participant remedy and financial settlement are related but not identical states.
CHAPTER 1 OF 13 · Define entitlements and ledgers
1. Define the entitlement before counting payments
Write the promised amount, form, timing, eligibility event, referral rule, deductions if any, expiry and remedy route from the approved study materials. Give each obligation a controlled case key and policy version. A provider transaction is not the entitlement: it is one attempt to discharge it. Preserve amendments so later reconciliation does not judge an earlier participant under a newer rule.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: A protocol amendment raises the visit payment at two sites; reconcile by visit date and approved policy version rather than one final rate. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 1 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
CHAPTER 2 OF 13 · Define entitlements and ledgers
2. Separate participant, research and finance identities
Use a controlled crosswalk so the payment case can be joined to eligibility without placing names, phone numbers or sensitive network relationships in research exports or routine vendor files. Limit access by role and log joins. The reconciliation identifier should support deduplication and remedy while revealing no more identity than the payment channel requires.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: A vendor requests the recruitment coupon code; provide only the minimum settlement key unless an approved purpose requires the network identifier. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 2 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
CHAPTER 3 OF 13 · Define entitlements and ledgers
3. Design one state model across heterogeneous channels
Represent approved, issued, accepted, failed, reversed, activated, used, expired, disputed, revoked, reissued and closed states with event time, source and confidence. Cash may need custody and signed payout events; digital transfers may expose provider callbacks; cards may expose activation but not use. Map channel-specific facts to shared meanings without pretending that unavailable evidence exists.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: Replace physical cards with mobile money at one site; keep entitlement and remedy meanings stable while adapting channel evidence. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 3 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
CHAPTER 4 OF 13 · Reconcile sites and vendors
4. Reconcile site ledgers before netting totals
For each site, compare eligible study events, approved obligations, payment attempts, usable delivery, reversals, reissues and open cases. Then aggregate. Netting sites first can hide one site’s underpayment behind another site’s unused float. Preserve participant-level exceptions under access control and publish only safe aggregate summaries.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: Site A is overfunded and Site B underfunded by the same amount; do not call the study balanced until participant obligations are traced. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 4 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
CHAPTER 5 OF 13 · Reconcile sites and vendors
5. Reconcile vendor settlements to obligations
Match provider invoices, prefunding, issue files, status callbacks, expiry credits, chargebacks, refunds and pending batches to the study ledger. Define a cut-off and later-adjustment process. A vendor may consider value delivered when a code is generated, while the study may require a usable instrument received by the participant; keep both views and reconcile the difference.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: A provider marks an email voucher sent, but delivery bounces; retain the financial charge and participant liability as separate facts. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 5 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
Worked three-site reconciliation
| Item | Study ledger | Vendor or cash evidence | Closeout decision |
|---|---|---|---|
| Site A interviews | 100 entitlements | 98 usable transfers, 2 failed | Keep 2 liabilities open |
| Site B referral rewards | 40 matured rewards | 39 cards activated, 1 disputed | Keep appeal route open |
| Site C cash float | £1,000 issued; £760 paid | £220 returned; £20 shortage | Investigate shortage separately |
| Vendor breakage | £35 expired value | Provider proposes credit | Do not erase participant claims |
Amounts are fictional and illustrate state reconciliation, not a payment rule.
CHAPTER 6 OF 13 · Control floats and liabilities
6. Control field cash floats through custody
Record float authorisation, denomination, custodian, handoff, secure storage, payout receipts, replenishment, returns, shortages and surprise counts. Separate the person approving eligibility from the person reconciling custody where feasible. A cash variance is an operational incident; it must not be solved by refusing a participant whose entitlement is otherwise evidenced.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: A field worker loses a cash envelope after valid interviews; investigate custody while restoring participant payments through an approved route. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 6 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
CHAPTER 7 OF 13 · Control floats and liabilities
7. Treat breakage as a provider outcome, not proof of no liability
Unused, expired or unclaimed instruments can create breakage under a contract, but that accounting label does not by itself extinguish the participant-facing promise. Determine whether expiry was clearly disclosed, access was practical, contact was possible, replacement is permitted and the study retains a remedy. Track provider credits separately from unresolved participant obligations.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: A card expires after the field site closes; preserve the appeal and reissue decision under the approved terms. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 7 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
CHAPTER 8 OF 13 · Control floats and liabilities
8. Maintain an outstanding-liability register
List every approved but not participant-safe-closed obligation with amount, currency, site, channel, age, reason, last action, owner, reserve treatment and next review. Reconcile the register to general-ledger accruals without exposing identities. Ageing helps prioritise action, but a long-open item should not disappear merely because it is inconvenient.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: Migrate finance systems during closeout; carry open obligations with stable lineage rather than recreating only aggregate balances. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 8 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
CHAPTER 9 OF 13 · Close safely and measure harm
9. Prevent duplicate value without criminalising ambiguity
Detect duplicate obligations, duplicate attempts and valid multiple rewards separately. Use linked lineage from original to revocation and reissue, with one usable-value rule where policy requires it. When an original instrument cannot be revoked, apply a predefined risk and participant-harm rule; do not turn an uncertain provider status into an accusation against the participant.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: A delayed transfer succeeds after a replacement is issued; follow the declared recovery or acceptance policy and preserve the chronology. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 9 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
Participant-safe closeout gates
| Gate | Required evidence | Failure response |
|---|---|---|
| Entitlement completeness | Eligible events linked to obligations | Reconstruct from issue-time sources |
| Delivery usability | Receipt, activation or controlled exception | Reissue or participant contact route |
| Vendor settlement | Invoices, credits, reversals and pending files | Hold reserve and escalation |
| Float custody | Issue, payout, return and variance | Investigate without delaying valid claims |
| Remedy continuity | Appeal owner, notice and retention | Keep case route beyond field closure |
One unresolved high-harm case can remain open even when aggregate amounts are small.
CHAPTER 10 OF 13 · Close safely and measure harm
10. Protect participant remedy beyond field closure
Publish a reachable, accessible and time-bounded contact route; preserve language, disability and technology alternatives; and name the decision owner after local staff leave. Case closure requires notice and usable resolution, not simply an internal journal entry. Keep contact data only as long as authorised for remedy and separate it from research analysis.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: A participant reports non-receipt one month after recruitment ends; route the case without requiring return to the closed field site. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 10 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
CHAPTER 11 OF 13 · Close safely and measure harm
11. Assess recruitment and inference consequences
Payment failures can affect trust, coupon sharing, repeat participation, recruitment depth and who remains in the sample. Compare failure and remedy by site, wave, channel and relevant access groups with privacy protection. Treat patterns as possible selection mechanisms, not proof of intent. Document whether sensitivity analyses or operational correction are needed.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: One site’s mobile provider fails during peak recruitment; examine recruitment chains and timing rather than treating the issue as finance-only. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 11 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
CHAPTER 12 OF 13 · Govern retention and transfer
12. Close sites, vendors and finance in the right order
Define independent gates for field inventory, site ledger, participant liabilities, vendor statements, credits, disputes, contact continuity, data retention and financial posting. A site can be operationally closed while cases remain centrally owned; a vendor contract should retain access to required status and remedy data until obligations are resolved. Preserve a reserve and escalation path for late reversals.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: A vendor contract ends before card expiry; export status evidence and agree who honours replacements before terminating access. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 12 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
CHAPTER 13 OF 13 · Govern retention and transfer
13. Retain evidence and write a bounded conclusion
Keep the minimum records needed for audit, participant remedy, financial duties and study integrity under approved retention schedules. Record destroyed contact data, unresolved limitations and transfer of ownership. Report totals by entitlement, channel and outcome with outstanding cases visible. Do not declare “all participants paid” when evidence proves only that funds left the study account.
Build the evidence record around the decision rather than the convenience of the software. Name the protected or measured unit, the version in force, the time boundary, the numerator and denominator, exclusions, missing cases and the person authorised to act. Keep raw observations separate from interpretation, and retain failed and rejected cases as well as successes. That separation lets a later reviewer distinguish a changed world from a changed judgement.
Convert the finding into a bounded action. Predefine the trigger, permitted response, owner, expiry, rollback and verification window. Keep one worked case that passes and one that fails. A system which stores only successful cases cannot demonstrate that its control detects the failure it was designed to contain.
Evidence discipline: record the observation, version or time boundary that supports this chapter’s conclusion. Preserve the rejected alternative as well as the selected action. That makes a later review able to distinguish a changed world from an undocumented change of mind.
Changed-context transfer: Transfer stewardship to a sponsor archive; prove the new owner can answer an appeal and reconstruct settlement without receiving unnecessary research identifiers. The method transfers only if the decision question and measurement meaning survive the change. If either changes, rebuild the comparison rather than copying the earlier threshold or weight.
Chapter 13 check · what should survive an audit
- State the decision and measurement unit in one sentence.
- Preserve version, timing, denominator, exclusions and missing-case evidence.
- Connect the finding to a bounded action, rollback and later verification.
Contents · Previous chapter · Return to the Intelligence guide
Verification lab: work the decision twice
Create ten fictional entitlements across bank transfer, voucher and cash. Include one failed transfer, one expired unused voucher, one lost cash envelope and one late reversal. Reconcile participant, site, vendor and finance views without netting away exceptions.
Give one participant an original card and a replacement after reported non-receipt. When the original later activates, apply a predefined duplicate-value rule and preserve a participant-safe notice plus full lineage.
Close a field site while two liabilities and one cash shortage remain. Transfer case ownership, reserve the amounts, keep the remedy route live and show which closure gates can pass independently.
Limits and misconceptions
A balanced bank account does not prove participants were paid
Usable delivery and remedy need participant-facing evidence.
Breakage does not automatically erase an entitlement
Contract accounting and the participant promise are distinct questions.
Duplicate detection is not fraud proof
Provider delays, reissues and data errors can create legitimate ambiguity.
Field closure is not remedy closure
Late failures and reversals need continuing ownership and contact routes.
Questions readers ask
What is the unit of reconciliation?
- The participant entitlement and its linked payment-attempt lineage, not only an invoice or bank total.
How should cash floats be controlled?
- With authorisation, custody, payout, counts, returns, variance investigation and role separation.
What is breakage?
- Unused or expired value under a provider arrangement; it does not by itself settle the participant obligation.
Can sites be netted against each other?
- Only after each site’s participant obligations and exceptions are visible.
When is a payment case closed?
- When the approved obligation has a documented usable resolution or an authorised, communicated alternative decision.
How long should the remedy route stay open?
- For the period required by the approved study, contract, ethics and applicable duties, with ownership explicitly transferred if fieldwork ends.
Practise, verify and continue
Build a multi-site ledger that joins each approved RDS event to payment attempts, vendor settlement, site custody, participant remedy and finance posting. Reconcile three channels and leave every unresolved liability visible.
Replace vouchers with instant mobile transfers at one site and a central cash float at another. Keep the entitlement, privacy and remedy logic stable while rebuilding delivery evidence, provider settlement and custody controls.
Practical evidence check
Before implementation, write a one-page evidence map with the decision, unit of analysis, version or time boundary, inputs, outcomes, uncertainty, authority and stop rule. Attach one worked case that passes and one that fails. A reviewer should be able to reproduce the reasoning without relying on the memory of the person who built the system.
Run one changed-context rehearsal before approval. Alter a mechanism rather than a cosmetic detail, then identify which calculation, safeguard or governance gate must change. Record any conclusion that does not transfer. This short rehearsal is often the fastest way to expose a hidden assumption before it becomes an operational dependency.
Related eduKate reading
RDS payment disputes and participant remedy
RDS non-cash incentive delivery and replacement pathways
RDS incentive fraud and payment reconciliation
RDS multi-site harmonisation and governance
Authoritative sources and scope
FDA guidance on payment and reimbursement to research subjects
ICH E6(R3) Good Clinical Practice guideline
The sources support documented participant payment terms, agreements, responsibilities and retained records in research. The ledger states, amounts and examples are illustrative. Real studies must follow their approved protocol, consent, ethics review, contracts, accounting standards, privacy rules and local law.