THE GOLD STANDARD OF INTELLIGENCE · SPECIALIST STUDY
Deliver cross-site RDS corrective action without confusing rollout completion with participant or analytical benefit
A cross-site recurrence portfolio produces value only when shared and local corrective actions reach field devices, translated protocols, participants, specimens, datasets and estimators in the right order. Delivery must respect common dependencies without erasing site readiness or local exceptions. Benefit validation then asks whether participant remedies closed, mixed-version exposure fell, estimator safeguards worked and recurrence mechanisms stayed absent under changed contexts. Independent challenge and reprioritisation keep the portfolio honest when a widely deployed action delivers uneven results.
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
Turn portfolio decisions into delivery contracts · chapters 1, 2, 3
Sequence shared dependencies and site readiness · chapters 4, 5
Close participant remedies and protect estimates · chapters 6, 7, 8
Validate benefit with changed contexts and independent challenge · chapters 9, 10, 11
Reprioritise, authorise and hand over · chapters 12, 13
The whole problem at a glance
| Delivery question | Required evidence | Unsafe shortcut |
|---|---|---|
| What is shared? | Dependency and mechanism map | One rollout plan |
| Is a site ready? | Local prerequisites and exercise | Manager sign-off |
| Who remains exposed? | Participant and case register | Ticket closure |
| Did benefit occur? | Changed-context outcome evidence | Deployment percentage |
The same corrective action can require different local sequencing without changing its protected outcome.
CHAPTER 1 OF 13 · Turn portfolio decisions into delivery contracts
1. Translate portfolio findings into corrective-action contracts
For every shared and local mechanism, name the protected participant, field, specimen or estimate outcome; the action; prerequisites; evidence; owner; deadline; rollback and closure gate.
Evidence record: Store portfolio and action versions, mechanism class, affected sites, dependencies, local variants, protected outcomes, authority, resources, expected benefit and residual exposure. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: No action enters delivery as a generic recommendation; it must have an observable protected result and a bounded cohort. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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-library fix protects field-script consistency, while an offline-device recall remains a separate action with its own 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 1 check · what should survive an audit
- Define the decision unit for “Translate portfolio findings into corrective-action contracts”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 2 OF 13 · Turn portfolio decisions into delivery contracts
2. Build the shared-dependency and precedence map
Map protocol packages, translations, device releases, identity services, training, specimen linkage, remedy channels and estimator code. Identify which actions enable, constrain or invalidate others.
Evidence record: Keep dependency versions, interfaces, owners, site consumers, failure effects, precedence, parallel work, fallback, validation fixtures and change notices. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Sequence around causal dependency and participant protection, not administrative ownership or the easiest deployment count. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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: Training starts only after the translated release passes contradiction checks, while participant contact capacity is prepared in parallel. 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
- Define the decision unit for “Build the shared-dependency and precedence map”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 3 OF 13 · Turn portfolio decisions into delivery contracts
3. Define site readiness without erasing local conditions
Assess staffing, language, device connectivity, protocol versions, participant contact routes, specimen systems, data cut, estimator pipeline and local approvals for each cohort.
Evidence record: Record site and cohort, readiness criteria, evidence date, gaps, temporary controls, local exceptions, owner, exercise result, approval, expiry and escalation. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: A site joins a delivery wave only when missing prerequisites are protected or explicitly accepted by authorised review. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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: An offline site enters a later device wave but starts manual version verification immediately. 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
- Define the decision unit for “Define site readiness without erasing local conditions”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 4 OF 13 · Sequence shared dependencies and site readiness
4. Stage delivery waves with rollback and learning
Begin with representative cohorts, observe field use and consequences, then expand. Keep old and new versions identifiable, quarantine mixed states and carry learning into later waves.
Evidence record: Retain wave plan, cohort denominator, versions, start and end, fixtures, adoption evidence, incidents, participant effects, estimator effects, rollback, decision and lessons. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Expansion requires observed behaviour in the cohort; package download or training attendance alone is insufficient. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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 clinic downloads the release but a hidden scenario reveals the old script in field use, so expansion pauses. 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
- Define the decision unit for “Stage delivery waves with rollback and learning”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 5 OF 13 · Sequence shared dependencies and site readiness
5. Control local exceptions and temporary safeguards
Bind exceptions for language, connectivity, device, staffing, legal or participant-access constraints to a compensating control, evidence, owner and expiry. Compare exception growth across sites.
Evidence record: Store exception scope, reason, affected mechanisms, participant and estimator consequence, temporary protection, monitoring, burden, authority, expiry and renewal history. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Expired, repeated or expanding exceptions become portfolio evidence and may reorder shared investment. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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 translated script delay is covered by supervised use of one validated bilingual version for a bounded period. 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
- Define the decision unit for “Control local exceptions and temporary safeguards”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
Worked delivery wave register
| Cohort | Shared dependency | Local readiness risk | Benefit test |
|---|---|---|---|
| Mobile teams | Device package | Offline return lag | Hidden stale release |
| Fixed clinics | Translated script | Training overlap | Contradiction probe |
| Laboratory sites | Specimen bridge | Identifier drift | Re-link sample |
| Analysis centres | Estimator guard | Late version mix | Sensitivity rerun |
Wave order follows risk and dependency evidence, not prestige or convenience.
CHAPTER 6 OF 13 · Close participant remedies and protect estimates
6. Close participant remedies as obligations, not tasks
Track contact, explanation, consent correction, benefit or referral restoration, confidentiality protection, repeat visit and non-contact outcomes without exposing identities in portfolio views.
Evidence record: Maintain restricted case evidence with eligibility, attempt chronology, channel, outcome, unresolved obligation, escalation and aggregate denominator; publish only the minimum necessary portfolio view. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: A remedy closes when the obligation is fulfilled or an authorised, documented path is exhausted; sending a message is not closure. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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 who cannot be reached remains a bounded unresolved obligation rather than a completed notification. 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
- Define the decision unit for “Close participant remedies as obligations, not tasks”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 7 OF 13 · Close participant remedies and protect estimates
7. Protect specimen, record and cohort integrity
Quarantine mixed-version records where needed, preserve lineage, bridge protocol variables, review specimen identifiers and prevent silent exclusion or duplication during delivery.
Evidence record: Keep record and specimen IDs under appropriate controls, version lineage, transformations, quarantine reason, bridge rules, discrepancies, reviewer, release and unresolved limits. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Corrective action must not improve apparent compliance by deleting difficult cases or breaking linkage evidence. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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 specimen collected under the old script remains traceable and is bridged with an explicit compatibility flag. 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
- Define the decision unit for “Protect specimen, record and cohort integrity”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 8 OF 13 · Close participant remedies and protect estimates
8. Apply estimator safeguards during mixed-version exposure
Define which estimators, weights, recruitment chains and sensitivity analyses can tolerate the transition. Freeze incompatible outputs, stratify versions and document uncertainty.
Evidence record: Store data cuts, protocol exposure, estimator and code versions, assumptions, diagnostics, sensitivity cases, exclusions, effect on conclusions, reviewer and release decision. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Release only when the estimator claim matches the supported mixed-version population and unresolved exposure is visible. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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 point estimate stays stable, but design effects widen; the report carries the changed uncertainty rather than only the central value. 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
- Define the decision unit for “Apply estimator safeguards during mixed-version exposure”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 9 OF 13 · Validate benefit with changed contexts and independent challenge
9. Validate adoption and mechanism interruption
Observe field behaviour, device state, script use, acknowledgements, contradiction checks, remedy flow and recurrence indicators. Test the mechanism rather than counting artefacts delivered.
Evidence record: Maintain site denominator, observations, device and protocol versions, fixtures, expected and observed behaviour, failed checks, latency, burden, recurrence signals and owner response. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: A delivered action passes only when the recurrence mechanism is interrupted in practice and evidence remains reconstructable. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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 hidden obsolete prompt is rejected by the device and recognised by staff during an unannounced exercise. 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
- Define the decision unit for “Validate adoption and mechanism interruption”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
Portfolio-benefit gate
| Gate | Pass evidence | Reopen when |
|---|---|---|
| Delivery | Observed use at site | Receipt without adoption |
| Remedy | Participant obligation closed | Unresolved contact |
| Estimator | Sensitivity bounded | Material shift |
| Portfolio | Independent changed-context pass | Mechanism recurs |
A portfolio can retain useful actions while reprioritising a weak shared dependency.
CHAPTER 10 OF 13 · Validate benefit with changed contexts and independent challenge
10. Run changed-context benefit tests
Test nights, staff turnover, translation updates, offline return, restored devices, late specimens, unusual recruitment chains and estimator edge cases that were not identical to pilot conditions.
Evidence record: Preserve context design, rationale, hidden fixtures, denominator, versions, expected and observed result, participant and estimator consequence, false results, remediation and retest. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Benefit is not generalised beyond the contexts actually exercised; a failed changed context narrows or reopens the action. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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 restored tablet misses the current package, revealing a deployment route that the normal update test did not cover. 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
- Define the decision unit for “Run changed-context benefit tests”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 11 OF 13 · Validate benefit with changed contexts and independent challenge
11. Commission independent portfolio review
Provide raw delivery, remedy, lineage, estimator, exception and changed-context evidence to reviewers independent of the action owners. Let them choose sites and hidden scenarios.
Evidence record: Document independence, sample design, access controls, reproductions, alternate mechanism classifications, discovered omissions, findings, disagreement and required action. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: No portfolio benefit is authorised solely by aggregated dashboards produced by delivery teams. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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: An independent sample finds that one site counted training attendance as adoption and corrects the denominator. 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
- Define the decision unit for “Commission independent portfolio review”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 12 OF 13 · Reprioritise, authorise and hand over
12. Validate benefit and reprioritise the portfolio
Compare observed participant protection, mechanism interruption, estimator reliability, burden and residual exposure with the approved benefit contract. Re-rank weak actions and shared dependencies.
Evidence record: Publish baseline and current measures, denominators, confidence, local variation, costs and burden ranges, failed claims, residuals, old and new ranking, deferred work and authority. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Retain actions that work, narrow claims that do not generalise and reprioritise when common dependencies or consequences outweigh rollout momentum. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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: Device recall works, but translation propagation remains weak across sites, so the shared library moves ahead of interface upgrades. 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
- Define the decision unit for “Validate benefit and reprioritise the portfolio”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 13 OF 13 · Reprioritise, authorise and hand over
13. Authorise bounded closure and hand over assurance
State which sites, mechanisms and outcomes are closed, which remedies or exceptions remain and what surveillance reopens the portfolio. Transfer fixtures, version controls and escalation authority.
Evidence record: Keep closure decision, cohort scope, tests, participant and estimator evidence, residuals, exceptions, owners and backups, runbooks, training, drill results, indicators and review calendar. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Closure requires successor owners to identify a stale version, protect participants, run an estimator sensitivity and reopen governance. Name the authorised owner, bounded scope, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the protected mechanism, not only a closed task.
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 site owner catches a restored-device failure during a drill and produces the complete remedy and analytical evidence 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 13 check · what should survive an audit
- Define the decision unit for “Authorise bounded closure and hand over assurance”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
Contents · Previous chapter · Return to the Intelligence guide
Verification lab: work the decision twice
Turn a fictional cross-site recurrence portfolio into dependency, readiness and wave plans for four different RDS cohorts.
Close participant remedies, bridge mixed-version records and run estimator sensitivity during one staged delivery.
Conduct independent changed-context tests, compare benefit with the contract and reprioritise one weak shared dependency.
Limits and misconceptions
Delivery receipts are not adoption
Observe field behaviour and mechanism interruption.
Local variation is not automatically noncompliance
Judge it against protected outcomes and authorised evidence.
Participant remedy and estimator repair are distinct
Track both without treating one as a proxy for the other.
A stable estimate does not erase exposure
Preserve lineage, sensitivity and unresolved obligations.
Questions readers ask
What is a corrective-action delivery contract?
- A versioned statement of mechanism, protected outcome, scope, prerequisites, action, evidence, owner and closure gate.
How are sites grouped into waves?
- By shared dependencies, local readiness, participant consequence, estimator risk and testability.
When is a participant remedy closed?
- When the obligation is fulfilled or an authorised exhausted path is documented—not when a task is sent.
How are estimators protected?
- Through version lineage, quarantine, bridging, diagnostics, sensitivity analysis and bounded release claims.
What makes a benefit test changed-context?
- It exercises a meaningful condition not identical to the pilot, such as restored devices, turnover or translation change.
When is the portfolio reprioritised?
- When delivery evidence changes mechanism reach, participant consequence, analytical risk, burden or shared-dependency leverage.
Practise, verify and continue
Take one cross-site RDS recurrence portfolio, create a dependency map and delivery waves, protect participants and estimates through mixed versions, run hidden changed-context tests and reprioritise from observed benefit.
Apply the method to any multisite field or public-health study. Preserve local ethics and governance, participant confidentiality, specimen and data lineage, estimator assumptions and the difference between rollout, adoption and benefit.
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 cross-site recurrence portfolio governance
RDS heightened-review reinstatement recovery
RDS post-backlog-retirement surveillance
RDS protocol-deviation trend review
Authoritative sources and scope
CDC NHBS-PWID 2024 operations manual
CDC HIV data programme resources
CDC data security and confidentiality principles
CDC National HIV Behavioral Surveillance overview
CDC sources support field operations, respondent-driven sampling context, data quality and confidentiality. They do not prescribe this cross-site corrective-action or portfolio-benefit method. Examples are fictional, and actual studies require protocol, ethics, participant, laboratory, statistical and jurisdictional review.