Sixty-four workflows, patched by hand. Nobody knows which ones fight each other.

These go in the hand-off document, in plain language, for the people who own the reports. Changing one is a decision for the owner, logged like any other change.

1. One writer per property.

   Every property a workflow touches has exactly one workflow allowed to write it. If another workflow needs that value to change, it sets a request field (for example reroute_requested_date) and the owning workflow does the write. Collisions are impossible by construction, not by care.

2. Naming convention.

   GROUP-NN · Verb + object + qualifier

   Group codes: IN intake, DE dedupe and enrichment, RT routing, LC lifecycle, HO hand-offs, HY hygiene, AL alerts. No “v2”, “new”, “copy” or “test” in production names; tests live in the sandbox.

3. One named owner, who works here.

   Every workflow lists a current owner. When someone leaves, their workflows are reassigned in the same week as their records, and the change goes in the log.

4. Trigger and exit criteria are documented.

   Each workflow states what enrolls a record and what has to be true for it to leave. Re-enrollment is off unless the reason is written next to it.

5. No workflow triggers on a property it writes.

   Directly or through another workflow. This is checked against the writer map before any switch-over.

Each entry lists its owner, trigger, exit criteria, the only properties it may write, and which of the original 64 it replaces. Select an original ID to see what it was.

The same seven properties. One writer each. Deal stage is set once, when the hand-off creates the deal; after that only reps move deals.

Nothing is silently dropped. Every original workflow has exactly one disposition, and the counts have to add back to the inventory before the switch-over is signed off.