Build an OCDS Procurement Implementation Document Auditor
Cross-reference OCDS procurement implementation releases against vendor certification registries. Flag active projects where required insurance credentials expire during the physical delivery phase.
What you are building
The core problem, expected build, and operating context for this challenge.
Cross-reference OCDS procurement implementation releases against vendor certification registries. Flag active projects where required insurance credentials expire during the physical delivery phase.
A public-contract implementation milestone evidence request coordinator for oversight teams.
Parse OCDS releases focusing on contract and implementation milestone arrays.
Match contracted supplier identifiers against internal vendor credential registries.
Compare implementation execution dates against supplier document expiration timestamps.
Assemble an implementation audit memo highlighting active contracts with lapsed certificates.
A contract award staging interface listing tender parties, documentation validity dates, and exception notices.
Utilize open sample releases from the Open Contracting Data Standard repository alongside mock supplier certificate files. Starter examples below are synthetic. They are not downloaded records.
Open Contracting Data Standard Parse OCDS release schema sections including parties, awards, and supplier organization references.
qdrant, pydantic, fastapi. Qdrant enables vector similarity lookup across multi-lingual supplier names and tender descriptions. Local or hosted embedding model for semantic party matching.
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.
Parses OCDS release JSON payloads extracting parties with supplier roles.
Compares contract award dates against supplier document expiration timestamps.
Outputs a structured audit report summarizing award eligibility and documentation deficiencies.
```json [ { "input": { "ocid": "ocds-213kz6-0012", "implementation": { "status": "active", "milestones": [ { "id": "m-1", "dueDate": "2024-06-30T10:00:00Z" } ] }, "supplier_registry_entry": { "id": "GB-COH-9921", "insurance_expiry": "2024-04-30", "status": "active" } }, "expected_output": { "ocid": "ocds-213kz6-0012", "supplier_id": "GB-COH-9921", "has_expired_credentials_during_implementation": true, "expired_items": [ { "document": "insurance_expiry", "expired_on": "2024-04-30" } ], "audit_verdict": "implementation_compliance_failed" } }, { "input": { "ocid": "ocds-213kz6-0013", "implementation": { "status": "active", "milestones": [ { "id": "m-2", "dueDate": "2024-10-30T10:00:00Z" } ] }, "supplier_registry_entry": { "id": "FR-RCS-1144", "insurance_expiry": "2025-01-01", "status": "active" } }, "expected_output": { "ocid": "ocds-213kz6-0013", "supplier_id": "FR-RCS-1144", "has_expired_credentials_during_implementation": false, "expired_items": [], "audit_verdict": "implementation_compliance_cleared" } } ] ```
Demonstration uses mock procurement records. No real government procurement bids or contracts are affected. Use mock external writes. Require human review before any real deployment.
Participation guide
Demonstration uses mock procurement records. No real government procurement bids or contracts are affected. Use mock external writes and human review.
How work is evaluated
Parses OCDS release JSON payloads extracting parties with supplier roles. Compares contract award dates against supplier document expiration timestamps. Outputs a structured audit report summarizing award eligibility and documentation deficiencies.
Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.
Challenge datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
Complete workflow
Parse OCDS releases focusing on contract and implementation milestone arrays. Match contracted supplier identifiers against internal vendor credential registries. Compare implementation execution dates against supplier document expiration timestamps. Assemble an implementation audit memo highlighting active contracts with lapsed certificates.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Parses OCDS release JSON payloads extracting parties with supplier roles. Compares contract award dates against supplier document expiration timestamps. Outputs a structured audit report summarizing award eligibility and documentation deficiencies.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
A contract award staging interface listing tender parties, documentation validity dates, and exception notices.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Demonstration uses mock procurement records. No real government procurement bids or contracts are affected.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Parse OCDS releases focusing on contract and implementation milestone arrays.
Match contracted supplier identifiers against internal vendor credential registries.
Compare implementation execution dates against supplier document expiration timestamps.
Assemble an implementation audit memo highlighting active contracts with lapsed certificates.
Reference links and supporting material
Utilize open sample releases from the Open Contracting Data Standard repository alongside mock supplier certificate files. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
Qdrant
Open-source vector database.
Evaluated output
No output checks are configured.
- Parse OCDS releases focusing on contract and implementation milestone arrays. Match contracted supplier ide...
- Parses OCDS release JSON payloads extracting parties with supplier roles. Compares contract award dates aga...
- A contract award staging interface listing tender parties, documentation validity dates, and exception noti...
- 2 public reference cases
- 2 configured tools
Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.
View technical recipe
Configured tools
- Qdrant · Optional
- Qdrant · Optional
Evaluation contract
- Complete workflow · Weight 40
- Correctness and evidence · Weight 30
- Review interface · Weight 20
- Safe execution · Weight 10
Reference cases
- 2 public reference cases
Workflow tasks
No workflow tasks are configured.
Recipe freeze marker
No recipe freeze time is recorded.