A remote leasing assistant misses an owner update. A maintenance ticket sits overnight between shifts. A new colleague keeps asking questions that the manager believes were covered in training. These problems can look like poor performance, but they may have different causes.
Before replacing a person or adding another meeting, inspect the work. The useful question is where the information, capacity or decision broke down. A Remote Team Member (RTM) needs the same clear responsibilities as an office colleague, plus explicit arrangements for the handoffs that proximity once covered.
Diagnose the symptom before choosing the fix
Use a recent, specific example. Read the ticket, message or work record together, including when it arrived, who could see it and what happened next. Avoid treating a green online status or a quiet chat channel as evidence of productivity.
| Problem | Possible cause | A practical test | Intervention | Review measure |
|---|---|---|---|---|
| Owner updates arrive late | The reporting deadline or input owner is unclear | Trace three missed updates to their missing inputs | Assign the input, drafting and approval steps separately | Updates sent by the agreed time; correction rate |
| Maintenance tickets stall between shifts | The outgoing person assumes the next person saw the ticket | Ask each person to identify who owns one open ticket now | Require an acknowledged handoff and a backup route | Unacknowledged handoffs; urgent tickets without an owner |
| Output falls while hours remain stable | Volume, interruptions or rework exceeds capacity | Sample a week’s incoming work, time and returned items | Remove duplicate work or rebalance the queue | Backlog age and first-pass quality together |
| A new hire repeatedly misreads instructions | Missing context, weak comprehension or inadequate training | Ask them to explain and perform one task using the current instructions | Repair the instructions or provide targeted practice | Correct independent completion of comparable tasks |
The measures are diagnostic tools, not universal targets. Set service standards according to your contracts, local obligations, team coverage and the seriousness of the work.
1. Communication fails when no one owns the next step
A message saying “the plumber has not replied” describes a problem without assigning action. The next shift needs the current situation, what has already been tried, the next deadline and who must act.
For a non-emergency maintenance request, an illustrative handoff might read:
Ticket M-305: The approved plumber has not confirmed tomorrow’s appointment. I contacted dispatch at 2 p.m. and 4 p.m. The resident is available from 9 a.m. to noon. Jordan owns follow-up at opening; if the plumber cannot attend, Jordan will ask the maintenance lead to authorize an alternative. The resident has been promised an update by 10 a.m., even if scheduling remains unresolved.
The receiving person acknowledges the handoff in the ticket. If no acknowledgement arrives before the outgoing person’s shift ends, the outgoing person contacts the designated backup. That does not mean extending a shift indefinitely; the manager must supply a staffed backup arrangement.
Urgent hazards use a separate emergency route. A resident reporting an immediate danger should not enter a routine queue while colleagues debate which time zone owns it. Train staff on the company’s locally reviewed emergency instructions and make the on-call contact reachable through a live channel.
Keep decisions in the work record. Chat can alert someone to a problem, but it should link to the ticket containing the facts and commitment. Otherwise the next person must search several conversations to reconstruct the case.
2. Processes fail when they omit decisions and exceptions
A checklist that says “send to owner for approval” leaves important questions unanswered. Which owner contact is authorized? What information is needed? What happens if the owner does not respond? Who decides whether waiting is appropriate?
Start with the workflow producing the most consequential confusion, such as urgent maintenance, lease renewals or owner onboarding.
Write down:
- The trigger.
- Required information.
- The responsible person.
- Permission boundaries.
- Completion evidence.
- The exception route.
Ask someone unfamiliar with the task to follow it using an anonymized case. Any question they cannot resolve reveals a gap worth fixing.
Do not document every minor action before improving one critical workflow. A short, usable procedure is more valuable than a comprehensive manual no one can navigate. The remote team playbook provides an operating-agreement structure for responsibilities, channels and handoffs.
Give people secure access to do the work
Use individual accounts, access limited to the role, and multifactor authentication where supported. Multifactor authentication combines different types of identity checks, such as a password and a code from an authenticator app. A protected password manager can help staff maintain unique credentials without sending them in chat.
Routine forced password changes are not a substitute for good access controls. NIST’s current authentication guidance rejects arbitrary periodic password changes and calls for changes when there is evidence of compromise. Your security lead should define the response to suspected compromise: report promptly, restrict affected access, revoke sessions or credentials as needed, and investigate. Staff should know whom to contact before an incident occurs.
3. Capacity problems can resemble motivation problems
Look at the queue before assuming that someone is distracted at home. A maintenance coordinator may close fewer tickets because more cases require owner decisions, vendors are missing appointments, or duplicate resident messages consume the afternoon.
For one representative week, record new work, completed work, time spent on rework, and items blocked by other people. Discuss what the team member can control.
In a fictional queue review, timings from comparable routine cases indicate that the week’s incoming requests and existing follow-ups need 28 hours of handling plus six hours of re-entering information already in the system. The coordinator has 30 hours available for that queue. Four cases are waiting on vendors; their elapsed waiting time is recorded separately from active follow-up work. Removing the duplicate entry is the first intervention: the estimated 34-hour demand would fall to 28 hours, within available capacity. The evidence points to avoidable work before it supports a motivation judgment or another hire. Over the next two comparable weeks, check whether backlog age and rework time fall while first-pass quality holds, including whether the required records remain complete.
A short obstacle-focused huddle can help during a busy period. Each person identifies work at risk and the decision or support needed. Routine status information belongs in an asynchronous update so the meeting does not become a recital of completed tasks.
Ask privately about workload and support. Relationship building has a place, but optional social activities cannot repair chronic understaffing, unclear pay or constant after-hours interruptions. If time monitoring is necessary, explain its purpose, review applicable privacy rules and collect only what you need. Screenshots can capture resident information and personal material; do not make them the default measure of contribution.
4. Distinguish selection problems from training needs
A candidate can speak confidently and still struggle to understand a dense lease file or write a clear resident update. Assess the work the role actually requires before making the offer.
Use a short, paid exercise with fictional information. Ask a leasing candidate to summarize an inquiry, identify missing facts and draft an appropriate reply. Ask a maintenance candidate to prioritize sample tickets and identify where approval is needed. The interview questions and hiring scorecard show how to evaluate these tasks consistently.
For a current team member, distinguish an assessment gap from a training gap. If the procedure changed, teach the change and provide practice. If the work was never part of the agreed role, address the role design. If clear instruction, reasonable workload and supported practice still do not produce acceptable work, document the performance issue and follow your management process.
Review the chosen intervention after enough comparable work has occurred. Check both speed and quality; a shorter queue is not progress if staff close unresolved requests. When the recurring problem is unclear responsibility across the team, BetterTeam Consulting can help you strengthen the Operational Framework behind the work.