What does a service catalog clarify about assistant scope disputes?

Question and scope

This review asks what a client-facing service catalog clarifies about disputes over an assistant's scope. The unit is a disagreement about whether a task, volume, or response time was included in the service. The scope covers recurring assistant and support roles sold to a business client. The review does not address employment classification, pricing strategy, or the legal interpretation of a contract, which require separate advice.

The question matters because many scope disputes are not caused by bad faith. The client and the provider often hold different pictures of the service because the sales conversation, the contract, and the daily request channel use different language. A catalog can align those pictures if it describes the work in observable terms. It cannot fix a relationship where one side deliberately hides the boundary.

The review treats the catalog as an operating document rather than a brochure. Its test is whether a client can read an entry and predict what will happen to a real request. A catalog that passes that test reduces the number of conversations about whether something is included. It also gives the provider a defensible basis for saying no. Keep the test in mind when writing each entry.

Why disputes start before the invoice

A scope dispute often begins with an ambiguous request that the assistant tries to help with. The client sees a helpful response and assumes the task is now part of the service. The provider later sees the work as an exception that should be billed or declined. The conflict is built into the first interaction, long before the invoice arrives.

The request channel makes the problem worse when it accepts work in any format. A chat message that says can you also handle this creates an implied commitment. A catalog that names the intake fields and the included work gives the assistant a neutral way to redirect the request. The boundary is easier to hold when it is visible before the work starts.

SBA guidance on hiring and managing employees emphasizes clear expectations and written terms, while the FTC's truth-in-advertising guidance addresses the accuracy of promises made to customers. Neither source prescribes a service catalog, but both support the principle that the published description should match the delivered service. A catalog is one way to make that match checkable. Read the current guidance rather than relying on a summary.

Included, excluded, and assumed work

A strong catalog has three lists for each service: what is included, what is excluded, and what is assumed about the client's environment. Included work names the tasks and the output. Excluded work names the tasks that require a different owner or a separate agreement. Assumptions name the access, volume, and turnaround the price depends on.

The assumed list is the one most often missing. A provider may assume that the client supplies a working account, a complete brief, and an approver who responds within a day. When those assumptions fail, the service slows and the client blames the provider. Writing the assumptions turns a hidden dependency into a shared expectation.

Keep the lists specific enough to test. A phrase such as general administrative support is not an inclusion because it does not name an output. A phrase such as draft and file the weekly customer report by Tuesday noon is testable. The catalog should use the second style wherever the work is recurring.

Response and review promises

Response time and review time are separate promises. A response time says when the assistant will acknowledge or begin, while a review time says when a person will approve the output. A catalog that promises a fast response but a slow review sets the client up for disappointment. Both clocks should be visible, with the starting event defined.

The review model also affects the scope. If the client reviews every outbound message, the assistant's work ends at a draft. If the assistant sends against a written standard, the scope includes judgment and the risk that comes with it. The catalog should name the model and the sample used to check it. A client who expects sending but pays for drafting will dispute the first late reply.

State the escalation path when a request falls outside the service. The client should know who to contact for a new task and how quickly the provider will respond. A named path prevents the assistant from improvising an exception at the edge of the scope. It also gives the provider a chance to price the work before it starts.

Change control for a living catalog

A catalog that never changes becomes inaccurate within a quarter. New tools, new clients, and new requests shift the work. The provider needs a change process that names who can request a change, who approves it, and how the price and schedule adjust. The process should be short enough to use during a busy month.

Version the catalog and record the effective date of each change. Tell the assistant which line changed and give one example of the new expectation. Keep the previous version for the current billing period so an invoice can be checked against the terms that applied. A quiet change creates the same dispute the catalog was meant to prevent.

Review the catalog with the client on a fixed cadence, such as each quarter. Compare the promised service with the requests that actually arrived. Add the work that has become routine and remove the entries no one uses. The review keeps the document tied to the relationship rather than to the original sale.

Evidence that the catalog is working

Track the number of requests that arrive outside the catalog and the time spent clarifying them. A falling count suggests that the client understands the service. A rising count may mean the catalog is hard to find or the request channel is unclear. The measure is a prompt for a conversation, not a score for the client.

Track the disputes that reach an invoice and the reason for each. If most disputes concern the same entry, the entry is ambiguous. If they concern a category that is not in the catalog at all, the service has drifted. Use the pattern to revise one entry at a time rather than rewriting the whole document.

Ask the assistant which request causes the most hesitation. Their answer often reveals a gap between the catalog and the real work. The assistant sees the request before the manager does and can describe the exact ambiguity. A catalog review that ignores that input will miss the entries that matter most.

Compare the catalog with the actual invoice lines once a quarter. A service that appears on the invoice but not in the catalog, or the reverse, is a drift signal. Reconcile the two before the next billing cycle. The invoice and the catalog should describe the same service in the same words.

Method and limitations

This review draws on business guidance and a quality framework rather than a study of dispute rates. The sources support clear expectations and accurate promises, but they do not measure the effect of a catalog on a specific client relationship. The recommendations are a practical design method that a buyer can test. They are not a substitute for a contract review.

A catalog also cannot resolve a disagreement about facts, such as whether a request was received or a deadline was met. Those questions need the queue, the timestamps, and the review record. The catalog defines the service, while the operating evidence proves what happened. A provider needs both to resolve a dispute fairly.

Decision checklist

List the recurring work in client language and name the output for each entry. Write the included, excluded, and assumed items separately. Define the response window, the review model, and the event that starts each clock. Publish the request channel and the fields a complete request needs.

Set a change process with an owner, a notice period, and an effective date. Version the catalog and keep the prior version for the billing period. Review the entries with the client each quarter. Track out-of-catalog requests and invoice disputes, then revise one entry at a time.