THE GOLD STANDARD OF INTELLIGENCE · SPECIALIST STUDY
Keep an RDS corrective portfolio trustworthy after reclosure
Reclosure transfers responsibility from the recovery team to ordinary operations, but protocols, devices, sites, participant needs and estimators continue to change. Post-reclosure surveillance must detect whether renewed benefit still reaches difficult field contexts, whether remedies remain durable and whether analytical safeguards still reproduce. Independent exercises and corrective reopening protect participants and estimates before drift becomes an accepted operating condition.
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
Freeze reclosure benefit and surveillance scope · chapters 1, 2, 3
Watch protocol, device and site drift · chapters 4, 5
Test remedy durability and estimator stability · chapters 6, 7, 8
Exercise changed contexts and independently challenge evidence · chapters 9, 10, 11
Correct drift and reopen bounded portfolio work · chapters 12, 13
The whole problem at a glance
| Surveillance question | Evidence | Unsafe shortcut |
|---|---|---|
| What reclosed? | Cohort-level contract | Task closure |
| What may drift? | Protocol, device and site deltas | Complaint count |
| Who stays protected? | Participant-remedy outcomes | Contact attempts |
| What proves stability? | Reproducible estimator checks | Release date |
A closed portfolio remains defensible only while successor owners can observe and act.
CHAPTER 1 OF 13 · Freeze reclosure benefit and surveillance scope
1. Restate reclosure and renewed-benefit conditions
Name reclosed sites, device and protocol cohorts, participant obligations, estimator safeguards, residuals, temporary protections, observation window and reopening authority.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Restate reclosure and renewed-benefit conditions”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Restate reclosure and renewed-benefit conditions” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Restate reclosure and renewed-benefit conditions”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
CHAPTER 2 OF 13 · Freeze reclosure benefit and surveillance scope
2. Freeze site, device and participant baselines
Capture the site, field-team, device, package, participant-case and analytical-output denominator at reclosure, preserving later additions and transfers.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Freeze site, device and participant baselines”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Freeze site, device and participant baselines” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Freeze site, device and participant baselines”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
CHAPTER 3 OF 13 · Freeze reclosure benefit and surveillance scope
3. Define leading, outcome and evidence-health indicators
Combine package beacons, expiry enforcement, supervisor response, remedy timing, participant outcomes, protocol adherence, estimator diagnostics and pipeline health.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Define leading, outcome and evidence-health indicators”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Define leading, outcome and evidence-health indicators” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Define leading, outcome and evidence-health indicators”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
CHAPTER 4 OF 13 · Watch protocol, device and site drift
4. Detect protocol and translation drift
Compare canonical guidance with translations, field aids, training artefacts, acknowledgements and observed practice; treat contradiction or stale language as material drift.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Detect protocol and translation drift”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Detect protocol and translation drift” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Detect protocol and translation drift”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
CHAPTER 5 OF 13 · Watch protocol, device and site drift
5. Detect device, package and connectivity drift
Observe package version, activation, offline behaviour, synchronisation, grace use, compatibility and safe failure across the real device estate.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Detect device, package and connectivity drift”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Detect device, package and connectivity drift” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Detect device, package and connectivity drift”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
Worked drift register
| Observation | Class | Protection | Exercise |
|---|---|---|---|
| Offline beacon falls | Device drift | Quarantine cohort | Two-day outage |
| Queue age rises | Capacity drift | Add remedy support | Peak-load drill |
| Repeat contact fails | Remedy durability | Escalate case | Delayed follow-up |
| Weights move sharply | Estimator drift | Hold release | Version-stratified rerun |
Each observation protects participants or estimates before cause is certain.
CHAPTER 6 OF 13 · Test remedy durability and estimator stability
6. Detect site-capacity and supervision drift
Measure staffing, backup supervision, workload, connectivity, escalation and remedy capacity rather than relying on a static readiness checklist.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Detect site-capacity and supervision drift”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Detect site-capacity and supervision drift” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Detect site-capacity and supervision drift”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
CHAPTER 7 OF 13 · Test remedy durability and estimator stability
7. Test participant-remedy durability
Revisit affected cases for outcome, accessibility, unresolved need, recurrence and whether the remedy created new burden or exclusion.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Test participant-remedy durability”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Test participant-remedy durability” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Test participant-remedy durability”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
CHAPTER 8 OF 13 · Test remedy durability and estimator stability
8. Monitor estimator stability and release gates
Track inclusion, recruitment chains, weights, nonresponse adjustment, exclusions, sensitivity runs and reproducible release decisions across changing cohorts.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Monitor estimator stability and release gates”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Monitor estimator stability and release gates” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Monitor estimator stability and release gates”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
CHAPTER 9 OF 13 · Exercise changed contexts and independently challenge evidence
9. Protect participants and outputs during review
Use bounded quarantine, supervisor review, accessible fallback, remedy acceleration and estimate holds without normalising indefinite temporary controls.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Protect participants and outputs during review”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Protect participants and outputs during review” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Protect participants and outputs during review”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
Corrective-reopening gate
| Gate | Pass evidence | Reopen when |
|---|---|---|
| Protocol | Active version behaves | Stale module |
| Site | Capacity and escalation hold | Unsupported context |
| Remedy | Outcome remains durable | Material recurrence |
| Estimator | Safeguards reproduce | Unresolved distortion |
Supported sites can continue while failed cohorts reopen.
CHAPTER 10 OF 13 · Exercise changed contexts and independently challenge evidence
10. Exercise offline, delayed and low-capacity contexts
Test connectivity loss, delayed synchronisation, mixed versions, supervisor absence, peak queues, participant recontact and analytical rerun.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Exercise offline, delayed and low-capacity contexts”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Exercise offline, delayed and low-capacity contexts” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Exercise offline, delayed and low-capacity contexts”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
CHAPTER 11 OF 13 · Exercise changed contexts and independently challenge evidence
11. Run independent cross-site surveillance challenge
Let reviewers choose quiet, low-capacity and previously failing sites, reproduce estimates and inspect participant-safe remedy evidence.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Run independent cross-site surveillance challenge”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Run independent cross-site surveillance challenge” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Run independent cross-site surveillance challenge”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
CHAPTER 12 OF 13 · Correct drift and reopen bounded portfolio work
12. Correct drift and reopen bounded portfolio work
Reopen only the failed shared dependency, site, participant-remedy class or analytical safeguard; sequence repair and temporary protection together.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Correct drift and reopen bounded portfolio work”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Correct drift and reopen bounded portfolio work” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Correct drift and reopen bounded portfolio work”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
CHAPTER 13 OF 13 · Correct drift and reopen bounded portfolio work
13. Renew ownership and hand over continuing assurance
Refresh runbooks, protocol library, beacons, site drills, remedy queues, estimator tests and reopening authority under named operational owners.
Evidence record: keep the versioned denominator, source, time, context, expected condition, observed result, exclusions, failed checks, burden and uncertainty for “Renew ownership and hand over continuing assurance”. This lets another reviewer reconstruct the claim instead of inheriting a dashboard label.
Decision rule: connect the observation to an authorised owner, bounded protective action, deadline, stop condition, remedy and verification window. Completion requires a changed-context test of the mechanism, not merely 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: Changed-context transfer: apply “Renew ownership and hand over continuing assurance” to a delayed, restored, offline, low-capacity or provider-changed cohort. Preserve what changes, what remains comparable and which conclusion must narrow. 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 evidence unit for “Renew ownership and hand over continuing assurance”.
- Reconcile the denominator and observation window.
- Name protection, owner, evidence gate and reopening trigger.
Contents · Previous chapter · Return to the Intelligence guide
Verification lab: work the decision twice
Turn a fictional RDS reclosure decision into a surveillance contract with participant and estimator outcomes.
Introduce protocol, device, capacity and remedy drift; protect participants and hold one estimate.
Run independent field exercises, reopen one cohort and renew successor ownership.
Limits and misconceptions
Reclosure is not disappearance
Keep cohorts, obligations and residuals visible.
Acknowledgement is not adoption
Observe active behaviour in field context.
A remedy needs a durable outcome
Revisit unresolved need and recurrence.
Estimator stability must reproduce
Keep versions, code and cohort bridges.
Questions readers ask
What is post-reclosure surveillance?
- Continuing observation of protocol, site, participant and estimator conditions after portfolio reclosure.
What is renewed-benefit drift?
- Loss or change in the protective mechanism or outcome that supported reclosure.
Why monitor site capacity?
- Because a valid protocol can fail when supervision, workload or remedy capacity changes.
How is remedy durability checked?
- By outcome, recurrence, accessibility and unresolved participant need, not contact attempts alone.
When is an estimate held?
- When affected cohorts or safeguards cannot be bounded and reproduced.
Must every site reopen?
- No. Corrective reopening should follow the failed mechanism and cohort.
Practise, verify and continue
Take one reclosed RDS portfolio, freeze its renewed-benefit claim, seed field and estimator drift, protect participants and reopen only the failed cohort.
Apply the method to multi-site health, education or social research. Preserve participant rights, protocol versioning, field realities and reproducible analytical decisions.
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-reopening delivery and revised-benefit assurance
RDS portfolio benefit-shortfall response and reopening
RDS cross-site corrective delivery and benefit validation
RDS heightened-review incident recovery
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.