The condition where a single organizational change — a hire, termination, promotion, plan switch, territory move, or reorg — has been recorded correctly in one system but not in every other system that depends on it. Org drift is silent until it surfaces as a payroll error, commission dispute, or audit finding.
The same idea as org drift, framed from the perspective of the systems involved: a verified mismatch between two systems that were supposed to agree after a business change should have propagated. The phrase emphasizes that no single-system reconciliation can detect it.
The operating layer where control execution happens, gets proven, and produces audit-ready evidence from the work teams already do. Sits underneath GRC and above the systems of record. Analogous to DevOps for software releases or RevOps for revenue.
A read-only system that observes other systems and proves they agree, without itself being a system of record. OrgDrift functions as an independent verification layer for HRIS, CRM, ICM, payroll, and benefits data.
OrgDrift’s persona-aware operational view of every open and recently resolved drift finding. Shows severity, system pair, affected records, exposure, owner, and status. The day-to-day workspace for control owners and analysts.
A composite measure of cross-system alignment health, scored on a 300–850 scale (FICO-style). Five weighted factors: control pass rate, material exposure ratio, critical finding density, drift velocity, and coverage confidence. Anchored to PCAOB AS 2201’s hierarchy of control weaknesses. ODIS is currently `v0.9 DRAFT` — empirical breakpoint calibration is in progress, and a public methodology page will follow.
A signed, timestamped, immutable record produced each time an OrgDrift control runs. Captures the populations compared, field mappings, hashes, source-of-truth conflicts, the result, and the human attestation. Designed to attach to management’s assertion as independent ICFR evidence.
Evidence formatted, signed, and attested to such that an external auditor can rely on it without rework — typically meaning it carries a tamper-evident signature, references the population and source of data, and includes a human attestation. Control Execution Records are the OrgDrift artifact that meets this bar.
The authoritative system for a given piece of organizational data. HRIS is typically the system of record for employee status; CRM for opportunity ownership; ICM for compensation plan assignments. Drift occurs when downstream systems disagree with the system of record.
The chain of systems an organizational change must reach for the company to operate correctly — for example, HRIS → CRM → ICM → payroll → benefits. OrgDrift verifies the path end-to-end, not just one hop.
A SOX/PCAOB term for any data, report, or population produced internally that is used in the operation of a control or relied on for an assertion. Auditors test IPE for completeness and accuracy. OrgDrift’s populations and exports are designed to satisfy IPE testing.
The document that maps risks to the controls that mitigate them, including ownership, frequency, and assertions covered. CERs map back to the RACM rows so each execution is traceable to the risk it addresses.
A control governed by Sarbanes-Oxley Section 404, requiring management to assert the effectiveness of internal control over financial reporting (ICFR) and external auditors to attest to that assertion. Many comp, payroll, and revenue controls fall under SOX.
A specific class of cross-system drift where HRIS changes — terminations, rate changes, reorgs, leave status — have not propagated to the payroll system before the next pay run. Payroll is the last gate before money leaves the company; drift here becomes an overpayment.
Cross-system drift between CRM, HRIS, and ICM/SPM — typically plan assignments, opportunity ownership, territory, or quota — that causes commissions to be calculated against stale state. Surfaces as overpayments, clawbacks, and rep disputes.
Cross-system drift between HRIS and benefits administration after a life event, status change, or termination. Causes ineligible enrollments, missed COBRA notices, or carrier file rejections.
Cross-system drift between HRIS, CRM, and ICM for territory or account ownership. Causes opportunities to credit the wrong rep, rep coverage to lag a reorg, and quota allocation to drift away from the operating model.
See these terms in action.
Run an ungated browser preview against simulated data and watch the artifacts get produced live.