Job Photos: Proof, Moderation, and Your Public Gallery (Trust That Survives Disputes)

Grunlo is field service operations software for landscaping, lawn care, and similar route-based businesses—this article is for owners who want photos to do three jobs at once: quality control, dispute prevention, and credible marketing.

Photos are cheap to capture and expensive to argue without. The difference is not “more pictures”—it is standards: what you capture, where it lives, and how it becomes public.

The two different jobs: job truth vs public marketing

Job truth is what your team needs to execute and defend work: access issues, before/after, debris, gate state, irrigation surprises—whatever your trade actually argues about.

Public marketing is what a stranger should infer in five seconds: competence, cleanliness, consistency.

Those are related, but not identical. Your system should not treat every job photo like a billboard.

What belongs on the job record (minimum viable proof)

A practical owner standard for common residential route work:

1. Before — enough context that “before” is not ambiguous (wide shot + problem close-up when relevant).
2. During — only when it reduces later disputes (damage risk, hidden conditions, access constraints).
3. After — the customer’s definition of “done,” not only your favorite angle.

Grunlo stores tech-uploaded photos with the job for office visibility, as described in Creating & managing jobs. Field workflow context lives in Field Tech mobile app.

If your standard is unclear, crews will optimize for speed—and you will buy “proof” with rework.

Moderation: the brand gate (and why backlog is a liability)

When Attachment moderation is enabled on your plan, uploads can go through a pending queue before public use. Moderators need the attachments.moderate permission. The full workflow—approve/reject, then publish—is documented in Attachment moderation.

Help is explicit about what rejection does on the job record—use that power carefully with training, not as punishment theater.

The public outcome is described in Public landing page: approved photos can be published to the gallery, with a 12-photo cap.

If moderation is always behind, you train the org that marketing does not matter—or you tempt people to bypass standards.

Customer-uploaded photos are still evidence

Customers can upload photos through the portal in some workflows (problem areas, access instructions)—see Customer portal overview. Those uploads can also enter moderation when enabled, per Attachment moderation.

Treat customer uploads as signal, not annoyance: they often prevent the classic failure mode—“nobody told us the gate code changed.”

Connect photos to money and scope (where fights actually start)

Photos do not replace estimates—but they make change orders and invoice conversations calmer when paired with clear commercial language:

• Change orders and scope creep
• Estimates that close

Connect photos to growth without turning the crew into influencers

Your landing page story is bigger than photos alone—see Public landing page and speed-to-lead. Still, a tight gallery is one of the fastest trust upgrades you can ship if the images are real work, well lit, and consistent.

How Grunlo helps

Grunlo is built so photos can live as job evidence first and become published marketing only after a deliberate step—so you are not accidentally publishing a customer’s driveway license plate or a messy corner you would not want repeated.

Key takeaways

• Separate job proof from public marketing—same source material, different bar.
• Write a minimum photo standard—otherwise “more photos” becomes more confusion.
• Moderation is a weekly habit—badge counts exist to make backlog visible.
• Photos strengthen estimates and invoices—they do not replace clear words.

Related reading

• Blog: What to put on your field tech’s phone — capture discipline starts in the field
• Blog: Reviews and referrals after the job — proof and reputation reinforce each other
• Help: Creating & managing jobs