Published October 27, 2026
A grounded mobile home park operations note for mobile home park owners: maintenance request with explicit evidence, decision rights, and a verified close.
The protocol does not estimate an industry benchmark; it produces a local description that mobile home park owners can review. The unit definition should be stable enough that two reviewers can classify the same case the same way. The definitions should be short enough to use at the queue and precise enough to defend in a review with tenant. The protocol should be short enough for an operator to follow and specific enough for a reviewer to repeat. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract.
The scope is one defined population of maintenance request cases observed from first request through verified close in the vendor bid folder. Exclude a reopened case only when the reopening did not create a new requirement; keep the exclusion count and reason. Define the start event, the stop event, the pause rule, and the treatment of a missing inspection log before collecting data. State whether the study covers one team, one client, or all cases in the defined service. At Mobile Home Biz, the maintenance request review should end with a dated note and a named owner for the next check.
The unit is one maintenance request case, from the opening request to the verified close, and linked events stay with that case. A case that moves between owners stays one case unless the process defines a new requirement at the handoff. The definition should make it possible to classify a case without asking the person who did the work. If the queue was archived during the window, report the loss and exclude the affected period rather than assuming the cases were resolved. If the evidence is sensitive, record the approved reference and access path rather than copying the content.
When several tenant intake updates belong to one request, state whether the request or each update is the unit and apply that rule consistently. Exclude cases opened outside the window only when the exclusion rule was written before collection. Use plain language in the definition and add one example and one non-example for the reviewer. Use the same case key across the queue export and the evidence extract to avoid double counting. The note should distinguish what was observed, what was inferred, and what still needs an owner decision.
Name the owner who can declare a case complete, and record that role in the data dictionary. Use a stable case key and a separate identity crosswalk stored in an approved system. Before collection, test the definitions on a missing tenant intake, a reopened case, and a handoff. Write the start and stop events as observable actions, not as opinions about whether the work felt finished. Record this decision in the study log with the case key, the review date, and the person who approved the classification.
Name the owner who can declare a case complete, and record that role in the data dictionary. Use a stable case key and a separate identity crosswalk stored in an approved system. A duplicate request is a separate intake event even when it points to the same underlying need; record the link. Write the start and stop events as observable actions, not as opinions about whether the work felt finished. Keep the evidence reference beside the coded value so a reviewer can test the same case without rebuilding the queue.
Use a pseudonymous case key and keep the identity crosswalk in an approved system with restricted access. Record the extraction time separately from the event time so a late entry is visible. Keep the original evidence reference next to the coded value so the reviewer can verify the classification. Pilot the dictionary with two reviewers and compare their classifications before the main sample. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it.
Mark missing, unavailable, and confirmed negative values separately; collapsing them hides the difference between no evidence and evidence of absence. Name the required fields for each article type and mark conditional fields in the dictionary. A missing value should have a reason code, not a blank cell or a zero. Record the source location, not just the file name, so a reviewer can reopen the exact evidence. At Mobile Home Biz, the reviewer should be able to explain this step to property manager from the case record alone.
Test the dictionary on five cases before the full sample; ambiguous fields should be fixed before collection, not after. Version the dictionary and report which version was used for each observation period. Record the data extraction date and the version of the rent ledger used for the population count. Archive the dictionary with the study so a later reviewer can reproduce the categories. Use the same note in the case file and the study extract; do not create a second version in a personal document.
Stop expanding the sample only when the review question is answered, not when the result starts to look favorable. Record the time of each observation so a later reviewer can distinguish a late entry from a changed decision. If a stratum has fewer cases than planned, report the smaller count instead of replacing it with a convenience case. Use a random start and a fixed interval when the frame is ordered, and record both. When a case needs an exception, record the reason, the owner, and the date before continuing the review.
Sample across the full observation window, including the days when the queue was busiest and the days when coverage changed. Collect the exception reason and the action taken before the close so the analysis can separate detection from resolution. Keep the sample selection reproducible by recording the export date, filter, and random seed or start rule. Record the date of the sample and the version of the queue export. Keep the measurement note short enough to read with the case and specific enough to support the reported open work orders.
Stop expanding the sample only when the review question is answered, not when the result starts to look favorable. Collect the exception reason and the action taken before the close so the analysis can separate detection from resolution. Do not expand the sample only because the early result looks weak or strong. Record the sampling frame as an export with a date, filter, and row count. If two reviewers disagree, preserve both classifications until the definition or the evidence is resolved.
If the sample is small, report the instability and the cases that drive the result instead of a precise-looking percentage. If two measures disagree, report both and explain what each one counts. Report the number of cases that changed status after the first extraction and how the change was handled. End with the decision the evidence supports and the decision it does not support. Link the observation to the exact field in the rent ledger and to the vendor bid that supports it.
Keep case-level detail available for review, because a summary chart without records cannot support a decision. Keep descriptive findings separate from causal claims. Use a simple before-and-after comparison only when the definitions and observation window are the same. When a rate changes, check whether the case mix or the evidence standard changed at the same time. Do not let a summary written later replace the evidence that was available at the first decision.
Report what remains unknown and what evidence would be needed to answer the next question. A clean summary can hide missing evidence, especially when the operator who did the work is also the reviewer. If the reviewer also performed the work, note the independence limitation and use a second reviewer for a subsample. If the queue changed during the window, explain how the change affects the denominator. If the case moved between owners, include both owner periods in the review note and name the handoff time.
The method also cannot observe work that never entered the queue, which may be the most important missing population. Selection bias remains when the team chooses cases that are easy to open or owners who are likely to cooperate. Report the limits of the the vendor bid folder data, including fields that were unavailable or changed during the window. Record the access problems that prevented a case from being reviewed. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory.
A quality review should end with an owner, a date, and one testable change, not a list of intentions. If the action changes unrepaired hazard, record the approval from park owner before implementation. Link the action to the specific maintenance request cases that motivated it. Report a failed action with the same detail as a successful one so the team can learn from it. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract.
Keep the review note with the maintenance request evidence so the next reviewer can see why the process changed. Choose one change and one measure to test it; a long action list is hard to evaluate. Keep the old process note until the new process has been tested; do not erase the baseline. Report a failed action with the same detail as a successful one so the team can learn from it. At Mobile Home Biz, the maintenance request review should end with a dated note and a named owner for the next check.
