A knock at the cabin door at half past seven
A neighbour arrives at the gate, angry. A delivery wagon blocked her drive again this morning. Last week it was dust on her car, and the week before that the radio from the scaffold. She has already emailed the office and phoned the council. Your site manager apologises, promises to sort it and goes back to the crane lift. The office replies to the email with a different answer. The council's officer then rings the client, who rings your director.
Nothing about this is unusual on an urban site. What makes it worse is that nobody has the whole story.
Why complaints get out of hand
Complaints come through every channel a site has, and there is no single owner. Site managers deal with the ones at the gate and forget to record them. The office deals with emails without knowing what site already said. The link between a complaint and the site activity that caused it is never made, so the same thing happens again.
- Complaints arrive at the gate, by phone, email, via the council and via the client.
- Nobody records complaints handled on the spot.
- Different people give neighbours different answers.
- Complaints are not linked to deliveries, working hours or particular works.
- Reports to the client or a considerate scheme monitor are pieced together by hand.
What poorly handled complaints cost
Relations with neighbours sour, and neighbours who feel ignored escalate to the council, the client and sometimes the local press. Planning conditions and agreed working arrangements can come under scrutiny, which your advisers and the client will want to handle carefully. Your site manager loses time to repeated visits from the same neighbour, and your company's name suffers on a street where you may want to work again.
The neighbour log we build
- Neighbours report through a web form or dedicated email and phone number on the site hoarding, and complaints raised at the gate are logged by the site team on a phone in a minute.
- Complaints forwarded by the council or the client are added to the same log, so each neighbour has one history.
- Each complaint is assigned to the site manager with a response time you set, and chased if it passes.
- The complaint is linked to the site activity at the time: booked deliveries, noisy works in the programme, working hours.
- The neighbour receives a reply with what is being done, written by your team from a suggested draft, and the reply is recorded.
- Patterns are shown: repeat complainants, repeat causes, times of day. The site manager can change the delivery route or timing that keeps causing trouble.
- A monthly summary is produced for the client and, where you are registered with a considerate scheme, for the monitor's visit.
| Complaint | Linked activity | Response |
|---|---|---|
| Wagon blocking a drive | Early block delivery, unbooked | Supplier told to use the booked route |
| Dust on cars | Cutting on the east boundary | Works method reviewed by site manager |
| Radio on scaffold | Scaffold trade on site | Trade briefed, neighbour updated |
| Parking in the street | Operatives' vans | Parking plan reissued |
What your site does in response is for the site manager and your managers to decide. The log makes sure each complaint gets a considered answer and nothing is lost.
Neighbours who feel heard
Each neighbour gets one consistent answer from you, recorded, and a follow-up when something changes. Your site manager can see at a glance what keeps causing complaints and deal with the cause. When the client or the council asks, you show them the log rather than trying to recall conversations. Over the life of the job, the complaints that do arrive are handled quickly, and the street sees a contractor that responds.
Is this how complaints reach your sites?
- Complaints are handled by whoever receives them.
- Complaints dealt with at the gate are not recorded.
- Neighbours get different answers from site and office.
- The same causes keep producing complaints.
- Reporting complaints to the client is done from memory.