Why SolveHFX CCs Your Councillor (And When to Contact Them Directly)
One of SolveHFX's features is auto-CC'ing your district councillor on every report. Not everyone loves this. So here's why we do it — and when you should contact them directly instead.
Why Councillors?
The 311 queue is deep. Reports get triaged, scheduled, deprioritized. Meanwhile, your street has had a pothole for 8 weeks.
Your councillor is politically motivated to respond. They want re-election. Constituent complaints are votes at risk. A pothole in their district that goes unfixed is a failure they own.
SolveHFX taps into that incentive.
When your councillor gets 5 reports on the same street, they escalate to HRM management: "Why are residents complaining about this? Fix it." Suddenly, it moves.
The Controversial Part
Some people argue councillors shouldn't be "service concierges." They have bigger responsibilities: policy, budgets, community planning.
Fair point. Councillors shouldn't be handling every pothole report manually.
But: Councillors absolutely should be aware of patterns. If one street has 10 reports, that's data. That's a systemic issue. That's worth escalating to infrastructure planning.
When to Use SolveHFX (311 + Councillor)
First-time issue: Report on SolveHFX. Let it route to 311. Councillor gets a copy.
You don't know who to contact: SolveHFX figures it out automatically.
You want pressure applied: Multiple reports on the same issue + councillor awareness = faster action.
When to Email Your Councillor Directly
1. 4+ weeks with no progress: "I reported this to 311 on [date]. Still no action. Can you escalate?"
2. Systemic issue in your district: "Three potholes on my block, multiple broken lights, graffiti not cleaned. Is this a resource issue?"
3. Safety concern: "This pothole is at a school crossing and kids are getting hurt."
4. Councillor campaign promise: "You promised to fix streets during your campaign. This one's still broken."
When NOT to Email Your Councillor
First report: Use 311 / SolveHFX first.
Routine issue: "My garbage can has a dent." (That's property standards, not councillor territory.)
Minor aesthetic preference: "This streetlight could be brighter." (311 handles this.)
Out of scope: "Can you change the transit route?" (That's separate city department territory.)
The Reality Check
Councillors get hundreds of emails per week. The ones that get attention:
Organized groups ("100 residents on my street have reported this...")
Safety emergencies
Persistent, ignored issues
Systemic problems (not one-off complaints)
A single pothole report? Councillor sees it but might not act on it.
Multiple reports from multiple residents on the same street? Councillor notices and escalates.
How to Use This Strategically
1. Report on SolveHFX (sends to 311 + councillor)
2. Ask neighbors to report the same spot (multiple reports = pattern)
3. Wait 3 weeks (let 311 process it)
4. If nothing: Email councillor directly with reference number + context: "I've reported this via 311 on [date]. Multiple residents reported the same pothole. Still broken. Can you check on this?"
That email gets action because it shows:
You're organized (reference number, specific date)
Multiple people care (not just one cranky resident)
You've given 311 time to respond (you're reasonable)
You're escalating appropriately (not your first move)
The Bottom Line
Councillor CC is for systemic issues and escalation, not routine service.
If you think that's wrong — if you believe councillors shouldn't see civic reports — then we need a different approach. But in practice, a councillor who knows about a pothole is a councillor who asks why it's not fixed.