Maintenance request photo upload workflow for properties

Maintenance request photo upload workflow for properties

SiteOps is a facility maintenance request platform for property managers. It helps small-to-mid property managers collect maintenance requests, organize request details, and track maintenance work through a simple status workflow.

Photo support can help property teams understand a maintenance issue more clearly. When a requester includes a photo, the property manager can review the image along with the request details.

How photo upload fits the request workflow

The SiteOps tenant request form supports an optional photo file. This means a requester can add a photo when it helps explain the maintenance issue.

The photo is optional. A requester can still submit the required request details without adding a photo.

What the tenant request form collects

The SiteOps tenant request form requires:

. category

. unit or room number

. description

. name

. email

These fields help property managers understand what the issue is, where it is located, who submitted it, and how the requester can receive updates.

Why photos can help property teams

A maintenance request photo can give property teams more context. For example, a photo may help show the condition of an item, the area where the issue is happening, or the visible details connected to the request.

Photos should be described as helpful context, not as a guarantee that the issue will be diagnosed automatically or repaired faster.

How a request starts

When a maintenance request is created, SiteOps stores the request with the status new.

SiteOps maintenance request statuses are:

. new

. in_progress

. done

For customer-facing language, these can be explained as:

. new

. in progress

. done

A new request has been created. An in progress request is being worked on. A done request has been completed or marked finished in the workflow.

Owner and requester emails

After a maintenance request is created, SiteOps sends a new-request email to the owner.

SiteOps also sends a confirmation email to the requester. This helps the requester know the maintenance request was received.

When a request status changes and a requester email exists, SiteOps sends a status update email.

Public status lookup

SiteOps has a public status page that lets a requester look up a request by confirmation code and unit number.

The status page shows request details and sorted request history. This helps the requester check the request without needing access to the owner dashboard.

Request history

SiteOps keeps request history connected to the maintenance workflow. When a request status changes, the history can show the status change and any note connected to the update.

This helps property managers and requesters understand how the request has moved through the workflow.

What SiteOps should not promise

SiteOps should not be described as guaranteeing repair speed, emergency dispatch, tenant satisfaction, automatic diagnosis, or automatic maintenance completion.

The safe way to describe SiteOps is as a maintenance request management platform that helps property managers collect requests, support optional photos, track statuses, send notifications, and show request history.

Final summary

SiteOps helps property managers collect maintenance requests with required request details and optional photo support. It helps keep request details, status updates, requester emails, owner notifications, and public status lookup connected in one maintenance request workflow.