Supply History
Review completed orders, value bands, delivery performance, issue rate, and history signals.
Supply History detail
Delivery Variance Notes
Two completed deliveries include small quantity variance notes that were resolved before invoice approval.
Supply History record
Delivery Variance Notes
Two completed deliveries include small quantity variance notes that were resolved before invoice approval.
2 notes
Monitor
Monitor
Open delivery proof guide
Performance record context
History records summarize delivery performance and supplier reliability across completed Register interactions.
2 notes
| Field | Why it matters | Signal |
|---|---|---|
| Performance record | Primary object this record is tied to. | 2 notes |
| Performance signal | The main amount, package, delivery, or capital signal to inspect. | Monitor |
| Status | Current visible state for this role. | Monitor |
| Next gate | Next allowed action or review step. | Open delivery proof guide |
Performance workflow
History review should expose performance outcomes, issue patterns, linked records, and improvement signals without making the supplier edit the score directly.
Linked orders
Delivery outcomes
Issue pattern
Invoice history
Performance signal
Evidence and source path
Performance evidence should remain tied to actual orders, deliveries, invoices, and issue records.
Quantity variance note
Substitution confirmation
Receipt signoff
Invoice approval trail
Future proof checklist
2 notes
Performance packet
The history packet summarizes completed interactions, delivery reliability, issue patterns, and future-fit signals without making the supplier manually edit performance results.
Monitor
| Signal | Visible value | Why it matters |
|---|---|---|
| Performance record | 2 notes | Shows the governing object this record belongs to. |
| Performance signal | Monitor | Highlights the main value, delivery, capital, or performance signal. |
| Next gate | Open delivery proof guide | Clarifies what the user can inspect or do next. |
| Source state | Source-backed | Keeps placeholder, source-backed, and planned integration data separate. |
| Visibility | Permissioned Register view | Protects private bids, quotes, payments, and restricted diligence fields. |
History lifecycle
History should remain tied to actual records so performance signals are explainable and not manually invented.
| Stage | Owner | Signal | State |
|---|---|---|---|
| Order history | Supplier | 2 notes | Complete |
| Performance summary | Register | Delivery reliability and variance notes | Monitor |
| Improvement loop | Supplier | Issue response or improvement note | Next |
| Fit signal | Register | Future need matching | Pending |
| Visibility review | Workspace owner | Profile-visible result only | Planned |
Improvement signal
Variance notes help suppliers strengthen future proof packages without turning resolved issues into blanket disqualification.
Two resolved delivery notes
Small quantity variance resolved before invoice approval
No current invoice blocker
Record substitution and variance notes during delivery proof upload
Monitored but not a hard block for new needs
Record facts
Two resolved delivery notes
Small quantity variance resolved before invoice approval
No current invoice blocker
Record substitution and variance notes during delivery proof upload
Monitored but not a hard block for new needs
Governed action guardrail
Atlas may summarize this record, explain gaps, and draft questions. It cannot approve, deny, publish, pay, award, select, or execute the next governed action. Human owners remain responsible for every decision gate.