Philippines staffing guide · Published
Write a delegation charter before adding a second task to an outsourced role
A second task changes authority, evidence, and review load. Use a short charter to define scope, stop rules, and an exit test before the work expands.
The short answer
Add a second task only after the charter states what the role may decide, what evidence the task must leave, and which decisions still return to the owner. A short written test prevents quiet scope creep.
Why a second task needs a charter
A first task usually arrives with a narrow brief and a reviewer who checks everything. A second task often arrives as one sentence in chat, with no revised boundary and no new examples.
The coordinator then has to guess which rules still apply and which ones changed. That guess is where quiet errors begin, long before anyone notices a customer problem.
A delegation charter is a one-page record of what the role owns, what it may decide, and what must come back to the owner. It is not a job description and it is not a contract.
It is the working agreement a reviewer uses when an item is ambiguous. Update it whenever the task list changes, because an outdated charter is worse than none at all.
Name the decision rights for each task
Write each task as an outcome, then list the decisions the coordinator may make without asking. For an inbox task, the coordinator may classify, route, and draft. For a billing task, the coordinator may reconcile a record but not issue a credit.
Keep the verbs concrete so a reviewer can compare a real item with the written right. If the list needs a page of exceptions, the task is not ready to delegate.
Name the person who holds each right the coordinator does not have. A role name is not enough when three supervisors share the queue. Record the backup and the hours that person is available.
When the owner is away, the item should wait in a named holding state rather than drift to whoever answers first. The charter should make waiting a legitimate outcome.
Set the evidence each task must leave
Every delegated task should leave a record that a stranger could follow. For a routing task, that means the source message, the chosen queue, the reason, and the time. For a research task, it means the question, the sources, the access date, and the open doubts.
Write the minimum evidence, not the ideal report. A coordinator who knows the minimum will produce it consistently.
Separate evidence from commentary. A note that says the customer was upset is not evidence unless it quotes the message and links the record. A note that says the item was checked is not evidence unless it names what was checked.
Reviewers should confirm the claim without asking the coordinator to remember the case. That standard protects both sides when a decision is questioned later.
Define what the coordinator may not do
Write the stop rules in the same place as the permissions. A support coordinator may not promise a refund, change an address on an identity document, or discuss a legal threat. An admin coordinator may not approve a new vendor or sign a contract.
Each stop rule needs a trigger, a holding action, and the person who takes over. A stop rule without a destination is just a dead end.
Test the stop rules against recent exceptions rather than hypothetical risks. Pull three cases that were escalated and three that were resolved quietly. Ask whether the charter would have produced the same decision.
Where the answer is no, rewrite the rule instead of blaming the coordinator. The charter is the control, and the case is the test.
Pilot the second task behind a review gate
Add the second task for a fixed window and review every item in the first batch. Keep the first task running so the coordinator is not asked to learn two new things at once.
Mark the new items in the queue with a simple tag, and have the owner check the tag daily. The point is to find gaps in the charter while the volume is still small.
Set an exit test before the pilot starts. A workable test is twenty consecutive items with no missing evidence, no wrong decision right, and no skipped stop rule.
If the test fails, repair the charter or the training and restart the count. Do not extend the pilot indefinitely, because a permanent training mode becomes an excuse to skip the review.
Revise the charter after the first month
At the end of the month, compare the charter with the items that actually caused questions. Add the field that was always missing, remove the report nobody read, and clarify the rule that produced two different answers.
Ask the coordinator which instruction was hardest to apply. That answer is usually more useful than a satisfaction survey.
Record the revision date and keep the prior version. When a decision is questioned, the old charter shows what the coordinator was told at the time.
Share the new version with the owner, the reviewer, and the provider supervisor. A charter that lives in one person's folder is a secret, not an agreement.
Keep the charter short enough to use
A charter that runs to eight pages will not be read during a busy queue. Put the decision rights, stop rules, and evidence minimum on the first page.
Move examples and background into an appendix that the reviewer can open when a case is unclear. The coordinator should be able to answer a live question without leaving the queue view.
Review the length at each revision and cut anything that no longer changes a decision. A rule that repeats the same instruction in different words adds weight without guidance.
Keep the language close to the words the team uses in the queue. A short document that people quote is stronger than a long one they file away.
Questions to copy for the sales call
- "Which decisions can the coordinator make without asking today?"
- "What is the minimum evidence a completed item must leave?"
- "Which stop rule most often sends work back to the owner?"
- "What would make us remove the second task again?"
Sources
- SBA: Hire and manage employees: Plain guidance on defining roles, expectations, and management responsibilities.
- DOL Wage and Hour Division: Reference point for separating worker classification and employment duties from task delegation.
- GAO: Assessing Data Reliability: A method for judging whether a record is complete enough for the decision it supports.
Common questions
Does a delegation charter need legal review?
It is an operating document, not a contract. Have counsel review it only when the role touches regulated data, employment terms, or contractual obligations.
How long should the charter be?
One page for a small role. If it grows beyond two pages, move examples into an appendix and keep the decision rights on the first page.
Who owns the charter?
The internal manager who answers for the work. The coordinator and provider supervisor should see it, but ownership stays with the person who can change the process.
Should every new task get a pilot?
Every task that carries a decision right should. A pure preparation task with no customer or money impact can start with a smaller sample review.