These are examples of institutional guidance, not universal legal requirements. Every project should follow its contract documents, inspection plan, owner requirements, professional responsibilities, and applicable regulations.<\/p>\n\n\n\n
What Work Commonly Needs Before-Cover Photos<\/h2>\n\n\n\n\n- Framing, blocking, backing, and structural connections before wall or ceiling finishes.<\/li>\n\n\n\n
- Mechanical, electrical, plumbing, and low-voltage rough-in before drywall, ceilings, or insulation.<\/li>\n\n\n\n
- Waterproofing, flashing, membranes, drainage layers, and penetrations before finishes or backfill.<\/li>\n\n\n\n
- Firestopping, fire-rated assemblies, sleeves, and penetrations before enclosure.<\/li>\n\n\n\n
- Reinforcement, embeds, anchor systems, conduits, and form conditions before concrete placement.<\/li>\n\n\n\n
- Underground utilities, joints, bedding, crossings, and service connections before backfill.<\/li>\n\n\n\n
- Insulation, air barriers, and concealed envelope transitions before cladding or interior finishes.<\/li>\n\n\n\n
- Inspection points, corrective work, and approved changes that will no longer remain visible.<\/li>\n<\/ul>\n\n\n\n
The exact list must come from the project. A checklist should reflect the construction sequence, specifications, inspection plan, risk profile, and owner requirements rather than copying a generic list without review.<\/p>\n\n\n\n
Use the Wide-Medium-Detail Method<\/h2>\n\n\n\nWide: establish the area<\/h3>\n\n\n\n
Show enough of the room, elevation, trench, bay, grid, or surrounding work for another person to identify the general location. Include fixed references when practical.<\/p>\n\n\n\n
Medium: show the relationship<\/h3>\n\n\n\n
Move closer while retaining the connection between the subject and nearby structure, equipment, openings, dimensions, or reference points. This view explains how the detail fits into the work.<\/p>\n\n\n\n
Detail: preserve the condition<\/h3>\n\n\n\n
Capture the connection, label, penetration, fastener pattern, joint, routing, repair, or other condition that motivated the record. Confirm focus, lighting, and readability before leaving.<\/p>\n\n\n\n
A detail image without context can be impossible to place later. A wide image without detail may not show the condition clearly. The three views work as a set.<\/p>\n\n\n\n
Add the Six Pieces of Record Context<\/h2>\n\n\n\n\n- When:<\/strong> capture date and time, project phase, and whether the image was taken before an inspection, correction, pour, enclosure, or backfill.<\/li>\n\n\n\n
- Where:<\/strong> project, building, level, room, grid, elevation, station, asset, map position, Plan Sheet, or defined area.<\/li>\n\n\n\n
- What:<\/strong> the visible work and the specific condition the record is intended to preserve.<\/li>\n\n\n\n
- Who:<\/strong> captured-by information and, when the project requires it, the responsible trade, reviewer, or inspector.<\/li>\n\n\n\n
- Why:<\/strong> the purpose of the record, such as progress, inspection support, coordination, a correction, owner documentation, or future maintenance context.<\/li>\n\n\n\n
- Link:<\/strong> inspection request, drawing, detail, specification, report, issue, field note, or earlier\/later record when applicable.<\/li>\n<\/ul>\n\n\n\n
A Before-Cover Workflow Teams Can Repeat<\/h2>\n\n\n\n1. Identify concealment points in the look-ahead plan<\/h3>\n\n\n\n
Review upcoming work for moments when visibility will be lost. Assign capture responsibility and define any required review before the covering activity begins.<\/p>\n\n\n\n
2. Confirm the project-specific requirement<\/h3>\n\n\n\n
Check the contract, specifications, owner standards, inspection plan, and applicable authority requirements. A photo workflow should support those processes, not replace them.<\/p>\n\n\n\n
3. Capture wide, medium, and detail views<\/h3>\n\n\n\n
Use consistent viewpoints and fixed references when practical. Capture labels, dimensions, or markers only when they are part of the approved project method.<\/p>\n\n\n\n
4. Attach context before leaving the area<\/h3>\n\n\n\n
Connect the set to its project, location, plan, area, activity, date, responsible person, and purpose while the information is still known.<\/p>\n\n\n\n
5. Verify coverage and readability<\/h3>\n\n\n\n
Review the photos at usable size. Check focus, glare, obstruction, location, sequence, and whether the set actually answers the intended project question.<\/p>\n\n\n\n
6. Complete required review before covering<\/h3>\n\n\n\n
Route the record through the project’s required inspection, approval, or quality process. Do not assume that uploading a photo authorizes the work to be covered.<\/p>\n\n\n\n
7. Preserve the set for retrieval<\/h3>\n\n\n\n
Store the images with the project record and keep their relationships intact. A future user should be able to retrieve the location and understand what became concealed.<\/p>\n\n\n\n
What These Photos Can and Cannot Establish<\/h2>\n\n\n\n
A clear, contextual photo set can document visible conditions at a stated time and place. It can help teams answer future coordination, maintenance, repair, inspection, and closeout questions.<\/p>\n\n\n\n
It cannot automatically prove code compliance, installation quality, contractual acceptance, causation, responsibility, or legal admissibility. Those conclusions may require inspections, measurements, testing, professional judgment, chain-of-custody controls, and project-specific documentation.<\/p>\n\n\n\n
How Filio Can Support the Record<\/h2>\n\n\n\n
Based on the approved product source, Filio organizes field records by project, connects them to Plan Sheet context, and can retain capture-time and location context. Teams can organize records with tags and contextual fields, review them in map and timeline views, find them using metadata and tags, and assemble field records into reports.<\/p>\n\n\n\n![\"Filio](\"https:\/\/blog.filio.io\/wp-content\/uploads\/sites\/6\/2026\/09\/V2-LOCATION-HIERARCHY-REVIEW-1.png\")
<\/figure>\n\n\n\nThat workflow helps preserve the location and history of before-cover evidence. It does not change the project’s inspection, approval, safety, contractual, or regulatory responsibilities.<\/p>\n\n\n\n
For broader category guidance, see construction photo documentation<\/a>. For long-term retrieval, see searchable construction project records<\/a>.<\/p>\n\n\n\n![\"Filio](\"https:\/\/blog.filio.io\/wp-content\/uploads\/sites\/6\/2026\/09\/V5-TIMELINE-HIERARCHY-REVIEW-1.png\")
<\/figure>\n\n\n\n![\"Filio](\"https:\/\/blog.filio.io\/wp-content\/uploads\/sites\/6\/2026\/09\/V6-REPORT-HIERARCHY-REVIEW-1.png\")
<\/figure>\n\n\n\nFrequently Asked Questions<\/h2>\n\n\n\nWhat should be photographed before drywall?<\/h3>\n\n\n\n
Common subjects include framing, blocking, backing, mechanical\/electrical\/plumbing and low-voltage rough-in, insulation transitions, firestopping, penetrations, and any approved changes that will become inaccessible. Use the project-specific inspection and documentation plan.<\/p>\n\n\n\n
How many photos are enough?<\/h3>\n\n\n\n
There is no universal number. Capture enough wide, medium, and detail views to identify the location, explain relationships, and show the required condition without ambiguity.<\/p>\n\n\n\n
Should measurements appear in concealed-work photos?<\/h3>\n\n\n\n
Only when the project method requires them and they can be captured clearly. A photo of a tape measure is not automatically a verified measurement record.<\/p>\n\n\n\n
Do pre-cover photos replace an inspection?<\/h3>\n\n\n\n
No. They may support an inspection or record, but required inspections and approvals must still follow the project’s governing process.<\/p>\n\n\n\n
How should concealed-work photos be organized?<\/h3>\n\n\n\n
Connect them to the project, exact location, plan or area, date, subject, responsible context, and related inspection or report. Keep wide, medium, and detail images linked as one record set.<\/p>\n\n\n\n
Document Before Visibility Is Lost<\/h2>\n\n\n\n
The best time to document concealed work is not after a question appears. It is during the short window when the work is visible, the people involved still know the context, and the team can verify that the record is complete.<\/p>\n\n\n\n
The exact list must come from the project. A checklist should reflect the construction sequence, specifications, inspection plan, risk profile, and owner requirements rather than copying a generic list without review.<\/p>\n\n\n\n
Use the Wide-Medium-Detail Method<\/h2>\n\n\n\nWide: establish the area<\/h3>\n\n\n\n
Show enough of the room, elevation, trench, bay, grid, or surrounding work for another person to identify the general location. Include fixed references when practical.<\/p>\n\n\n\n
Medium: show the relationship<\/h3>\n\n\n\n
Move closer while retaining the connection between the subject and nearby structure, equipment, openings, dimensions, or reference points. This view explains how the detail fits into the work.<\/p>\n\n\n\n
Detail: preserve the condition<\/h3>\n\n\n\n
Capture the connection, label, penetration, fastener pattern, joint, routing, repair, or other condition that motivated the record. Confirm focus, lighting, and readability before leaving.<\/p>\n\n\n\n
A detail image without context can be impossible to place later. A wide image without detail may not show the condition clearly. The three views work as a set.<\/p>\n\n\n\n
Add the Six Pieces of Record Context<\/h2>\n\n\n\n\n- When:<\/strong> capture date and time, project phase, and whether the image was taken before an inspection, correction, pour, enclosure, or backfill.<\/li>\n\n\n\n
- Where:<\/strong> project, building, level, room, grid, elevation, station, asset, map position, Plan Sheet, or defined area.<\/li>\n\n\n\n
- What:<\/strong> the visible work and the specific condition the record is intended to preserve.<\/li>\n\n\n\n
- Who:<\/strong> captured-by information and, when the project requires it, the responsible trade, reviewer, or inspector.<\/li>\n\n\n\n
- Why:<\/strong> the purpose of the record, such as progress, inspection support, coordination, a correction, owner documentation, or future maintenance context.<\/li>\n\n\n\n
- Link:<\/strong> inspection request, drawing, detail, specification, report, issue, field note, or earlier\/later record when applicable.<\/li>\n<\/ul>\n\n\n\n
A Before-Cover Workflow Teams Can Repeat<\/h2>\n\n\n\n1. Identify concealment points in the look-ahead plan<\/h3>\n\n\n\n
Review upcoming work for moments when visibility will be lost. Assign capture responsibility and define any required review before the covering activity begins.<\/p>\n\n\n\n
2. Confirm the project-specific requirement<\/h3>\n\n\n\n
Check the contract, specifications, owner standards, inspection plan, and applicable authority requirements. A photo workflow should support those processes, not replace them.<\/p>\n\n\n\n
3. Capture wide, medium, and detail views<\/h3>\n\n\n\n
Use consistent viewpoints and fixed references when practical. Capture labels, dimensions, or markers only when they are part of the approved project method.<\/p>\n\n\n\n
4. Attach context before leaving the area<\/h3>\n\n\n\n
Connect the set to its project, location, plan, area, activity, date, responsible person, and purpose while the information is still known.<\/p>\n\n\n\n
5. Verify coverage and readability<\/h3>\n\n\n\n
Review the photos at usable size. Check focus, glare, obstruction, location, sequence, and whether the set actually answers the intended project question.<\/p>\n\n\n\n
6. Complete required review before covering<\/h3>\n\n\n\n
Route the record through the project’s required inspection, approval, or quality process. Do not assume that uploading a photo authorizes the work to be covered.<\/p>\n\n\n\n
7. Preserve the set for retrieval<\/h3>\n\n\n\n
Store the images with the project record and keep their relationships intact. A future user should be able to retrieve the location and understand what became concealed.<\/p>\n\n\n\n
What These Photos Can and Cannot Establish<\/h2>\n\n\n\n
A clear, contextual photo set can document visible conditions at a stated time and place. It can help teams answer future coordination, maintenance, repair, inspection, and closeout questions.<\/p>\n\n\n\n
It cannot automatically prove code compliance, installation quality, contractual acceptance, causation, responsibility, or legal admissibility. Those conclusions may require inspections, measurements, testing, professional judgment, chain-of-custody controls, and project-specific documentation.<\/p>\n\n\n\n
How Filio Can Support the Record<\/h2>\n\n\n\n
Based on the approved product source, Filio organizes field records by project, connects them to Plan Sheet context, and can retain capture-time and location context. Teams can organize records with tags and contextual fields, review them in map and timeline views, find them using metadata and tags, and assemble field records into reports.<\/p>\n\n\n\n<\/figure>\n\n\n\nThat workflow helps preserve the location and history of before-cover evidence. It does not change the project’s inspection, approval, safety, contractual, or regulatory responsibilities.<\/p>\n\n\n\n
For broader category guidance, see construction photo documentation<\/a>. For long-term retrieval, see searchable construction project records<\/a>.<\/p>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\nFrequently Asked Questions<\/h2>\n\n\n\nWhat should be photographed before drywall?<\/h3>\n\n\n\n
Common subjects include framing, blocking, backing, mechanical\/electrical\/plumbing and low-voltage rough-in, insulation transitions, firestopping, penetrations, and any approved changes that will become inaccessible. Use the project-specific inspection and documentation plan.<\/p>\n\n\n\n
How many photos are enough?<\/h3>\n\n\n\n
There is no universal number. Capture enough wide, medium, and detail views to identify the location, explain relationships, and show the required condition without ambiguity.<\/p>\n\n\n\n
Should measurements appear in concealed-work photos?<\/h3>\n\n\n\n
Only when the project method requires them and they can be captured clearly. A photo of a tape measure is not automatically a verified measurement record.<\/p>\n\n\n\n
Do pre-cover photos replace an inspection?<\/h3>\n\n\n\n
No. They may support an inspection or record, but required inspections and approvals must still follow the project’s governing process.<\/p>\n\n\n\n
How should concealed-work photos be organized?<\/h3>\n\n\n\n
Connect them to the project, exact location, plan or area, date, subject, responsible context, and related inspection or report. Keep wide, medium, and detail images linked as one record set.<\/p>\n\n\n\n
Document Before Visibility Is Lost<\/h2>\n\n\n\n
The best time to document concealed work is not after a question appears. It is during the short window when the work is visible, the people involved still know the context, and the team can verify that the record is complete.<\/p>\n\n\n\n
A Before-Cover Workflow Teams Can Repeat<\/h2>\n\n\n\n1. Identify concealment points in the look-ahead plan<\/h3>\n\n\n\n
Review upcoming work for moments when visibility will be lost. Assign capture responsibility and define any required review before the covering activity begins.<\/p>\n\n\n\n
2. Confirm the project-specific requirement<\/h3>\n\n\n\n
Check the contract, specifications, owner standards, inspection plan, and applicable authority requirements. A photo workflow should support those processes, not replace them.<\/p>\n\n\n\n
3. Capture wide, medium, and detail views<\/h3>\n\n\n\n
Use consistent viewpoints and fixed references when practical. Capture labels, dimensions, or markers only when they are part of the approved project method.<\/p>\n\n\n\n
4. Attach context before leaving the area<\/h3>\n\n\n\n
Connect the set to its project, location, plan, area, activity, date, responsible person, and purpose while the information is still known.<\/p>\n\n\n\n
5. Verify coverage and readability<\/h3>\n\n\n\n
Review the photos at usable size. Check focus, glare, obstruction, location, sequence, and whether the set actually answers the intended project question.<\/p>\n\n\n\n
6. Complete required review before covering<\/h3>\n\n\n\n
Route the record through the project’s required inspection, approval, or quality process. Do not assume that uploading a photo authorizes the work to be covered.<\/p>\n\n\n\n
7. Preserve the set for retrieval<\/h3>\n\n\n\n
Store the images with the project record and keep their relationships intact. A future user should be able to retrieve the location and understand what became concealed.<\/p>\n\n\n\n
What These Photos Can and Cannot Establish<\/h2>\n\n\n\n
A clear, contextual photo set can document visible conditions at a stated time and place. It can help teams answer future coordination, maintenance, repair, inspection, and closeout questions.<\/p>\n\n\n\n
It cannot automatically prove code compliance, installation quality, contractual acceptance, causation, responsibility, or legal admissibility. Those conclusions may require inspections, measurements, testing, professional judgment, chain-of-custody controls, and project-specific documentation.<\/p>\n\n\n\n
How Filio Can Support the Record<\/h2>\n\n\n\n
Based on the approved product source, Filio organizes field records by project, connects them to Plan Sheet context, and can retain capture-time and location context. Teams can organize records with tags and contextual fields, review them in map and timeline views, find them using metadata and tags, and assemble field records into reports.<\/p>\n\n\n\n That workflow helps preserve the location and history of before-cover evidence. It does not change the project’s inspection, approval, safety, contractual, or regulatory responsibilities.<\/p>\n\n\n\n For broader category guidance, see construction photo documentation<\/a>. For long-term retrieval, see searchable construction project records<\/a>.<\/p>\n\n\n\n Common subjects include framing, blocking, backing, mechanical\/electrical\/plumbing and low-voltage rough-in, insulation transitions, firestopping, penetrations, and any approved changes that will become inaccessible. Use the project-specific inspection and documentation plan.<\/p>\n\n\n\n There is no universal number. Capture enough wide, medium, and detail views to identify the location, explain relationships, and show the required condition without ambiguity.<\/p>\n\n\n\n Only when the project method requires them and they can be captured clearly. A photo of a tape measure is not automatically a verified measurement record.<\/p>\n\n\n\n No. They may support an inspection or record, but required inspections and approvals must still follow the project’s governing process.<\/p>\n\n\n\n Connect them to the project, exact location, plan or area, date, subject, responsible context, and related inspection or report. Keep wide, medium, and detail images linked as one record set.<\/p>\n\n\n\n The best time to document concealed work is not after a question appears. It is during the short window when the work is visible, the people involved still know the context, and the team can verify that the record is complete.<\/p>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\nFrequently Asked Questions<\/h2>\n\n\n\n
What should be photographed before drywall?<\/h3>\n\n\n\n
How many photos are enough?<\/h3>\n\n\n\n
Should measurements appear in concealed-work photos?<\/h3>\n\n\n\n
Do pre-cover photos replace an inspection?<\/h3>\n\n\n\n
How should concealed-work photos be organized?<\/h3>\n\n\n\n
Document Before Visibility Is Lost<\/h2>\n\n\n\n