Registered lobbyist
Benjamin Sanders
- Clients
- 1
Clients by year
Top clients
RegistrationsSubjects
- Technology2
- Emergency Services1
- Social Services1
- Fire Services1
Clients by year· 3 rows
| Year | Client | Registrations |
|---|---|---|
| 2026 | HyperYou, Inc | 1 |
| 2025 | HyperYou, Inc | 1 |
| 2024 | HyperYou, Inc | 1 |
Offices contacted
Communications per year
2025 to 20267 communications, most in 2026 (6)
How and with whom
By method · 4 meetings
By office holder
Most-contacted offices
Meeting rate
Share of this lobbyist's communications recorded as a meeting, presentation or video meeting
Rates are reported only above 20 contacts. Some subjects are mostly handled by email, so rates are best compared within subject category.
Offices contacted· 5 rows
| Office | Office holder type | Communications | Meetings | Last contact |
|---|---|---|---|---|
| Technology Services | City staff | 3 | 2 | 2 March 2026 |
| Customer Experience Division (CXD) | City staff | 1 | 1 | 2 February 2026 |
| Technology | City staff | 1 | 0 | 5 February 2026 |
| Technology Services Division | City staff | 1 | 0 | 5 February 2026 |
| Toronto Fire Services | City staff | 1 | 1 | 10 January 2025 |
Registrations
Registrations by start year
Status
Data table· 3 rows
| Registration | Client | Subject matter | Dates | Status | Communications |
|---|---|---|---|---|---|
| SM37371 | HyperYou, Inc | Emergency Services; Social Services; Technology | 30 January 2026 – 30 June 2026 | closed by lro | 6 |
| SM36994 | HyperYou, Inc | Fire Services | 25 September 2025 – 30 June 2026 | closed by lro | 0 |
| SM35986 | HyperYou, Inc | Technology | 4 October 2024 – 30 June 2025 | closed by lro | 1 |
Linked agenda items
No published links to agenda items.
Former-official status
No match with a former member of council, councillor staff or City staff. A match appears only when a decision model comparing the two records scores it 0.95 or higher.
Disclosure timeliness
Lobbyists must record a communication within 3 days. lobbyTO measures the gap between a communication's date and the first daily snapshot of the registry export in which it appears. The export refreshes daily, so a 1-day gap is expected.
Measurement in progress. Daily snapshots began on 4 October 2026 (2 days of snapshots so far); results appear after 6 months of snapshots, from 4 April 2027. Communications dated before the first snapshot are not measured.