Platform
Better Data is built around operating loops, not disconnected records and screens. Each loop is a versioned state machine with deterministic transitions and compliance-ready history.
Operating model (canonical): Sense → Decide → Approve → Execute → Improve. Approve is explicit: human authority, policy, and evidence before high-impact execution — surfaced in Govern and Loops. Narrative and diagrams: Architecture on betterdata.co.
A loop has a lifecycle, transitions triggered by domain events, and a full transition history by default.
| Traditional SCM | Better Data | |---|---| | Navigate records and trigger manual actions | Loops surface the right actor at the right state | | Audit trail is separate from execution | Audit trail is a natural output of loop transitions | | Integrations require custom side channels | Domain events are the integration boundary | | Modules are siloed by screen | Modules participate in shared loops |
These pages mirror how operators navigate Sense through Improve in product docs. Sense hub: Analyze overview (URLs /sense/* redirect there).
Sense
What's happening now — inventory, demand, and risk signals (Analyze section in sidebar).
Decide
Forecasting, planning, and policy-based recommendations before execution.
Approve
Human authority, roles, policy gates, and evidence — primary home in Govern; mechanics in Loops.
Execute
Procurement, fulfillment, transfers, and catalog operations through governed transitions.
Improve
Dashboards, KPIs, and accuracy metrics to close the loop.
Govern also covers trust, traceability, compliance, and security across all steps — not only approval. See Govern overview for the full pillar.
| Loop | Typical path | |---|---| | Procurement | Intent -> PO -> Confirmation -> Receipt -> Invoice Match -> Settlement | | Fulfillment | Demand -> Reservation -> Pick/Pack -> Ship -> Delivery -> Inventory Settle | | Quality | Trigger -> Lot ID -> Hold -> Assessment -> Resolution -> Audit | | Replenishment | Signal -> Threshold Breach -> PO Trigger -> Procurement spawn |
Every transition records actor identity, timestamp, and correlation context, so compliance evidence is generated during normal operation. This supports regulated flows across DSCSA, FSMA, FDA 21 CFR Part 11, and CSRD-oriented traceability where applicable.
Compliance alignment is built into loop mechanics. You still validate final legal obligations with your compliance and legal teams.