THE GOLD STANDARD OF INTELLIGENCE · SPECIALIST STUDY
Turn a reopened RDS corrective portfolio into observed protection and defensible reclosure
Reopening a corrective portfolio protects participants and estimates only if revised actions reach real sites, devices, field teams, remedy queues and analytical releases. Delivery must separate shared dependencies from local readiness, accelerate overdue participant remedies, preserve selection and weighting evidence, and keep temporary protections bounded. Changed-context tests across offline, delayed, mixed-version and low-capacity settings show whether the revised benefit travels. Independent review then supports reclosure only where mechanisms, outcomes and successor ownership remain observable.
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
Restate the reopened portfolio and revised benefit · chapters 1, 2, 3
Repair shared dependencies and site readiness · chapters 4, 5
Accelerate remedies and protect estimators · chapters 6, 7, 8
Validate changed contexts and independently challenge evidence · chapters 9, 10, 11
Reclose the portfolio with continuing assurance · chapters 12, 13
The whole problem at a glance
| Delivery question | Required evidence | Unsafe shortcut |
|---|---|---|
| What changed? | Versioned revised portfolio | Task completion |
| Where is readiness? | Site and device denominator | Training attendance |
| Who remains exposed? | Participant-remedy register | Aggregate closure rate |
| What proves benefit? | Mechanism and outcome tests | Rollout percentage |
Delivery is not benefit until the protected mechanism works in the affected context.
CHAPTER 1 OF 13 · Restate the reopened portfolio and revised benefit
1. Restate the reopened portfolio contract
Name the original shortfall, revised actions, expected mechanism, site and participant denominator, estimator safeguard, temporary controls, benefit range, exclusions and reclosure authority.
Evidence record: Keep incident and portfolio versions, causal findings, action mapping, baselines, affected cohorts, remedies, estimator risks, controls, owners and expiry. 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 item enters delivery without its protected outcome, evidence gate and relationship to the revised benefit. 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 shared offline-module repair is separated from local supervisor coaching because they prove different mechanisms. 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 “Restate the reopened portfolio contract”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 2 OF 13 · Restate the reopened portfolio and revised benefit
2. Freeze delivery denominator and chronology
Capture all sites, field teams, devices, protocol packages, participant cases, remedy queues and analytical outputs in scope at reopening.
Evidence record: Retain site and device IDs, versions, readiness state, first exposure, remedy status, estimate linkage, transfers, exclusions and reconciliation. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Sites cannot disappear from the denominator through relabelling, temporary inactivity or ownership transfer. 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 paused site remains in scope until its participant obligations and device inventory are resolved. 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 “Freeze delivery denominator and chronology”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 3 OF 13 · Restate the reopened portfolio and revised benefit
3. Translate benefit into leading and outcome measures
Define measures for dependency availability, version propagation, supervisor response, participant-remedy timing, protocol adherence, quarantine, estimator release and evidence health.
Evidence record: Store definition, owner, denominator, cadence, raw source, missingness, expected range, false results, manual validation 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: No single rollout percentage substitutes for mechanism, participant and estimator 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: Training reaches every site but offline-module use still fails, so benefit remains partial. 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 “Translate benefit into leading and outcome measures”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 4 OF 13 · Repair shared dependencies and site readiness
4. Repair shared protocol and device dependencies
Deliver versioned packages, compatibility rules, offline enforcement, beacons, expiry, migration, fallback and rollback across the actual device estate.
Evidence record: Keep package and dependency versions, device cohort, distribution receipt, install and activation proof, beacon state, expiry, failures, fallback 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: A download receipt is not adoption; verify active behaviour and safe failure under loss of connectivity. 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 field tablet receives the package but stays on an old module until an offline fixture exposes it. 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 “Repair shared protocol and device dependencies”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 5 OF 13 · Repair shared dependencies and site readiness
5. Establish site readiness and local ownership
Test staffing, supervision, connectivity, device coverage, escalation, training acknowledgement, participant communication and remedy capacity in each operating context.
Evidence record: Maintain site owner and backup, readiness checklist, evidence, exceptions, capacity, drill results, open risks, deadlines 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: Paper readiness does not support reclosure when the site cannot operate the safeguard during peak field work. 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 low-capacity site passes a live escalation drill only after a backup supervisor is assigned. 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 “Establish site readiness and local ownership”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
Worked delivery register
| Condition | Immediate action | Benefit test | Escalation |
|---|---|---|---|
| Shared module missing | Freeze release | Offline fixture | Dependency owner |
| Site queue overloaded | Add capacity | Remedy latency | Programme lead |
| Mixed device versions | Quarantine bridge | Version-stratified test | Technical authority |
| Weighting evidence late | Hold estimate | Reproducible rerun | Analytical lead |
Each row carries protection while revised benefit is still being established.
CHAPTER 6 OF 13 · Accelerate remedies and protect estimators
6. Accelerate participant remedies and prevent recurrence
Prioritise missed contacts, unsafe modules, delayed acknowledgements, unresolved consent or privacy issues and cases whose remedy window is closing.
Evidence record: Link participant-safe case ID, exposure, contact attempts, remedy, timing, outcome, unresolved need, escalation, privacy controls and completion evidence. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Administrative closure cannot replace observed remedy or documented inability after proportionate attempts. 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 affected participant receives corrected follow-up while device quarantine prevents the same path for others. 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 “Accelerate participant remedies and prevent recurrence”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 7 OF 13 · Accelerate remedies and protect estimators
7. Protect participants during uneven rollout
Use bounded quarantine, supervisor review, field-safe fallback, targeted pause and rapid support without creating indefinite exclusion or inaccessible alternatives.
Evidence record: Record control scope, owner, start, workload, bypass, participant impact, accessibility, renewals, retirement test and complaints. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Temporary protection must be equitable, observable and time-bounded; burden itself can reopen portfolio design. 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 manual confirmation step protects one site while an accessible offline replacement is tested. 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 participants during uneven rollout”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 8 OF 13 · Accelerate remedies and protect estimators
8. Preserve estimator safeguards and analytical lineage
Map device, protocol and participant cohorts into inclusion, recruitment chains, weights, nonresponse adjustment, exclusions, releases and downstream interpretation.
Evidence record: Keep dataset and code versions, cohort flags, selection paths, weights, diagnostics, sensitivity runs, holds, corrections, 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: Do not release an estimate whose affected cohort cannot be bounded or whose correction cannot be reproduced. 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 mixed-version cohort is flagged and a sensitivity rerun shows which headline remains supportable. 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 “Preserve estimator safeguards and analytical lineage”.
- 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 changed contexts and independently challenge evidence
9. Sequence delivery dependencies and local adaptations
Order shared repair, device migration, site readiness, participant remedies, analytical bridges and control retirement so later tasks do not assume unproven earlier benefit.
Evidence record: Publish dependency graph, critical path, local adaptations, owners, dates, protected outcomes, failure modes, fallback and evidence gates. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Schedule pressure cannot convert a blocked dependency into completion; adaptations need their own compatibility proof. 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-specific translation waits for canonical protocol approval but prepares field testing 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 9 check · what should survive an audit
- Define the decision unit for “Sequence delivery dependencies and local adaptations”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
Portfolio-reclosure gate
| Gate | Pass evidence | Remain open when |
|---|---|---|
| Dependency | Shared repair reaches cohort | Hidden version |
| Readiness | Site can operate and escalate | Unsupported context |
| Participant | Remedies timely and complete | Material queue |
| Estimator | Safeguards reproduce | Unresolved distortion |
A site or cohort can remain open while independently verified cohorts reclose.
CHAPTER 10 OF 13 · Validate changed contexts and independently challenge evidence
10. Validate offline, delayed and mixed-version contexts
Exercise connectivity loss, stale package, delayed synchronisation, supervisor absence, low-capacity remedy queue, participant recontact and analytical rerun.
Evidence record: Store context rationale, hidden fixture, versions, denominator, expected and observed behaviour, latency, false results, burden and remediation. 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 tested contexts; failed cohorts remain protected and open. 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 package passes online testing but fails expiry enforcement during a two-day outage. 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 “Validate offline, delayed and mixed-version contexts”.
- 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 changed contexts and independently challenge evidence
11. Run independent cross-site benefit review
Let reviewers select sites, devices, participant cases and analytical outputs, including quiet, low-capacity and previously failing cohorts.
Evidence record: Document independence, sample design, raw evidence access, reproductions, hidden fixtures, findings, disagreements, residuals and retests. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: The delivery team cannot select only high-readiness sites or mark missing evidence as success. 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 reviewer finds that one site’s remedy receipts are acknowledgements rather than completed outcomes. 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 “Run independent cross-site benefit 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 · Reclose the portfolio with continuing assurance
12. Authorise cohort-level portfolio reclosure
Compare revised benefit against approved ranges for dependency repair, readiness, participant protection and estimator safeguards; reclose only supported cohorts.
Evidence record: Keep reclosure version, authority, denominator, tests, exceptions, controls, residuals, participant obligations, analytical limits and reopening triggers. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Partial reclosure is preferable to an estate-wide claim that depends on unresolved sites or hidden device versions. 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: Three sites reclose while a low-connectivity cohort remains under bounded corrective work. 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 “Authorise cohort-level portfolio reclosure”.
- Bind each conclusion to a versioned denominator and observation window.
- Connect evidence to an owner, protective action and reopening trigger.
CHAPTER 13 OF 13 · Reclose the portfolio with continuing assurance
13. Hand over continuing benefit assurance
Transfer inventories, beacons, protocol library, site drills, remedy queues, estimator tests and reopening authority to named operational owners.
Evidence record: Publish owners and backups, runbooks, service objectives, fixtures, review calendar, vendor obligations, open residuals, escalation and proof of rehearsal. Preserve source, time, version, denominator, exclusions, failed checks, burden and uncertainty so another reviewer can reconstruct the decision rather than inherit confidence.
Decision rule: Reclosure completes when successor teams can detect drift, protect participants, hold an estimate and reopen the portfolio. 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: Operations discovers a stale package, quarantines its cohort and runs the analytical bridge without the recovery team. 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 “Hand over continuing benefit 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
Translate a fictional reopened RDS portfolio into delivery units tied to participants, sites, dependencies and estimator safeguards.
Repair a shared module, ready two contrasting sites, accelerate remedies and run an analytical bridge.
Exercise offline and mixed-version contexts, perform independent review and reclose only supported cohorts.
Limits and misconceptions
Rollout is not benefit
Measure active mechanism, participant outcome and estimator protection.
Shared repair does not create local readiness
Test each operating context and escalation path.
Temporary controls can exclude people
Measure burden, accessibility and duration.
Reclosure can be partial
Keep unsupported sites and cohorts visibly open.
Questions readers ask
What changes after portfolio reopening?
- Actions, benefit expectations, denominators and evidence gates are revised from the incident findings.
What is shared-dependency repair?
- Repair of protocol, device, version or service components whose failure crosses sites.
How is site readiness proven?
- Through observed operation, escalation, capacity and changed-context drills.
Why protect estimators during delivery?
- Because uneven protocol and remedy states can change inclusion, weights and interpretation.
Who performs independent review?
- A reviewer with sufficient separation, raw evidence access and authority to select their own samples.
When can the portfolio reclose?
- When supported cohorts show durable mechanism, remedies, safeguards and continuing ownership.
Practise, verify and continue
Take one reopened RDS corrective portfolio, map revised actions to protected outcomes, deliver shared and local repairs, validate difficult contexts and reclose only independently supported cohorts.
Apply the method to multi-site public-health, education or social research. Preserve participant rights, privacy, 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 portfolio benefit-shortfall response and reopening
RDS cross-site corrective delivery and benefit validation
RDS heightened-review incident recovery
RDS post-backlog-retirement surveillance
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.