Modern architectural railway station interior

DECISION-TO-REQUIREMENT REVIEW

DECISION-TO-REQUIREMENT REVIEW

Start with the decision.

Start with the decision.

Start with the decision.

Define the information.

Define the information.

Define the information.

Build traceability.

Build traceability.

Build traceability.

We help infrastructure clients and asset-owning organisations connect organisational decisions to clear information requirements, responsibilities and acceptance criteria. The result is a clearer, traceable route from organisational need through the relevant information requirements and exchanges to information that can be reviewed, accepted and used.

We help infrastructure clients and asset-owning organisations connect organisational decisions to clear information requirements, responsibilities and acceptance criteria. The result is a clearer, traceable route from organisational need through the relevant information requirements and exchanges to information that can be reviewed, accepted and used.

Why this review starts with the decision

Information requirements should be derived from the decisions and organisational needs they must support.

Public strategies, policies and asset information can provide useful initial evidence, but they are not sufficient on their own to establish an organisation's information requirements.

The review combines available evidence with structured discussion and client validation. The objective is to understand why information is needed before defining what information should be requested.

This creates a clearer route from organisational decisions through requirements and the information exchanges that support them.

Decision
RequirementsOIR · AIR · EIR
Information NeedLOIN
Exchange PointIEPs
Review & Acceptance
Use
What the review includes

A structured route from decisions to trusted information.

The precise scope is agreed with the client, but a Decision-to-Requirement Review may focus on the following areas.

Decision clarity

Clarify the decisions, outcomes and operational activities that information must support.

Priority decisions & evidence needs

Identification of the decisions that drive value, risk and assurance — and the evidence each decision requires.

Information requirements

Clarify and prioritise the information requirements needed to support the identified decisions and outcomes.

Requirement traceability

Improve traceability between organisational decisions, information requirements and relevant exchanges.

Review & acceptance responsibilities

Clarify who provides, reviews, receives and accepts information, including the criteria and authority for acceptance.

Prioritised next actions

Prioritised actions to address the most important gaps, clarify ownership and strengthen information management.

Typical outcomes

Clarity before information is requested or exchanged.

A clearer link between organisational decisions and information
Traceable requirements from organisational need through exchange and acceptance
Defined responsibilities for provision, review, receipt and acceptance
Visibility of gaps, assumptions and areas requiring validation
A practical route from current state to stronger information control
What the review considers

Six areas that shape reliable information.

01
Purpose
The decisions, activities or outcomes the information must support.
02
Requirements
Whether the necessary organisational, asset and exchange information requirements are sufficiently clear.
03
Information Need
Whether the information requested is appropriate and proportionate to its stated purpose.
04
Exchange
When information is needed, between whom, and where relevant exchange points occur.
05
Responsibilities
Who provides, reviews, receives and accepts information, and where responsibility needs greater clarity.
06
Traceability
Whether requirements and information remain connected to the decisions and sources they support.
Review, validation and approval

Kendi supports the review. The client retains authority.

Kendi provides advisory review, information requirements support, traceability and gap identification. Kendi does not replace the client's dutyholders or assume approval or acceptance authority.

Publicly available information may be used as initial evidence, but requirements are developed through review, discussion and validation with authorised client representatives.

Draft advisory output for review, validation and approval by the client's authorised representatives.

Start with the decision the information must support.

If your organisation is defining information requirements, reviewing existing requirements or trying to trace information from organisational need through exchange and acceptance, start with a conversation.
Discuss a Decision-to-Requirement Review →
Why this review starts with the decision

Information requirements should be derived from the decisions and organisational needs they must support.

Public strategies, policies and asset information can provide useful initial evidence, but they are not sufficient on their own to establish an organisation's information requirements.

The review combines available evidence with structured discussion and client validation. The objective is to understand why information is needed before defining what information should be requested.

This creates a clearer route from organisational decisions through requirements and the information exchanges that support them.

Decision
RequirementsOIR · AIR · EIR
Information NeedLOIN
Exchange PointIEPs
Review & Acceptance
Use
What the review includes

A structured route from decisions to trusted information.

The precise scope is agreed with the client, but a Decision-to-Requirement Review may focus on the following areas.

Decision clarity

Clarify the decisions, outcomes and operational activities that information must support.

Priority decisions & evidence needs

Identification of the decisions that drive value, risk and assurance — and the evidence each decision requires.

Information requirements

Clarify and prioritise the information requirements needed to support the identified decisions and outcomes.

Requirement traceability

Improve traceability between organisational decisions, information requirements and relevant exchanges.

Review & acceptance responsibilities

Clarify who provides, reviews, receives and accepts information, including the criteria and authority for acceptance.

Prioritised next actions

Prioritised actions to address the most important gaps, clarify ownership and strengthen information management.

Typical outcomes

Clarity before information is requested or exchanged.

A clearer link between organisational decisions and information
Traceable requirements from organisational need through exchange and acceptance
Defined responsibilities for provision, review, receipt and acceptance
Visibility of gaps, assumptions and areas requiring validation
A practical route from current state to stronger information control
What the review considers

Six areas that shape reliable information.

01
Purpose
The decisions, activities or outcomes the information must support.
02
Requirements
Whether the necessary organisational, asset and exchange information requirements are sufficiently clear.
03
Information Need
Whether the information requested is appropriate and proportionate to its stated purpose.
04
Exchange
When information is needed, between whom, and where relevant exchange points occur.
05
Responsibilities
Who provides, reviews, receives and accepts information, and where responsibility needs greater clarity.
06
Traceability
Whether requirements and information remain connected to the decisions and sources they support.
Review, validation and approval

Kendi supports the review. The client retains authority.

Kendi provides advisory review, information requirements support, traceability and gap identification. Kendi does not replace the client's dutyholders or assume approval or acceptance authority.

Publicly available information may be used as initial evidence, but requirements are developed through review, discussion and validation with authorised client representatives.

Draft advisory output for review, validation and approval by the client's authorised representatives.

Start with the decision the information must support.

If your organisation is defining information requirements, reviewing existing requirements or trying to trace information from organisational need through exchange and acceptance, start with a conversation.
Discuss a Decision-to-Requirement Review →
Why this review starts with the decision

Information requirements should be derived from the decisions and organisational needs they must support.

Public strategies, policies and asset information can provide useful initial evidence, but they are not sufficient on their own to establish an organisation's information requirements.

The review combines available evidence with structured discussion and client validation. The objective is to understand why information is needed before defining what information should be requested.

This creates a clearer route from organisational decisions through requirements and the information exchanges that support them.

Decision
RequirementsOIR · AIR · EIR
Information NeedLOIN
Exchange PointIEPs
Review & Acceptance
Use
What the review includes

A structured route from decisions to trusted information.

The precise scope is agreed with the client, but a Decision-to-Requirement Review may focus on the following areas.

Decision clarity

Clarify the decisions, outcomes and operational activities that information must support.

Priority decisions & evidence needs

Identification of the decisions that drive value, risk and assurance — and the evidence each decision requires.

Information requirements

Clarify and prioritise the information requirements needed to support the identified decisions and outcomes.

Requirement traceability

Improve traceability between organisational decisions, information requirements and relevant exchanges.

Review & acceptance responsibilities

Clarify who provides, reviews, receives and accepts information, including the criteria and authority for acceptance.

Prioritised next actions

Prioritised actions to address the most important gaps, clarify ownership and strengthen information management.

Typical outcomes

Clarity before information is requested or exchanged.

A clearer link between organisational decisions and information
Traceable requirements from organisational need through exchange and acceptance
Defined responsibilities for provision, review, receipt and acceptance
Visibility of gaps, assumptions and areas requiring validation
A practical route from current state to stronger information control
What the review considers

Six areas that shape reliable information.

01
Purpose
The decisions, activities or outcomes the information must support.
02
Requirements
Whether the necessary organisational, asset and exchange information requirements are sufficiently clear.
03
Information Need
Whether the information requested is appropriate and proportionate to its stated purpose.
04
Exchange
When information is needed, between whom, and where relevant exchange points occur.
05
Responsibilities
Who provides, reviews, receives and accepts information, and where responsibility needs greater clarity.
06
Traceability
Whether requirements and information remain connected to the decisions and sources they support.
Review, validation and approval

Kendi supports the review. The client retains authority.

Kendi provides advisory review, information requirements support, traceability and gap identification. Kendi does not replace the client's dutyholders or assume approval or acceptance authority.

Publicly available information may be used as initial evidence, but requirements are developed through review, discussion and validation with authorised client representatives.

Draft advisory output for review, validation and approval by the client's authorised representatives.

Start with the decision the information must support.

If your organisation is defining information requirements, reviewing existing requirements or trying to trace information from organisational need through exchange and acceptance, start with a conversation.
Discuss a Decision-to-Requirement Review →

Exploring how better information requirements, exchange and assurance support better decisions across the built environment.

Topics

Information Requirements

Information Exchange

Information Assurance

Drawing Information

Asset Information

Health & Safety Information

© 2026 Kendi. All rights reserved.

Exploring how better information requirements, exchange and assurance support better decisions across the built environment.

Topics

Information Requirements

Information Exchange

Information Assurance

Drawing Information

Asset Information

Health & Safety Information

© 2026 Kendi. All rights reserved.

Exploring how better information requirements, exchange and assurance support better decisions across the built environment.

Topics

Information Requirements

Information Exchange

Information Assurance

Drawing Information

Asset Information

Health & Safety Information

© 2026 Kendi. All rights reserved.