What Your Technicians Should Capture for Social Media

The camera roll is not the content system.

A technician can finish a good job and still leave the office with almost nothing usable if the photos are random, the notes are thin, or the privacy status is unclear.

That is why the field team needs a simple capture list. Not a marketing plan. Not a copywriting assignment. Just enough structure to save the job story before everyone moves on.

The 5-shot job story is the cleanest version:

1. what the homeowner noticed
2. what the crew found
3. one process photo
4. the finished result
5. whether the material can be used publicly

That is enough for the office to turn one job into a caption, a carousel, a short video, or a proof post later.

LinkedIn Page admins can post text, images, videos, and documents. Instagram supports carousels with up to 10 photos or videos, and Instagram help says you can add a caption before sharing a post. Facebook Pages can share photos, videos, and links. The field team does not need to know all of that. They just need to capture enough real material so the office can use the right format later.

The five shots

1. What the homeowner noticed

Start with the symptom or concern.

Examples:

• water near a basement wall after rain
• one room that feels off compared with the rest of the house
• a roof area that needs inspection after a storm
• a project area that is ready for the next phase

This shot might be a wide photo, a close-up, or simply the first note the tech writes on the tablet. The point is to save the problem before the details blur.

2. What the crew found

This is the first proof shot.

It should show the condition, detail, or inspection result that matters most. That might be a visible defect, a process note, or a detail the homeowner would not know to photograph.

Examples:

• a blocked drain point
• a flashing detail
• an airflow or filter issue
• a protected floor or prep area

If the crew is not sure the shot is safe to publish, the note should say so.

3. One process photo

The best posts are rarely only before and after.

A process photo shows how the team worked. It can be a setup shot, a close-up of the repair, a walkthrough photo, or a cleanup step. It helps the office write a caption that explains the judgment behind the result.

4. The finished result

The finished result is the proof most people want to see.

It should show what changed after the work, but it should not do all the work by itself. The office still needs the problem, the finding, and the sharing note.

5. Approved to share

This is the part technicians often skip.

If the photo includes private interior details, names, screens, family items, license plates, or anything else that could identify the customer, the office needs to know that before the post is written.

The note can be as simple as:

Approved to share: needs review

That is better than guessing.

What to write in the note field

A good note is short and factual.

Use the same language a homeowner would use when they tell the story back to someone else.

Example:

Homeowner noticed water near the basement wall after rain. Crew found a

visible condition near the affected area. One process photo shows the repair

in progress. Finished result is documented. Approval to share still needs review.

That note is not a finished caption. It is the raw material the office can use to write one later.

What to capture by trade

Plumbers

• the leak or clog the homeowner noticed
• the inspection detail that mattered
• one process photo from the repair
• the finished cleanup or result
• the sharing note

HVAC Companies

• the comfort problem the homeowner reported
• the airflow, filter, or thermostat detail
• one process shot from the service visit
• the finished condition
• the sharing note

Roofers

• the storm or leak symptom
• the flashing or roof detail
• one process or inspection shot
• the finished condition
• the sharing note

Contractors

• the room or project stage the homeowner cared about
• the protection, progress, or material decision
• one process or walkthrough shot
• the finished result
• the sharing note

The trade changes, but the capture logic stays the same.

What not to capture

Do not capture private paperwork, screens, addresses, family photos, or anything that could expose the customer without review.

Do not rely on memory.

Do not write a vague note like "fixed issue" and expect the office to fill in the rest.

Do not assume every image is public.

Do not ask the tech to invent a caption.

The capture job is to save facts, not to market the company from the truck.

How the office turns it into posts

Once the tech has the 5-shot job story, the office can turn it into:

• a Facebook photo post
• an Instagram carousel
• a short Reel or video
• a LinkedIn text or document post
• a proof block on the website later

That is why the field capture matters. One good note can become several useful posts if the office has enough real detail to work with.

Bad content starts on the truck

Most of the work that ends up looking like a content problem is actually a capture problem one step upstream. The office cannot write a useful caption from a single after-photo and a one-word note. It can write almost anything from a symptom photo, a finding shot, a process shot, the result, and a clear approved to share publicly.

The five shots are not a content task asked of the field team. They are five small acts of saving the story before it disappears — and the sharing note at the end is the one that decides whether anyone outside the office ever sees the job at all.