Reconcile Conflicting Monitoring Records

Evidence and applicability: use only supplied evidence for source values, historical facts, quotations, completed checks and approvals. Cite source labels and row, page or section references. Distinguish observed facts, source claims, analyst calculations, assumptions and proposals. Keep missing evidence unknown or not evidenced; it does not prove that an activity did not happen. Do not invent values, verification, agreement requirements, authority or sign-off. Apply only rules actually supplied and applicable to the task. Descriptive reach and monitoring totals do not demonstrate outcomes or causal impact.

Use only material supplied in this conversation. Ask me to provide the competing source extracts and definitions before making record-specific findings; do not treat this request as evidence that they exist.

Before adjudicating a discrepancy, require safe substantive extracts of the competing records with stable source labels and row references, indicator definitions and inclusion rules, units and reporting periods, coverage and source versions, plus whatever verification evidence and decision rules actually exist. A file name, summary assertion or unsigned proposed rule alone cannot verify a value. Ask only for missing essential material, and continue the supported parts of the ledger. Do not ask for personal names, contact details or sensitive case histories; use nonidentifying record references and aggregate extracts.

Help reconcile the supplied conflicting monitoring records as an adjudication work item.

1. Inventory each source and preserve its original claim verbatim or as a faithfully labeled extract. Record the source label, location, version/date, reporting status and supplied provenance. Retain raw evidence unchanged. Flag missing metadata and whether sources share an upstream record rather than treating repeated copies as independent corroboration.
2. Check whether claims are comparable: indicator definition, people versus contacts or other units, inclusion rules, population, site/partner coverage, reporting window, cutoff, revisions and aggregation level. Show any supported arithmetic bridge or transcription check with its inputs and formula. Do not silently normalize noncomparable figures or treat plausible arithmetic as verification of the underlying records.
3. Produce an adjudication ledger with discrepancy ID, each competing claim and source reference, comparability issue, evidence checked, supplied decision rule and its applicability, supported finding, unresolved unknowns, and next verification action. Separate evidence-supported conclusions from proposed decisions. State unresolved when evidence or authority cannot settle a claim. A newer, signed or higher-level report is not automatically correct. Do not select a minimum, average, majority value or convenient figure as verified. Where equal-authority claims conflict, retain both until a supported resolution exists.
4. For every proposed correction, retain the old and proposed values, source/version references, reason, supporting evidence, affected downstream totals and remaining checks. Identify an actual decision owner or approval only if supplied; otherwise mark it unknown and request clarification. Distinguish a documented authorization decision from independent verification. Never imply that this chat changed a register or report, and never overwrite raw evidence.
5. Finish with a short decision note: what can be supported now, what remains disputed, what cannot responsibly be finalized, and targeted evidence requests. If a deadline is supplied, propose transparent provisional wording and explain the reporting limitation without fabricating permission to submit a disputed value. Suggest owners and dates only as proposals when not already agreed.