US-Calibrated Executive Support: How to Spot the Real Thing

US‑calibrated executive support: one crisp definition

US‑calibrated executive support is a dedicated executive assistant (EA) recruited, trained, tested, and measured to operate by U.S. business norms: business‑level English and idiom familiarity, predictable overlap with U.S. working hours (declared in UTC with DST notes), calendar and inbox conventions common to American executives, and documented SLA and escalation practices you can contract against. This guide is targeted at U.S. executives and hiring leaders weighing a vendor‑run US‑calibrated EA (e.g., Aurora’s Brazil‑sourced model) vs. a stateside hire or lower‑skill LATAM VAs.

Why 'US‑calibrated' matters: concrete gaps with generic remote EAs

• Language & tone: beyond grammar: idioms, concise subject lines, and the right register for investors, boards, or legal teams.
• Timezone overlap: decisions often happen in narrow windows; you need declared overlap hours (with UTC math) and clear weekend rules.
• Calendar etiquette: U.S. calendars favor blocks for deep work, 15/30/50 meeting conventions, and explicit pre‑reads on invites.
• Escalation & follow‑through: U.S. leaders expect proactive confirmations and closed‑loop follow‑up (not open task lists).
• Security expectations: formal NDAs, role‑based access to credentials, and documented credential rotation/offboarding.

What US‑calibration looks like in practice: small examples that matter

Calibration shows up in high‑visibility moments. Below are three short, anonymized sample artifacts you should request and compare.

Sample email: board update (anonymized)

Subject: Q1 OKR readout: 10 min prep before Friday board Hi [Name], Ahead of Friday’s board, please find a 2‑slide summary of Q1 progress attached. Key ask: approve the product launch timeline (slide 2). If you’d prefer a 5‑minute pre‑brief, I’m available Thursday 4–4:30pm ET. , [EA name]

Sample meeting follow‑up: decisions and owners

Subject: Vendor call: integration decision log (15m) Decisions from today’s call: 1) Integrate v1 API by May 12: Owner: Eng Lead (Jane): Next step: Jane to share spec by May 5. 2) Pilot customer onboarding scheduled May 20: Owner: Ops (Sam): Action: Sam to confirm participants by May 8. If anything needs correction, please reply all within 24 hours; otherwise I’ll update the project tracker and block the next check‑in.

Sample travel confirmation (day‑of clarity)

Subject: Travel itinerary: NY investor meetings, May 11–13 Itinerary summary: Flight arrives 9:05am ET May 11 (LGA). Ground ETA to hotel: 10:15am. Meetings: May 11 2:00–3:00pm (Investor A, 330 Madison), May 12 10:00–11:00am (Board). Local contact: [Name, phone]. I will update you immediately for any changes; in case of flight disruption I’ll text and call your mobile and follow escalation plan A (backup itinerary+driver).

Calendar & meeting templates you can test immediately

• Invite title format: “30m: Q2 Ops sync: pre‑read attached | Decision: X”
• Agenda rule: 3 bullets max; required pre‑read file and 1 key decision listed in the invite body
• Buffer policy: 10–15 min buffers between meetings for internal transitions and travel where applicable

How Aurora operationalizes US‑calibration (vendor specifics & what to verify)

Aurora builds US‑calibration with selective EA recruiting, business‑English testing and live roleplays, an explicit 30/90 onboarding cadence, SLA reporting, and replacement workflows. Operational guarantees like a '48‑hour launch' or specific replacement windows are vendor‑specific: ask your Aurora sales rep for availability and exact contract language. For practical guides on working with remote EAs, see Remote Executive Assistant: How It Works and Why It Often Works Better and hiring guidance at How to Hire an Executive Assistant Who Actually Frees Up Your Time.

Recruiting & language vetting: what to require

• EA experience filter: request CVs showing ≥2 years in EA/Chief‑of‑Staff style roles (not task‑only VAs).
• Language: ask for a recent business English assessment (CEFR B2/C1 or equivalent) and a recorded roleplay where the EA drafts a board email and schedules a complex meeting.
• References & background: require documented reference checks and a summary of background‑check scope.

Onboarding & 0–90 day milestone plan (copyable)

0–7 days (initial launch): daily check‑ins first week; calendar audit; shared working hours; 3 approved email templates. Day 8–30 (stabilize): weekly playbacks, decision log template in use, inbox rules applied, travel SOP drafted. Day 31–90 (mature): weekly KPI report, cadence with stakeholders, proactive items queued, maturity review and optimization plan documented. Require these deliverables in your SOW and use them as acceptance criteria during the pilot.

SLA targets and example contract language (negotiation‑ready)

Note: remedies (credits, free ramp time) differ by vendor. If uptime or response is mission‑critical, negotiate an explicit credit schedule (e.g., percentage credit for missed SLA buckets) and require proof logs/audit capability.

Timezone math: BRT vs U.S. timezones (DST caveat)

Brazil Standard Time (BRT) is typically UTC‑3. U.S. Eastern Time (ET) is UTC‑5 in standard time and UTC‑4 in Daylight Saving Time (DST). Practical overlap examples (subject to DST shifts): - When ET = UTC‑5 (standard): BRT (UTC‑3) is 2 hours ahead: typical overlap of most business hours is ~6–8 hours. - When ET = UTC‑4 (DST): BRT is 1 hour ahead: overlap increases; expect ~7–9 hours overlap on typical 9–5 windows. Pacific Time (PT) is UTC‑8 standard / UTC‑7 DST; overlap with BRT typically yields 4–6 useful hours depending on the schedules. Always get declared overlap hours in UTC from the vendor and note DST handling in the contract.

Pricing signals & illustrative packages (use as a comparison framework)

Exact pricing varies by vendor, scope, seniority, and billing model. Below are illustrative monthly bands (qualified estimates for comparison; verify with sales): - US‑based senior EA (full‑time W‑2/contractor, fully loaded): $8,000–$15,000/month (salary, taxes, benefits/contractor premium). - US‑calibrated dedicated EA (vendor model, higher EA skill, SLA + operations): $3,000–$7,000/month depending on hours and level. - General LATAM/VA task worker (lower EA specialization): $800–$2,500/month. Typical add‑ons: launch/placement fees ($0–$2,000), premium travel support or after‑hours coverage (extra retainer), and expedited replacement guarantees. Use this framework to compare 'what you get': dedicated hours, scope (calendar + inbox + travel vs. project coordination), account management time, and SLA guarantees.

Sample math: if a senior U.S. exec values recovered time at $400/hr and a calibrated EA returns 4–6 hours/week (~16–24 hrs/month), the initial monthly cost can pay for itself quickly. Always ask for client references and concrete before/after metrics during procurement.

Benchmark: Aurora vs U.S.-based EAs vs LATAM VAs (compact comparison)

Short anonymized case studies (attributed metrics and quotes)

• VP of Sales, Series B SaaS (2024 pilot): consolidated recurring meetings, established protected prospecting blocks, recovered 4–6 hours/week for the VP within six weeks. Quote: “Within a month we stopped losing time to calendar friction: the EA’s decision log made follow‑ups disappear.”
• Founder, hybrid schedule (roadshow, Q2 2024): vendor managed multi‑city travel and on‑the‑day changes; zero missed investor calls across three cities and one same‑day flight disruption resolved with backup transport in under 90 minutes. Founder quote: “Travel used to derail a day; this time we kept every investor slot and closed the round.”
• COO, scaling operations (2023 engagement): instituted meeting agendas and a leadership decision log; reduced follow‑up clarification emails by ~50% and shortened weekly leadership meeting time by ~15% after 8 weeks.

Security & a sample SOW/data‑handling clause you can copy

Ask for an NDA and require role‑based access via a password vault (LastPass/1Password) or SSO. Require documented background checks and an operations runbook that describes credential rotation and offboarding. Below is a short sample SOW/data‑handling clause to include in procurement documents.

Sample SOW clause (copy‑ready): “Vendor will: (a) sign Customer’s standard NDA prior to work commencement; (b) assign named EA(s) and provide background‑check summaries; (c) provision access via Customer‑approved password vault or SSO; (d) implement credential rotation and offboarding within 24 hours of EA removal; (e) provide monthly audit logs of access events on request. Vendor makes no legal or regulatory compliance guarantees: Customer remains responsible for PHI/regulated data decisions and must explicitly designate any data that is off‑limits.”

How to evaluate vendors quickly: checklist & interview script

1. 1Request a 30/90 onboarding plan and named operations contact; require day‑7/30/90 deliverables in writing.
2. 2Ask for English assessment evidence and a 15–20 minute live roleplay where the EA drafts a board email and schedules a complex multi‑attendee meeting.
3. 3Get declared overlap hours written in UTC and verify DST handling; ask for concrete weekday/weekend availability rules.
4. 4Review SLA metrics and replacement policy; require a rematch timeline in the contract and define remedies (free ramp hours or credits).
5. 5Pilot for 2–4 weeks on the core scope (calendar + inbox triage + travel) with a clear exit/replace clause and acceptance criteria tied to the onboarding milestones.

Quick start: pilot options and CTAs

If you want a low‑risk test, ask vendors for: (1) a 48‑hour launch option (vendor‑specific: verify availability and exact scope), (2) a calendar/inbox audit to establish priorities, and (3) a 2–4 week pilot limited to core EA tasks with written acceptance criteria tied to day‑7/30/90 deliverables. For a no‑commitment start, request a 90‑minute executive support audit or a short roleplay session with the candidate; Aurora can provide these evaluation activities through its sales team.

Final checklist: what to get in writing before you sign

• Named EA and operations contact, with CV and reference summary.
• Declared overlap hours in UTC and DST handling.
• English proof: assessment result + recorded roleplay artifact.
• Onboarding milestones for day 7/30/90 (deliverables and acceptance criteria).
• SLA matrix with remedies (credits/free ramp) and a rematch/replacement timeline.
• Security controls: NDA, password vault/SSO, background‑check scope, and operations runbook access.