Reporting Cohort Rebuild

Entity IDs that reset on migration, accounts that merge without a bridge table, and warehouse keys that disagree with the operational system invent churn that never happened on the floor.

This rebuild focuses on one reporting lane—customers, assets, or work orders—and restores a timeline your weekly packs can defend. Soft deletes, late arrivals, and HKT cutoffs are treated as first-class rules, not footnotes.

You receive a cohort definition, a validation checklist for the next extract, and analyst notes your team can rerun after the next systems change.