How do you integrate our policy if it’s a big Word document?
We do not “auto-understand” long Word documents. Instead, we translate relevant sections into a small set of machine-enforceable rules (typically 5–20), then confirm a mapping table: policy text → rule ID → enforcement behavior.
Which has higher priority: our policy or Tranzia scoring?
Policy always has higher priority. Scoring provides advisory context; policy defines constraints. Options that violate policy are labeled FAIL regardless of score.
Can Tranzia contradict our policy?
Tranzia should not contradict your policy. If a policy rule is ambiguous or required inputs are missing, Tranzia reports WARN/FAIL with explicit reasons and lists gaps under uncertainty.
How do we know policy is enforced every time?
Every Decision Receipt includes policy identifiers (policy_id, policy_version) and rules_evaluated results. You can audit enforcement by exporting receipts and reviewing PASS/WARN/FAIL outcomes.
Do you support exceptions and overrides?
Yes. Exceptions are normal in operations. Tranzia can record: recommended options, chosen action, and an optional reason code or supervisor acknowledgement requirement.
What if we change policy over time?
Policies are versioned. Receipts record policy_id and policy_version so you can prove which policy was applied at the time of each decision.
What inputs do you need to enforce policy?
Only what your policy requires. Common inputs: local time, mode, after-hours flag, solo/escorted flag, maximum spend, and approved exception paths. PII is not required.
Can we run policy-only without relying on local safety signals?
Yes. For low coverage areas, Tranzia can operate in policy-first mode: enforce your rules and document uncertainty about local signals.
Will staff be blocked from traveling?
Tranzia is advisory, but you can integrate it into a gating workflow you control (dispatch assignment, authorization, reimbursement) if you want strict enforcement. You choose advisory vs fail-closed per workflow.