How do I get remote terms confirmed during onboarding?

Ask for days per week, core hours, anchor days, and who can change them, then send a dated email restating the answer. A confirmation email is the artifact that survives a manager change; a verbal yes does not.

What should the 90-day criteria include?

Specific deliverables, the metric or evidence for each, the owner who evaluates them, and a mid-point checkpoint date. Write them with your manager and confirm by email so the criteria are not invented after the fact.

How do I show output when nobody sees my work?

Publish it. Ship one measurable item in weeks two to four and post the before and after numbers in the team channel, then send a short weekly note listing what shipped and what is blocked.

What if access delays make me look slow?

Document the dependency, not the excuse. Send one note naming the blocked item, the owner, and the date raised, then request a written deadline adjustment if it persists, so the delay is attributed correctly. Log the ramp checkpoints and the week-one artifacts in the application tracker so the 30-day pilot has a dated trail.

Remote Onboarding: First 30 Days

Remote onboarding fails in silence: nobody tells you the real process, decisions happen in meetings you never see, and your ramp gets read as low output. Fix it with structure, not effort.

Week 1: Build the Comms Map

Take every 1-on-1 with camera on. Ask: who defends the team, what ships first, what gets punished, where decisions happen.
Get the meeting calendar and the async channels: standup, weekly team, client cadence. Remote teams run on calendars, not doors.
Write your own onboarding doc: decisions, glossaries, tools, and the names behind them. It becomes your first visible win.

Output Visibility

Ship one small, quantifiable fix in weeks 2-4 (a doc, a script, a dashboard). Announce it in the team channel with before/after numbers. Remote output gets counted by what is visible, not what is done.

The 30-Day Pilot

Core hours, response SLA, and anchor days: get them in writing in week one. The remote proposal generator formalizes the pilot, and the remote policy guide shows how managers really enforce hybrid.

Ramp Proof

Ask for the 90-day success criteria in writing; co-write them with your manager. Those lines become your first self-assessment language (see the performance season guide). Onboarding chaos is not your fault; self-structure reads as seniority.

Ask For These Items In Week One

Remote ramp problems are usually missing information, not missing skill. Ask for nine things in the first week, and write the answers into your own document so nobody has to repeat them.

The team calendar for the next month, including recurring meetings.
The async channels: where decisions are posted, where blockers are raised.
The on-call and coverage rotation, with the response expectation.
The definition of done for your role: review, merge, deploy, or client sign-off.
The names behind each function, plus who approves time off.
The access list you still need, with the owner of each request.
Equipment and stipend expectations in writing.
Core hours, anchor days, and the remote arrangement, in writing.
The 90-day success criteria, co-written with your manager.

Send the remote terms request with the remote work proposal, and confirm the success criteria by email after the conversation. Criteria you co-write become your first self-assessment language later.

Artifacts That Make The Ramp Visible

Remote output is counted by what is visible. Produce three artifacts in the first thirty days, each small and each announced.

An onboarding doc you write yourself: decisions, glossary, tools, and the names behind them. It is also evidence you created process.
One measurable fix: a document, a script, a dashboard, or a broken test, posted with before and after numbers.
A weekly note in the team channel: what shipped, what is blocked, what you need.

Frame the numbers yourself rather than waiting for someone else to measure them. Keep the same wording for the first review with the performance review self-assessment generator, and if scope slips because of access or unclear ownership, request a written extension with the deadline extension request instead of absorbing it silently.

The Failures That Happen Quietly

Remote onboarding fails in ways that look like poor performance until you name them.

Invisible decisions: choices happen in meetings you were not invited to, then arrive as instructions.
Undefined ramp: nobody wrote the 90-day criteria, so expectations are inferred from other people.
Access lag: permissions arrive late, and the delay is read as slow output.
Time-zone drift: response expectations are unclear, so you are rated on availability rather than delivery.
Undocumented remote terms: a verbal flexibility reverses at the first manager change.

Name each one in writing once, with the date and the specific blocker. Where a ramp gap is health- or disability-related, request the adjustment through the interactive process with the ADA accommodation request generator rather than working around it quietly. Work the longer arc inside the workplace, remote and review section.

Week	Ask For	Artifact You Produce
Week 1	Calendar, channels, access list	Your own onboarding doc
Week 2	Definition of done and on-call rule	First shipped item with numbers
Week 3	Written remote terms and core hours	Weekly team note in the channel
Week 4	90-day criteria co-written	Ramp summary your manager can quote

For the current text behind these numbers, start with the California job exit rules page and the New York job exit rules page, along with the At-Will Employment definition. Those sources state the rule in full; this page only points at them.

Frequently Asked Questions

How do I get remote terms confirmed during onboarding?: Ask for days per week, core hours, anchor days, and who can change them, then send a dated email restating the answer. A confirmation email is the artifact that survives a manager change; a verbal yes does not.
What should the 90-day criteria include?: Specific deliverables, the metric or evidence for each, the owner who evaluates them, and a mid-point checkpoint date. Write them with your manager and confirm by email so the criteria are not invented after the fact.
How do I show output when nobody sees my work?: Publish it. Ship one measurable item in weeks two to four and post the before and after numbers in the team channel, then send a short weekly note listing what shipped and what is blocked.
What if access delays make me look slow?: Document the dependency, not the excuse. Send one note naming the blocked item, the owner, and the date raised, then request a written deadline adjustment if it persists, so the delay is attributed correctly. Log the ramp checkpoints and the week-one artifacts in the application tracker so the 30-day pilot has a dated trail.