Stakeholder Notification Log Template
Written from experience on CTRL, Crossrail and Network Rail
This stakeholder notification log records who was told about the works, when, how, and when they acknowledged it, from the highway authority and planning department to the Environment Agency, utilities, neighbours and emergency services.
See what you get →Completed except the facts only you know
£25 + VAT
£30 inc. VAT
- Fills in: The register header for your project.
- Stays [TO CONFIRM]: Names and references you haven’t given us. Entry rows are left blank.
- A competent person must review before use.
- Company logo in header
- Delivered in minutes
- Word document (.docx)
Template
£9 + VAT
£10.80 inc. VAT
Blank register — fill in yourself
- Word document (.docx)
- Guidance notes included
- Instant download
- Use on any project
Prices exclude VAT: UK customers pay 20% VAT; VAT is not charged for customers outside the UK.All documents are drafts. Placeholders marked [TO CONFIRM] must be completed with your site-specific details. A competent person must review before use on site.
What it's for
Missing a notification can delay a start, lead to complaints, or cause problems with a permit or consent. The log shows at a glance who has been told and who has not replied, and gives you a dated record if anyone later says they were not informed.
When you need it
Before work starts, and whenever the works change in a way that affects others, such as new road closures, noisy work, out-of-hours working or a new phase.
Who signs it
The project manager.
What's inside
- Project details
- A notification log with stakeholder, contact, method, date sent, date acknowledged and notes
- A starting list of common stakeholders: local authority highways and planning, the Environment Agency, Network Rail where relevant, neighbouring properties, utility companies and emergency services
- Blank rows for others
- Project manager sign-off
FAQ
- Who should be on the list?
- Anyone affected by the works or whose permission or cooperation you need. The template starts with the most common stakeholders and leaves room for others.
- Is a letter drop to neighbours enough?
- Record how and when they were told. For disruptive work, many contractors also give a contact number for queries and complaints.
- Should acknowledgements be chased?
- Yes, for anyone whose response you need before work starts. The acknowledgement column shows who has not replied.
- Can I keep using it during the works?
- Yes. Add a row each time you notify someone about a change, such as a road closure, out-of-hours working or a new phase, so the log stays a complete record of who was told and when.
- What is [TO CONFIRM]?
- Details only you know, such as names, references and dates. We never guess these. They appear as highlighted [TO CONFIRM] placeholders, and the register opens with a list of every one. The entry rows are always left blank: we never invent entries, so you record them as the work goes on.
- Can I edit the document?
- Yes. Both options are Word documents you can edit freely.
- Do I still need to review it?
- Yes. A competent person must check every document against the actual site and works before it is used. ClarusDocs gives you a complete first draft, not a substitute for that check.
Related documents
- Site Instruction LogLog every instruction now — so you can claim it later
- Permit to DigSign-off that buried services are found and marked before anyone breaks ground
- Daily Site DiaryThe record that wins disputes — one page a day
- Subcontractor Attendance and Output RecordWho was here, what they did — agreed and signed each week
- Hot Works PermitApproval for welding, cutting or grinding, with the fire watch afterwards
- Permit to AccessApproval to work in a client's or tenant's premises, applied for 24 hours ahead