Measuring cycle time for tenant intake from request to verified close

Published October 27, 2026

A grounded mobile home park operations note for mobile home park owners: tenant intake with explicit evidence, decision rights, and a verified close.

A useful scope is narrow enough to reproduce and specific enough to show whether missed rent posting is being detected. If one request produces several tenant intake updates, define whether the unit is the request or each update before sampling. Record how corrections, reopens, and duplicate requests are treated so rent posting accuracy cannot be inflated by reclassification. Keep the protocol with the tenant intake batch so the next reviewer can see what was measured. Link the observation to the exact field in the park management software and to the tenant intake that supports it.

Write the primary question and one supporting question, then stop; a long list of questions usually hides an undefined unit. The unit definition should be stable enough that two reviewers can classify the same case the same way. Write the primary measure and one supporting measure; a measure without a denominator or observation window is not ready. Record the exclusions in advance so a difficult case cannot be removed after the result is known. Do not let a summary written later replace the evidence that was available at the first decision.

Record the opening count by owner and channel, because a single total can hide a queue concentrated in one person. The population should include unresolved cases, not only closures, or the study will overstate completion. Write the rule for a missing rent ledger entry before the first case so the treatment is consistent. If a request was reopened after the window, keep it in the original population and report the later event separately. If the case moved between owners, include both owner periods in the review note and name the handoff time.

Record how duplicate requests were matched, merged, or kept separate, because that choice changes the denominator. Report the number of cases that could not be classified and the reason, rather than forcing them into a category. The start event should be the first recorded request, not the first time the team opened the case. Report a case that moved between owners as one case with two owner periods unless the process creates a new requirement. Keep the review note with the case so the next sampler does not have to reconstruct the decision from memory.

Test each definition on a routine case, a missing-evidence case, and a case that crossed owners. A blank field, a not-applicable field, and a confirmed negative field should have different codes. Before collection, test the definitions on a missing maintenance request, a reopened case, and a handoff. A definition that depends on the reviewer’s memory is not reproducible enough for this study. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract.

Define how a correction after close is linked to the original case and whether it creates a new case. Define allowed values for status, reason, owner, and evidence state before collection. A duplicate request is a separate intake event even when it points to the same underlying need; record the link. Define whether the measure counts requests, cases, or destination updates, and use that unit consistently. At Mobile Home Biz, the tenant intake review should end with a dated note and a named owner for the next check.

Each case needs the source, the observation time, the field supported, the owner, and the reviewer. Version the dictionary and report which version was used for each observation period. Record the source identifier, the field name, the observation time, and the reviewer for every extracted value. Archive the dictionary with the study so a later reviewer can reproduce the categories. If the evidence is sensitive, record the approved reference and access path rather than copying the content.

Test the dictionary on five cases before the full sample; ambiguous fields should be fixed before collection, not after. Give every case a study key that is not the client name, member number, or candidate email. Use one row per case and one column per required field; do not bury evidence in a long free-text note. Define who may change a coded value and how the change is logged. The note should distinguish what was observed, what was inferred, and what still needs an owner decision.

Keep free-text notes separate from coded fields so the analysis does not depend on inconsistent wording. Name the required fields for each article type and mark conditional fields in the dictionary. Store sensitive evidence in the approved repository and keep only the reference in the analysis file. Pilot the dictionary with two reviewers and compare their classifications before the main sample. Record this decision in the study log with the case key, the review date, and the person who approved the classification.

Stop expanding the sample only when the review question is answered, not when the result starts to look favorable. A second reviewer should re-extract a small subsample and record disagreements before the full analysis. Do not expand the sample only because the early result looks weak or strong. Keep a table of planned, eligible, selected, and reviewed counts for each stratum. Keep the evidence reference beside the coded value so a reviewer can test the same case without rebuilding the queue.

Use a random or systematic start rule for the first case, then take consecutive cases within each stratum. Use the same collection form for every case and keep the original record linked to the extracted fields. Do not expand the sample only because the early result looks weak or strong. If a selected case is out of scope, replace it only with the next case in the same stratum and record the substitution. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it.

A convenience sample of recently closed cases will overrepresent easy work and underrepresent the tail that needs attention. 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. At Mobile Home Biz, the reviewer should be able to explain this step to tenant from the case record alone.

Keep case-level detail available for review, because a summary chart without records cannot support a decision. For tenant intake, report the age distribution and the share of cases waiting on a named owner. Keep the case-level table available for review and summarize only the measures that answer the question. Keep descriptive findings separate from causal claims and label exploratory results. Use the same note in the case file and the study extract; do not create a second version in a personal document.

Keep case-level detail available for review, because a summary chart without records cannot support a decision. Report denominators with every rate and separate missing evidence from negative evidence. Report the number of cases that changed status after the first extraction and how the change was handled. When a rate changes, check whether the case mix or the evidence standard changed at the same time. When a case needs an exception, record the reason, the owner, and the date before continuing the review.

Report what remains unknown and what evidence would be needed to answer the next question. The cited sources describe recordkeeping, privacy, security, or control practice; they do not supply a local benchmark. If the queue changed during the window, explain how the change affects the denominator and the interpretation. State that the result describes the observed sample, not the whole industry or every team in the service. Keep the measurement note short enough to read with the case and specific enough to support the reported rent posting accuracy.

Selection bias remains if the team samples only records that are easy to open or cases handled by cooperative owners. A clean summary can hide missing evidence, especially when the operator who did the work is also the reviewer. If the queue changed during the window, explain how the change affects the denominator and the interpretation. State that the result describes the observed sample, not the whole industry or every team in the service. If two reviewers disagree, preserve both classifications until the definition or the evidence is resolved.

Keep the review note with the tenant intake evidence so the next reviewer can see why the process changed. Repeat the protocol with the same definitions and window, then compare the same measures. Report the action result even if the change did not work; a failed test is still evidence. Record the owner, due date, and exact change that will be tested at the next review. Link the observation to the exact field in the rent ledger and to the rent ledger entry that supports it.

Name the owner who will read the result and set a review date before the sample is collected. If the result is inconclusive, say so and choose a narrower question rather than claiming a trend. Report the action result even if the change did not work; a failed test is still evidence. Record the owner, due date, and exact change that will be tested at the next review. Do not let a summary written later replace the evidence that was available at the first decision.