Virtual Assistant Provider guide
A founder inbox decision digest that does not hide the difficult messages
A practical founder inbox decision digest routine for a Philippines-based virtual assistant, with evidence, checks, handoff rules, and a manager-owned decision boundary.
Key takeaways
- a short digest that links each source message, states the requested decision, names the deadline, and separates drafts from owner-only calls
- Group by decision owner, not by sender.
- The assistant can classify, summarize, and draft. They should not accept terms, commit money, resolve a personnel matter, or speak for the founder without a written rule.
- End with decisions due today, replies ready for approval, waiting items, and the first item for tomorrow.
Start with the real problem
A crowded inbox is rarely one problem. It contains routine replies, decisions only the founder can make, quiet risks, and messages that simply need filing. For Virtual Assistant Provider, the useful routine is the one that leaves the next person with a reliable record—not a vague “done” message.
Define a finish line
Treat the completed founder inbox decision digest as a short digest that links each source message, states the requested decision, names the deadline, and separates drafts from owner-only calls. Write that definition beside the recurring task so the assistant and reviewer are checking the same outcome.
Run the work in a visible sequence
Begin from the approved source, record the current state, prepare the permitted action, run the checks, and preserve the result. When information conflicts or a required approval is absent, stop in a visible waiting state.
- Group by decision owner, not by sender.
- Quote the request briefly instead of rewriting its meaning.
- Keep “no action” messages out of the decision list.
Keep judgment with its owner
The assistant can classify, summarize, and draft. They should not accept terms, commit money, resolve a personnel matter, or speak for the founder without a written rule.
Review the first five examples
Demonstrate one example, then review the next four against the source. Record corrections by cause: missing input, unclear instruction, access gap, execution error, or late owner decision. If the founder keeps reopening the inbox to understand the digest, sample five entries together. The likely repair is better context, not a longer report.
Protect accounts and source material
Use a named account, multi-factor authentication, and only the permissions the lane requires. Keep sensitive details in approved systems and link to them when possible. NIST’s framework is useful for assigning governance and response ownership; CISA’s guidance supports stronger sign-in controls.
Close the day with a usable handoff
End with decisions due today, replies ready for approval, waiting items, and the first item for tomorrow. The handoff should tell the next reader what changed, what remains safe to do, and which decision cannot be delegated.
Further reading
daily planning guide, handoff guide, NIST Cybersecurity Framework 2.0
Provider questions to copy
"Can you show how this role is screened, trained, checked each week, and replaced if fit is poor?"
"Can we start with a small task list before we expand the role?"
FAQ
Who should own the founder inbox decision digest?
A virtual assistant can own repeatable preparation and checks. A named manager owns exceptions, approvals, and business judgment. The assistant can classify, summarize, and draft. They should not accept terms, commit money, resolve a personnel matter, or speak for the founder without a written rule.
What evidence should remain?
Keep the source, action, check result, timestamp, exception, and reviewer decision. Store sensitive material only in its approved system.
When can review move from every item to a sample?
Only after the lane is stable across normal and exception cases. Return to full review after a serious miss, instruction change, or permission change.
Sources and notes
These sources are included as planning references. They do not replace legal, tax, security, or HR advice.
- NIST Cybersecurity Framework 2.0: Use named ownership, protection, detection, response, and recovery outcomes when a routine touches business systems.
- CISA More than a Password: Protect work accounts with multi-factor authentication and an explicit recovery owner.
- Google Search Central: Creating helpful, reliable, people-first content: Make each operating record useful to the person who must review or act on it.