Finding a site photo without asking the whole crew

A client calls about a crack near a bay window fitted three months earlier. The site manager knows a photo of the support, taken before the fitting, exists somewhere. He just doesn't know where. He messages the team leader, who searches his gallery and finds nothing, then asks the fitter who installed the window. The photo turns up an hour later, from a third phone.

Where the photos end up, and why they get lost#

A renovation company running several sites at once produces dozens of photos a week: a support before work starts, a snag to clear, a hidden connection that will disappear under a wall, progress to show a client. They land in three different places, none of them tied to the site:

• the personal gallery of whoever took the photo, mixed in with family pictures;
• a group chat for that site, which closes down or gets lost once the site wraps up;
• sometimes a shared folder, fed whenever someone remembers, not for every photo.

While the site is running and the crew stays the same, asking around still works. The day a fitter has left the company, a site has changed hands between two site managers, or a photo is needed six months later for a dispute, it is nowhere anyone knows to look.

What a photo needs to carry with it#

A useful site photo is not just an image: it is an image tied to four pieces of information, captured the moment it is taken, never typed in afterwards.

Sorting photos after the fact, once a week or once a month, almost never works: the person who should do it is busy elsewhere, and the pile grows faster than it shrinks. The only method that holds over time attaches the information to the photo the moment it is taken, not later.

A worked example#

Take a renovation company with fewer than ten people, running three sites in parallel. A site manager looks for an existing photo about twice a week: to answer a client, for an insurer, to show progress. Count 15 minutes each time, the time for a message to two or three people and waiting for a reply: 30 minutes a week.

Over 45 working weeks, that's a little over 22 hours a year, just to find photos that already exist. At €32 an hour loaded, that's over €700 a year for one person alone. Across a team of three site managers, the total passes €2,000 a year, without counting the time of the team leaders chasing the photo.

What changes with an application built for the company#

When the application is built around the company's own sites, taking a photo from a phone during a visit attaches it automatically to the site open that day. No folder to pick, no caption to type: the site, the date and the author are already known the moment the shot is taken.

Finding a photo becomes a search by site, reachable from any phone on the crew, not a dig through a personal gallery or a chat history. Photos tied to a site handover or to snags still open stay in the same record, without having to be searched for elsewhere on the day they matter.

What not to do#

Don't wait until the end of the site to sort the photos: by then, nobody remembers what each image showed, or where. And don't rely entirely on a consumer chat app's history: a group can be deleted, a phone replaced, a conversation lost. A photo meant to prove something in a dispute has to be filed the day it is taken, not hoped findable later.

Site photos: the key takeaways#

A site photo only has value if it stays findable months after it was taken, at the moment it actually matters: a client's question, an insurance check, a dispute. That depends on what happens the moment the shot is taken, not on a sort promised for later.

The simplest thing to try tonight: ask the crew to name every shared photo with the site's name and the date, even just in a message. It's not a lasting method, but it already saves half the lost searches.