THE GOLD STANDARD OF INTELLIGENCE · SPECIALIST STUDY
Respond when RDS post-reclosure drift triggers corrective reopening
Corrective reopening is a planned safety response when post-reclosure evidence no longer supports a site, protocol, device, participant-remedy or estimator claim. It is not proof that every site failed. The response must preserve the trigger, partition affected cohorts, keep participant protections accessible, hold or qualify analytical outputs where needed, repair shared and local mechanisms, and independently exercise the difficult contexts that ordinary monitoring can miss. Reclosure follows participant and estimator evidence, not administrative completion.
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
Open the corrective incident and preserve its evidence · chapters 1, 2, 3
Partition site, device, participant and estimator scope · chapters 4, 5
Protect participants and repair shared dependencies · chapters 6, 7, 8
Independently exercise field and analytical contexts · chapters 9, 10, 11
Authorise bounded reclosure and renew ownership · chapters 12, 13
The whole problem at a glance
| Incident question | Required evidence | Unsafe shortcut |
|---|---|---|
| Why did work reopen? | Raw surveillance trigger and cohort version | Escalation label |
| Who is affected? | Site, device, participant and estimator partition | All sites |
| What must be protected? | Participant and output safeguards | Task list |
| What permits reclosure? | Independent field and analytical retest | Action closure |
A failed shared dependency can affect several sites, while a local capacity failure may remain site-specific.
CHAPTER 1 OF 13 · Open the corrective incident and preserve its evidence
1. Preserve the corrective-reopening trigger and field chronology
Freeze the surveillance observation, protocol and device versions, affected site, participant protection and analytical state before remediation changes the evidence.
Keep beacons, expiry events, synchronisation logs, supervisor actions, remedy records, case and output identifiers, estimator versions and the first protective decisions.
Validate whether the trigger reflects true drift, a stale package, site-capacity loss, participant-remedy failure, estimator instability or missing evidence.
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: Replay the trigger during a two-day connectivity loss and state which field and analytical conclusions remain valid. 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
- Identify the evidence unit and denominator for “Preserve the corrective-reopening trigger and field chronology”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
CHAPTER 2 OF 13 · Open the corrective incident and preserve its evidence
2. Restate the reclosure claim that no longer holds
Define the sites, devices, protocol modules, participant obligations, estimator safeguards, temporary controls, accepted residuals, observation window and reopening authority.
Attach the baseline and evidence that supported reclosure, including low-capacity and offline conditions, so current drift can be compared with the actual claim.
Narrow the claim when a cohort was not tested; do not treat acknowledgement or training completion as proof of field adoption.
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: Move one site to a replacement device estate and test whether the reclosure claim transfers without a version bridge. 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
- Identify the evidence unit and denominator for “Restate the reclosure claim that no longer holds”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
CHAPTER 3 OF 13 · Open the corrective incident and preserve its evidence
3. Start participant-safe and output-safe containment
Use bounded case quarantine, accessible fallback, supervisor review, remedy acceleration, data hold or qualified release while scope and cause are investigated.
Record population, purpose, authority, start time, accessibility, burden, privacy, output impact, exceptions, stop rule and owner.
Choose protection that does not pressure participants, erase withdrawal choices or conceal data-quality uncertainty.
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: Operate the fallback when the usual supervisor is absent and verify that consent, privacy and escalation remain intact. 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
- Identify the evidence unit and denominator for “Start participant-safe and output-safe containment”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
CHAPTER 4 OF 13 · Partition site, device, participant and estimator scope
4. Partition sites, devices and shared dependencies
Group sites by protocol version, translation, device package, connectivity pattern, staffing, supervisor coverage, vendor service and analytical pipeline.
Use fleet inventory, beacons, acknowledgements, observed sessions, incident logs, staffing records and code or configuration lineage rather than site labels alone.
A shared dependency widens scope across sites; a local failure remains bounded only after common mechanisms are tested.
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: Introduce the same stale package at a quiet site and a peak-volume site to compare mechanism with capacity effects. 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
- Identify the evidence unit and denominator for “Partition sites, devices and shared dependencies”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
CHAPTER 5 OF 13 · Partition site, device, participant and estimator scope
5. Reconcile participant cohorts and remedy obligations
Identify participants exposed to the failed condition, pending remedies, accessibility needs, repeat contact, unresolved results, withdrawal requests and downstream service obligations.
Keep case identifier, event, consent and contact constraints, remedy promised, accessibility, timing, outcome, recurrence, owner and unresolved need.
Separate a completed contact from a durable remedy outcome; revisit material cases without creating unnecessary burden.
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: Delay follow-up beyond the normal window and test whether the remedy remains accessible and meaningful. 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
- Identify the evidence unit and denominator for “Reconcile participant cohorts and remedy obligations”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
Worked corrective-reopening register
| Observation | Possible class | Immediate protection | Changed-context test |
|---|---|---|---|
| Offline package is stale | Device recurrence | Quarantine module | Two-day outage |
| Remedy queue exceeds limit | Capacity drift | Add accessible support | Peak-load drill |
| Participant cannot complete follow-up | Remedy failure | Case escalation | Delayed recontact |
| Weights shift after exclusion | Estimator instability | Hold release | Version-stratified rerun |
Protect participants and outputs before the full causal picture is complete.
CHAPTER 6 OF 13 · Protect participants and repair shared dependencies
6. Protect recruitment chains and field integrity
Freeze affected coupons, recruitment trees, seed or wave context, duplicate and fraud controls, site activity and protocol deviations without exposing participant identities unnecessarily.
Retain pseudonymous chain links, coupon state, issue and redemption times, site and device versions, deviations, quarantine reasons and authorised access.
Do not delete a chain to simplify analysis; preserve the evidence needed to bound recruitment and estimator effects.
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: Restore an offline device with delayed coupon synchronisation and reconcile every issued and redeemed coupon. 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
- Identify the evidence unit and denominator for “Protect recruitment chains and field integrity”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
CHAPTER 7 OF 13 · Protect participants and repair shared dependencies
7. Protect estimator inputs and release decisions
Map affected records into inclusion rules, network-size reports, recruitment chains, weights, exclusions, nonresponse adjustments, sensitivity analyses and published outputs.
Keep code and configuration version, cohort, denominator, transformations, diagnostics, output, release decision, limitations and protective hold.
Hold or qualify an output when affected scope cannot be bounded; do not imply every deviation changes the estimate before rerun evidence exists.
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: Rerun the estimator after excluding one quarantined site and compare results with a bridged inclusion rule. 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
- Identify the evidence unit and denominator for “Protect estimator inputs and release decisions”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
CHAPTER 8 OF 13 · Protect participants and repair shared dependencies
8. Repair shared and site-specific mechanisms
Test canonical guidance, translations, training aids, device packages, expiry logic, synchronisation, site capacity, supervision, remedy queues and estimator safeguards against competing causes.
Preserve hypotheses, targeted tests, versions, timestamps, participants protected, contradictions, residuals and the reason each corrective action matches the mechanism.
Sequence shared dependency repair before local reclosure where the same package or protocol can recreate failure across sites.
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: Apply the repair at a site with different language and connectivity conditions to test propagation and adoption. 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
- Identify the evidence unit and denominator for “Repair shared and site-specific mechanisms”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
CHAPTER 9 OF 13 · Independently exercise field and analytical contexts
9. Work a participant-and-estimator incident case
Use a fictional site where an offline module remains active, one participant receives outdated guidance, a remedy is delayed and the affected record changes a weight diagnostic.
Build a chronology joining device beacon, protocol text, session, participant-safe remedy, quarantine, estimator rerun, supervisor decision and final evidence.
The case passes only when the participant outcome is addressed, stale use is blocked, the record disposition is justified and the estimate decision reproduces.
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: Change the record to a participant withdrawal and recalculate what evidence may be retained and how the analytical cohort changes. 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
- Identify the evidence unit and denominator for “Work a participant-and-estimator incident case”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
Bounded-reclosure gate
| Gate | Pass evidence | Remain reopened when |
|---|---|---|
| Protocol | Canonical and field versions agree | Stale module |
| Participant | Remedy outcome is durable | Unresolved need |
| Site | Capacity and escalation survive exercise | Unsupported context |
| Estimator | Protected reruns reproduce | Unbounded distortion |
Supported sites may reclose while a shared or local dependency remains open elsewhere.
CHAPTER 10 OF 13 · Independently exercise field and analytical contexts
10. Exercise offline, low-capacity and mixed-version contexts
Test long outages, delayed synchronisation, supervisor absence, peak remedy queues, mixed translations, replacement devices, participant recontact and analytical reruns.
Keep hidden fixture design, field safety review, versions, expected and observed action, latency, accessibility, false results, discovered cohorts and operator knowledge.
At least one exercise must reproduce the context that escaped post-reclosure surveillance rather than a comfortable training scenario.
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: Run the same mixed-version drill at a small site and a high-volume site to separate mechanism from operational capacity. 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
- Identify the evidence unit and denominator for “Exercise offline, low-capacity and mixed-version contexts”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
CHAPTER 11 OF 13 · Independently exercise field and analytical contexts
11. Run independent cross-site and analytical challenge
Let reviewers select quiet, previously failing and apparently healthy sites, inspect participant-remedy evidence and reproduce protected estimators from versioned inputs.
Document independence, sampling, access limits, privacy controls, exclusions, contradictions, unresolved cases and every change to scope or causal conclusion.
Independent challenge may narrow as well as widen the incident, but it cannot replace participant protection with statistical convenience.
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: Ask the challenger to select a site not named by the response team and trace one case from field version to estimator decision. 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
- Identify the evidence unit and denominator for “Run independent cross-site and analytical challenge”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
CHAPTER 12 OF 13 · Authorise bounded reclosure and renew ownership
12. Authorise bounded site and cohort reclosure
Compare protocol adoption, device safety, site capacity, participant-remedy durability, estimator stability and evidence health with approved ranges.
Publish the reclosed cohort, tests, limitations, unresolved cases, residuals, temporary safeguards, authority, observation window and automatic reopening triggers.
Reclose only supported cohorts; keep a failed shared dependency open even when local task lists are complete.
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: Reclose sites with verified packages while one low-capacity site retains enhanced supervision and a qualified output gate. 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
- Identify the evidence unit and denominator for “Authorise bounded site and cohort reclosure”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
CHAPTER 13 OF 13 · Authorise bounded reclosure and renew ownership
13. Renew ownership, exercises and corrective reopening
Refresh protocol controls, translations, beacons, site drills, remedy queues, estimator tests, privacy safeguards and reopening authority under named owners and backups.
Keep baseline versions, service objectives, exercise calendar, case-review cadence, analytical reproducibility checks, residual expiry and escalation paths.
Handover completes when ordinary operations can detect stale field use, protect a participant, hold an output and reopen bounded corrective work.
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: Admit a new site after handover and test package deployment, participant remedy, estimator bridge and reopening from end to end. 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
- Identify the evidence unit and denominator for “Renew ownership, exercises and corrective reopening”.
- Preserve the rejected explanation and the protection used while uncertainty remains.
- Name the owner, decision deadline, verification gate and condition for reopening or return.
Contents · Previous chapter · Return to the Intelligence guide
Verification lab: work the decision twice
Open a fictional RDS corrective-reopening incident, preserve its field and analytical trigger, and restate the failed reclosure claim.
Partition sites and participant cohorts, protect one participant and one estimate, and repair a shared device mechanism.
Run an independent mixed-version field exercise and estimator rerun, then reclose supported cohorts only.
Build the corrective-reopening evidence packet so a field, participant-protection and analytical reviewer can reach the decision independently. Include protocol and translation versions, device inventory and beacons, site capacity, participant-safe case chronology, remedy outcomes, recruitment-chain disposition, estimator code and configuration, sensitivity runs, output holds, causal tests, exercises, independent findings, residuals and reclosure authority. Remove direct identifiers from the review copy while preserving the linkage needed to reconstruct decisions under the applicable privacy and ethics rules.
Run a second exercise in which the stale module is blocked but the accessible remedy queue becomes overloaded. Protect affected participants first, measure unresolved need and delay, add bounded capacity, and rerun the analytical safeguard for records whose treatment changed. The site does not reclose merely because the device fix passed. Reclosure requires the participant outcome, field adoption and estimator decision to remain defensible together under the changed capacity context.
Close the exercise with a cohort decision table that separates shared dependency, local site, participant-remedy and estimator states. For each row, record evidence, temporary protection, owner, deadline, reclosure condition and automatic reopening trigger. Ask the successor supervisor to detect one hidden stale package, protect the participant and initiate the analytical hold without assistance; that observed response is part of the handover evidence.
Final review: sample one true protocol drift, one benign version difference and one missing-evidence case. Confirm participant-safe action, site escalation, record disposition, estimator decision and retained evidence for each. Reclosure is ready only when the system distinguishes these cases without weakening consent, privacy or remedy obligations.
Limits and misconceptions
Corrective reopening is not universal site failure
Partition scope by shared and local mechanisms.
Contact is not a durable remedy
Revisit participant outcome, accessibility and unresolved need.
A protocol can be valid while site capacity fails
Exercise staffing, supervision and queues.
Estimator protection must reproduce
Retain versions, cohorts, code and decision gates.
Questions readers ask
What is corrective reopening?
- A bounded return to corrective work when post-reclosure evidence fails for a protocol, site, participant or estimator condition.
Must every site reopen?
- No. Scope follows shared dependencies, affected cohorts and current evidence.
How are participants protected?
- Through accessible fallback, bounded case review, remedy acceleration and privacy-respecting evidence handling.
When is an output held?
- When affected scope or analytical safeguards cannot be bounded and reproduced.
Why run independent field exercises?
- Because quiet, offline and low-capacity contexts may not appear in ordinary dashboards.
What permits reclosure?
- Field adoption, durable participant remedies, reproducible estimator decisions, independent retest and renewed ownership.
Practise, verify and continue
Take one fictional RDS portfolio that reopens after reclosure, preserve its trigger, partition shared and local scope, protect a participant and an estimate, repair the mechanism, and reclose only independently supported cohorts.
Apply the method to multi-site health, education or social research. Preserve participant rights, protocol lineage, field realities, analytical reproducibility and bounded state changes.
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 post-reclosure surveillance and drift response
RDS post-reopening delivery and revised-benefit assurance
RDS portfolio benefit-shortfall response and reopening
RDS cross-site corrective delivery and benefit validation
Authoritative sources and scope
CDC NHBS PWID 2024 operations manual
CDC National HIV Behavioral Surveillance programme
CDC data-security and confidentiality principles
CDC NHBS methods and populations
CDC materials support multi-site surveillance operations, respondent-driven sampling procedures, participant protections, data security and quality control. They do not prescribe this portfolio-delivery framework. Examples are fictional; ethics, consent, privacy, sampling, weighting, disclosure and participant remedies require study-specific governance.