Before You Design Anything: What Is Actually on the Table?

The first question in community engagement isn’t ‘how do we engage?’ — it’s ‘what can the community actually influence, and when?’

The single most damaging sequencing error in community engagement happens before most project teams realise they are making a decision at all.

The briefing room problem.

A project team is briefed on a major infrastructure upgrade. The engagement manager starts designing the process: sessions, methods, timeline, stakeholder list. The work is thorough and well-intentioned.

Three months into engagement, a community group raises a fundamental question about the location of the facility. The project manager explains that the site was chosen eight months ago, is locked in by a funding agreement, and is not open for discussion.

The community group is furious. The engagement team is frustrated. Neither the project manager nor the engagement manager did anything wrong in isolation. But the engagement was designed without anyone first asking: what decisions are actually open to community influence, and when do those decisions close?

Most engagement processes are designed around the question of how to engage. The assumption is that the what and the when have already been established — and that the engagement team’s job is to design a process that reaches the right people and collects good data.

That assumption is where the most fundamental sequencing error originates. The decision space — what decisions are being made, who holds authority over them, and when they will be made — is the anchor point for every other decision in the engagement design process. Without it, you are designing a process that may be technically excellent but structurally disconnected from the decisions it is meant to inform.

Engagement not anchored to real decisions and real decision timelines cannot meaningfully influence outcomes — regardless of how well it is run.

What the decision space actually is

The decision space is the set of decisions that are genuinely open to influence at the time engagement is designed — and the timeframe within which that influence must occur to matter.

It has three dimensions. The first is scope: what specific decisions will community input inform? Not the broad project — specific choices about design, location, timing, scope, or implementation approach that are genuinely open. The second is authority: who has decision-making power over each of those choices, and what is the process by which community input reaches them? The third is timing: when will each decision be made, and what is the latest point at which community input can meaningfully affect the outcome?

Mapping these three dimensions is not a bureaucratic exercise. It is the act that transforms engagement from a consultation process into a genuine mechanism for community influence.

Three questions to map the decision space

1. What specific decisions are genuinely open to community influence on this project?2. Who holds decision-making authority, and how does community input reach them?3. When will each decision be made, and when must engagement conclude to inform it?

The decision window

Decisions don’t stay open indefinitely. Every project has a decision window for each key choice — a period during which the decision is genuinely open to influence. Once that window closes — through a funding agreement, a council resolution, a contract signing, or simply the accumulation of prior commitments — the decision is effectively made, whether or not it has been formally announced.

The decision window closes earlier than most engagement practitioners realise, for two reasons. The first is that organisations accumulate de facto commitments well before formal decisions are recorded. A preferred option that has been presented to a minister, modelled in a business case, or discussed publicly has significantly less flexibility than its formal status suggests. The second is that organisations often conflate the start of engagement with the start of the decision window, when in reality the decision window may have been open for months or years before engagement was initiated.

Understanding the decision window tells you whether there is still meaningful community influence to be had — and if the window is already narrow, it shapes the honest answer to the question of what level of engagement you can run.

Narrow window failure: Engagement is initiated after the key design decisions have been made but before formal approval. Communities are invited to give input on a project whose shape is effectively fixed. Extensive engagement runs. Community input modifies minor details. Communities experience this as consultation theatre — because it is.

What to do when the window is already narrow

Sometimes engagement practitioners are brought in after the decision window has already narrowed significantly. This is a common reality in government contexts, where project timelines, procurement processes, and political pressures mean that engagement is often initiated later than is ideal.

The answer is not to pretend the window is wider than it is. The answer is to be honest about what is genuinely open, design engagement that focuses specifically on those open decisions, and communicate clearly to communities about what is and is not on the table.

Honest Consult on a narrow decision space is more valuable — and more ethical — than Collaborate on a decision space that has effectively closed. It also avoids the trust damage that comes from communities discovering mid-process that the space they thought was open had already been determined.

The honest question isn’t ‘how do we engage?’ It’s ‘is there still something meaningful to engage about?’

Anchoring the engagement timeline to the decision timeline

One of the most consistent sequencing errors in government engagement is designing the engagement timeline around internal project schedules and team capacity, rather than around decision milestones. The engagement runs when the team is ready, rather than when it needs to run to influence the decisions that matter.

The fix is straightforward: start with the decision timeline, identify the latest point at which community input must be available to influence each key decision, and work backwards to determine when engagement must begin and conclude. If internal constraints make that timeline impossible, the conversation to have is with the project manager about decision timelines — not with the community about expectations.

The anchor point principle

Your engagement design timeline should be driven by decision milestones, not project schedules. Ask: when must we have community input in hand for it to genuinely influence this decision? That date is your anchor. Everything else — session scheduling, recruitment timelines, analysis — is built backward from it.

Download Companion Resource

Part of the CE Canvas series: Order of Operations

This post is part of a series on the sequence that drives effective community engagement. Read the full framework in our pillar post: Order of Operations — Why community engagement fails before the first session runs.

Part of Order of Operations for Community Engagement.

Next: A Promise, Not a Preference