The procurement rules aren't a document somebody maintains. They're generated from how the system is set.
Most organisations keep a policy in a Word file and a system that enforces something else. Atlas has one source — the thresholds, regime and region you configure. The rules page, the clause library and the enforcement all read it, so words and behaviour cannot drift.
Your procurement rules, written by the system from your own settings.
The page a buyer, approver or auditor reads to know what the rules here actually are — generated, not typed. Change a threshold and the page changes with it, because it is the configuration the enforcement reads.
- From the settingsValue bands, the regime, the region and the sector are set once in configuration; this page is written from them
- Not a claimIt describes what the system will do, not what someone hopes it does — the guidance and the enforcement share one source
- Below and above thresholdIt states the duties that apply beneath each threshold and the procedure required above it, in the figures you set
- Reads the same to everyoneThe requester who wants to know what happens next and the auditor checking what should have happened read the same page
Set the region and the doctrine changes — not just the currency and the tax.
A regime is more than a tax rate. Contract A/B in Canada, the Procurement Act 2023 in the UK, Directive 2014/24 in the EU, PDPL residency in the GCC — each with its own thresholds, procedures and binding language. The region setting selects the whole set.
- The threshold matrixTrade-agreement and statutory thresholds load for the region — NWPTA/CFTA/CETA, the Act's bands, the Directive's, by entity type
- The doctrineWhether a compliant solicitation forms a binding process contract is a regional question. The generated rules answer it in the region's own terms, not a borrowed one
- SwitchableChange region from the same settings screen; nothing else needs reconfiguring for the rules to follow
- Named in writingThe region the workspace runs under is stated, so a residency or compliance review has a one-line answer
The whole page is downstream of a handful of settings.
No rules document to write, no policy PDF to keep in sync. The administrator sets region, value bands and sector; everything the reader sees and everything enforced follows from that.
- Region & currencyRegion profile sets the currency, the tax and the threshold matrix in one move
- Your bandsThe value ladder and the delegation of authority are your figures, in the group's reporting currency
- Public or privateThe sector switch changes which duties apply and which documents the library offers
- Inert until setLeave a control unset and it simply does not appear as a rule — the page never asserts something the system will not do
The clauses and templates are generated for the regime, not pasted from a folder.
A rules engine that stopped at a web page would leave the tender documents to a shared drive. The clause library is generated for region and sector too, so the solicitation a supplier receives says what the rules page says.
- Generated per regimeThe master documents and response forms are produced for the region's doctrine and the sector, not kept as a one-size template
- Refuses the wrong clauseWhere a clause would be wrong for the region — a process-contract term in a jurisdiction with no Contract A — it is not generated
- One trailThe document issued, the rule it came from and the event it was used on are the same record. The paperwork is evidence, not a copy
- Branded, not rewrittenYour organisation's name and logo sit on the standard set; the wording stays the generated, defensible one
