Research

How often does a maintenance request close without a completion photo?

A measurement protocol for the maintenance request completion in mobile home park operations, with a frozen population, an evidence sample, and a dated review.

MobileHomeBiz Research Desk9 minutes read10 sources citedVerified 2026-11-02
How often does a maintenance request close without a completion photo? research illustration
Key finding: A local measurement protocol for the maintenance request completion, not an industry benchmark.

Key takeaways

  • Freeze the population before collection.
  • Report the denominator and the missing evidence.
  • Keep the decision with the park owner or manager.

Published November 2, 2026

Question and scope

This protocol asks what the maintenance request completion record can show about evidence, timing, and closure in mobile home park operations. It is a local measurement method, not an industry benchmark, an audit opinion, or a legal conclusion. The result describes one defined population during one observation window.

The scope is maintenance requests closed during the review window. State the start event, the stop event, and the treatment of a case that is reopened before collecting data. A count without a denominator is not a measurement, especially when the queue changes size during the day.

Population and unit

The unit is one maintenance request from first report through recorded close. Test the definition on a case that crosses owners, a case that is still open, and a case that was reopened. Apply the same rule to every case and record the rule beside the extract so a later reviewer can repeat it.

The primary measure is the share of closed requests with a dated completion photo. Add two supporting measures: the median days from report to photo, and the count of closed requests with no photo and no written exception. Report each measure with its denominator, observation window, and exclusion count. A percentage without those three elements is only a mood.

Definitions and measures

Define completion before the first case. For this protocol, completion means the share of closed requests with a dated completion photo is supported by the maintenance log entry and the dated completion photo. A case that fails the definition stays open even when a status field says closed. The reviewer should record the status field and the evidence separately.

Each case needs the maintenance log entry, the dated completion photo, and, when applicable, the exception note when a photo is impossible. Mark missing, unavailable, and confirmed negative values separately. Collapsing them hides the difference between no evidence and evidence of absence.

Evidence standard

Collect the case in a consistent order: open the request, then record the repair, then attach the completion photo. Stop at the verified close. If a case moves between owners, include both owner periods and name the handoff time in the review note.

Use a random or systematic start rule, then take consecutive cases within each stratum. Stratify by risk, channel, and owner so the sample is not dominated by the easiest queue. Include at least one adverse case: a missing source, a conflict, an unavailable owner, or a deadline that forced a decision.

Sampling and collection

Sample across the full observation window, including busy days and days when coverage changed. A sample drawn only from quiet days can make a fragile control look stable. Record the date and time of each observation.

Separate observation from interpretation. A high completion rate on a small easy sample is not evidence of a strong control. Report the numerator, the denominator, the exclusions, and the number of cases that drive the result.

Analysis and reporting

Show the distribution, not only the mean. A median close time can hide a long tail of cases that nobody reviews. Report the open-case count and the oldest case age by owner so the reader can see where delay accumulates.

When two groups differ, check whether the difference survives after adjusting for case mix and evidence standard. Do not rank owners on a small sample. The useful question is which step produces the missing evidence, not who looks worst.

Limits and sources of error

The main limit is that the maintenance request completion record may be incomplete, delayed, or maintained outside the team. This method cannot infer missing work from a clean summary. It also cannot establish whether a policy was followed in cases that left no trace.

Record the limitations before the result. The cited public sources frame recordkeeping, privacy, security, and internal control practice. They do not provide a result for this sample and should not be presented as one.

Review cadence

A change in systems, policy, client mix, or volume can make the result stale. Record those triggers with the finding. If the definition changes, keep the old and new rules side by side for the transition period and label which rule applies to each case.

Give this review a named owner and a review date. The report should end with the decision the evidence can support and the decision it cannot support. A report without a review owner is an archive, not a control.

Choose one next action from the review: fix the source, simplify the field, change the queue, or stop the work until the owner decides. Then repeat the protocol after the change and compare the same definitions.

Sources