Outsourced CompanyPowered by StealthAgents

Philippines staffing guide · Published

Build an executive inbox delegation log for an outsourced executive assistant

An assistant who replies from the principal's inbox makes commitments the principal may never see. A delegation log records what was sent, what was held, and who owns the next step.

Build an executive inbox delegation log for an outsourced executive assistant operations illustration

The short answer

Define the categories the assistant may answer alone, log the commitment before the message leaves, and review the log weekly with the principal. Sensitive threads need a restricted path that is defined and practiced before the first one arrives.

Decide which messages may leave the inbox

An executive inbox contains messages that look routine but carry commitments the principal has not approved. Write down the categories the assistant may answer alone, the categories that need a draft, and the categories that always go to the principal.

Use examples from the last month, not abstract labels. A category with no example will be interpreted differently by every assistant.

Scheduling confirmations, receipt acknowledgments, and requests for publicly available documents usually sit in the first group. Messages about price, personnel, legal matters, or public statements usually sit in the last. The middle group is where most risk lives, because a polished draft can still commit the principal.

Name who reviews the draft before it is sent. Update the list when a real message does not fit any group, and tell the assistant why.

Log the delegation before the send

The log should exist before the message leaves, not after someone asks who replied. Record the thread, the sender, the category, the action taken, and the time.

If the assistant sent a reply, note the exact commitment made. A log built from sent mail after the fact misses the drafts that were never sent and the calls that were never logged.

Keep the log short enough to maintain on a busy day. Five fields are usually enough, and a link to the thread replaces a long summary. Do not duplicate the principal's entire inbox.

The log is an index of decisions, not a second mail store. Review the fields with the assistant after the first week and remove any that nobody uses.

Write the handoff note the owner will read

When a thread moves to the principal, the handoff note should state what is needed and by when. Include the requester's deadline, the history that matters, and a recommended response if the assistant has one.

Separate facts from recommendations so the principal can accept the facts and change the advice. A note that only says please review forces the principal to reread the whole thread.

For sensitive threads, keep the handoff inside the approved system rather than a personal message. Say who else has seen the thread and whether a draft already exists. Flag any commitment the assistant made earlier so the principal does not contradict it.

The note should let the principal reply in one pass, not three. Mark the note with the date and the name of the person who prepared it.

Set a rule for waiting and chasing

Delegated work stalls when nobody owns the follow-up. Set a waiting period by category, then have the assistant send one clear chase with the original request attached. After the second chase, move the item to the principal or close it with a reason.

A thread that is chased forever trains requesters to ignore the first message. The point of the limit is to return the decision to the principal, not to punish the requester.

Record the chase dates in the log so the principal can see the effort. Do not let the assistant apologize for a delay the principal caused; state the new date plainly. If the principal is the bottleneck, the log should show it.

That visibility is uncomfortable but it is the point of keeping a delegation record. Review the chase pattern monthly and remove any step that adds delay without information.

Handle sensitive threads outside the log

Some messages should never appear in a shared delegation log. Personnel complaints, legal threats, medical details, and board matters need a restricted path with named access. Define that path before the assistant encounters the first one.

The log can record that a restricted item exists without describing its contents. Name the restricted path in the assistant's written instructions and test it once.

Access to the restricted path should follow the client's own policy, not the assistant's convenience. Use named accounts, not shared passwords, and remove access when the role changes. Test the path with a dry run so the assistant knows where to send a sensitive thread under pressure.

A policy nobody has practiced is a guess. Record the access review date so the client can see when it was last checked.

Review the log weekly with the principal

A weekly review should cover what the assistant sent, what waited too long, and what categories caused disagreement. Read two or three actual messages together and ask whether the assistant's judgment matched the principal's intent. Update the category list when the answer is no.

End the review with one written change rather than a general agreement to do better. The review is a calibration session, not a performance scorecard.

Track the number of drafts returned for changes and the number of threads that missed a deadline. These are signals about unclear rules, not only about effort. If a category keeps producing rework, rewrite the rule or move it to the principal.

A log that is reviewed but never changes is documentation of a problem, not a fix. Bring one returned draft to the review and ask what rule would have prevented it.

The review should include one thread the assistant chose not to answer. Ask what made it risky and whether the category list explains that decision. If the assistant cannot point to a rule, the boundary is still implicit and will not survive a busy week.

Write the missing rule down and test it on the next similar thread. A boundary that lives only in one person's judgment cannot be covered during leave.

Questions to copy for the sales call

  • "Which inbox categories may the assistant answer without a draft?"
  • "What commitment was made in the last message the assistant sent?"
  • "Where does a sensitive thread go, and who can access that path?"
  • "Which threads have waited past the agreed follow-up window?"

Sources

Common questions

Should the assistant use the principal's login?

No. Use a named delegated account with the minimum access needed. Shared credentials remove accountability and make it impossible to tell who sent a message.

Can the log live in a spreadsheet?

Yes, if the client approves the location, access is restricted, and a backup exists. The log should not sit in a personal drive or an unmanaged chat channel.

What counts as a commitment?

Any statement that creates an expectation about a date, a price, a meeting, a deliverable, or a decision. Record the exact wording when the assistant sends it.

How often should the categories change?

Review them at the weekly session and update when a real message exposes a gap. Keep the change small and tell the assistant which example now belongs in which group.

Philippines staffing intake

Define the position before hiring begins.

Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.

Contact Us