Product Map

Product map Decisions Detailed Decision Workflow

Detailed Decision Workflow

Capture the detail needed to review and revisit important decisions.

Released Available now
Explore Nortrue Learn more about Decisions

Capability overview

Important decisions need more than a final answer. Future teams also need to understand the context, trade-offs, timing, and assumptions that made the choice sensible.

Detailed Decision Workflow gives teams a structured way to capture decision type, rationale, accepted trade-offs, effective date, review date, and revisit triggers. Status and ownership keep the next step clear as a decision moves from proposal to an agreed direction and later review.

The result is a decision record that supports follow-through today and remains useful when circumstances change.

What this helps with

  • Preserve the reasoning behind important choices
  • Make accepted trade-offs explicit
  • Set effective dates and planned review points
  • Record the conditions that should reopen a decision
  • Classify decisions for clearer filtering and review
  • Keep ownership and status visible throughout the workflow

Common use cases

  • Documenting an architecture choice with known constraints
  • Recording a vendor decision that should be reviewed before renewal
  • Capturing a delivery trade-off with a time-bound review point
  • Setting triggers for revisiting a risk or security decision
  • Giving future leaders enough context to reassess an earlier choice

Who it helps

Technology and architecture leaders documenting consequential choices

Delivery leaders managing time-bound trade-offs

Platform owners reviewing vendor and lifecycle direction

Risk and security owners preserving review conditions

Operations teams maintaining accountable decision workflows

How this connects to Nortrue

Detailed Decision Workflow builds on the Decision Register and works with Decision Context Linking, Decision Timeline, and Decision Status & Supersedence.

Review dates and revisit triggers help decisions stay connected to changing project, risk, platform, agreement, and strategy context rather than becoming static historical notes.

Frequently asked questions

What extra detail can a decision record include?

A decision can include its type, rationale, accepted trade-offs, effective date, review date, revisit triggers, owner, status, and linked operating context.

Why add a review date to a decision?

A review date creates an explicit checkpoint for testing whether the decision still fits the organisation’s needs and assumptions.

What is a revisit trigger?

A revisit trigger records the condition or change that should prompt the team to reconsider a decision before its planned review.

Can the workflow support proposed decisions?

Yes. A decision can be proposed before it is decided, then later be withdrawn or superseded as direction changes.