Oracle Role is now a Take/Pass/Ask desk — kill slow leads fast with locked filters. This post explains how we used to decode roles manually.

Blogchecklist

Remote vs Onsite: Clarifying Questions Checklist

Contractor checklist: clarify remote, hybrid, or hard onsite before you apply — days in office, which site, travel pay, time zones, equipment, and whether ‘flexible’ is written in the SOW.

"Remote," "hybrid," and "flexible" are marketing words until you nail the operating rules.

Contractors lose weeks when a "remote-friendly" posting resolves to four days in a named office after kickoff. Use this checklist before you rewrite a CV or quote a rate.

OracleRole flags hard onsite / office-mandatory language on the homepage decoder. This article is the clarifying-questions layer on top.

Remote vs onsite clarifying questions checklist

How to use this checklist

Score the JD in one pass, then send unanswered items in writing. One vague answer is a conversation. Several vague answers on location usually mean assume onsite until proven otherwise.

Pair with the 2026 red-flags checklist when Dutch fluency, visa, agency, or urgency appear alongside location.

Career and offer guides consistently recommend getting arrangement details in writing (offer letter or SOW): expected office days, assigned site, travel, and whether the deal can change.

The checklist

1. What does "remote" mean here?

Ask: Is this fully remote, hybrid, or remote-eligible with periodic onsite?

Look for in the JD: "onsite only", "no remote", "must be based in…", hybrid that lists five office days, "remote" with a mandatory city.

Why it matters: Postings use remote loosely. Hard onsite is a first-class constraint for freelancers — the decoder treats office-mandatory language as a red flag for a reason.

2. How many days onsite — and who decides?

Ask: How many days per week or month are expected in office? Fixed policy, team habit, or manager preference?

Why it matters: "Hybrid" that is manager-discretionary often drifts. Fixed 2/5 is negotiable; "come in when needed" without a cap is a commute tax.

3. Which office am I attached to?

Ask: Which site is the home office? Can that change? What happens if I move cities or countries?

Why it matters: Hybrid attached to Office A is a different job than "any EU hub." Cross-border limits show up late if you do not ask.

4. Time zones and core hours

Ask: Are there mandatory core overlap hours? Fully async, or daily standups in a specific zone?

Why it matters: Remote with 06:00 standups is not the same product as async delivery. For contractors, schedule control is part of the engagement — not a perk paragraph.

5. Travel and offsites

Ask: Are team offsites or client visits required? How often? Who pays travel, hotel, and non-billable transit time?

Why it matters: Occasional travel can be fine. Unpriced travel eats margin. Get reimbursement and billable vs non-billable rules in the SOW.

6. Equipment, tools, and workspace rules

Ask: Who provides laptop and licenses? Any camera-on / dedicated-desk expectations? Stipend or expense process?

Why it matters: Offer and remote-work checklists treat equipment and reimbursements as first-order cost questions. Contractors should also watch whether tool mandates imply employee-like control — clarify delivery independence without turning the call into legal advice.

7. Can the arrangement change after start?

Ask: Is remote/hybrid probationary? Review date? Can policy force a return-to-office mid-contract?

Why it matters: Verbal "we're flexible" evaporates. Ask where the exception or cadence will be documented.

8. Language and permit gates tied to site

Ask: Is onsite required for language (e.g. Dutch-facing stakeholders) or for access/compliance — or habit?

Why it matters: OracleRole also surfaces Dutch fluency and visa/work-permit friction. Location + language + permit often travel together; price or pass as a bundle.

Quick pass/fail

Clarity Suggested move
Fully remote + time zone + no surprise travel Decode, quote, apply
Hybrid with fixed days + named office + travel rules Clarify remaining gaps; price commute
"Flexible" with no days/office/travel answers Written clarification before deep process
Hard onsite / no remote + you will not relocate Pass, or price discovery only

Sample clarifying note (short)

Thanks — before we schedule further: is the role fully remote, hybrid, or onsite? If hybrid, how many days, which office, and who covers travel? Happy to confirm time-zone overlap. I keep location terms in the SOW so kickoff stays clean.

Decode it on OracleRole

Paste the JD. If you see Hard onsite / office-mandatory (and related Dutch / visa flags), do not argue with the H1 — run this checklist and put answers in writing.

Then reuse the pitch angle: address location up front so you waste zero interview cycles.

Open the free decoder →

For pricing location risk into the rate conversation, see Contractor Rate Negotiation from a Decoded JD.

Related

Take/Pass/Ask Desk

Kill slow leads fast. Score each inbound Take / Pass / Ask one against your locked kill-filter + get send-ready reply. No re-prompting.

Open Oracle Role desk →