What Are Decision Traces in Hiring?
A Decision Trace is the signed, queryable record of a proposed workflow and the decision that followed. Nodes ingests and processes permitted evidence, then proposes a cross-system workflow with ROI. A named human can approve, edit, or decline it, and the system acts only after approval. In hiring, the trace records the evidence, model and policy versions, recommendation, projected cost of action and inaction, human input, approved action, and later outcome when available. It does not turn a manager's choice into ground truth.
What a Decision Trace records
- Evidence: the permitted records used across the relevant systems.
- Versions and policy: the model, policy, and workflow versions in force.
- Recommendation: the proposed cross-system workflow and its projected economics.
- Human input: the named reviewer's approval, edits, decline, and rationale.
- Approved action: what the system executed across the permitted systems after approval.
- Later outcome: the defined result when it becomes available.
The value is the chain. A reviewer can inspect what the system knew, what it proposed, what the human changed, and what happened later.
Why the trace includes more than a prediction
A prediction estimates a future result. A Decision Trace preserves the full operating record around that estimate, including the evidence boundary, the recommendation, the human decision, the action, and the later outcome. That record lets teams review a decision without assuming that the prediction or the human response was correct.
What you can ask a decision trace
A Decision Trace makes cross-system questions inspectable. For example: show each recommendation affected by an industry-experience rule, who approved or edited it, which action followed, and how the defined production outcome compared later. No single system holds that full chain.
Where decision traces have been studied
The production evidence comes from one Fortune 500 insurance carrier. Across 10,765 agents, a linked-record audit tested 3,597 resume keywords against a production milestone. None predicted that milestone after Bonferroni correction, and 30 were anti-predictive. The result shows why the evidence and outcome need to remain attached to the decision record. Read the full research.
Frequently asked questions
What is a decision trace? A signed, queryable record of the evidence, versions and policy, recommendation, human input, approved action, and later outcome behind a decision.
Is a decision trace a prediction? A prediction may appear inside a Decision Trace. The trace also records how that prediction was produced, what a named human decided, what action followed, and what happened later.
What data is needed to build one? The permitted records needed for the defined decision and outcome. In hiring, those records may come from the CRM, HRIS, ATS, and assessment systems, joined under the customer's access and governance rules.
Who uses decision traces? Talent, risk, security, and audit teams use Decision Traces to inspect the evidence, human oversight, approved action, and later outcome behind a workflow.
Related reading
- Decision traces: the full research
- What is talent intelligence infrastructure?
- Why ATS keywords fail to predict performance
See what a decision trace surfaces in your hiring data. Request a Decision Replay.