Published October 27, 2026
Create an intake gate for tenant intake that preserves the source
A grounded mobile home park operations note for mobile home park owners: tenant intake with explicit evidence, decision rights, and a verified close.
MobileHomeBiz Team

On this page
Source and intake evidence
A grounded mobile home park operations note for mobile home park owners: tenant intake with explicit evidence, decision rights, and a verified close.
When tenant intake crosses a shift or a time zone, the next person may inherit a tidy summary that hides the missing tenant intake, the unresolved question, or the owner who never replied. A single missing tenant intake can turn a routine tenant intake request into a search through messages, spreadsheets, and memory, which is exactly when the team is most likely to guess. Use the park management software as the destination of record, and use the tenant intake to prove what the operator saw before making the change. The risk is highest when the park management software looks current but the tenant intake behind it was never opened.
The tenant intake queue rarely fails in a dramatic way; it usually drifts when a familiar request arrives and the operator copies the previous outcome instead of reopening the rent ledger. The team may also overstate maintenance response time, because a closed status is counted before the rent ledger entry and the destination update are verified. Use the rent ledger as the destination of record, and use the rent ledger entry to prove what the operator saw before making the change. A queue that mixes new requests with corrections will overstate demand and understate the time spent repairing earlier work.
Ownership and decision boundary
Do not treat a forwarded email as the record itself when the governing value lives in the rent ledger; the email may explain intent, but it does not replace the field. The reviewer should be able to open the rent ledger entry from the case without searching a personal drive or asking for a screenshot. Keep an exception note that explains which value was used, which was rejected, and why; a later reviewer should not have to infer the choice from the final number. The evidence map should show which fields are required, which are conditional, and which may be marked unavailable.
The source of truth may be a system, a signed document, or an approved message, but the team should name it once and use the same definition every day. For recurring tenant intake work, use the same maintenance request type and the same field labels so a sample can be compared across owners. A conflict is not a reason to rewrite history; it is a reason to show the reviewer exactly where the tenant intake record stopped agreeing with itself. The evidence map should show which fields are required, which are conditional, and which may be marked unavailable.
Start the evidence map by naming the field in the vendor bid folder that the tenant intake action is supposed to change. The reviewer should be able to open the vendor bid from the case without searching a personal drive or asking for a screenshot. After the conflict is resolved, add a short correction entry to the tenant intake log and link it to both source versions. A source that cannot be opened by the reviewer is not a usable source, even if the operator can see it on their screen.
Daily queue and exceptions
Maintenance dispatcher may prepare, compare, label, and route the tenant intake, while park owner keeps the decision that changes the destination record in the maintenance queue. A decision right is not the same as system access; the operator may be able to edit a field without being authorized to decide its value. The approval record should point to the maintenance request that was reviewed, not only to the request that started the work. For high-risk tenant intake work, require a second reviewer who is not the person who prepared the packet.
For mobile home park operations work, the safest split is preparation by the operator and judgment by the accountable owner, with both actions visible in the vendor bid folder. The approver may accept, reject, or ask for more evidence, but the response should be recorded in the tenant intake case rather than left in a chat. An approval that cannot be linked to a specific tenant intake case is too vague to support the destination change. Write the approval channel next to the decision right so the operator knows where a yes must appear.
If the queue cannot be reconciled in the morning, record the gap and assign an owner before starting new tenant intake work. A status update should describe a verifiable event, not a feeling about progress; link the event to the vendor bid folder or the vendor bid. Close the day by checking that each completed tenant intake has a destination update in the vendor bid folder and a confirmation for the requester. Use the same tenant intake status values across owners so the daily count means the same thing to everyone.
Verification and close
Start the tenant intake review by opening the lease repository, sorting the oldest unresolved item, and checking the lease renewal before reading the latest summary. Use the maintenance response time field to flag a possible exception, but do not let the flag replace the evidence review. Record any correction made during the day and link it to the original tenant intake record. At the end of the day, compare the open queue with the morning list and explain every unexplained difference.
Start with the cases that affect stale inspection, then move to routine requests; age alone is not the only priority signal. When the next step belongs to park owner, write the request and the due time instead of leaving the case in a waiting state. The end-of-day review should show what was completed, what is blocked, who owns the next step, and which inspection log is still missing. A daily stand-up should review exceptions and aging items, not read every completed ticket aloud.
An exception is not a generic failure; name the evidence problem so the team can fix the source instead of blaming the operator. The packet should state what the operator did not do and why, so the owner can see the boundary that was preserved. A stop is not a failure of service; it is the control working before the error reaches park owner. A workaround used during a the lease repository outage should have an expiry time and a reconciliation owner.
Weekly review and next action
Do not let an exception close because the requester stopped asking; keep the case open until the evidence or the decision is resolved. After the decision, link the response to the destination change and close the exception with the reason it occurred. A stop is not a failure of service; it is the control working before the error reaches property manager. If the same exception appears in three cases, review the intake form or the inspection log requirement.
Use separate reason codes for missing tenant intake, conflicting source, wrong tenant intake, expired approval, unavailable tenant, and a the park management software outage. After the decision, link the response to the destination change and close the exception with the reason it occurred. A stop-work rule should name the trigger, the person who can release the work, and the evidence needed to restart. The escalation packet should be short enough to read on a phone and complete enough to decide without a meeting.
If the destination is another team, the tenant intake is not closed until that team acknowledges the handoff. When the inspection log is sensitive, record the approved reference and the access location rather than copying the content into the queue. When the same tenant intake reopens repeatedly, review the intake, the inspection log, and the approval boundary rather than only the final step. Closed cases should remain searchable by object, owner, date, and source so a later correction can find them.
A sent message, a closed ticket, or a verbal yes is not proof that the tenant intake outcome reached the record. Record the confirmation from maintenance vendor when the outcome affects a customer, employee, payment, or access decision. When the same tenant intake reopens repeatedly, review the intake, the tenant intake, and the approval boundary rather than only the final step. A close note should name the evidence reviewed and the person who confirmed the result.
Keep the sample small enough to finish and large enough to expose a repeated gap. Review the exception mix each month; a rising missing-evidence count may be an intake problem rather than an operator problem. Record the decision to accept the risk when the team chooses not to change the process; an explicit acceptance is better than an invisible workaround. Choose the sample from the queue export before the meeting so the discussion cannot drift to memorable cases.
Record the sample frame, the reviewer, the criteria, and the result before discussing the cause. Track maintenance response time with a clear denominator and a review owner; a count without context is not a control. If the gap is caused by an unavailable property manager, add a backup decision path rather than letting the tenant intake queue wait indefinitely. Give the review an owner and a follow-up date; a finding without an action is only an observation.