The problem
Photos are how field teams prove what happened on a job: pre-existing damage, cable runs before drywall, rack builds, completed installs, and problems that need a decision from the office. Today the app lets you attach files to a project, task, or service call, but there is no way to work with those photos as a visual record. There is no timeline, no way to see progress over time, no way to mark up a photo to point at something, and no easy way to find the photo you need later.
Many integrators run a separate jobsite photo app alongside D-Tools to fill this gap — CompanyCam, Raken, and similar tools. That means photos live in one system and the project lives in another, and nobody looking at the project record later can see the visual history.
What we're considering
- Fast capture of multiple photos without leaving the project, task, or service call
- Automatic organization by project, date, and who took the photo
- A project photo timeline, so anyone can scroll the visual history of a job
- Markup on a photo: arrows, circles, and text to call out a specific issue
- Before-and-after pairing for the same location or piece of equipment
- Tagging by room, location, or project phase
- Search and filter across a project's photos
- Simple sharing with the client, or pulling selected photos into a report
What we'd like your feedback on
- Which of the above matters most to you, and which you'd skip
- Whether you use a separate photo app today, and what specifically keeps you on it
- Who needs to see these photos: technicians, project managers, clients, or all three
- Whether markup and annotation is essential or a nice-to-have
Allow Sales/Technicians staff to capture photos and post directly to Opportunity notes/images. Currently we have to take photos, then upload them to a PC and add to project.
What we're considering
Fast capture of multiple photos without leaving the project, task, or service call
Automatic organization by project, date, and who took the photo
A project photo timeline, so anyone can scroll the visual history of a job
Markup on a photo: arrows, circles, and text to call out a specific issue
Tagging by room, location, or project phase. This can simply be done by allowing a photo to be named or a description to be added to it
Search and filter across a project's photos
What we'd like your feedback on
Above shows what we use an external photo app for, it would be GREAT to do this within the task
We use project lens now, we are on it for the ease of use in naming the photos as we are taking them, and easily being able to view/search through the photos whether we are in the field or on the desktop.
technicians, project managers, clients, or all three - ALL THREE
Whether markup and annotation is essential or a nice-to-have. Markup us not essential, but a description of the photo is essential. If I have 5 photos of TVs in 5 classrooms is does me no good when I cannot tell which photo is which room number.