Site Condition Before and After Documentation Form
Document site condition on arrival and departure with time-stamped photos, work notes, and customer sign-off. Use it to create a clear audit trail for jobs, hazards, damage, and follow-up.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Field Service · Facilities Management · Construction · Cleaning Services · Property Management
Overview
This Site Condition Before and After Documentation Form captures the state of a job site at arrival, the work completed, and the condition at departure. It is built for teams that need a simple record of what was present, what changed, and whether the site was left clean and safe. The structure supports time-stamped photos, short condition summaries, hazard notes, materials used, and customer acknowledgment, so the final record is useful both operationally and in disputes.
Use this template for service visits, maintenance work, cleaning jobs, installations, repairs, inspections, and any visit where the site condition could be questioned later. It is especially helpful when multiple people touch the same site, when a customer wants proof of cleanup, or when you need to document damage or incidents immediately after they are observed.
Do not use it as a general intake form or as a replacement for a full incident report when a serious safety event occurs. If the job does not involve site condition, photos, or handoff confirmation, this template adds unnecessary steps. Keep it focused: collect only the fields you will actually use, and use conditional logic so follow-up questions appear only when damage, incidents, or changes are reported.
Standards & compliance context
- Use clear consent language for photo and notes collection when images may include people, private property, or other PII.
- Follow data minimization principles by collecting only the contact and site details needed to complete the job and document the visit.
- Make the form accessible with labeled fields, readable contrast, and keyboard-friendly controls to support WCAG 2.1 AA use.
- If the form is used in HR, intake, or accommodation-related settings, include prompts that allow reasonable-accommodation notes without forcing unnecessary disclosure.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Submission Notice and Consent
This section sets expectations for photo use, note-taking, and acknowledgment so the record is collected with clear consent and minimal PII.
- Purpose of this documentation
- I understand that photos and notes collected in this form will be stored with the job record for documentation and audit trail purposes.
- I understand this form should not collect unnecessary PII and should only include information needed for the job.
Job and Site Details
These fields identify the visit and tie the documentation to the correct job, site, and technician without relying on free-text guessing later.
- Job / Work Order Number
- Site Name
- Site Address
-
Customer Contact Name
Optional. Only collect if needed for site access or sign-off.
- Technician Name
- Visit Date
Arrival Condition Documentation
This section captures the starting point, which is the most important reference for proving pre-work condition and any hazards already present.
- Arrival Time
-
Arrival Condition Summary
Briefly describe the condition of the site when you arrived, including any visible pre-existing damage or hazards.
-
Arrival Photos
Upload time-stamped photos showing the site condition on arrival.
- Hazards observed on arrival
Work Performed
This section explains what changed during the visit so the before-and-after record shows the actual work, not just the final result.
- Work Completed
-
Materials or Parts Used
List only what is necessary for the job record.
- Did the work change the site condition?
- Describe the change to site condition
Departure Condition Documentation
These fields confirm the site was left in its final state, including cleanup and safety status, before the team leaves.
- Departure Time
-
Departure Condition Summary
Describe the site condition when leaving, including any remaining issues or areas that need follow-up.
-
Departure Photos
Upload time-stamped photos showing the site condition at departure.
-
Site left clean and safe
Confirm the area was left in a safe and orderly condition to the best of your knowledge.
Damage, Incidents, and Customer Sign-Off
This section records exceptions, follow-up needs, and acknowledgment so disputes and next steps are documented in one place.
- Was any damage, incident, or customer concern observed during the visit?
- Describe the damage, incident, or concern
-
Customer or site representative acknowledgment
Optional sign-off confirming the site condition documentation was reviewed.
- Follow-up required
- Follow-up notes
How to use this template
- 1. Set up the form with required fields for job and site details, then keep photo, notes, and sign-off fields optional unless your process truly needs them.
- 2. Assign the form to the technician or site lead before arrival so they can record the starting condition, hazards, and time-stamped photos immediately on site.
- 3. Capture the work performed section as the job progresses, including materials used and any changes made to the site or equipment.
- 4. Complete the departure section before leaving by documenting the final condition, cleanup status, and after photos that match the arrival view where possible.
- 5. If damage, incidents, or customer concerns are observed, use the follow-up fields to record details, request acknowledgment, and route the submission to the right reviewer.
- 6. Review submissions after the visit to confirm the record is complete, then trigger any follow-up tasks, claims, or customer communications needed.
Best practices
- Take arrival photos before any tools are unpacked or work begins so the starting condition is unambiguous.
- Use the same angles for before and after photos whenever possible so changes are easy to compare.
- Mark required versus optional fields clearly and avoid forcing every field to be completed on every job.
- Use conditional logic to show damage and incident questions only when something actually happened.
- Keep condition summaries short and factual, focusing on visible facts rather than opinions or blame.
- Record the departure time after cleanup is complete and before the technician leaves the site.
- If customer acknowledgment is needed, capture it at the end of the visit while the site is still fresh in memory.
- Collect only the minimum PII needed for the job and explain how photos and notes will be used.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template records what a site looked like before work started and after work finished, with time-stamped photos, notes, and sign-off. It is useful when you need proof of site condition, a record of hazards, or a clear handoff to a customer. The form also helps document any damage, incidents, or follow-up items in one place.
When should this form be completed?
Complete it at the start and end of every visit where site condition matters, such as service calls, installations, repairs, inspections, or cleanup-sensitive work. The arrival section should be filled out before work begins, and the departure section should be completed before leaving the site. If conditions change during the job, note those changes in the work section rather than waiting until the end.
Who should fill out and sign this form?
The technician, field worker, or site lead should complete the form because they are closest to the actual conditions. A customer contact or site representative should review the departure summary and sign off when a handoff is needed. If your process includes a supervisor review, they can use the record as an audit trail after submission.
Does this form have a compliance angle?
Yes, it supports documentation practices tied to safety, incident reporting, and customer accountability. If you collect names, contact details, or photos that may include people or private spaces, use clear consent language and collect only what you need under data minimization principles. For public-facing forms, make sure the layout is accessible and the fields are labeled clearly for WCAG 2.1 AA use.
What are the most common mistakes when using this form?
Common mistakes include skipping the arrival photos, writing vague condition summaries, and forgetting to note hazards or changes made during the job. Another frequent issue is using free-text fields for details that should be structured, such as dates, times, or yes/no acknowledgments. Teams also miss the chance to document what happens after submission, which can leave the record incomplete.
Can I customize this template for different job types?
Yes, and you should tailor the fields to the work you actually perform. For example, a cleaning crew may emphasize cleanliness and debris removal, while a maintenance team may focus on repairs, access issues, and equipment condition. Use conditional logic to show only the fields that apply so the form stays short and easy to complete.
How does this compare with ad-hoc photo messages or email updates?
Ad-hoc messages are easy to lose, hard to compare, and rarely capture the same details every time. This template standardizes the record so each job includes the same core evidence: arrival condition, work performed, departure condition, and sign-off. That makes it easier to review disputes, track recurring issues, and keep a consistent audit trail.
What integrations are useful with this form?
This form works well with photo uploads, job scheduling, customer records, and ticketing or work-order systems. You can also route submissions to a shared folder, a supervisor review queue, or a follow-up task list when damage or incidents are flagged. If you use automation, keep the workflow simple so the submission still feels quick in the field.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
Frontline workers observe critical issues that never reach operational systems. See how AI-powered media capture in forms and inspections closes that gap.
-
MangoApps launches centralized task management for frontline workers, streamlining workflows, compliance, and execution across locations.
-
Discover how manual performance review processes drain HR productivity, introduce payroll errors, and stall talent strategy — and what automated systems fix.
-
Employee Self-Service Hubs streamline HR, boost engagement, and empower employees with 24/7 access to essential services.
Ready to use this template?
Get started with MangoApps and use Site Condition Before and After Documentation Form with your team — pricing built for small business.
