A council tender for 1.2 kilometres of road reconstruction through a shopping strip carries a returnable called “Community and Stakeholder Management Plan”, weighted at ten per cent. Three contractors submit. Two of them return a two-page document that promises to “maintain open communication with all stakeholders” and to “minimise disruption to the community”. The third names the eleven businesses on the strip, states which four of them take deliveries before 7am, and explains how their access will be maintained through the two weeks their frontage is being rebuilt.
The third contractor did not write a better document. They wrote a plan for that job instead of a plan for any job — and a community and stakeholder engagement plan is the returnable where that difference is most visible, because the evaluator scoring it usually lives or works in the affected area.
The fifth management plan
Civil contractors know the management-plan family. Four documents appear in almost every returnable schedule, and the library covers each of them:
- WHS management plan and SWMS — how you will not hurt anyone.
- Construction environmental management plan — how you will not damage anything.
- Traffic management plan and traffic guidance scheme — how traffic will keep moving.
- Quality management plan and ITPs — how you will prove it was built right.
The fifth is the community plan, and it is the odd one out in a useful way. The other four are technical documents assessed by technical people against technical standards. The community plan is a behavioural document, and the thing it is really being assessed for is whether this contractor understands that a construction site sits inside somebody’s suburb. Consultation with Traditional Owners is a separate obligation with its own statutory basis and is not part of this plan — see our guide to Aboriginal cultural heritage in civil works.
That is why it is the plan most often submitted as generic boilerplate, and the plan where boilerplate is most obvious. An evaluator cannot always tell whether your ITP frequencies are realistic. They can absolutely tell whether you have looked at the street.
Five names for the same returnable
The naming is inconsistent across agencies and councils, which causes contractors to miss the returnable or answer the wrong question. These are the versions you will meet:
| What it is called | What is actually being asked for |
|---|---|
| Community and Stakeholder Engagement Plan (CSEP) | The full document — identification, engagement approach, notification, complaints, reporting |
| Communications Plan / Community Communications Strategy | Weighted towards the outbound side: who gets told what, when, by which channel |
| Stakeholder Management Plan | Weighted towards identification and relationship management, often with a register as the core artefact |
| Community Liaison Plan / Community Relations Plan | Council language, usually smaller in scope, focused on residents and businesses |
| A criterion with no plan attached | A scored question inside the methodology or management criterion, answered in one to three pages |
Two practical consequences. First, read the returnable schedule for all five phrasings before concluding the tender does not ask for one — this is one of the returnables most often missed, and a missing returnable is a compliance problem before it is a scoring problem, as covered in common tender mistakes that cost civil contractors work.
Second, where it appears as a scored question rather than a plan, answer the question rather than attaching the plan. A three-page appendix in response to a 300-word question is a common way to score badly on something you actually do well.
Why it became a scored criterion
Three forces pushed community engagement out of the “nice to have” column and into the weighted criteria.
The client carries the reputational risk, not you. When a resident is angry about a road being dug up, they do not ring the contractor. They ring the council, or their councillor, or the local paper. A council procurement officer has watched a project consume a general manager’s week over a driveway access dispute. They are buying protection from that, and they will pay for it in the scoring.
Conditions of approval flow down. On larger works, the planning approval itself imposes community obligations — a community contact number staffed at all times, complaints acknowledged and recorded, notification periods before certain activities, restrictions on out-of-hours work. Those conditions become contract conditions, and the principal needs a contractor who can discharge them. Where a project has a formal approval, the tender documents will usually reference it directly, and the plan you submit has to be capable of satisfying it.
Amenity has become measurable. Noise, dust, vibration, access and parking are now written into specifications with numbers attached, and the community plan is where a contractor explains how they will stay inside them. That connects it to the CEMP — and on many projects the community plan is formally a sub-plan of it.
The weighting is usually modest — five to fifteen per cent where it is separately scored, often folded into a broader management or methodology criterion. But because so many submissions are generic, the spread between a good answer and an average one is unusually wide. It is one of the cheapest places in a civil bid to gain a genuine scoring advantage.
Who your stakeholders actually are
Most weak plans fail at the first step: they list stakeholder categories instead of stakeholders. “Residents, businesses, road users, council, service authorities” is not a stakeholder analysis. It is a table of contents.
A stakeholder map that scores has three columns beyond the name — what they are affected by, how much, and what you will do about it. Work through the categories below against the actual site, using the drawings, an aerial image and a drive-through.
| Group | What to identify specifically | Typical impact |
|---|---|---|
| Directly adjoining residents | Number of properties, which have driveways onto the works, which have on-street parking only | Access, noise, dust, vibration, parking |
| Businesses | Named, with trading hours, delivery times and customer parking dependency | Trade loss — the highest-heat impact in civil work |
| Schools and childcare | Name, drop-off and pick-up windows, crossing locations, term dates | Pedestrian safety, congestion at fixed times |
| Aged care, medical, disability services | Name, access requirements, patient transport arrangements | Access continuity, noise, mobility-impaired detours |
| Emergency services | Nearest station, and whether the works sit on a primary response route | Response time — never manage this by letterbox drop |
| Public transport | Route numbers, stop locations affected, operator contact | Stop relocation, timetable and detour coordination |
| Waste and service collection | Collection days, side of street, vehicle access constraints | Missed collections — small, frequent, high irritation |
| Service authorities | Water, sewer, power, gas, telecommunications assets in the corridor | Shutdowns, planned outages, relocation coordination |
| Councillors and the client | Ward councillor, project manager, communications team | They receive the complaint before you do |
| Community and interest groups | Progress associations, chambers of commerce, sporting clubs, user groups | Organised, vocal, and usually reasonable if consulted early |
| Aboriginal and Torres Strait Islander groups | Relevant land council or registered parties where the works trigger heritage obligations | Statutory and cultural — see §11 |
Two things separate a strong map from a competent one. It is counted — “34 residential properties, 11 businesses, one primary school and one bus route” tells the evaluator you have been there. And it is prioritised — a plan that treats all stakeholders equally has not thought about which ones will actually cost the client a phone call.
The engagement spectrum, and where civil work sits
Australian agencies overwhelmingly frame community engagement against the IAP2 public participation spectrum — five increasing levels of participation, from inform through consult, involve and collaborate to empower.[1] Referencing it correctly signals that you speak the client’s language. Referencing it incorrectly does the opposite, and contractors do this constantly.
The correction worth internalising: construction delivery almost always sits at “inform”, with elements of “consult”. The design decisions were made and approved before the contract went to tender. Promising to “collaborate with the community on project outcomes” is not ambitious — it is a promise you cannot keep, because you have no authority to change the scope, and an experienced evaluator reads it as inexperience.
| Level | What it means in delivery | Where it legitimately applies |
|---|---|---|
| Inform | Telling people accurately, early and in the right channel | The default position for almost everything you do |
| Consult | Seeking input on matters you can actually change | Staging, timing, access arrangements, out-of-hours proposals |
| Involve | Working directly with affected parties through the works | A business whose access will be constrained for weeks |
| Collaborate / Empower | Shared or delegated decision-making | Rarely the contractor’s role — this sat with the client at planning stage |
The high-scoring formulation is a sentence that shows you know the difference: engagement during construction operates primarily at the inform level, with targeted consultation where the contractor genuinely holds discretion — staging, working hours, and individual access arrangements. That single distinction puts a submission ahead of most of the field.
The plan, section by section
Where the tender prescribes a structure, use it exactly — submitting your own format is an avoidable compliance risk, as set out in non-conforming and alternative tenders. Where the format is open, this spine covers what agencies and councils ask for, and it maps onto the assessment.
| Section | What it must contain | Length |
|---|---|---|
| 1. Purpose and scope | The project, its footprint, and the approval or contract conditions the plan responds to | Half a page |
| 2. Objectives | Three to five measurable objectives, not aspirations. See below | Quarter page |
| 3. Stakeholder identification and analysis | The map from §04, as a table, counted and prioritised | One to two pages |
| 4. Roles and responsibilities | Named people, with the community contact role identified and its hours stated | Half a page plus a simple chart |
| 5. Engagement approach | Level of engagement by stakeholder group, and the reasoning | Half a page |
| 6. Communication tools and channels | Each tool, its audience, its trigger and its lead time — as a table | One page |
| 7. Notification schedule | The activity-by-activity notification plan tied to the programme | One page |
| 8. Complaints and enquiries management | The process, the timeframes, the register, and escalation | One page |
| 9. Issue-specific management | Access, noise and out-of-hours, parking, dust, vibration, property condition | One to two pages |
| 10. Monitoring, reporting and review | What is measured, what is reported to the client, and when the plan is updated | Half a page |
| 11. Appendices | Draft notification letter, complaints register template, stakeholder register | As required |
Objectives that are actually measurable
Section 2 is where most plans announce their quality. Compare:
- Weak: “Minimise disruption to the local community and maintain positive relationships throughout the project.”
- Strong: “Every directly affected property receives written notification at least seven days before works commence at their frontage. Every complaint is acknowledged within 24 hours and closed out within five business days. No unplanned loss of vehicular property access at any point in the works. Zero out-of-hours activity without prior approval and prior notification.”
The second version is four commitments an evaluator can picture being audited. It also tells them you have run a job like this before, which is the underlying question in every management-plan criterion.
The notification regime
Notification is the operational core of the plan and the part contractors most often get wrong — not by failing to notify, but by treating notification as one event at the start of the job rather than a rolling obligation tied to the programme.
The structure that works is a table linking activity to audience to lead time. Typical periods used across Australian council and agency contracts are set out below; always use the periods the tender specifies where it specifies any, because they are contractual.
| Trigger | Who | Typical lead time | Channel |
|---|---|---|---|
| Project commencement | All identified stakeholders in the footprint | 7–14 days | Letterbox drop, client website, site signage |
| Works starting at a specific frontage | That property and immediate neighbours | 7 days | Letterbox drop, followed by door knock for businesses |
| Loss or change of vehicular access | Affected property, individually | 48 hours minimum, ideally 7 days | Face to face or phone, confirmed in writing |
| Changed parking or waste collection arrangements | Affected street | 48 hours | Letterbox drop and on-street signage |
| Out-of-hours, night or weekend work | Everyone within the noise-affected area | 5–7 days, plus reminder | Letterbox drop, and phone for sensitive receivers |
| Utility shutdowns | Affected customers, via the asset owner’s process | As the authority requires, typically 3–5 days | Authority-issued notice, supported by yours |
| Programme change or extended duration | All previously notified parties | As soon as known | Letterbox drop and client update |
| Completion | All notified parties | At completion | Thank-you notice — rare, cheap, and remembered |
Three details that lift this section:
- Include a draft notification letter as an appendix. It costs half a page and it proves the process exists. Keep it plain: what, where, when, how long, what to expect, who to call. Most contractors submit nothing; a good letter is a differentiator out of proportion to its effort.
- State who approves notifications before they go out. Almost every council and agency requires client sign-off on anything with their logo on it, and building that approval loop into the lead time — “drafted 10 days out, submitted for approval 9 days out, distributed 7 days out” — shows you have done it before.
- Tie it to the programme. A sentence connecting the notification schedule to the construction programme — and naming who reviews the four-week lookahead for notification triggers — converts a policy into a system.
Complaints: the 24-hour standard
Complaints management is where the plan stops being a communications exercise and becomes a contractual one. On projects with formal conditions of approval, the obligations are typically explicit — a contact number available at all times during works, complaints acknowledged within a short fixed period, a register maintained and made available to the client or regulator, and reporting of complaint numbers and resolution. Most of those complaints are about noise, vibration or dust, and the controls that reduce them are covered in our guide to noise, vibration and dust management.
Even on small council jobs where nothing is specified, adopting the same discipline is the right answer and reads well.
The process, in the order it should appear
- Receipt. Every channel funnels to one place — site number, client referral, email, in-person on site. Name the number in the plan and say who answers it and when.
- Acknowledgement within 24 hours. Not resolution — acknowledgement, by the same channel the complaint arrived through where possible.
- Record. Logged in the complaints register at the point of receipt, not retrospectively. Date, time, complainant, contact details, nature, activity complained of, and location.
- Investigate. Who is responsible, and what they check. Where the complaint concerns noise, dust or vibration, this links to your CEMP monitoring.
- Respond and resolve. A stated target — five business days is a common and defensible commitment — with a mechanism for complaints that cannot be resolved in that window.
- Escalate. Name the two-step path: site supervisor, then project manager, then the client’s representative. Say what triggers each step.
- Close out and report. Confirmed with the complainant, closed in the register, and reported in the monthly client report with numbers, categories and trends.
The register itself has a life beyond community relations. A complaints record showing that a resident reported vibration on the day you were breaking rock at a particular chainage is contemporaneous evidence — the same category of record discussed in contract administration for civil SMEs, and occasionally useful when a property damage claim arrives six months later.
One reframe worth putting in the plan explicitly: a complaint is a data point about the works, not an attack on them. A submission that says complaints are reviewed at the weekly site meeting for what they reveal about the method — and gives an example of a change made as a result — reads as a mature operator.
Business and property access — the hardest one
If a civil job generates a complaint that reaches a councillor, it is most often about access. Everything else is tolerated; being unable to get a car out of a driveway, or a customer being unable to reach a shop, is not.
This is also the section where a plan can demonstrate genuine method rather than good intentions, because access management is a construction sequencing problem before it is a communications one.
| Situation | What a strong plan commits to |
|---|---|
| Driveway crossings being reconstructed | Individual consultation before the pour; agreed timing; steel plates or temporary ramps where access must continue; the concrete cure period stated in days so the resident can plan |
| Businesses with deliveries | Delivery windows identified in advance and worked around, or an alternative loading arrangement nominated. Named businesses, not “affected businesses” |
| Customer parking loss | Alternative parking identified and signposted; “open for business” signage; staging that avoids taking the whole frontage at once |
| Pedestrian access to shopfronts | Continuous compliant footpath or a defined alternative, maintained daily, and lit if works run into darker months |
| Mobility-impaired residents | Identified during the door knock, and a specific arrangement recorded for each |
| Waste collection | Bin relocation point agreed with the resident and the collection contractor, not assumed |
| Emergency access | Maintained at all times, with the arrangement described — this is a safety commitment, not a courtesy |
The strongest thing you can do in this section is connect it to the traffic management plan and to your staging. If your methodology says the shopping strip is built in three 60-metre stages so that no more than four business frontages are affected at once, say that here, in community terms, and reference the same staging in the methodology. Consistency across returnables is one of the things evaluators actively check, as discussed in writing a construction methodology statement that wins tenders.
Out-of-hours work and the noise conversation
Standard construction hours are set by state environment regulators and by council conditions, and they are broadly consistent: daytime weekday work, a shorter Saturday, and no Sunday or public holiday work without approval.[2] Where the tender or approval states hours, those are the hours — but the guideline positions are worth knowing because they are the default when nothing else is specified.
Two things belong in the plan.
The approval pathway for out-of-hours work. Night and weekend work is sometimes unavoidable — a road that cannot be closed in the day, a concrete pour that must be continuous, a service shutdown the authority will only permit overnight. A plan that sets out the pathway — justification to the client, approval, notification lead time, respite arrangements, a dedicated contact for the duration — turns a likely complaint source into a managed process. It also protects you commercially, because unapproved out-of-hours work is a common source of directions to stop.
Practical noise mitigation you actually use. Not a list of everything possible. Three or four things that are true: scheduling the noisiest activity away from the most sensitive part of the day, non-tonal reversing alarms, plant selection and positioning, no idling near residences, and a respite pattern for extended breaking. This links directly to the plant commitments in your plant and equipment schedule — and claiming low-noise plant you do not own is easy to test.
Stakeholders that need naming
Four groups where a generic approach reads badly and a specific one scores.
Schools and childcare
Name the school, state the drop-off and pick-up windows, and commit to what you will do in them — no heavy vehicle movements through the peak, a traffic controller at the crossing, no delivery scheduling in those windows. Note the term calendar if the works span a holiday period, because scheduling the disruptive work into a school holiday is exactly the kind of thinking that gets noticed.
Emergency services and health
Direct notification, not a letterbox drop, and a named contact who is told of every road closure and detour before it is implemented. Where the corridor serves a hospital, aged care facility or patient transport route, say so and describe the arrangement. This is a safety commitment and evaluators treat it as one.
Aboriginal and Torres Strait Islander stakeholders
Where the works trigger cultural heritage obligations, the engagement is statutory and sits alongside the plan rather than inside it — the duty of care, the relevant parties, and the procedure to follow if something is uncovered belong in the CEMP and its unexpected finds protocol. What belongs in the community plan is the relationship: who the registered or relevant parties are, how and when they are engaged, and how site personnel are inducted on the requirements. Where the project also carries Indigenous participation commitments, those are a separate scored obligation covered in social and Indigenous procurement policies and local content, skills and training requirements — do not conflate the two, because evaluators notice when a contractor treats cultural heritage and procurement targets as the same subject.
The client’s own communications team
The most under-used stakeholder in most plans. Councils and agencies have communications staff with their own channels, their own brand rules and their own approval requirements, and the contractor who works with that function rather than around it makes the client’s life easier. State that all public-facing material is provided for client approval, that you will supply content for their channels, and who your single point of contact is. It is a small commitment that speaks directly to the person likely to be on the evaluation panel.
What makes a plan look site-specific
Seven details, each cheap, that together make it impossible to read the document as a template.
- Counts. The number of properties, businesses, driveways and bus stops affected.
- Names. The school, the shopping centre, the aged care facility, the bus route number.
- Times. The school pick-up window, the bakery’s 5am delivery, the Thursday waste collection.
- A map or extract. An aerial with the footprint and the sensitive receivers marked. One image does more than two pages of text.
- A named person. The community contact, their role, and the hours the number is answered. “A community liaison officer will be appointed” is weaker than a name and a mobile.
- A local reference. One sentence about a comparable job — same council, similar setting, complaint outcome. This ties the plan to the evidence in your past project experience.
- An artefact. The draft notification letter, or the complaints register format. Proof, not description.
None of these require access to information you do not have. All of them are available from an hour with an aerial photograph, a drive-through and two phone calls — and that hour is usually the highest-scoring hour spent on the whole submission.
How evaluators score it
Against the scoring scales used in Australian civil tenders — described in how government tenders are scored — a community plan tends to separate along four axes.
| Axis | Low score | High score |
|---|---|---|
| Specificity | Categories of stakeholder, generic commitments | Named, counted, mapped, with impacts identified |
| Realism | Promises the contractor cannot deliver or does not control | Commitments sized to the job and to the contractor’s actual resources |
| Systems | Intentions described in prose | A process with triggers, timeframes, records and an owner |
| Integration | A standalone document that contradicts the methodology | Staging, traffic, environment and community all describing one plan |
The integration axis is worth dwelling on. Evaluators read the returnables together, and the community plan is unusually easy to cross-check: it should be consistent with the programme’s durations, the traffic plan’s closures, the environmental plan’s monitoring, and the methodology’s staging. When those four agree, the whole submission reads as one plan by one team. When they do not — a community plan promising continuous business access alongside a methodology that closes the frontage for three weeks — the contradiction damages every one of them.
After award: the plan you build to
The tender version is a commitment document. Once awarded, the plan usually has to be submitted in final form for the principal’s acceptance before works commence — frequently a hold point, in the same way that the environmental and quality plans are — and it becomes a document you are audited against.
Three consequences worth understanding before you write the tender version.
- Everything you promised is now a measurable obligation. A commitment to a 24-hour acknowledgement is auditable, and the register is the evidence. Do not commit in a bid to a standard the business cannot maintain across a two-year job.
- The plan is a live document. It should be reviewed when the programme changes, when a new stakeholder emerges, and after any significant complaint. Say so in the tender version — the review trigger is one of the cheapest marks available.
- Reporting is usually monthly. Complaint numbers, categories, resolution times, notifications issued, and upcoming engagement. Setting up that report in the first month is far easier than reconstructing it in month six, and it is exactly the kind of contemporaneous record that supports you in a dispute — see contract administration for civil SMEs.
There is a commercial dimension too. Where community requirements are onerous — a full-time community liaison officer, extensive door-knocking, out-of-hours respite arrangements — those are costs, and they belong in the estimate rather than being absorbed. They are a preliminaries item, priced in the same way as any other project on-cost, and covered in preparing civil works cost estimates. Where the tender’s community obligations are heavier than the scope suggests, that is a legitimate input into the go/no-go decision.
Eight failures that cost marks
- Stakeholder categories instead of stakeholders. The single most common failure, and the easiest to fix.
- Promising collaboration. Offering the community influence over decisions already approved. Reads as inexperience and creates an expectation you will have to manage.
- A corporate plan with the project name changed. Evaluators recognise it immediately, usually from the absence of any local detail.
- No named contact or no stated hours. “A 24-hour contact will be provided” is not a 24-hour contact.
- Contradicting the methodology or the traffic plan. Cross-check access, staging and closures across all returnables before submission.
- Ignoring businesses. Residents complain; businesses claim. A plan that treats a shopping strip as “adjacent land uses” has missed the commercial risk entirely.
- Confusing consultation with notification. Telling people is not consulting them, and describing a letterbox drop as consultation invites a lower score.
- No monitoring or review mechanism. A plan with no feedback loop is a statement of intent, and it scores like one.
Pre-submission checklist
- Have you searched the returnable schedule for all five names this document goes by?
- Is the plan in the tender’s required format, or the required page limit?
- Are stakeholders named and counted rather than categorised?
- Have you identified every business, school, health facility and bus route in the footprint?
- Are your objectives measurable — timeframes, not adjectives?
- Is the level of engagement correctly pitched at inform and consult?
- Is there a notification table linking activity, audience, lead time and channel?
- Is the client’s approval step built into the notification lead times?
- Is there a complaints process with an acknowledgement timeframe, a register and an escalation path?
- Is property and business access addressed as a sequencing question, not just a communications one?
- Is there an out-of-hours approval pathway?
- Is there a named community contact with stated hours?
- Does the plan agree with the programme, the traffic plan, the CEMP and the methodology?
- Is there a map or aerial extract?
- Is a draft notification letter or register template attached?
- Have the community costs been priced into preliminaries rather than assumed?
The short version
- The community plan is the fifth management plan, and the one where generic writing is most visible.
- Name and count your stakeholders. An hour with an aerial photograph and a drive-through outscores a week of careful prose.
- Pitch the engagement at inform and consult. Promising collaboration on decisions already approved reads as inexperience.
- Notification is a rolling obligation tied to the programme, not a single letterbox drop at the start.
- Acknowledge complaints within 24 hours, register them at the point of receipt, and report them monthly. The register has an evidentiary life beyond community relations.
- Access is the complaint that reaches the councillor. Solve it in the staging, then describe it in the plan.
- Everything you promise becomes an auditable obligation after award — and a cost. Price it in preliminaries.
Sources and further reading
This guide is general information for Australian civil construction businesses and is not legal advice. Community engagement obligations, notification periods, permitted working hours and complaints requirements are set by the tender documents, the contract, the development or planning approval, and the applicable state environmental legislation and council conditions — and they differ between jurisdictions and between projects. All examples are illustrative. Always work from the tender documents, the conditions of approval and current regulatory requirements.
- International Association for Public Participation (IAP2) — IAP2 Public Participation Spectrum, as adopted and referenced by Australian government agencies and local councils in community engagement policies and frameworks: five levels of increasing public impact — inform, consult, involve, collaborate and empower — each with a stated public participation goal and promise to the public. Australian agencies commonly require tenderers to describe their engagement approach against this spectrum, which is why the level a construction contractor can legitimately operate at is a scored distinction. Referenced in §05.
- State environment protection guidance on construction hours and construction noise — including the NSW Environment Protection Authority’s Interim Construction Noise Guideline (recommended standard construction hours of 7am–6pm Monday to Friday, 8am–1pm Saturday, and no work on Sundays or public holidays, with a separate assessment pathway for works outside those hours), EPA Victoria’s guidance for civil construction, building and demolition (normal working hours and unreasonable-noise provisions), and the noise provisions applying to building and construction work under the Queensland Environmental Protection Act 1994. Council conditions of consent and project-specific approvals frequently impose tighter hours than the guideline positions. Referenced in §10 — always work to the hours stated in the tender, contract or approval.
- Related TenderBuilt guides carrying the primary-source detail referenced above: construction environmental management plans (site-specific environmental management plan requirements, sub-plans, monitoring and hold points), traffic management plans and traffic guidance schemes (road occupancy, closures and the authorisation regime by state), how government tenders are scored (evaluation panels, scoring scales and moderation), and how council procurement actually works (the local government procurement rules that sit behind council tender conditions).