In this article
“Something is wrong” starts a conversation. A useful request preserves what someone actually observed, where the issue is, and what the next person needs to verify.
Record the symptom before the theory
A tenant describing a rattling sound may not know its cause. Rewriting that report as a broken motor changes an observation into an unverified diagnosis. Preserve the reported symptom, the general location and whether it is happening now. Let a qualified person assess the cause. The difference matters because a vendor may prepare very differently for a confirmed replacement than for an inspection.
DoorLoop’s documentation says managers can record a tenant request received by phone, text or in person, as well as handle portal-originated requests. Its fields include a subject, description, status, optional priority and assignees. These are containers for information, not substitutes for a sensible intake conversation.
Use a small intake pattern
- Observed: what happened, in the reporter’s terms.
- Located: the relevant property, unit or shared area in the authorized management record.
- Changed: when the issue was first noticed and whether it has changed.
- Next: the person responsible for clarification or assessment.
Ask only questions that help the next step. A useful photo may show the affected fixture, but a wide room image can accidentally include personal possessions or documents. Do not ask for sensitive images merely because the system allows attachments. Keep actual tenant names and records inside the authorized property workflow, not in a public editorial tool.
Separate access from assignment
Assigning a request does not establish permission to enter a home. DoorLoop documents an access-permission field and separate notification choices. Treat permission, scheduling and who receives an update as distinct checks. Record only verified access arrangements using the organization’s approved process. Do not infer consent from a maintenance report, and do not circulate entry codes in an ordinary email summary.
Fictional desk note
“Kitchen cabinet door hangs unevenly; noticed this morning; no photo yet; coordinator to clarify which hinge appears loose.” This is more useful than “replace kitchen cabinets.” The first note preserves the question; the second invents a scope of work.
Choose a responsible next step
A status label describes a record. It does not prove that someone has accepted the work. Name a responsible role in the internal handoff and decide what acknowledgment will close that gap. Avoid setting a speculative completion date simply to fill a field. A date for the next update can be more honest than a repair deadline that no vendor has agreed to meet.
If the situation may involve immediate danger, leave the routine queue and use emergency services or the property’s verified emergency procedure. This publication cannot triage a hazard, dispatch help or decide whether a dwelling is safe.
Before the request becomes a work order
Review whether the report is clear enough for another person to act without reconstructing the whole conversation. Then use the work-order handoff guide to separate reported facts from approved work. When progress changes, use the communication loop to distinguish a recorded update from a delivered message. Our local checklist can organize these questions without taking any tenant data.
Sources and scope
Official public sources checked October 21, 2026. The coordination methods and fictional examples are original editorial analysis, not a tested DoorLoop account workflow or legal, accounting or emergency advice. Features depend on plan, settings, permissions and product changes.