ModelRefs / Procurement Intake — Canonical Workflow
Procurement Intake — Canonical Workflow
Procurement Intake: provisional AI workflow implementation reference with candidate models, providers, tools, and architecture.
Overview
Classify procurement requests and prepare policy, vendor, budget, risk, exception, and approval routing for authorized human review. Operations deployment requires organization-specific access, retention, approval, exception, and audit controls. Integrations with ERP or workflow systems must be validated against the target data, permissions, and failure paths. Outputs remain provisional decision support and require accountable human review before consequential actions.
Implementation profile
| Category | llms |
|---|---|
| Implementation maturity | production |
| Primary use cases | extraction, enterprise-automation |
| Deployment options | managed-api, hybrid |
| Architectures | serverless-api, managed-container, hybrid-private-cloud |
What this evidence does not establish
- No jurisdiction, procurement policy, catalog, vendor list, budget hierarchy, competition rule, risk taxonomy, or approval matrix is registered.
- No measured classification accuracy, policy recall, budget-validation error, routing accuracy, reviewer burden, or cycle-time outcome is attached.
Candidate models with published references
- BGE-M3
- GPT-5
- GPT-5 Mini
- Claude Sonnet 4.5
- Claude Opus 4
- Gemini 3 Pro
- Llama 4 Scout
- DeepSeek R1
- Mistral Large 2
- Command R+
- o3
- o4 Mini
Coverage means the model is a candidate worth evaluating for this workflow, not a ranking or a recommendation. Models whose reference pages are still in review are omitted.
Benchmarks relevant to this workflow
- IFEval — Instruction-following evaluation with verifiable constraints.
- HellaSwag — Commonsense NLI: select the most plausible 4-way continuation of an ActivityNet/WikiHow paragraph.
- MMLU — Massive Multitask Language Understanding — 57 academic and professional subjects.
These are the benchmarks whose task shape bears on this workflow. Each one only describes its own protocol and date, so confirm the harness matches your workload before treating a score as evidence.
Continue your research
Use these connected ModelRefs sections to compare alternatives, inspect implementation paths, and review the evidence and governance boundaries relevant to Procurement Intake — Canonical Workflow.