How do you coach a rep who is always late to their meetings in 2027?

What it is and why it matters

Coaching chronic lateness is fundamentally a diagnostic exercise before it's ever a corrective one. A rep who shows up ten minutes late to a Tuesday pipeline review isn't automatically lazy, disrespectful, or disengaged — lateness is a surface behavior with several distinct underlying causes, and treating all of them the same way is why so many managers coach this issue for months without resolution. The three buckets that show up most often in RevOps teams are a time-management skill gap (the rep genuinely can't sequence a day with back-to-back demos, internal syncs, and admin work), an avoidance pattern tied to a specific meeting type (reps who are on time for customer calls but chronically late to pipeline reviews are usually dreading the scrutiny, not managing their calendar poorly), and a motivation or "will" gap where lateness is a passive signal of disengagement, burnout, or a rep already mentally checked out of the role.

This matters more in a RevOps context than in most other functions because meetings are load-bearing infrastructure for revenue operations — forecast calls, deal reviews, and 1:1s are where deal risk gets surfaced, where coaching actually happens, and where cross-functional handoffs between sales, marketing, and CS get coordinated. A rep who is always late to these doesn't just lose a few minutes; they arrive after the context has been set, miss the reasoning behind a forecast adjustment, and force the rest of the room to either re-explain or let them operate on incomplete information. Multiply that by a team of eight or ten reps and the cumulative drag on meeting efficiency, morale, and trust becomes a real operational cost, not just an etiquette complaint. Left unaddressed, chronic lateness also sets an informal norm: other reps notice who gets away with it, and punctuality erodes team-wide, because people rationally match the lowest enforced standard rather than the stated one.

The coaching goal, then, isn't punctuality for its own sake — it's restoring the reliability that meetings depend on to function as a coordination and coaching mechanism. A manager who treats this as "just be on time" without diagnosing why misses the chance to fix a root cause that may also be quietly hurting the rep's pipeline hygiene, forecast accuracy, or customer follow-through.

The step-by-step process

The coaching conversation itself should follow a repeatable sequence rather than an improvised lecture, because the structure is what keeps the exchange collaborative instead of adversarial. Start by naming the pattern with specific data rather than a vague impression — "you've been five to ten minutes late to three of our last four 1:1s and two team stand-ups" lands very differently than "you're always late," which invites defensiveness and denial. Follow immediately with genuine, non-judgmental listening: ask an open question like "help me understand what's happening before these meetings start" and then stop talking. Most reps will tell you the real reason — an overloaded morning, dread about a specific agenda item, or a logistics problem — if the tone is curious rather than accusatory.

Once you understand the driver, move into co-creating the fix rather than prescribing one. Ask directly: "what would it take for you to be on time for the next two weeks, and what do you need from me?" If the answer is a calendar reminder, agree on one together. If the rep admits they dread the pipeline review because it feels like an interrogation, that's useful information about how you're running the meeting, not just about their behavior. The fifth and final step is setting a clear, time-bound follow-up: name the exact standard, the exact window (typically two weeks), and what happens if the pattern repeats. Close the loop the next time it happens — either reinforce the improvement immediately and specifically, or address a repeat lapse the same day rather than letting it accumulate into a bigger, colder conversation later.

Costs, timelines, and typical ranges

The cost of chronic lateness is easiest to see in raw meeting minutes, but the real cost compounds through re-explaining context and lost coaching time. A rep who is ten minutes late to a 30-minute 1:1 has effectively turned it into a 20-minute meeting, and if the manager re-summarizes the first ten minutes for their benefit, the whole session shrinks further while everyone else in a group setting sits idle. Across a team of eight reps each averaging even two late arrivals a week at eight minutes each, that's over two hours of lost collective meeting time weekly — before counting the intangible cost of a forecast review that starts distracted instead of focused.

On timelines, most reasonable coaching arcs run two to four weeks and two to three documented conversations before a manager should consider a formal Performance Improvement Plan. The first conversation is diagnostic and collaborative; the second, roughly a week or two later, checks whether the agreed fix is holding and adjusts if it isn't; a third conversation, if lateness persists past three to four weeks despite genuine effort, is where the manager should be explicit that the next step is a formal PIP. If the rep shows zero engagement with the first conversation — deflecting, denying the pattern exists, or making no attempt at the agreed fix — that timeline compresses, and moving to a PIP after a single failed follow-up is reasonable rather than premature.

PIP timelines for a punctuality-specific issue typically run 30 days, since the behavior is observable daily and doesn't require the longer 60-to-90-day windows used for skill-based performance issues like quota attainment. A typical PIP language sets a hard threshold — for example, no more than one late arrival across all scheduled meetings in the 30-day window — with a stated consequence for failure that's proportionate to the role and prior performance history, ranging from a written warning to termination for a rep who is also underperforming elsewhere. Accommodations for legitimate external factors like childcare or a documented medical issue should be handled as a schedule adjustment rather than folded into the same disciplinary timeline, since the underlying issue there isn't a will or skill gap at all.

Where teams get it wrong

The single most common mistake is skipping the diagnosis step entirely and jumping straight to a generic "be more punctual" directive. This treats a rep dreading a badly run pipeline review the same way as a rep who's genuinely checked out, and it fails both — the avoidant rep gets no relief from what's actually driving the behavior, and the disengaged rep gets a soft nudge instead of the clear consequence they need. Managers who skip diagnosis usually end up repeating the same ineffective conversation every few weeks without the behavior actually changing, because they're treating a symptom as if it were the disease.

A second frequent error is calling out lateness publicly, in the meeting itself, as it happens. This might feel efficient, but it puts the rep on the defensive in front of peers, which almost always produces excuse-making rather than honest disclosure, and it can permanently damage the trust needed for the rep to be candid in a private follow-up. Public correction should be reserved for cases where private coaching has already failed and the team's collective start-time discipline is visibly eroding — and even then, it should target the norm, not the individual by name.

Teams also frequently under-invest in modeling the standard they're enforcing. A manager who is chronically ten minutes late to their own 1:1s and stand-ups has no real standing to coach a rep on punctuality, and reps notice this inconsistency immediately — it undermines the entire intervention before it starts. Related to this is the failure to start meetings on time regardless of who's missing; managers who wait for latecomers before beginning are training the whole team that the stated start time is negotiable, which makes individual coaching conversations feel arbitrary and unfair when they do happen.

Finally, many managers set vague or unenforced consequences — a verbal warning with no specific follow-up date, or a PIP threat that never gets written down or revisited. A consequence that isn't concrete and time-bound isn't really a consequence; it's a mood. The rep learns that lateness produces conversations but no real change in outcome, and the pattern persists indefinitely because nothing has actually shifted the incentive.

Decision framework: when to choose what

Choosing the right intervention depends almost entirely on what the diagnosis reveals, and using the wrong tool for the underlying cause is why so many coaching attempts stall. A pure skill gap — a rep who wants to be on time but has no functional calendar system — responds well to concrete tools: enforced buffers between meetings, a five-minutes-early personal rule, and a pre-meeting ritual like closing tabs and pulling up the agenda before the call starts. This is the lowest-friction fix and usually resolves within one or two weeks if the rep engages with it honestly.

An avoidance pattern needs a different lever entirely: safety and redesign, not tools. If a rep is only late to a specific recurring meeting, the fix is examining whether that meeting itself needs to change — is a pipeline review structured as an interrogation rather than a working session, and would reframing it as collaborative problem-solving remove the dread that's driving the avoidance? Tools alone won't fix this, because the rep isn't struggling to arrive on time; they're subconsciously choosing not to.

A will or motivation gap is the category where consequences, not systems, are the correct tool, and this is also where managers most often under-react out of a desire to stay supportive. If a rep shows no effort after a genuinely collaborative first conversation, escalating quickly to a written, time-bound expectation is not punitive — it's the appropriate match for a problem that isn't about capability. Legitimate external factors like childcare or a medical situation sit outside this whole framework and should be handled as a scheduling accommodation with a clear boundary once the adjusted time is agreed, since punishing a genuinely unavoidable constraint just damages trust without changing anything the rep controls.

Related questions

How do you coach a rep whose forecast is always wrong?

Separate over-optimism from poor pipeline hygiene by auditing their deal-stage definitions against actual close data, then require weekly written commit reasoning per deal rather than a gut-feel number, tightening accountability without micromanaging every opportunity.

How do you spot a struggling remote rep before it's too late?

Watch for declining meeting camera use, slower Slack response times, shrinking pipeline activity in the CRM, and skipped optional syncs — these leading indicators typically appear two to three weeks before a visible performance drop.

How do you coach an SDR who books meetings that never show up?

Audit the qualification questions asked before booking; low-show-rate SDRs are usually optimizing for volume over fit, so tying part of their metric to held meetings rather than booked meetings realigns the incentive.

How do you handle a rep who is on time for customers but late internally?

This is almost always a values signal, not a skill gap — the rep has decided internal meetings matter less, so the coaching conversation should focus on reconnecting internal syncs to outcomes the rep actually cares about, like deal support and commission accuracy.

FAQ

What if the rep has a legitimate reason like childcare or a medical appointment?

Accommodate it with a genuinely adjusted schedule rather than forcing the original time, but still set a firm boundary: once a new meeting time is agreed, the same punctuality standard applies to it.

Should I ever call out lateness in front of the team? No, not as a first step. Address it privately first; reserve any team-level comment for reinforcing a shared norm without naming the individual, and only after private coaching has already failed.

How many conversations should happen before a PIP? Generally two to three documented conversations across two to four weeks. If the rep shows real effort but still struggles, extend the timeline slightly; if they show no engagement at all, move to a formal plan sooner.

Can chronic lateness be a symptom of burnout rather than a discipline issue? Yes — if it's paired with low energy, missed deadlines, or visible disengagement, treat it as a possible burnout signal and offer support or a reduced load before defaulting to a disciplinary track.

Does a top performer get a pass on lateness because of their numbers? No. Letting a high performer skip the standard erodes trust with the rest of the team faster than almost anything else a manager can do, and it signals that results buy exemption from basic professional norms.

How do I know if this is really a RevOps process problem and not just one rep? If more than one or two reps on the same team are chronically late to the same recurring meeting, audit the meeting itself — a widely-avoided meeting is often poorly designed, not evidence of multiple discipline problems.

Sources

• https://hbr.org/
• https://www.shrm.org/
• https://www.ccl.org/
• https://www.mindtools.com/
• https://www.indeed.com/career-advice
• https://www.forbes.com/
• https://www.gallup.com/workplace

Related on PULSE

• How do you coach a rep who always defaults to a feature dump instead of benefits
• How do you coach a rep whose forecast is always wrong?
• How do you spot a struggling remote rep before it's too late?
• How do you coach an SDR who books meetings that never show up?
• How do you coach reps to book more meetings from cold outreach?