Part of our guide: How to manage a remote team in the Philippines
Communication problems cause more friction in remote assistant relationships than skill gaps do. A message sent on the wrong channel, an urgent request buried in email, an unclear instruction that leads to a day of wasted work — these are process problems, and they're solvable with a few explicit norms.
This guide covers the norms we recommend: which channel to use for what, response-time expectations, how to escalate, and how to write instructions that work asynchronously.
Why norms matter more when you're remote
In an office, a quick "got a sec?" resolves ambiguity. Remotely, every question costs a message and a wait. Even when your assistant's schedule overlaps much of your day, you're not physically nearby, and you're often in meetings when they need you. Clear norms reduce the number of questions and make the remaining ones faster to answer.
Norm 1: One channel per purpose
Agree which tool to use for which kind of communication. A common setup:
| Purpose | Channel |
|---|---|
| Urgent, needs you within the hour | Phone call or text |
| Quick questions, same-day | Slack or Teams direct message |
| Task assignments and tracking | Task tool (Asana, Notion, ClickUp, Todoist) |
| Detailed context, decisions, external-facing drafts | Email or shared doc |
| Weekly update | Written pre-read before the check-in |
The specific tools matter less than consistency. Write the table down and share it.
Norm 2: Response-time expectations
Ambiguity about response times creates anxiety on both sides. Set expectations explicitly:
- Your assistant to you: acknowledge messages within a set window during their working hours, even if the full answer takes longer.
- You to your assistant: decide what you can realistically commit to. "I'll reply to DMs by end of day; call me if it can't wait" is a perfectly good norm.
Also agree what happens when you don't respond: when can the assistant proceed on a recommended default, and when must they wait?
Norm 3: Define "urgent"
Everyone's definition of urgent differs. Write yours down. For example:
- Urgent: anything involving a customer escalation, a board member, a same-day flight change, a legal or financial deadline today.
- Not urgent: scheduling for next week, routine vendor questions, internal meeting moves.
Your assistant can then route correctly without guessing.
Norm 4: Decision rights
Clarify what the assistant can decide without asking:
- Decide and do: reschedule internal meetings within the same week; book travel within policy; file routine email.
- Decide and tell: decline vendor pitches; move a recurring meeting; respond to routine requests on your behalf with standard language.
- Recommend and wait: anything involving money above a set threshold, external commitments, sensitive relationships or new situations.
This framework, revisited as trust builds, prevents both bottlenecks and overreach.
Norm 5: Write instructions that stand alone
Async instructions must make sense without a conversation. A good instruction includes:
- What: the task, specifically.
- Why: the purpose, so the assistant can make good choices.
- When: the deadline.
- Done looks like: the expected output.
- Constraints: budget, preferences, people to include or avoid.
Compare: "Set up a dinner with the Acme folks" versus "Book dinner for four with Acme's CEO and CFO the week of the 14th, near their office. Purpose: relationship-building after the pilot. Budget per person within our policy. Somewhere quiet enough to talk. Send me two options."
Norm 6: Batch your requests
Ten separate messages during the day fragment your assistant's focus just as interruptions fragment yours. Where possible, batch non-urgent requests into your task tool or a single end-of-morning message.
Norm 7: Close the loop in writing
Ask your assistant to confirm completion briefly in the original thread or task — "Done: dinner booked at X, invite sent." That creates a record and saves you checking.
Norm 8: Handoffs at the start and end of the day
If your assistant's shift starts before yours or ends after, short written handoffs help:
- Start-of-day note: what they handled before you came online, what needs you today.
- End-of-day note: what's open, what's waiting on whom, anything they'll pick up tomorrow.
Even when hours overlap fully, an end-of-day note is a useful habit.
Norm 9: Use recordings for anything visual
When a process involves clicking through a tool, record a short screen-share instead of writing a long explanation. Tools such as Loom or your video platform's recording feature work well. Ask the assistant to turn recordings into written SOPs — see how to write an SOP for your assistant.
Norm 10: Revisit the norms quarterly
As the role grows, norms need updating. Add a quarterly agenda item to your weekly check-in: "Are our communication norms still working?"
Overlapping versus non-overlapping hours
Most leaders agree a schedule that fits their needs and budget, usually with some overlap during the US business day. Some prefer a shift that starts earlier so overnight email is triaged before they begin. If overlap is partial:
- Put the most collaborative work in the overlap window.
- Rely more on written handoffs.
- Agree an emergency contact method for the non-overlap window.
Our time-zone guide covers scheduling patterns.
Sample norms document
How we work together - Urgent (needs me within the hour): call/text. - Same-day questions: Slack DM. I reply by end of day. - Tasks: Asana. Every task has a due date and a "done looks like." - Weekly: pre-read by Thursday; check-in Friday 25 min. - You can: reschedule internal meetings this week; book travel within policy; decline vendor pitches. - Ask first: anything over our spend threshold; external commitments; anything involving the board. - End-of-day: short note of open items.
When norms break down
You'll know norms need attention when you see repeated patterns: urgent items arriving by email, duplicated requests across channels, or tasks without due dates. Don't fix it with a reprimand; fix the norm. Ask your assistant what's confusing, adjust the one-page document and re-share it. Norms that both sides helped write are the ones that stick.
Norms for part-time and full-time schedules
Your norms should match the hours your assistant actually works. Most remote assistants work part-time, typically around 20 hours a week, or full-time, typically around 40 hours a week, and the two need slightly different rules.
With a part-time or full-time assistant, the biggest risk is over-communication. When someone is available all day, it's tempting to send every thought as it occurs to you, which turns their day into a stream of interruptions. Batch non-urgent requests into a task list, keep chat for genuinely same-day questions and protect a few hours of the assistant's day for focused project work.
With a part-time assistant, the biggest risk is the gap between blocks. A request sent just after their shift ends may sit until the next day, and that's fine if everyone expects it. Make three things explicit:
- What waits. Anything that can be handled in the next block goes in the task list, with a due date.
- What doesn't. Define the small set of truly urgent items and what happens when one comes up outside their hours. Often the answer is that it comes back to you, and that's acceptable.
- What they find on arrival. Ask yourself to leave a short note at the end of your day with priorities for the next block. Two or three lines are enough.
Writing requests that work across time zones
The single most useful async skill is writing a request that can be completed without a follow-up question. A simple template helps:
What: Book a 45-minute meeting with Dana Reyes next week. Why: Review the Q3 vendor proposals before the budget meeting. When: Any afternoon Tuesday through Thursday; avoid Friday. Done looks like: Invite sent with the proposal PDFs attached and a one-line agenda. Constraints: Dana is in Pacific time. Don't move my 2 p.m. Wednesday call.
It takes a minute longer to write than "set up time with Dana," but it saves a round trip that could cost a day when you and your assistant are working different hours.
Encourage your assistant to use the same structure in reverse when they need a decision from you: the question, the options they see, their recommendation and the deadline. A request like "The hotel is sold out; options are A or B; I recommend A because it's closer to the venue; I need an answer by noon to hold the room" can be answered in one word.
Building trust through visible work
Async relationships work best when progress is visible without anyone having to ask. Three habits make this easy:
- A shared task board where every request lives, with a status anyone can check.
- An end-of-day note with done, in progress, blocked and questions.
- A weekly summary that highlights the most important outcomes and anything that's drifting.
These aren't about surveillance. They give you confidence that work is moving, and they give the assistant a record of what they've delivered, which is useful at every review.
Signs your norms need a refresh
Revisit your norms when you notice any of these: the same question being asked more than once, urgent messages arriving through the wrong channel, tasks completed late because the request was unclear, or either of you working outside agreed hours to keep up. Each is a small signal that the written agreement no longer matches how you actually work. A 20-minute conversation to update it is almost always enough. Growth is another trigger: when an assistant moves from a part-time to a full-time schedule, or takes on work for a second leader, rewrite the norms rather than patching them.
Tools are secondary
Teams sometimes look for a tool to fix communication problems. Slack, Teams, Asana, Trello, Notion and plain email can all work. What matters is that each has a clear purpose, everyone uses it the same way and the norms are written down. Choose the simplest set of tools your team already uses, then spend your energy on the habits above.
Quick answers
Do we really need a written norms document? Yes. One page prevents dozens of small misunderstandings, and it's easy to share with new team members.
Key takeaways
- Assign one channel to each purpose and write it down.
- Define urgent explicitly.
- Spell out decision rights in three tiers: do, do and tell, recommend and wait.
- Write instructions that include what, why, when, done and constraints.
The bottom line
Remote assistant relationships run on explicit norms: one channel per purpose, clear response times, a shared definition of urgent, written decision rights, stand-alone instructions and daily handoffs. Write them down in a single page, share it, and revisit it as the role grows.
Want a dedicated assistant who already knows this playbook?
ExecWing places dedicated, managed assistants from the Philippines, Mexico and Colombia with US leaders, on a part-time or full-time basis (typically 20- or 40-hour workweeks). Month-to-month, quoted per role. See pricing or how it works.
Schedule a Free Consultation