Start with the event itself: a payer enrollment relationship changing around an effective date. Give the work one stable, privacy-safe locator and record the intake time, source location, current state, and provider enrollment owner. The row should make sense to an authorized colleague who did not see the event happen.
Gather the evidence before proposing an action: the dated payer source, provider and location relationship, prior and current configuration, claim dates, acknowledgments, and change approval. Preserve original identifiers, wording, versions, and timestamps in approved systems. Event time, system time, retrieval time, and review time answer different questions.
The practical risk is that an approval date can be mistaken for an effective date and a current portal screen can erase useful history. Mark values as observed, externally reported, calculated, owner-interpreted, or unknown. When two sources disagree, keep both and route the conflict instead of choosing the more convenient value.
Define the counting unit for routine 2 before work begins. Freeze the opening population, filters, cutoff, timezone, and duplicate rule. Record late arrivals and reopened items as movements so the denominator does not change silently.
Support staff may retrieve permitted records, compare fields, reproduce documented arithmetic, index files, and draft a bounded question. The provider enrollment owner retains decisions that change claim content, coding, clinical meaning, credentials, money, access, submission, legal interpretation, or external communication.
Use statuses that explain the work: evidence gathered, conflict found, access blocked, awaiting owner, authorized action, or carried forward. A generic complete label is not enough unless the record shows what changed, who approved it, and where the result can be checked.
Review one ordinary row and one exception with a second authorized person when both are available. Compare identifiers, sources, timing, scope, and arithmetic. Preserve disagreement because it may reveal an unstated rule or a source transformation.
The close test is exact: each boundary-date claim has a source-supported state and the prior configuration remains traceable. Unresolved rows need one accountable next actor and review date. Missing or inaccessible evidence stays in the count.
Keep protected information in approved tools and use the minimum necessary locator in shared trackers. An access failure belongs with the access owner; it is not permission to borrow credentials or copy sensitive records elsewhere.
This September 10, 2026 guide is an administrative control. It does not make a clinical, coding, coverage, credentialing, contract, legal, privacy, or accounting determination.