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