Chapter 1
Open the decision packet
Michael Grant opens a decision packet for the proposed welding fixture. The view explains the amount, business purpose, plant, budget context, attached specification, prior procurement review, and the rule that routed the request to Finance. Evidence is grouped by source and timestamp. Michael is not asked to approve from a notification alone; the decision context is available in the record.
- Evidence visible
- Request fields · Business rationale · Budget context · Specification · Prior decision · Routing rule
- Human action
- Michael reviews the packet and opens the budget evidence.
- Policy or system boundary
- Access, routing, and approval authority follow the configured Northstar Industrial Systems workflow.
- Accessible alternative
- Chapter 1 shows Michael's finance decision packet with the request, rationale, budget context, evidence, prior review, and routing reason.
Read the complete walkthrough
Open the decision packet
Michael Grant opens a decision packet for the proposed welding fixture. The view explains the amount, business purpose, plant, budget context, attached specification, prior procurement review, and the rule that routed the request to Finance. Evidence is grouped by source and timestamp. Michael is not asked to approve from a notification alone; the decision context is available in the record.
Inspect the route
The route explanation shows which approval steps are complete, why Finance is next, and when the final operations approval becomes active. A conditional safety review is shown as not triggered because the submitted fixture class is outside that fictional rule. The interface explains the condition instead of hiding it. This path is illustrative and not a universal control design.
Ask for evidence
Michael notices that the budget attachment covers equipment purchase but not installation. He selects Request clarification, identifies the missing installation estimate, and assigns the response to Maya. The request pauses at the finance step. The question is recorded with its author and time, and the current packet remains available for comparison when new evidence arrives.
Resolve the exception
Maya attaches the installation estimate and explains how it changes the total request value. The record preserves the earlier attachment and adds a new version rather than silently replacing evidence. The fictional routing rule reevaluates the updated total and confirms that the same finance and final approval path applies. Michael can compare the change before deciding.
Act or escalate
Michael now has enough evidence to act. He approves the finance step and records a decision note. The screen also shows how a delayed step could be flagged or escalated under a configured policy, but no fixed service level is claimed. The final operations approver receives the updated packet, route rationale, and Michael's decision. Notifications support the workflow; they are not the decision itself.
Read the in-platform trace
The completed trace shows Maya's submission, the routing version, procurement review, Michael's question, the added evidence, both approval decisions, and their notes. It supports review of approvals completed within the illustrated platform workflow. It does not claim immutable records or coverage of decisions made outside the platform. The viewer can use this pattern to identify which evidence should accompany a real approval.