Requirement Type

Requirement Type

Definition

Vocabulary applied to template_requirements (planned rename form_template_requirements per Q-OQR1-16) capturing the type of requirement a form imposes (e.g. mandatory certification evidence, capability statement, financial declaration). HYBRID per §6.2 — core 7 values ship as baseline; clients may add domain-specific requirement types via admin UI deferred to v1.1.

Synonyms / Acronyms

None formalised. Procurement-specific requirement codes (e.g. SSQ section identifiers) may live as aliases when cataloguing forms.

Baseline values

key	label	provenance
policy	Policy	core
statement	Statement	core
evidence	Evidence	core
data	Data	core
narrative	Narrative	core
declaration	Declaration	core
reference	Reference	core

(Source: template_requirements_requirement_type_check CHECK constraint, verified 14/05/2026. All 7 values observed in prod with row counts: data 32, declaration 21, narrative 16, evidence 12, policy 7, statement 5, reference 3.)

Relationships

• template_requirements.requirement_type — CHECK enum on the column (constraint name template_requirements_requirement_type_check, verified supabase/types/database.types.ts template_requirements shape).
• template_requirements table — also carries template_id FK to form_templates, requirement_text, is_current.
• Will move to form_template_requirements.requirement_type post-Q-OQR1-16 combined PR (rename pending).
• Adjacent to CV 26 form_type — a form_template’s form_type constrains which requirement_types are typically used.
• Layer 5: consumed by form_templates and form_template_requirements as part of the Theme A form pipeline.

Consumers

• lib/templates/template-coverage.ts — coverage scoring against template requirements.
• lib/mcp/formatters/templates.ts — MCP tool result formatter for template surfaces.
• components/coverage/template-coverage-section.tsx — coverage UI surface.
• app/api/coverage/gaps/route.ts — gap analysis endpoint (which requirements lack content).
• Bid response coverage analysis (which requirements are met by which content).
• Future admin UI for client-added requirement types (v1.1 per Q-OQR1-13).

Notes

• 7 values verified S236 W1 against the template_requirements_requirement_type_check CHECK constraint; all 7 observed in prod.
• Carries is_current column today; a provenance column will be added per Q-OQR1-11 ratification.
• Per §6.2, “Theme A form-type generalisation implies clients may add domain-specific requirement types”.
• Marked HYBRID (core baseline + client-extension); editable_via: admin_ui (deferred to v1.1).