At a big company, taking vacation is a transaction with a system. You open a portal, click some dates, an approval comes back from someone you've never met, done. Nobody feels anything.
At a small company there is no portal. There's Dave, who owns the place, who you'll see at the coffee machine an hour after you ask, who knows that your being gone means someone specific covers your work, possibly Dave. There's no policy doc to point at. Sometimes there's no stated vacation allowance at all beyond a vague "we're flexible" from your first week, which sounded generous at the time and now functions as fog. So the request that would be a click anywhere else becomes a small social event, and you've been putting it off for three weeks, and the trip is getting closer, and the flights are getting more expensive while you rehearse.
First, the reframe, because the wording problem is really a framing problem. You are not asking Dave for a favor. Time off is part of your compensation, as real as your paycheck, and using it is not a withdrawal from Dave's personal goodwill account. The fog of "we're flexible" makes it feel like every request is a special exception you're begging for, but that's a feature of the fog, not a fact about your standing. The employees who thrive at small companies are the ones who treat time off as normal, because treating it as normal is what makes it normal. The ones who tiptoe teach the company that tiptoeing is the price.
That reframe writes the message for you. You're not requesting permission to want a vacation. You're informing, coordinating, and leaving room for a genuine conflict, in that order:
Hi Dave, I'm planning to take October 6 through 10 off, a long planned family thing. That's far enough out that I'll have the month end close done before I go, and I'll write up where everything stands for whoever needs it. Flag anything you can see conflicting, otherwise I'll book it this week.
Notice the moves. It states dates rather than asking "would it maybe be possible." It answers the only question a small company owner has, which is never "do you deserve rest" and always "what breaks while you're gone," before he can ask it. And "otherwise I'll book it this week" sets a default. Requests with no default float forever in the small company way, where nothing is refused and nothing is confirmed and three weeks later you're re-asking. A soft deadline isn't pushy. It's mercy for both of you.
Put it in writing, even at a company where everything happens out loud. Not because you're building a legal file against Dave, but because verbal yeses at small companies evaporate. Dave says "sure, should be fine" at the coffee machine, means it fully, and retains it for four days. A message thread means neither of you is relying on memory in October. If the yes happens verbally, close the loop yourself: "Great, thanks, confirming the 6th through the 10th so it's on both our calendars."
And if there really is no stated policy, no number anywhere, don't let each request be a fresh negotiation with the fog. After this one goes through, ask the structural question once, in a calm moment, not attached to any trip: "Can we pin down what my annual time off actually is? Easier for me to plan around a number." Small companies skip writing these things down through inertia, not malice, and most owners will name a number the moment someone asks like it's a normal question. Which it is.
The dread you feel is real, and it's also mostly inherited from the fog. Clear requests, stated dates, coverage handled, a default set. Ask like it's normal three times and it will be.
