Measuring decision latency in tenant intake

Published October 28, 2026

Question and scope

The question should name the unit, the start event, the stop event, and the decision the result is meant to inform. State how duplicate requests are identified and whether they are merged, linked, or counted separately. A case is complete only when the park management software shows the approved destination value and the tenant intake supports it. If the study is exploratory, label it exploratory and do not present the result as a stable baseline. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. The October 28 tenant intake exception log should show the reason code, owner, and release decision.

The question should name the unit, the start event, the stop event, and the decision the result is meant to inform. A count without a denominator is not a measurement, especially when the queue changes size during the day. Define the start event, the stop event, the pause rule, and the treatment of a missing rent ledger entry before collecting data. Record the exclusions in advance so a difficult case cannot be removed after the result is known. If the evidence is sensitive, record the approved reference and access path rather than copying the content. The October 28 tenant intake recovery test should record the restore point and the maintenance response time result.

Population and unit

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. Define how a case that waits for tenant is counted: paused, open, or excluded, but not silently dropped. Use the same case key across the queue export and the evidence extract to avoid double counting. Record this decision in the study log with the case key, the review date, and the person who approved the classification. The October 28 control note for Mobile Home Biz should name the tenant intake source, the owner, and the next review time.

Record how duplicate requests were matched, merged, or kept separate, because that choice changes the denominator. The population should include unresolved cases, not only closures, or the study will overstate completion. If the definition of vendor approval cycle changes, keep the old and new values side by side for the transition period. Record the extraction date and the queue filter so another reviewer can reproduce the population count. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. The October 28 evidence trail for tenant intake should show the source version and the maintenance vendor decision.

Definitions and measures

Measure elapsed time from the first recorded request to the verified destination update, and report waiting intervals separately. Do not store sensitive content in the analysis file when a reference to the approved repository is enough. A duplicate request is a separate intake event even when it points to the same underlying need; record the link. State how duplicate, cancelled, and reopened cases enter the numerator and denominator. Use the same note in the case file and the study extract; do not create a second version in a personal document. The tenant intake review at Mobile Home Biz should state whether the maintenance request was current on October 28.

Name the owner who can declare a case complete, and record that role in the data dictionary. Do not store sensitive content in the analysis file when a reference to the approved repository is enough. A duplicate request is a separate intake event even when it points to the same underlying need; record the link. Record the pause rule and the person authorized to release a paused case. Keep the measurement note short enough to read with the case and specific enough to support the reported open work orders. The October 28 tenant intake note should distinguish a missing vendor bid from a confirmed negative.

Data dictionary and evidence

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. Store sensitive evidence in the approved repository and keep only the reference in the analysis file. Do not use a zero or an empty string to represent missing evidence. Link the observation to the exact field in the vendor bid folder and to the vendor bid that supports it. The tenant decision on tenant intake should be dated October 28 and linked to the vendor bid.

Keep free-text notes separate from coded fields so the analysis does not depend on inconsistent wording. Use a controlled list for exception reasons; do not let free text become the analysis category. Run a five-case pilot before the full sample and revise any field that two reviewers interpret differently. A case key should remain stable if the case moves between owners or changes status. If the case moved between owners, include both owner periods in the review note and name the handoff time. The October 28 tenant intake close should name the destination field, the approver, and the maintenance response time check.

If the source is a document, record the page or field; if the source is a system, record the record identifier and extraction time. Name the required fields for each article type and mark conditional fields in the dictionary. Run a five-case pilot before the full sample and revise any field that two reviewers interpret differently. Archive the dictionary with the study so a later reviewer can reproduce the categories. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. The October 28 tenant intake exception log should show the reason code, owner, and release decision.

Sampling and collection

Record the eligible count, the sample size, and every exclusion so another reviewer can reproduce the sample. Keep the collection window and the number of collectors in the report; both affect how the result should be interpreted. Do not expand the sample only because the early result looks weak or strong. Record the date of the sample and the version of the queue export. If the evidence is sensitive, record the approved reference and access path rather than copying the content. The October 28 tenant intake recovery test should record the restore point and the lease renewal lead time result.

Record the eligible count, the sample size, and every exclusion so another reviewer can reproduce the sample. Collect the case from the emergency contact list, the inspection log, and the approval record, and stop at the verified close. Stratify by risk, channel, and owner so the sample is not dominated by the easiest queue. A case that is difficult to access is still part of the frame; report the access failure rather than replacing it silently. Record this decision in the study log with the case key, the review date, and the person who approved the classification. The October 28 control note for Mobile Home Biz should name the tenant intake source, the owner, and the next review time.

Sample across the full observation window, including the days when the queue was busiest and the days when coverage changed. Collect the case from the park management software, the tenant intake, and the approval record, and stop at the verified close. If a stratum has fewer cases than planned, report the smaller count instead of replacing it with a convenience case. Include at least one case from each owner in scope when the frame allows it. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. The October 28 evidence trail for tenant intake should show the source version and the tenant decision.

Analysis and reporting

Separate observation from interpretation; a high completion rate on a small easy sample is not evidence of a strong control. Compare periods only after checking the case mix, the definitions, and the queue rules. Write the finding in plain language and separate what was observed from what the team believes caused it. Use a case-level table to explain an outlier before treating it as a process signal. Use the same note in the case file and the study extract; do not create a second version in a personal document. The tenant intake review at Mobile Home Biz should state whether the inspection log was current on October 28.

If the sample is small, report the instability and the cases that drive the result instead of a precise-looking percentage. A small sample should be reported with the number of cases that drive the result. 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. Keep the measurement note short enough to read with the case and specific enough to support the reported open work orders. The October 28 tenant intake note should distinguish a missing tenant intake from a confirmed negative.

Limitations

Changes in definitions, staffing, or the park management software during the window can create a trend that is not a process effect. The study cannot determine whether a professional judgment was correct, only whether the record supports it. Name the follow-up evidence that would reduce the largest uncertainty. Record the access problems that prevented a case from being reviewed. Link the observation to the exact field in the park management software and to the tenant intake that supports it. The park owner decision on tenant intake should be dated October 28 and linked to the tenant intake.

The record may be incomplete, delayed, or maintained outside the team, so the method cannot infer missing work from a clean summary. Changes in staffing, access, or the rent ledger during the window can create a difference that is not a process effect. Record the response or access problems that prevented a case from being reviewed. If the reviewer performed the work, use a second reviewer for a subsample and report the disagreement. If the case moved between owners, include both owner periods in the review note and name the handoff time. The October 28 tenant intake close should name the destination field, the approver, and the maintenance response time check.

Review and next action

Name the owner who will read the result and set a review date before the sample is collected. Report what moved, what stayed the same, and what the study still cannot explain. Report the action result even if the change did not work; a failed test is still evidence. Use a short action log that names the change, the owner, the due date, and the measure that will show whether it worked. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. The October 28 tenant intake exception log should show the reason code, owner, and release decision.

Report what moved, what did not, and which result is still unexplained. Name the owner, the review date, and the decision the study is expected to inform. If the action requires a policy or access change, route it to the owner and record the decision. Link the action to the case evidence that prompted it, not only to the meeting notes. If the evidence is sensitive, record the approved reference and access path rather than copying the content. The October 28 tenant intake recovery test should record the restore point and the vendor approval cycle result.