Small business outsourcing workflow guide
Decide what a small business should never hand to an assistant
A practical boundary list for small-business owners who want to delegate the work without delegating the decisions that can change the business.
Separate a task from a decision
A task has a clear input, a defined output, and a review point. A decision changes money, policy, access, or a customer relationship. The same activity can contain both, which is why a boundary list is more useful than a list of job titles. The owner should delegate the task and keep the decision.
Write the boundary in the role brief, not only in a conversation. For each task, say what the assistant can do alone, what needs a draft and a review, and what must be escalated before any action. A boundary that is not written down will be tested by the first unusual request. The written version gives both people a shared reference.
Keep pricing and credit exceptions
Pricing, discounts, and credit terms change the economics of the business. An assistant can prepare a quote from an approved price list and can collect the information needed for a credit decision. The assistant should not invent a discount, extend a payment term, or approve a credit limit. Those decisions belong to the owner or a named finance lead.
If a customer asks for an exception, the assistant should record the request and route it with the relevant history. The owner can then decide with the full picture. A quick yes from an assistant can set a precedent that is hard to reverse. A clear no from the owner is easier to defend.
Keep hiring and termination decisions
An assistant can screen applications, schedule interviews, and prepare onboarding materials. The decision to hire, discipline, or terminate belongs to the owner and should follow the applicable employment rules. The assistant should not promise a role, a rate, or a start date without approval. Those promises can become legal obligations.
If the assistant manages other staff, define the limits of that authority in writing. For example, the assistant may assign daily work but may not change pay or issue a formal warning. Route any performance concern to the owner with the facts. A clear escalation path protects both the assistant and the employee.
Keep legal and regulatory judgments
An assistant can gather documents, track deadlines, and prepare a draft for a professional to review. The assistant should not decide whether a contract clause is enforceable, whether a filing is required, or whether a customer complaint creates a legal risk. Those questions need a qualified adviser and the owner's decision. Keep the final judgment with the owner and the adviser, and record who gave the advice.
When a legal question appears, the assistant should stop and route it rather than searching for an answer online. Record the question, the date, and the person who received it. A fast but wrong answer can cost more than a short delay. The boundary should be explicit in the role brief.
Keep access grants and removals
Access to accounts, files, and payment systems is a security decision. An assistant can prepare an access request and confirm that the user has completed the required training. The assistant should not grant admin access, share a password, or remove access without the owner's approval. Those actions should follow a written process with a record.
If the assistant needs access to do the work, give the smallest permission that supports the task. Review the access at a fixed interval and remove it when the work ends. A shared login makes it impossible to know who did what. The owner should be able to see the access list and approve changes.
Keep the customer promise in a crisis
In a normal week, an assistant can confirm a delivery date or a service window from a written rule. In a crisis, the promise may affect safety, reputation, or a large customer. The owner should decide what the business will commit to and who will communicate it. The assistant can prepare the facts and the draft message.
Define what counts as a crisis for the business, such as a service outage, a safety issue, a data breach, or a public complaint. Write the escalation path and the first person to call. Do not wait for the assistant to judge the severity alone. A short list of triggers is enough to start.
Document the boundary in the role brief
The role brief should list the tasks, the decisions, the approval path, and the escalation triggers. Keep it to one or two pages and use examples from the business. Review it with the assistant before the first shift and again after the first month. A brief that is never discussed is only a document.
Update the brief when the role changes. If the assistant takes on a new task, decide whether it includes a decision and add the boundary. If a task is removed, remove the access that supported it. The brief should reflect the current work, not the work from the first week.
Review the boundary as the role grows
A trusted assistant will eventually be asked to make judgment calls that were not in the original brief. That is normal, but the owner should decide which calls to delegate. Review the boundary every quarter and look for tasks that could move from draft-and-review to independent. Move one step at a time and keep the record.
Ask the assistant which decisions feel ambiguous and which requests keep landing outside the brief. The answers show where the process needs a clearer rule. Update the brief and tell the customer-facing team what changed. A boundary that grows deliberately is safer than one that erodes by accident.
Sources and next steps
- U.S. Small Business Administration, manage your business
- NIST Cybersecurity Framework
- Federal Trade Commission, protecting personal information
Compare this workflow with the small-business outsourcing service guides and bring a redacted source record to the scoping call.
Related guides
Write a phone-answering script that survives a busy Monday
A short call script for a small business that captures the right details, routes the urgent calls, and still sounds like a person.
Build a customer onboarding checklist for a service business
A handoff checklist that moves a new customer from signed agreement to first delivery without losing the details sales promised.