ARCH9090 Chap.4 Participation Levels and Public Promises
Participation Levels and Public Promises
The IAP2 spectrum connects five levels of public influence with specific participation goals and promises. This chapter distinguishes Inform, Consult, Involve, Collaborate and Empower, then tests apparent participation against real authority, timing and feedback. The spectrum is not a quality ranking: honest Inform can be appropriate, while a collaborative label attached to a closed decision damages trust.
What this chapter covers
- 01
Inform as balanced and objective information about a decision or settled requirement
- 02
Consult as obtaining feedback and explaining how input influenced the decision
- 03
Involve as working with participants so concerns are understood and considered
- 04
Collaborate as partnering on alternatives and incorporating advice as far as possible
- 05
Empower as placing final decision-making in public hands
- 06
Authority, timing, fixed constraints and feedback as tests of an honest promise
Worked example · free
Classify a workshop by influence rather than appearance
- 1Separate the closed route and station decisions from the open design details. The marks here are used only for independent practice and do not represent a University assessment scheme.
- 1Classify feedback on the fixed route as Consult if it is heard and reported but cannot change the choice.
- 1Classify the open details as Involve only when participants work through revision and see their concerns considered.
- 1Publish a promise that names both boundaries instead of calling the whole process Collaborate.
Key terms
- Inform
- The participation level that provides balanced and objective information without promising decision influence.
- Consult
- The participation level that obtains feedback and reports how public input influenced a decision.
- Involve
- The participation level that works directly with people so concerns are understood and considered throughout.
- Collaborate
- The participation level that partners with the public in developing alternatives and identifying preferred solutions.
- Empower
- The participation level that places the final decision in the hands of the public.
Participation Levels and Public Promises FAQ
Is a workshop automatically collaborative?
No. A workshop may only provide information or gather feedback if the important decisions are already fixed. Classify the process by the influence participants have over criteria, alternatives, recommendations or the final decision, not by how interactive the event appears.
Is Empower always the best level?
No. The appropriate level depends on authority, law, risk, timing and the open decision. Inform can be honest for a settled statutory requirement. The ethical problem is promising more influence than the institution can deliver, not choosing a lower level when its boundary is clear.
What should a participation promise contain?
State what participants can shape, what is fixed, who makes the final decision, how input will be considered and when people will receive feedback. A participant should be able to describe their influence in the same terms as the project team.
Can one project use several participation levels?
Yes. A project may involve people early in defining criteria, consult on a developed option and later inform the public about an approved decision. Classify each decision stage separately and communicate the boundary at that time. Do not describe the whole project with the highest level it reached once.
The feedback report should show which criteria, alternatives or recommendations changed at each stage so the public promise can be tested against actual influence. Assign responsibility for notifying participants when the level changes, because a revised promise has little value if it remains inside the project team.
Assessment move
Build a five-row spectrum from memory, but attach a decision test to every row. For a real or invented project, list which elements are fixed, open to feedback, jointly developed or delegated. Classify each element separately because one project can operate at different levels across its decisions. Rewrite vague promises such as have your say into statements of influence, authority and feedback.
Study common mismatches: a vote with retained authority is not empowerment, a workshop after option closure is not collaboration, and a general invitation does not prove involvement. In practice, read the recruitment page and the final report side by side. The language of promise should match the evidence of influence. If the two differ, identify whether the design or the label needs repair.
Practise classifying the same technique under different authority conditions. A survey on a settled rule is Inform or Consult, while a survey result with binding authority could support Empower. This prevents memorising techniques as levels. Draw a timeline and mark when criteria, options, recommendations and final approval become fixed. A process cannot offer influence after the relevant choice has closed.
Write one sentence for each IAP2 level describing what the institution must later prove in its feedback report. Then test a public promise with a sceptical participant: would the ordinary meaning of decide, partner or shape match the legal and organisational authority available? Where multiple decisions exist, publish separate promises rather than choosing the highest label.
Keep a record of how advice altered criteria or alternatives so Collaborate and Involve can be evidenced. A label is never the proof; the decision trail is.