How to build a shared-inbox delegation matrix for a Philippines executive assistant

The route-local operating guide

Start by defining the population and the cutoff. For this shared executive inbox, the working record contains mailbox, sender class, message purpose, sensitivity, permitted action, reply template, approval rule, escalation route, response target, and review date. Keep links to approved systems instead of copying restricted material into chat, personal files, or a convenient spreadsheet. Mark unknown, conflicting, and not-applicable values explicitly. That discipline lets the next reviewer reproduce what the specialist saw and prevents a blank field from being interpreted as a negative answer.

The routine is designed for a founder or operations leader delegating email work. The Philippines-based specialist may gather permitted evidence, compare it with a written rule, prepare a draft or proposed state, and route an exception. Final interpretation and approval remain with the executive or delegated inbox owner. Write those permissions beside the task. Job title, experience, urgency, or repeated prior approval should not silently expand authority.

Use a hold when a message falls outside the approved sender, topic, wording, or commitment boundary. A hold is an active state with a reason, current owner, permitted next action, and review time. It is not a forgotten item or a way to avoid reporting unfinished work. Work that can safely continue—such as collecting an existing record or checking a system identifier—should be named separately from the decision that cannot proceed.

A practical case shows the boundary. A supplier asks whether a proposed fee is acceptable while the executive is offline. The assistant may label the thread, collect the contract and prior correspondence, and draft a neutral acknowledgment. Price acceptance remains held for the executive. The record shows why the thread was not sent through the ordinary vendor template. This is the value of a bounded support lane: preparation becomes faster because the specialist does not need to improvise the consequential decision, and the owner receives a small question supported by the relevant evidence.

Build privacy and security into the ordinary path. Private correspondence may be exposed too broadly; a draft may be mistaken for authority; calendar, price, employment, legal, or customer promises may be made without context; and forwarding can duplicate restricted information in another tool. Give each person an individual account, least-necessary permissions, and an approved place for evidence. Never place passwords, full identity documents, health information, financial details, or privileged material in a general handoff merely to make the queue look complete.

Use the cited first-party guidance as a starting point, not as a substitute for the client’s current policy or professional advice. The source may establish a control principle while the company’s systems, jurisdiction, contract, risk, and customer promise determine the operating rule. Record the source, retrieval date, proposition supported, and limitation. If guidance changes, route the affected public or internal wording for review instead of silently swapping a link.

Quality review should sample both routine completions and held exceptions. Check source identity, cutoff, required fields, authority, evidence, destination state, and communication. Record defects by type and exact location. Do not turn a small or risk-weighted sample into a universal score for a worker or team. Counts need denominators, and a fast queue does not establish accuracy, customer outcome, legal compliance, or business impact.

Completion means sample sent items agree with the matrix, held threads show an owner and next review time, individual accounts appear in the audit trail, and revoked permissions no longer work. A sent message, saved form, checked box, or reassignment is only an intermediate event unless the approved procedure defines it as the final state. Reopen the destination through the reader or operator path, preserve the verification time, and keep any limitation visible.

Review the routine after ordinary cases and at least one real exception. Look for repeated missing fields, avoidable returns, unclear approval signals, excessive access, and decisions that wait without an owner. Improve the intake or rule that produced the friction. Do not respond by giving the support role broader informal discretion. A narrow lane with trustworthy evidence is easier to expand than a fast lane whose decisions cannot be explained.

Set up the controlled work lane

Open one record for each eligible item and identify the authoritative system, time zone, cutoff, and version of the rule being applied. The minimum fields for this lane are mailbox, sender class, message purpose, sensitivity, permitted action, reply template, approval rule, escalation route, response target, and review date.

Use a clear ready state. An item is ready only when identity, scope, source access, and the normal action are known. Reject duplicate records and preserve prior history instead of creating a fresh item to escape an old exception.

Route decisions without losing momentum

Preparation stays with the support specialist; approval stays with the executive or delegated inbox owner. The specialist should package the exact observation, the applicable rule, competing evidence, available options, and the one decision required.

When a message falls outside the approved sender, topic, wording, or commitment boundary, stop the consequential action. Record safe preparation that can continue, the unblock owner, and the next review time. Never convert silence, an emoji, a calendar deadline, or an earlier decision on another item into approval.

Verify and improve from evidence

Close the item only when sample sent items agree with the matrix, held threads show an owner and next review time, individual accounts appear in the audit trail, and revoked permissions no longer work. Retain the source references, owner decision, resulting identifier or state, verifier, and verification time.

Review returns and exceptions by cause. Change a field, example, permission, or review interval only when the evidence shows the current design is weak. Keep the conclusion bounded to the inspected population and preserve unresolved items in the denominator.

Authoritative starting source

Consult the relevant first-party guidance at https://www.cisa.gov/secure-our-world/use-strong-passwords. Apply it through the client’s approved policies and accountable professional owners; the source does not grant the support specialist new authority.