AITA for refusing to move my vacation for my coworkers honeymoon?

An employee at a small startup carefully planned and secured approval for a late-August vacation well in advance, only to learn it overlaps with his sole department colleague’s honeymoon. With just two software team members, simultaneous absences would halt progress entirely. The coworker, unable to get the time off due to the prior approval, asked if the original planner could reschedule.

After discussing with his wife, the couple decided shifting plans would prove too disruptive and risky—they might skip the break altogether. Now facing the choice to hold firm or accommodate a once-in-a-lifetime event, he questions if refusing makes him unreasonable in a tight-knit work setting.

‘AITA for refusing to move my vacation for my coworkers honeymoon?’

In a small startup, overlapping vacations in the two-person software team would grind work to a halt.

The coworker discovered his planned honeymoon clashes directly with the already-approved dates.

After weighing the option, the couple concluded rescheduling would be too disruptive.

Vacation approvals typically follow “first-come, first-served” in small teams, rewarding proactive planning—here, the poster secured dates responsibly, while the coworker booked personal plans without confirming availability. Honeymoons hold emotional weight, yet they’re elective, not emergencies; expecting colleagues to upend non-refundable arrangements sets unfair precedent.

Some flexibility fosters goodwill in close-knit workplaces: attempting rescheduling (with reimbursement for costs) could preserve harmony, especially since daily collaboration continues post-honeymoon. Refusal risks resentment, though entitlement to others’ approved time undermines fairness.

Broader norms stress communication: shared calendars prevent conflicts, and companies should mandate checking before booking. Ultimately, no obligation exists to sacrifice personal rest for another’s oversight—poor planning isn’t an emergency—but weighing long-term dynamics matters in duo teams.

Here’s the feedback from the Reddit community:

Many users emphasized first-come priority and the coworker’s planning failure.

Several leaned no assholes here, suggesting consideration for workplace harmony.

A few highlighted practical solutions or company shortcomings.

Views split between strict fairness (you booked first) and relational pragmatism (try accommodating for harmony), with most agreeing the coworker bears responsibility for not checking availability. No clear assholes emerge—polite asking and declining are both reasonable—but small-team dynamics amplify fallout from inflexibility.

In tiny departments, would you reschedule for a colleague’s milestone if costs were covered, or hold your ground on first-come rules? How should startups handle shared calendars to avoid these conflicts? Drop your workplace vacation stories below.