Before-and-After Job Photos: Review the Exact Copies Before Posting

The short answer

Keep the original job evidence in its controlled record. Create separate public copies, review their exported contents and labels, and ask about the exact versions, caption and destination before posting. Record the response and match the approved package to what actually goes live. Under this editorial protocol, a pending answer means hold.

A customer photo request for an estimate is not marketing authorization. Internal job evidence, customer delivery and public promotion serve different purposes. This is an operational record for selected copies, not a legal release, compliance decision or guarantee that the respondent can authorize every person or property shown. Rights of others, minors, tenants and regional obligations need separate review; if uncertain, omit the image and seek appropriate advice.

Review the exported copy, not just the original

1. Choose the smallest useful set. Identify the originals and assign each proposed public copy an ID and version. Preserve the originals in the authorized job record.
2. Inspect visible identifiers. Look for unrelated faces, house numbers, mail, vehicle plates, reflections and access details. A crop can leave identifying context; obscuring an area does not promise anonymity.
3. Inspect the outgoing package. Check filename, caption, location, time and any displayed photographer or project detail. Review the actual exported file after edits, not just an editing preview.
4. Define the exact use. Record destination, caption and context. Website use does not silently include ads, social posts or future revised images.
5. Record a response and its limits. Keep approved, declined and pending distinct. If the package changes, review the new version before reuse.

Jobber's notes and attachments guide describes internal notes by default and deliberately selected email attachments that can be shared. Keep job evidence controlled and customer delivery intentional. An editable note is not an immutable authorization trail, and an attachment sent to a customer does not establish public marketing approval.

Know whether you are sharing a snapshot or a live feed

CompanyCam's sharing guide distinguishes handpicked Galleries from Timelines. People holding a Gallery link can view and download without logging in, so forwarding remains possible. Timeline links can be disabled; users cannot disable Gallery links themselves and need Support. A narrowly selected set is not an authenticated private approval portal.

The Gallery and Timeline explanation describes a Gallery as a snapshot that does not acquire later photos, while a Timeline adds photos automatically. Photographer, time, location or other details may be visible. Review what the recipient actually sees before choosing a channel for the proposed copies. A live project feed can exceed a selected-copy request even when the original selection was appropriate.

CompanyCam Showcases are a separate public publishing surface available on select plans. Selected photos, draft creation, a publish toggle and unpublishing are distinct controls; later project photos are hidden by default. A draft or selected photo is not permission to publish. Match that separate public action to the recorded package rather than assuming a share link and Showcase have the same scope.

Copy the selected-copy authorization record

Use private references rather than reproducing customer details in a public log. A spreadsheet or paper sheet works if it keeps versions and decisions understandable. Results stay blank until checked.

An original request draft, not sent

Hello [name], we would like to use versions [IDs] with caption [caption] on [specific destination]. Please tell us whether you are comfortable with that exact use, prefer changes, or do not want posting. We will keep the request pending until you respond. Contact [person/channel] about this request.

Show the exact reviewed copies through an appropriate channel alongside the request. This wording is not a legal release and does not settle another person's rights. Do not treat silence, an estimate request or a previous photo delivery as an affirmative answer.

Two fictional examples to check the boundary

Cleaning photos with mail and a house number

A fictional before-and-after pair contains mail on a counter and a visible house number. The office creates revised public copies, checks the exported files and prepares a caption without a location reference. It records a proposed website-only use. If that exact package is approved, social use still remains pending until separately reviewed and answered. No approval, editing result or customer response was tested for this example.

A repair photo added after the selection

A fictional repair team selects two images, then later adds a defect photo to the project. A selected Gallery snapshot and a live Timeline have different documented update behavior. The reviewer must check that the sharing surface matches the request and does not expose later work beyond it. This is a hypothetical scope risk, not an observed CompanyCam failure.

Log publication and handle change requests

When a change or removal request arrives, pause future reuse while the responsible person reviews it. Locate the destinations in the log, remove or change the copies you control, and verify the result. Keep unresolved destinations visible. Do not promise to erase downloads, screenshots, caches or reposts that you do not control.

The CompanyCam and Jobber routing protocol covers where job photos land. The cleaning proof-of-service guide covers software evaluation. This selected-copy record answers a different question: what exact public package has been reviewed and what remains pending. A solo operator can keep that boundary with a small controlled record, without another product purchase.