Work Arrangements
Working Temporarily from Another State: Get Location Approval Before You Go
A fictional employee prepares a ten-day Oregon work request and tracks operational, HR, payroll, risk, and IT reviews, keeping conditional support separate from authorization to start.
Get written approval for the actual state, worksite, and dates before working temporarily from another state. An existing remote-work agreement or a manager’s “fine with me” may not cover payroll, employment requirements, benefits, or information security. Submit a concrete location request, identify the final decision owner, and keep conditional reviews separate from permission to start. A short visit is not automatically exempt from your employer’s process.
This LandOffer.ai guide uses public employer policies and official state guidance checked October 27, 2026. Named university policies illustrate their own scope; they are not rules for every employer. The completed request and review record below are fictional. They do not determine anyone’s tax residency, withholding, insurance coverage, or legal obligations. No travel, HR record, payroll setting, device configuration, leave request, or employer communication was changed.

Remote permission is tied to an arrangement
A remote-work agreement can specify both how you work and the locations where you may work. Read your current agreement for its authorized location, duration, reporting requirements, and approval route. Find out whether a temporary domestic worksite change uses the same form as a permanent relocation. Avoid treating a mailing-address update as either permission to work elsewhere or a complete description of your physical work location.
Public policies show why the details matter. The University of Washington’s out-of-state policy, updated July 30, 2026, requires advance approval within its stated staff framework and calls for accurate payroll work-location information. Its separate telework policy asks agreements to specify location, schedule, duration, communication, equipment, and onsite expectations. These are useful questions for your request, not a claim that your company uses UW’s decision hierarchy.
The University of Illinois policy has a different scope. It covers specified paid employees, excludes faculty and several other categories, and describes out-of-Illinois locations lasting 60 or more consecutive days where the employee typically would be considered resident for tax purposes. It also covers a primary work location outside Illinois. Those qualifications are essential: the policy does not establish a nationwide 60-day allowance, and a shorter trip is not automatically authorized under another employer’s rules.
Ask HR which current policy applies to your classification and request. If your employer has no clear temporary-location form, ask for the review route in writing. A colleague’s earlier approval may have involved a different state, role, employer entity, or set of dates. Use it as a reason to ask a question rather than as permission for your own trip.
Build a request someone can actually evaluate
Give reviewers the worksite, travel dates, workdays, hours, duties, and return plan so they can evaluate the actual arrangement. State whether you are proposing work during a personal visit, an employer-directed assignment, or a permanent move. Describe the actual plan without deciding its legal classification yourself. If multiple addresses or states are involved, list them separately; a two-week stay is not one worksite if you intend to move between homes.
Keep private details in the approved HR channel. A reviewer may need a street address and other information, but a broad team email does not need the host’s personal address or sensitive family circumstances. Tell HR how you will provide the required detail securely. Do not invent a medical explanation to make the request sound more compelling. Where leave or accommodation is relevant, ask about the appropriate separate process.
Describe work that cannot travel with you. Examples include physical testing equipment, onsite customer duties, confidential paper records, and attendance already scheduled at the office. Explain the proposed coverage and record whether the other person accepted it. Naming a coworker in a form does not commit them to taking your responsibilities.
Also specify what happens if approval is delayed. A flight or accommodation booking deadline does not establish when your employer must complete its review. A fallback might be staying at the authorized worksite, changing travel dates, or separately requesting leave. The fallback must itself be feasible and authorized; an unapproved leave request does not solve an unapproved work-location request.
Completed request: two weeks in Portland, with a defined fallback
Mara is a software engineer at fictional Alder Instrumentation. Her current agreement permits work from her Seattle home and requires scheduled office attendance. She wants to visit family in Portland, Oregon, and work from one private study there. This is a domestic temporary-location request, not international work or a change of employer. All details and responses are invented for this example.
Her proposal covers presence in Portland from November 28 through December 13, 2026. The requested working period is November 30 through December 11: ten Monday-to-Friday workdays. Under the fictional company calendar, all ten are regular scheduled days. The request includes no weekend work, travel-time work, or work from intermediate stops. Mara plans to resume her existing Seattle arrangement on December 14.
Her completed submission reads:
Subject: Temporary Oregon work-location request — November 30–December 11
I request approval to perform my normal engineering duties from one private study in Portland, Oregon, ZIP 97205, for the ten scheduled workdays from November 30 through December 11, 2026. I can provide the full proposed worksite address through the restricted HR intake channel. My usual authorized worksite is Seattle, Washington. This is a personal family visit; I am not requesting a permanent relocation or treating it as employer-directed travel.
I propose 9:00 a.m.–5:30 p.m. Pacific time, with a 30-minute unpaid lunch and eight scheduled work hours daily: 80 hours across the requested period. Seattle and Portland use the same local time during these dates. I will remain available for the normal team meetings and record work time through the existing process. This proposal does not request overtime or change any applicable timekeeping rule.
Planned duties are simulator-test review, code changes, and the weekly engineering planning discussion. The physical sensor-bench session on December 3 cannot be performed from Portland. I have asked Jonas whether he can cover it, but he has not accepted; please treat that coverage as unresolved. I will not represent him as committed or carry lab equipment to the temporary site.
I propose using my managed company laptop, existing approved remote-access tools, and a private workspace. IT must confirm whether the site and access arrangement meet company requirements. I will not use personal devices, local printing, or new file-sharing services as a workaround.
Please identify the HR, payroll, benefits or risk, and IT reviews required, who gives final location approval, and whether any approved changes must be entered before work begins. I would appreciate a status update by November 13 so I can decide whether to retain the travel plan. That is a planning request, not an assumed approval deadline.
If the reviews or bench coverage are not complete, I will remain in Seattle and follow my current arrangement. I will not work from Oregon unless the authorized decision owner confirms the location and dates in writing. Any later change of dates, address, or scope will be submitted for review before I rely on it.
This is a complete request because it provides a bounded proposal and an honest unresolved dependency. It does not pretend to supply the employer’s tax or insurance answer. HR still needs the exact site information through its designated channel. The ten-day count supports workload planning; it does not prove exemption from a state requirement or employer policy.
Record each review, then get the final decision
Mara’s manager can assess deliverables and team coverage, but the fictional employer’s process gives HR responsibility for coordinating location clearance. Payroll reviews employer-side reporting and withholding implementation; IT reviews the proposed access setup. The company also routes workers’ compensation questions to its risk contact. These roles are example assignments, not a universal approval chain.
Here is the completed status record as of November 13. It distinguishes a person’s actual statement from the conclusion Mara would like to draw:
| Reviewer and date | What the fictional reviewer actually recorded | Status and next dependency |
|---|---|---|
| Manager, November 4 | Duties are workable remotely if December 3 bench coverage is accepted | Conditional operational support; cannot authorize Oregon location alone |
| Jonas, November 5 | Accepts the December 3 bench session and agrees to send the existing test record | Coverage accepted; the session itself has not occurred |
| IT, November 6 | Managed laptop and approved access route are acceptable in principle; full site review still needed | Conditional technical review, not a new security guarantee or final location approval |
| Payroll, November 9 | Needs final address and approved dates through HR before completing its review | Pending; no statement that withholding remains unchanged |
| HR and risk contact, November 13 | Workers’ compensation and location review remain open; final approval has not been issued | Not authorized to start Oregon work; HR owns next status update |
The table resolves one dependency: Jonas accepted coverage. It leaves other dependencies open rather than counting the number of positive replies as a majority vote. A technically workable laptop and a supportive manager do not fill the missing HR and payroll decisions. “No objection so far” is not a dated authorization.
Mara’s completed response to the review is:
Thank you for the updates. Jonas’s acceptance resolves the proposed bench coverage, but location, risk, and payroll review remain incomplete. I will retain my current Seattle work arrangement for November 30–December 11 and will not work from Oregon under this request. Please record this proposal as not activated, rather than approved or implemented. If I propose different dates later, I will submit a revised request and confirm the required reviews first.
This is a finished decision record with a mixed result: the work plan was partly viable, while the location request was not activated. It does not assert that Oregon work is unlawful, that approval would never be possible, or that the employer denied every future request. Mara keeps the worksite decision explicit instead of treating the viable work plan as location permission.

Separate payroll review from personal tax conclusions
A company’s permission to work from a state does not settle your individual tax return, and a payroll-system field is not a legal determination of residence. Give payroll the facts it requests and retain actual work-location dates. If personal filing questions arise, use current official guidance and a qualified adviser familiar with the relevant states. Do not assume a temporary visit leaves every withholding or filing obligation unchanged.
New York’s official nonresident FAQ illustrates why a simple “tax only follows my laptop” rule is unreliable. For a nonresident whose primary office is in New York, it describes telecommuting days outside the state as New York workdays unless the employer has established a bona fide employer office at that location. This New York example does not determine the tax treatment of Mara’s Washington-to-Oregon proposal.
Likewise, do not treat another employer’s withholding practice as a tax exemption. Ask payroll what it will record, when an authorized change would take effect, what information it needs from you, and how to report a date change. You are seeking an accountable implementation answer, not asking a manager to guarantee a tax outcome. Keep any personal tax advice separate from the team’s operational discussion.
If approval arrives, preserve its boundaries
For an actually approved request, keep the final written authorization with the exact worksite, start and end dates, schedule, review conditions, and return arrangement. Confirm who enters authorized HR or payroll updates and when. Do not make a false permanent-address change merely to force a system to accept a temporary site; ask for the correct process. Check the first affected record for consistency and report discrepancies through the designated channel.
Tell the relevant owner before extending the stay, changing the worksite, adding another state, or working during travel. Approval for a private study does not automatically cover a coworking space or a public network. An emergency change deserves prompt disclosure and instructions, not a concealed workaround. This remains a domestic-location process; overseas work can require a separate review entirely.
Before departure, ask one final operational question: does the written authorization actually permit work to begin, or does it still depend on unfinished reviews? If a required condition remains open, ask the decision owner whether work may begin; do not mark the condition complete yourself. Use the completed request and status record above to get a clear answer. LandOffer.ai is the publisher of this workplace guide; it does not approve work locations or administer employer payroll.



