NaavekNAAVEK
ProductRequirements & Decisions

Requirements & Decisions

From requirement to decision, in a single card

Most tools split requirements and decisions across different systems. In Naavek, the same card transitions through the whole lifecycle, so the history is always in one place.

Live demo

Try the lifecycle yourself

Assign teams, collect acceptance, watch it lock into a permanent decision record.

1
2
3
PS
REQ-0001
Requirement

API authentication method

System must support OAuth 2.0 and token-based authentication for all API endpoints accessed by third-party integrations.

Click + Assign to bring in teams

1
Unassigned
PS
REQ-0001
REQUIREMENT

API authentication method

Requirement created, no teams assigned yet.

Assign

Requirement created. No teams assigned. Lives in a backlog until actioned.

2
Under discussion
PS
REQ-0001
REQUIREMENT

API authentication method

Two companies assigned. Awaiting acceptance.

2 pending

Companies assigned. Each company sees Accept and Reject controls. Status shows pending count.

3
Decision
PS
REQ-0001
DECISION

API authentication method

All companies accepted. Card is now locked.

Decided

All companies accepted. Strip desaturates, badge locks, text dims. The card is now immutable, a permanent record.

Requirements

Requirements that stay alive, not archived

Most AEC teams manage requirements in spreadsheets. Naavek gives them a structured, versioned home, so changes are tracked, owners are clear, and nothing quietly drifts.

  • Version history on every requirement
  • Owner and status tracking
  • Linked directly to decisions and deliverables
  • ISO 19650 compliant structure
  • Change notifications to affected team members

No more requirement amnesia

When a client changes a structural requirement on week 14, every downstream deliverable is flagged automatically. Your team sees what is affected before the damage is done.

Requirement card in Naavek

How it works

01Capture requirements from the client brief
02Assign owners by discipline and company
03Track status through the delivery lifecycle
04Link every requirement to a decision or deliverable

Decisions

Every decision, structured and searchable

Decisions made verbally, over Slack, or buried in meeting notes are decisions that come back to haunt you. Naavek gives every decision a permanent, linked record.

Decision card in Naavek

Decision states

DraftDecision in progress, not yet formal
FinalApproved and locked to the record
ArchivedSuperseded but preserved for history
  • Structured decision records with rationale
  • Linked to the requirements they affect
  • Decision owner and date stamped
  • Searchable full text
  • Exportable for client or audit review

Audit-ready at any point

Export a full decision register with linked evidence for any ISO 19650 information delivery milestone. No last-minute scramble.

Explore the full product

See how requirements and decisions connect to team coordination and the trace graph.