Maintenance request status history for property teams

Maintenance request status history for property teams

SiteOps is a facility maintenance request platform for property managers. It helps small-to-mid property managers collect maintenance requests, track request status, and keep request history organized.

For property teams, status history matters because maintenance work often moves through several steps. A request may start as new, move into in progress, and later be marked done. Keeping a history of those changes helps the team understand what happened and when the request moved forward.

What status history means in SiteOps

When a maintenance request status is updated, SiteOps keeps a request history record. The history can include the previous status, the new status, an optional note, and information about who made the change.

This helps property managers review the request timeline instead of relying only on memory, scattered messages, or separate notes.

Supported maintenance request statuses

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.

How a maintenance request starts

SiteOps has a property-specific tenant request form. The form collects the details needed to create a maintenance request.

The tenant request form requires:

. category

. unit or room number

. description

. name

. email

The form also supports an optional photo file. A photo can help provide more context about the issue when the requester chooses to include one.

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.

When a request status changes and a requester email exists, SiteOps sends a status update email. This helps the requester stay informed as the request moves through the maintenance workflow.

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 timeline without needing access to the owner dashboard.

Why status history helps property teams

Property teams may manage many requests across different units, rooms, or properties. A status history gives the team a clearer record of what changed during the request workflow.

This can help property managers review:

. when a request was created

. what status the request currently has

. whether the request moved from new to in progress

. whether the request was marked done

. whether a note was added during a status change

. what the requester can see through the public status page

What SiteOps should not promise

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

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

Final summary

SiteOps helps property teams keep maintenance request status history organized. It supports new, in progress, and done request statuses, sends owner and requester emails, and lets requesters look up request details and sorted request history by confirmation code and unit number.