Dependency and decision log

Event / owner / version: [ ]

For each dependency, identify both the person supplying the input and the person waiting for it. A status such as 'in progress' does not close the dependency.

IDRequired input / decisionInput ownerReceiving ownerEnables activity IDRequired byEffect if lateAvailable alternativeDecision approverAgreed decision / timeEvidence of handoverStatus
D01Approved room layout[ ][ ][ ][ ][ ][ ][ ][ ][ ]Open
D02Confirmed access conditions[ ][ ][ ][ ][ ][ ][ ][ ][ ]Open
D03Approved presentation version[ ][ ][ ][ ][ ][ ][ ][ ][ ]Open
D04Artist requirement review[ ][ ][ ][ ][ ][ ][ ][ ][ ]Open

Coordination review

Current limiting dependency: [ ]

Next approval deadline: [ ]

Action / owner before next review: [ ]

Affected teams informed: [ ]

Next review time: [ ]

Escalation wording: '[Input] is needed by [time] to enable [activity]. If it is not confirmed, [consequence]. The available choices are [options]. [Approver] must decide by [time].'

ThreeSixZero · Event planning worksheet. Adapt to your agreed scope and responsibilities.