Requirement categories

Overview

Requirement categories organize compliance requirements across pursuits — Technical, Legal, Financial, and custom labels. Categories drive in-depth analysis classification, Questionnaire filters, and SME auto-assignment.

New teams receive 19 seeded categories automatically. Customize labels and colors; slugs auto-generate on create. Keep slugs stable once pursuits reference them.

Tip: Before bulk requirement import, confirm you have:

  • Trimmed default 19 to categories your review committees actually use

  • Distinct colors for categories reviewers scan daily

  • SME assignments mapped to finalized categories

  • Avoided deleting categories active in open pursuits

  • Planned rename vs. slug change (rename label preferred)

Caution: Deleting a category revokes SME assignments and leaves requirements needing recategorization.

Default categories (seeded)

Slug

Label

Color

technical

Technical

blue

functional

Functional

purple

business

Business

amber

security

Security

red

compliance

Compliance

emerald

legal

Legal

slate

regulatory

Regulatory

indigo

operational

Operational

orange

financial

Financial

green

administrative

Administrative

gray

eligibility

Eligibility

teal

evaluation

Evaluation

pink

deliverables

Deliverables

cyan

quality

Quality

lime

environmental

Environmental

emerald

social

Social

rose

Post award

Post Award

violet

products_and_services

Products & Services

stone

misc

Miscellaneous

stone

Customize labels/colors; slugs derive from names on create.

How to open

Team → Questionnaires → Requirement categories

Element

Text

Title

Requirement categories

Description

Used in in-depth analysis and reviewer assignment

Action

Add category (+)

Table

Columns: label (badge), slug, actions (edit, delete).

Add category dialog

Field

Required

Notes

Name

Yes

e.g. Technical

Slug

Auto

Lowercase, underscores — preview shown

Color

Yes (default blue)

17 color keys; live badge preview

Create disabled until name produces valid slug. Success toast: Category created.

Edit category dialog

Update label, slug, or color. Slug changes emit events syncing SME assignments. Success: Category updated.

Prefer label rename over slug change when pursuits already reference slug.

Delete category dialog

Confirms deletion. Success: Category deleted. Revokes SME ties to that slug.

States

State

UI

Loading

Centered loading indicator

Error

Empty + Retry

Empty (rare)

No categories yet + Add

Populated

Table

Where categories appear

Flow diagram

Surface

Behavior

In-depth analysis import

Classifies extracted requirements

Pursuit questionnaire

Filter, group, tag rows

SME assignments

Assignment targets

Assistant

Can list team categories

Numbered workflow — align categories with governance

  1. List your real review committees (Technical, Legal, QS, etc.).

  2. Edit default labels to match internal vocabulary.

  3. Delete unused categories (no open pursuit references).

  4. Add custom categories (e.g. Cybersecurity) if needed.

  5. Open SME assignments — map members.

  6. Run pursuit analysis import — verify classification distribution.

  7. Bulk-fix miscategorized rows in questionnaire.

Permissions

View: team members. Create/edit/delete: team management permission.

Slug stability and migrations

Action

Impact

Label edit only

Safe — SME and requirements keep slug

Slug edit

Events update SME; pursuit rows may need check

Delete

Requirements may become uncategorized system bucket

Create duplicate name

Slug collision — pick different name

Uncategorized system slug catches requirements without explicit category — not shown in team table.

Best practices

  • Keep slug stable once pursuits use category

  • Distinct colors for high-traffic categories

  • Do not delete categories in active pursuits — reclassify first

  • Align set with bid review committees

  • Document mapping in internal wiki (slug → committee chair)

Edge cases

Symptom

Cause

Action

Create fails duplicate slug

Collision

Different name

SMEs lost after delete

Category removed

Re-assign SMEs

Categories missing in pursuit

Wrong team / cache

Refresh; check active team

All requirements misc

Analysis pass used wrong defaults

Re-run with categories enabled

FAQ

Rename Technical to Engineering?

Edit label; keep slug technical if referenced.

What is Uncategorized?

System bucket for requirements without category — not in admin table.

Per-pursuit categories?

Team-global catalog only.

Import CSV categories?

Not standard — UI create/edit.

Color blind accessibility?

Pick distinct hues + rely on label text in filters.

19 defaults mandatory?

Can delete unused if no references — rare to empty entirely.

  • SME assignments

  • Questionnaire

  • In-depth analysis — create

  • Create pursuit from notice

  • Team overview

  • First pursuit workflow