Governance practice · Practical guide

Tracking Dependencies Between Committee Actions

Make blocked work visible with prerequisite evidence, named owners and realistic escalation paths.

Identify the dependency, not just the delay

An action may be blocked because a prior approval, data set, legal review or budget release has not arrived. Record the actual prerequisite rather than marking the owner “late” without context. Distinguish a hard dependency, where work cannot proceed safely, from a preference or coordination request. A dependency should have its own owner and expected evidence; otherwise the action register merely moves the uncertainty to another column.

Create traceable links

Assign stable IDs to each action and link the dependent item to its prerequisite. Record who owns the prerequisite, the expected deliverable, due date and the meeting that authorised it. Avoid circular chains in which Action A waits for B while B waits for A; flag these for the chair or programme lead. Where a dependency sits outside the committee’s authority, document the external contact and decision point without implying the committee can compel delivery.

Use clear status and dates

Keep the original deadline and any approved revised deadline, with a reason for change. A blocked status should not automatically excuse a missed deadline. Record when the block was identified, what interim work is possible and when the dependency will next be reviewed. Do not reset overdue counters simply to make the dashboard look green. An escalation threshold can be based on risk, elapsed time or impact, but it must reflect actual policy.

Prepare an exception report

Before each meeting, produce a short list of blocked actions showing the prerequisite, responsible person, current evidence and proposed decision. Ask whether to escalate, re-sequence, allocate support, formally revise a date or accept a risk. Only the authorised body should approve material changes to mandate or deadline. Keep the discussion focused on what unlocks the work, not on attributing blame without evidence.

Fictional worked example

A fictional neighbourhood committee asks a volunteer to publish an accessibility guide by 20 May. Publication depends on a facilities inspection report due 10 May. The report is delayed because the inspection was rescheduled. The secretary links the two action IDs, records the revised inspection date and places the publishing deadline before the chair for review. The volunteer is not falsely recorded as having completed the guide.

Close the loop

Once the prerequisite arrives, attach or reference the approved evidence and confirm that the dependent owner has received it. Reassess the remaining work rather than automatically declaring the blocked action complete. Preserve the sequence of updates so future reviewers can distinguish an avoidable failure from an authorised change of plan.

This is general operational guidance, not legal advice. Follow your governing documents and applicable law. All examples are fictional. SecretAIry's interactive demo does not access customer records.