Setting up Venzeo™ for public lighting

Street lights as places of interest and photos from every repair, audit and inventory, so each pole has a history you can look back on.

You look after thousands of light points, and contractors repair, audit and inventory them. Without photos, you cannot tell later how a pole looked before a repair, or when a fault started. Ask the contractor to document this work with photos in Venzeo™, and every light point has complete documentation as soon as the photos upload.

Ask your contractors for photo documentation

Ask your contractor to document every repair, audit and inventory in Venzeo™. Ask for photos of the lamp, the pole and its base, and preferably the LED module. Each photo is taken in the Venzeo™ app, with the time and GPS position. See Why photos must be taken in the Venzeo™ app.

The contractor also gains from this. Its crew takes photos in one app instead of sending files by email. Every photo is filed under its pole and job number, so the contractor does not have to sort them later.

Put each contractor in its own group, so they see only their own work. Add your own administrators to every contractor group, or they will not see the contractors’ reports. See Setting up groups for separate teams.

Make every light point a place of interest

Create a place of interest for each pole or light point, with your pole number as the custom ID. Put a QR code or NFC tag with the number on the pole, so the crew scans it instead of searching. For thousands of poles, create them from your GIS or asset register through the Venzeo™ API. See Setting up places of interest (POIs) and Connecting your system to Venzeo through the API.

Keep a history for every pole

Make places of interest required, so every report belongs to a pole. The Places of Interest view then shows all reports of one pole, each with time and GPS position. Compare the photos to:

  • see how rust on the pole or its base has developed over the years
  • find the first report where water got inside the lamp
  • see the vegetation around the pole before a repair, so the crew brings the right equipment, such as a lifting platform or tools to cut branches

Example: an LED module fails because of water inside the lamp. The operator opens the pole’s place of interest and finds the first photo with water in it, taken in an audit two years earlier.

Use tags (previously called types) for what the crew finds, such as Rust, Water inside and Damaged pole, and send an email alert on Damaged pole to the duty manager. See Adding and editing tags (types) for reports and Activating an email alert notification.

Give each job a task with the contractor’s job number

Send the contractor a task for each repair or audit. Use the contractor’s job number as the custom ID and connect the pole as the place of interest. The crew photographs the pole before and after the work. Before you approve the invoice, filter the reports by the job number. See Creating and assigning tasks.

Which features to use

Feature Use it? How
Places of interest Yes One per light point, pole number as custom ID, QR code on it
Tasks Yes One per repair or audit, contractor’s job number as custom ID
Groups Yes One per contractor
Tags Yes What the crew finds, such as Rust, Water inside, Damaged pole
Email alerts Sometimes A Damaged pole tag to the duty manager
Assets Rarely Only when you track lamps or controllers separately from poles

Ask your favourite AI about Venzeo

Open a new chat that answers from our help center.

Connect via MCPFor AI apps that support MCP servers.
https://help.venzeo.com/mcp
  • Claude: Settings → Connectors → Add custom connector, then paste the URL.
  • ChatGPT: Settings → Apps & Connectors → turn on developer mode → Create, then paste the URL.
  • Claude Code, Cursor, VS Code: Add the URL as a remote (HTTP) MCP server.