You need to find a relevant job example while talking to a builder. Sort job photos by job type so you can find them. Keep each project’s originals, records, and public selections together. Start with recent work you can identify instead of sorting your entire camera roll at once.
Use the filing method below as a starting point. Use it in the storage tool your company already controls. It does not require a new subscription or assume that an app offers these fields.
Use the camera roll as an inbox
Use the camera roll as the capture inbox. Move selected photos into your project files, or add an index pointing to them. Record the scope and permission there. Do not use a date-sorted camera roll as your only project record.
For a starting batch, choose one recent project you expect to discuss again. Gather its images, check their origin, and label the stages. Finish that folder before choosing the next project.
Do not spend your first session renaming every file. Define a structure, test whether you can retrieve a useful example, then extend it. Leave unidentified old images in an unsorted area until you can confirm them.
If a photograph’s job is uncertain, keep that uncertainty visible. Do not infer the address, client, installer, or date from a familiar-looking room. Keep a good-looking photo out of the portfolio if you cannot confirm whose work it shows.
Organize job photos by job type, then project
Choose categories that match the scopes you want next. For a mixed trade business, those might include additions, finish installation, repairs, and occupied-home remodels. Use those as examples, not required category names.
Within each job type, give every project an internal ID that stays the same. Keep the client name and exact address in a private register if your records need them. Use a neutral public project label separately.
Try this layout:
Scroll to read all columns.
| Layer | Purpose | Suggested contents |
|---|---|---|
| Job type | Find comparable work | Scope categories matching your business |
| Project | Keep a job’s evidence together | Stable identifier and project index |
| Originals | Preserve the capture record | Unedited photos and creator information |
| Records | Explain and support the images | Scope, relevant documents, permissions |
| Public selections | Prepare permitted sharing | Reviewed images and approved captions |
If a job fits several categories, keep one master project record. Add an index reference or tag for the other category where your tool supports it. Avoid separate versions with conflicting captions or permissions.
Give each project a short index
Keep a short index with the files. Record the job type, your company’s role, completed scope, photo stages, and supporting records. Add the permission status and the location of any reference-contact consent.
Write the index so you can use the pictures without asking the photographer what they show.
What did your crew perform? Which work belongs to another company? Which views are public? What remains unfinished?
Keep a caption table with the file identifier, visible subject, capture stage, and supporting record. Add the capture date from confirmed information. Do not replace it with the date you organized the folder.
If the current crew differs from the crew in an older project, explain that privately when preparing an introduction. The project history and today’s staffing are separate questions. Do not let an old photo imply that a specific crew member will work on the next job.
Use filenames that support the index
Choose one naming pattern and keep it simple. A proposed pattern is project-id_area_stage_sequence. Use a date only when confirmed. Store the full meaning in the index rather than forcing every fact into the filename.
For example, project-id_kitchen_before-cover_detail is a placeholder pattern. Replace it with your own identifiers. Do not use a real client’s address as the public filename.
The Library of Congress photo-archiving guidance recommends descriptive filenames and a written description of the folder structure.
Keep original filenames in your source record if you rename working copies. Record which original each public copy came from. Make that link clear enough to follow without guessing.
Put approval in a filename only when the actual approval record supports it. “Rough-in” and “approved rough-in” carry different claims. Use a neutral stage label until you confirm the status.
Keep public selections separate
Create the public folder only after checking the image, caption, rights, and client permission. Copy selected material into it. Keep documents, precise location, and private contact details in the project record.
The Copyright Office explains that owning a copy of a photograph does not resolve its copyright ownership. Record who took the photo and what gives you the right to publish it. Keep that evidence with the project.
Review metadata during the public-copy step. Apple’s photo-sharing guidance identifies location, capture information, device information, and captions as metadata that can accompany sharing. Check the exported file and the site or app you share it through.
Use a public filename and caption that do not reveal the client’s identity. Do not share the master folder merely because one image is cleared. See the photo privacy workflow for the release check.
Use albums without confusing them with your archive
Use albums to find photos. Apple’s iPhone album guidance describes named albums and folders for organizing them. It also says deleting an album leaves its photos in the library and other albums.
If you use albums, name them by job type or project. Check that you can find a job that way. Keep a separate index for rights, captions, and supporting records. Do not assume an album carries all the information your private project file needs.
Apple’s download guidance explains how to export unmodified originals. Its deletion guidance says deleting an iCloud Photos image on one device also removes it from other devices using the same account.
Before changing a shared or synchronized library, check the service’s current behavior. Keep an independent copy of records you need to retain. Verify that a sample file opens from that copy before removing any local material.
Check that you can recover the file from your sorted view. Test that separately from whether the thumbnail appears on your phone.
Set aside ten minutes each week for filing
Start with a ten-minute filing window. Some weeks will take longer. The first setup and a backlog will need their own time. Aim to keep new work from adding to that backlog.
Use this suggested order:
- Identify the week’s images by project.
- Move or index them into the right project record.
- Label context, before-cover, correction, and finished stages.
- Add missing scope and creator notes.
- Review one useful public selection and its caption.
- Test one retrieval from the job-type index.
When time runs out, leave a specific next task. “Confirm project for these files” is useful. “Sort photos later” returns you to the same pile.
Ask the person who captured an unclear set while the job is recent. Keep unanswered questions out of the public selection. Do not guess who did the work just to finish the week’s filing.
Test the folder with a real inquiry
Choose a scope a builder might ask about. Find a similar project, the relevant photos, and your role description without relying on memory. Check whether the public selection is permitted and current.
If you cannot find the job, check the index before adding more folders. A category may be too broad, an identifier may be missing, or the selected images may lack captions. Fix what stopped you finding the job.
Use the portfolio guide to assemble the public project card. Use the job-photo guide when the missing step is capture.
Where Cercha fits
The Cercha app includes named portfolio projects with photos, Gallery work captions, and Messages. Select reviewed images from your organized records for the professional presentation. Keep originals, permissions, and detailed evidence in your private project archive.