Define what will be accepted

Describe the deliverables with the people who will use them. Specify the acceptance criteria and the scope boundaries. These elements allow you to discuss an observable outcome rather than an isolated percentage of progress.

Make dependencies explicit

Identify external contributions, validations and shared resources. A blocked task must indicate what is missing and who can unblock the situation. The schedule must reflect these dependencies.

Avoid confusing an activity report with a decision taken.

Make the review a place of decision

Focus the review on significant gaps, risks and trade-offs. Record decisions with their owner and deadline. Do not confuse an activity report with a decision made.

Prepare the next steps

Delivery also includes handover and operating conditions. Check the responsibilities after commissioning. Within DTSC, SPARK handles project and programme management in Engineering & Infrastructure and IT & Digital.

A decision log that supports action

Illustrative example: a supplier announces a delay to a component needed for an installation. Project tracking should show the affected deliverables, available options and deadline for choosing. The project manager prepares the consequences of each option; the authorised decision-maker decides. The decision is then reflected in the schedule and communicated to the teams involved. Keep the log short: it should make it possible to understand why a choice was made.

  • The issue to resolve, the options and the decision deadline.
  • The decision-maker, people consulted and assumptions used.
  • The choice made, its consequences and assigned actions.
  • The conditions that would justify reviewing the decision.
Written byThe DTSC ecosystem27 July 2026 · 3 min read
Deliver& Improve

SPARK delivers

Does this topic concern you?

Let’s start from your situation: a first conversation is enough to see what can be done, with whom and within what timeframe.