Procurement policies
Govern versioned procurement categories, fixed routes, supplier flow-down, incoming-inspection derivation and conditional role approvals through independent publication.
Screen orientation
Tenant administration is required. Policy author and publisher must be different named users; every referenced role must have the server-required operational permission.
A structured editor covers policy identity, category/criticality, five fixed routes, clauses, inspection requirements and approval rules. Simulation and immutable history precede publication.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Policy key · Policy name · Purpose | Text | Required. | Create a stable controlled policy identity and bounded purpose. | Forms the immutable version register. |
| Criticality levels · Procurement categories | Structured lists | At least one allowed pair is required. | Define code/name and exact permitted combinations. | Controls governed RFQ selection. |
| Route name · Minimum invited suppliers · Minimum complete quotations · Controlled route description | Fixed-route controls | Required for all five code-owned routes. | Set bounded competition minima without adding route codes. | Freezes route definitions. |
| Rule key · Name · Exact role · Precedence | Conditional approval controls | Required per rule. | Reference an eligible exact role and unique order. | Materialises future ordered approvals. |
| Requirement key · Title · Inspection level · Exact Quality role · Precedence | Incoming-inspection controls | Required per requirement. | Define exact STANDARD/ENHANCED/FULL derivation and accountable role. | Freezes the inspection definition. |
| Controlled inspection description · Sampling / checklist plan reference | Inspection evidence fields | Required as applicable. | State the supplier/inbound expectation and exact checklist reference. | Pins future receipt/inspection handoff evidence. |
| Clause key · Title · Type · Document · Precedence · Controlled supplier-facing text | Flow-down clause controls | Required per clause. | Create versioned structured supplier requirements. | Builds the immutable rendered flow-down. |
| Effective from · Change reason | Version controls | Required for a successor. | Bound future use and explain the version change. | Preserves prior published transactions. |
| Category · Criticality · Currency · Ownership · Classification · Project reference · Contract reference · Total value · Supplier lifecycle · Line count | Simulation facts | Required according to rules. | Exercise only the fixed safe declarative fact catalogue. | Stores the exact simulation result/checksums without a transaction. |
| Simulation note | Long text | Required. | Explain the tested scenario. | Provides attributable pre-publication evidence. |
Actions and effects
When to use: After a complete structured definition.
What it does: Checks references and exact policy/route/inspection checksums without creating an RFQ.
When to use: After a successful current-checksum simulation.
What it does: Freezes the version for independent decision.
When to use: By a different Tenant Administrator.
What it does: Publishes for future governed RFQs or retains rejection; old snapshots remain unchanged.
When to use: When a published definition changes.
What it does: Creates an immutable successor and leaves existing transaction snapshots pinned.
Lists and states
- Policy and definition register: use status, exact version and accountable actors to distinguish current work from retained history.
- History and evidence: hashes and source/version references identify the immutable facts used by each decision.
Authority boundary
Policy chooses among code-owned procurement, inspection and approval gates. It cannot execute scripts/SQL, qualify a supplier, create procurement/receipt/inspection/custody/stock/ledger records or rewrite existing snapshots.