Address Chronic Lateness with a Direct Report
Practice a manager 1:1 about repeated lateness with a direct report who has personal constraints and some resentment. Learn to address the pattern clearly, show care, and leave with a specific attendance plan.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Hr · Customer Service · Hospitality · Frontline · Education
Overview
This roleplay template practices a private manager 1:1 about chronic lateness with a direct report who has been 10 to 20 minutes late several times in two weeks. The situation is specific on purpose: the employee has historically been reliable, but the pattern is now affecting morning handoffs and team coverage, which means the learner has to address both the behavior and the business impact.
Use this template when you want to practice a conversation that needs clarity, restraint, and follow-through. The learner must name the lateness pattern directly, acknowledge the employee's personal situation without excusing the behavior, and set a concrete improvement plan that can be checked later. The persona is defensive and mildly resentful, so the roleplay tests whether the manager can stay calm when the employee pushes back or feels singled out.
Do not use this template for a general performance review, a one-time tardy, or a formal disciplinary meeting that already has a scripted HR process. It is also not the right fit when the issue is really an accommodation request, leave issue, or broader conduct concern. The value of the template is in practicing the exact middle ground: respectful, specific, and accountable, with enough realism to build better manager judgment.
How to use this template
- Read the situation carefully and identify the behavior you need to address, the impact it is having, and the outcome you want from the conversation.
- Start the roleplay and open with a direct, private statement that names the lateness pattern without using vague language or accusations.
- Talk to Morgan as you would in a real 1:1, acknowledging the employee's situation, listening to the pushback, and keeping the discussion focused on attendance and coverage.
- Complete the roleplay against the scored rubric so you can see whether you named the issue, explained the impact, and set a specific expectation.
- Review the feedback, revise your opening line or follow-up questions, and retry until you can land a calm, clear improvement plan.
Best practices
- Name the pattern early by referencing the repeated late arrivals, not just one recent instance.
- Acknowledge the employee's personal situation before moving into expectations so the conversation does not feel dismissive.
- Connect lateness to a concrete operational impact, such as missed handoffs, delayed coverage, or extra burden on teammates.
- Set a specific standard for the next period, including what on-time means and how long the improvement needs to hold.
- Ask one practical question about what would help the employee meet the expectation, then keep ownership with the employee.
- Avoid debating intent or character; stay on observable behavior, timing, and the effect on the team.
- End with a clear follow-up date so the conversation produces an action plan instead of a vague agreement.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this roleplay template help me practice?
It helps you practice a real manager conversation about repeated lateness with a direct report. The learner has to name the pattern, acknowledge the employee's situation, explain the impact on the team, and agree on a concrete attendance plan. It is designed for the kind of 1:1 where care and accountability need to happen in the same conversation.
Who should use this template?
This template is for people managers, team leads, and HR partners who coach managers on attendance issues. It is also useful for new managers who need practice staying calm when an employee is defensive or mildly resentful. The scenario is especially relevant when the employee is usually reliable and the issue is a new pattern, not a long-term performance problem.
How often should a manager have this kind of conversation?
Use it as soon as a pattern becomes visible, rather than waiting for it to become a bigger attendance problem. In practice, that usually means after several late arrivals within a short period, especially when handoffs or coverage are being affected. The goal is to address the behavior early and set expectations before the issue becomes normalized.
Does this template replace a formal attendance policy or HR process?
No. It is a practice scenario for the conversation itself, not a policy document or disciplinary workflow. It can support a manager's first coaching step, but any formal warning, leave accommodation, or escalation should follow your organization's HR process. If the lateness may involve a protected reason or accommodation need, the manager should involve HR appropriately.
What is the common mistake this scenario is designed to surface?
The most common mistake is jumping straight to solutions or discipline without first naming the pattern and acknowledging the employee's situation. Another frequent miss is being vague about the impact, which leaves the employee unclear about why the issue matters. This roleplay also exposes managers who soften so much that the expectation never becomes concrete.
Can I customize the employee's reason for being late?
Yes. You can adjust the personal reason, the level of defensiveness, and the team impact to match your workplace. The key is to keep the situation specific enough that the learner has to balance empathy with accountability. You can also adapt the opening line to reflect your team's tone and the manager's style.
How does this compare with an ad hoc coaching conversation?
An ad hoc conversation often lacks a consistent scenario, clear rubric, and repeatable feedback. This template gives the learner a realistic situation, a dynamic persona, and observable scoring criteria so they can practice the same skill multiple times. That makes it easier to improve phrasing, pacing, and follow-through instead of just talking through the issue once.
What should the manager leave the conversation with?
The manager should leave with a specific expectation, such as on-time arrival for the next two weeks, plus a plan for how the employee will meet it. That may include a revised start routine, a check-in date, or a note to revisit coverage if the issue continues. The conversation should end with mutual clarity, not a vague promise to try harder.
Related templates
Go deeper on the topic
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
Scheduling is the operational heart of any business built on hourly labor — who works when, which shifts get covered, and how fast the schedule adapts to...
-
Learn how targeted updates to onboarding, inspections, and worker safety create a defensible audit trail when regulators, attorneys, or insurers come calling.
-
Reduce recruiting pipeline friction with faster sourcing, scheduling, and comp benchmarking to hire top talent before competitors do.
-
MangoApps Shifts & Schedules unifies frontline scheduling, time, and leave management in one native platform for faster, simpler operations.
-
Boost intranet adoption with personalized recommendations and a department page that drive employee engagement from day one.
Ready to use this template?
Get started with MangoApps and use Address Chronic Lateness with a Direct Report with your team — pricing built for small business.
