Keep the system understandable when things change.

Check whether records support the next decision; completeness is not the same as usefulness.

Give tags a clear meaning, owner and retirement rule before adding more.

Check the selected plan and demonstrated permissions against who genuinely needs each class of information.

Reassign open work and verify ownership before removing access; never share the departing person’s login.

Verify what a saved export actually contains and what it would take to reconstruct the working process.

Separate data export, usable reconstruction, connected accounts and billing decisions.

Use an approved retention policy and check open obligations before disposing of records.

Establish whether the expected route was manual logging or sync before reconnecting or forwarding everything again.

Check owner, filters and the linked record’s status before creating a replacement task.

Preserve the original record and establish what actually happened before retrying an action that might contact someone.

Name which system owns each record, direction of travel and recovery process before enabling a connection.

Keep the original identifiers and compare outcomes before rerunning a job that may already have partly succeeded.

Record the changed promise, decision owner and next action instead of silently rewriting the accepted scope.

Judge whether the team can now recover commitments more reliably, not whether everyone has logged in.