1. Communication Objective

The objective of this communication is to address a persistent pattern of lateness with a core team member, clearly define how their arrival time impacts our morning marketing syncs and operational pipelines, and establish a mutual agreement on punctuality moving forward while maintaining a collaborative, respectful working relationship.

2. Key Issues to Address

• Consistency of the Pattern: Addressing a repeated habit rather than an isolated, understandable emergency.
• Impact on Collective Workflows: Explaining how missing morning alignment syncs stalls content planning, delays marketing sprint handoffs, and impacts overall project momentum.
• Team Equity: Protecting team morale by ensuring operational accountability is applied fairly across all members of the department.
• Supportive Troubleshooting: Uncovering if there are specific, addressable scheduling or logistical blockers causing the delay before moving to formal disciplinary steps.

3. Draft Conflict Resolution Message

Subject: Alignment on morning schedules and team syncs

Hi [Employee Name],

I’m reaching out to set up a quick, 10-minute touchbase tomorrow morning so we can align on arrival times and our daily operational workflow.

Over the past few weeks, I’ve noted a consistent trend of you logging in or arriving past our standard 9:00 AM start time. Because our morning marketing syncs and campaign stand-ups depend heavily on everyone being present to map out the day’s sprint, late arrivals mean the team frequently has to pause, restart, or repeat key tactical context. This creates a bottleneck that pushes back our production timeline for the rest of the day.

Our priority is ensuring you have the bandwidth to execute your work successfully, while also respecting the shared schedule of the broader team. I want to use our brief chat tomorrow to check in, see if there are any current logistical constraints or blockers impacting your morning routine, and establish a clear, predictable timeline that we can both commit to moving forward.

Please let me know if 10:30 AM or 11:00 AM works best for a quick chat tomorrow.

Best regards,

[Your Name]
[Your Title / Operations Lead]

4. Tone and Framing Notes

• De-escalation via Context: The draft intentionally avoids phrases like “you’re being unprofessional” or “you lack commitment.” Instead, it anchors the issue entirely to operational data: a 9:00 AM start time, delayed sprint handoffs, and team bottlenecks.
• Collaborative Open Loop: Framing the meeting as a “check-in” to uncover “logistical constraints” prevents the employee from immediately entering a defensive fight-or-flight mindset, making them more likely to take ownership of the solution.
• Explicit Clarity: The expectations are crystal clear. There is no ambiguity about what the problem is (lateness) or what needs to change (predictable morning arrival).

5. Follow-Up Recommendations

• The Post-Meeting Summary Email: Immediately following the conversation, send a brief, written recap to solidify the agreement. (e.g., “Thanks for chatting today. Just to recap our alignment, we’ve agreed on a dependable 9:00 AM start time moving forward, with the understanding that you’ll notify me by 8:30 AM if an unexpected external delay occurs.”)
• Consistency Check: Monitor the situation closely over the next two weeks. If the behavior is successfully corrected, offer a brief, informal “thank you for the adjustment” during your next regular 1-on-1 to lock in the positive behavior change.

6. Escalation Risks to Avoid

• The Public or Chat-Room Callout: Avoid sending “Are you running late?” messages in shared channels or group project boards. Addressing attendance in front of peers triggers public humiliation, which replaces accountability with resentment.
• Snooping or Assuming Intent: Do not guess the reason behind the lateness or lecture them on personal habits (e.g., “you need to sleep earlier”). Keep the focus strictly on the threshold of the workplace: the clock hits 9:00 AM, the sprint begins, and their presence is required.