Workation

Once it was settled that work gets done from home, one question stayed open: if home is allowed, is a beach town allowed?

At Pagedeck the person who raised it first was Theo. His family was staying on Jeju for two weeks, and he wanted to work weekday hours there and keep the evenings and weekends. Grace went looking through the internal policy and found that the work location clause listed the office and the employee's home, and nothing else. There was no basis to approve it and none to refuse it. The clause had been written when everyone worked from one of two places.

The verbal yes was easy; what followed was not. Three similar requests arrived the next month, one of them for three weeks in Thailand. Domestic and overseas can't run on one standard, and two weeks and three weeks can't either. Above all, nobody had decided whether this period counted as leave or as work, so when Theo missed a meeting from Jeju the team read the situation two different ways.

That's why the arrangement got its own name and its own procedure. A workation isn't a standing release of location constraints; it's a program with duration, destination, and headcount fixed in advance and applications reviewed against them. The standing version already has a different name: remote work.

Five things get decided and written down by the company first. Applications come after that.

1. Duration and frequency. Two weeks per year taken once, or five days per quarter, in that shape. Without a ceiling this quietly becomes relocation, which is a different policy question.
2. Destination scope. Domestic only, particular countries, or a rule based on time zones. The time zone version is the easiest to administer: a band of three hours either side of the home office keeps collaboration hours overlapping.
3. Working-hours commitment. Where a core time exists — the window everyone is required to overlap in — it holds unchanged. Meeting attendance and response times stay what they were.
4. Cost split. Travel and lodging usually sit with the employee while the company covers some connectivity or a coworking day pass. Unwritten, this turns into a negotiation with every application.
5. Security conditions. Company hardware only or not, whether access routes through the company network, and whether customer data may be opened on the shared Wi-Fi at a cafe or a guest house.

The application path stays short: manager approval, an HR record, a change to the registered work location. Lengthen it and the policy lives only in the document.

The point that most often goes wrong is the nature of the period. A workation is working time, so no annual leave is deducted and the usual output is expected. Skipping a meeting for a sightseeing booking isn't covered, and a day off inside the window is taken as leave like any other. That distinction belongs in writing, since a verbal approval leaves it to interpretation.

Crossing a border adds problems that have nothing to do with attendance. Whether working in a country entered on a tourist basis is permitted varies by country, and staying long enough in one place approaches the line where tax is owed there. So many companies cap overseas stays at something short like five or ten days.

Policy documents and job postings are where it surfaces first. To a candidate the single line works as a signal about working style in general, so a company with a workation policy gets read as one with room in its office-day expectations too.

Whether it's needed at all depends on the company's working model. Where people may work from anywhere, being on Jeju and being at home are the same thing on paper, so the name isn't required. In a company where daily attendance is the default, or one running hybrid work with a mix of office and remote days, it exists as a separate application. Spending two weeks on Jeju under a three-office-days-a-week default means those attendance obligations have to be waived, and this policy is where that waiver is handled.

Operating models split in two as well. One is individuals applying on their own; the other is a whole team going to one place at one time. The second gets its own budget and purpose. When a distributed team gathers once a year to spend two weeks in the same room, that's collaboration design rather than a benefit.

Whether the policy actually runs shows up in application counts. A year after launch with zero applications, the problem isn't the policy but the approval path or the atmosphere around it. Once word gets around that a manager was reluctant, the next person doesn't apply.

"I'd like to apply for two weeks. Core time stays the same, right?"

The dates and location change while the collaboration window stays exactly as it was.

"Overseas is capped at five days. Anything longer needs a tax review."

Longer stays pull in taxation and immigration status, so the company set a ceiling.

"This is work, not leave. Days you actually take off come out of your annual leave."

Work and rest can't be blended inside one window; each has to be filed separately.

Pagedeck wrote the policy down after Theo's Jeju request. Two weeks a year, unlimited within the country and five days abroad, core time observed, company laptop and company network required. Applications end at manager approval, with only the work location updated in the HR system. What Grace paid attention to was the atmosphere rather than the count: assuming one refusal would end applications for good, she required any refusal to come with its reason in writing.

The most common misreading is that this is an extension of vacation. The first half of the word points at a holiday, so it sounds that way. But the period is working time and pay is calculated as working time. Someone who books it as leave misses meetings and answers late, and then colleagues who followed the rules fall under the same suspicion. One person's misunderstanding closing the policy for everyone is a common outcome.

The second frequent assumption is that any company allowing remote work automatically allows this. Permission to work from home makes location feel already open. But most written policies name the employee's home specifically, and a place that isn't home isn't in that sentence. Security conditions differ too: a home router and a guest house's shared Wi-Fi are not the same risk, and some internal systems block access from abroad outright. Leave without checking and you can end up unable to reach customer data at all.