Resolve Conflicts and Open Questions

Marketing says Priya should become Sales-ready once she requests a walkthrough and matches the target segment. Sales says that only happens after a seller reviews the request and accepts the handoff. An automation author has to finish the routing workflow anyway, so they pick Marketing's definition because the fields already exist. The workflow didn't resolve the disagreement. It hid it inside a field update.

A conflict record is a business decision that has to earn its keep

Write a conflict record whenever two interpretations would change a lifecycle, stage, handoff, reporting population, or downstream rule. It needs: competing interpretations, evidence reviewed, a decision owner, required reviewers, affected systems, and the check that will prove the decision got applied.

Business precedence decides which approved business definition controls a record transition. It never means the latest writer wins. Some questions can wait, but the temporary treatment has to be genuinely safe: it should block an unsupported state change, preserve evidence, name an accountable owner, and set a review date.

What stays true while the definition is open

Priya stays Engaged, work status stays Awaiting acceptance, both interpretations get recorded, and the handoff routes for review. No automation gets to convert temporary handling into a completed lifecycle state on its own authority.

Carry this into your business

Schedule a short definition review with the people who own the work, the decision, and the reporting. Keep a conflict record whenever a definition changes, because it gives Operations a place to protect reporting history.