Outsourced CompanyPowered by StealthAgents

Philippines staffing research · Published · Updated

How a service catalog drifts in a long outsourcing engagement

A service catalog is accurate on the day it is signed. Small requests, new reports, and quiet exceptions then move the work without changing the document. The drift is predictable, and it can be managed.

A client and provider team comparing a printed service list with a project board on the wall

Research findings

A service catalog describes what the provider will do, for whom, and at what cadence. It is usually written during the sales process and approved with the contract. For the first month, the description matches the work. Over a year, the two can separate until the catalog describes a service that nobody receives and the team performs work that nobody has priced.

Drift starts with a small request. A client asks the coordinator to add one field to the weekly report, then to copy a second person on the summary, then to check a figure before the finance meeting. Each request takes minutes and none seems worth a contract change. The cumulative effect can be an hour a day, which is a real capacity change.

The provider contributes to the drift. A team that wants to be helpful says yes without recording the request. A supervisor absorbs the extra work into the existing queue. The client learns that the request route is a conversation, not a change process. By the time the provider raises capacity, the client sees the extra work as part of the original service.

A catalog also drifts through omission. Work that was expected but never written down does not appear in the baseline. The provider may perform it for months before discovering that it is outside the scope. The client may assume it is included because nobody said otherwise. Both sides can be honest and still disagree about what the catalog covers.

Tool changes accelerate the drift. A new system may add a reconciliation step, a second approval, or a data export that the old system handled automatically. The catalog still describes the old workflow. The team performs the new one. If the change is not reflected in the service description, the effort disappears from the account review.

Volume changes do too. A catalog may specify a monthly report, then the client asks for a weekly version during a busy quarter. The cadence is a scope term, not a formatting preference. Four reports a month is a different commitment from one, even when the template is the same. The catalog should name the cadence and the expected effort.

Discussion

The first control is a change log that any team member can add to. It should capture the request, the date, the requester, the estimated effort, and whether the work was accepted. The log does not need to be a formal contract amendment. It needs to be complete enough that the monthly review can see the pattern.

The second control is a monthly scope review with the client owner. Read the change log, group the requests by theme, and decide which ones should be added to the catalog, priced separately, or stopped. A short review is more useful than a quarterly argument. The client sees the cost of the small requests before they become a budget surprise.

The catalog should have an owner on each side. The provider owner maintains the description and the effort estimate. The client owner confirms the priority and the budget. When the two disagree, the contract change route decides. A catalog without owners becomes a document that both sides cite and neither side updates. When an owner changes, update the name and tell the client in the same message.

Implications and limits

Version control matters more than length. Give each version a date and a short summary of changes. Keep the prior version so a disputed request can be checked against the description that was active at the time. A catalog stored in an email attachment is already drifting, because nobody knows which copy is current. A short change summary is more useful than a long revision history that nobody reads.

The review should also look for work that has stopped. A report that nobody reads, a check that the new system now performs, or a meeting that no longer has a decision can be removed. Drift is not only additive. A catalog that never shrinks becomes expensive and hard to explain, and the team loses time on work that no longer matters.

The final test is whether a new team member can use the catalog to decide what to do with an unusual request. If the answer depends on asking a supervisor who has been on the account for years, the catalog is incomplete. Write the examples and the boundary cases into the description. The document is useful when it can answer a question without the original author.

How a catalog drifts

Drift happens through small accepted requests, undocumented expectations, and tool changes. None of these is a crisis on its own. The problem is that they are invisible in the account review because the catalog still looks the same. The gap between the document and the work grows without a decision. The monthly review should name which of the three caused the largest change.

Look for the signs: a team that is always busy but reports no volume change, a client who says the provider used to do something that is not in the catalog, or a supervisor who cannot take leave without the queue slowing. These are symptoms of work that has moved outside the written description. Ask the supervisor which requests they handle from memory, because those are the ones missing from the catalog. Then compare the answers with the change log and the last scope review.

The informal request

An informal request is not a failure of goodwill. It is a normal part of a working relationship. The failure is the absence of a place to record it. Give the team a one-line form or a channel field and review it weekly. The act of recording turns a favor into a decision without making the client feel bureaucratic.

Set a threshold for immediate acceptance. A request under a few minutes can be done and logged. A request that changes a recurring output, a deadline, or a customer commitment should go to the owner before the team starts. The threshold protects the relationship and the capacity plan at the same time. Write the threshold down so two supervisors do not make different decisions about the same request.

Versioning and ownership

Use a date and a version number, and state what changed in one sentence. Store the current version where both teams can reach it. Link the contract, the catalog, and the change log so a reader can follow the history. Version control is a small habit that prevents a large argument. A reader should be able to tell from the header whether the document is current.

Name the owners in the document itself. A role name is better than a person name because it survives turnover. Add the review cadence and the route for an urgent change. The catalog is a living agreement, and the owner is the person who keeps it alive. Add the date of the last review beside the names so a reader knows how current the document is.

Reviewing the catalog with the client

Bring the change log and a short list of themes, not a long complaint. Ask the client which additions are now essential and which were experiments. Decide together whether to add, price, or stop each theme. Record the decision and the effective date. Keep the meeting short and end with a written decision for each theme.

Review the stopped work as well. A report that is no longer used can be removed and the time returned to the queue. Clients often appreciate the question because it shows the provider is managing the service rather than defending the scope. The review should leave both sides with a shorter, clearer list. The time released should be visible in the capacity plan, not just removed from a list.

When to renegotiate

Renegotiate when the cumulative change affects capacity, cost, or risk. A single small request does not need a contract amendment. A recurring weekly output, a new approval step, or a new system may. Use the change log to show the pattern and the effort rather than arguing from memory. Bring the change log and a short effort estimate so the conversation starts from evidence.

Bring options rather than a demand. The provider can offer to add the work, remove something else, or move it to a separate service. The client can then choose based on priority and budget. A catalog review that produces options is more likely to end with a workable agreement than one that produces a bill.

Questions

How often should the catalog be reviewed?

Monthly for the change log and at least quarterly for the full catalog. Review sooner after a tool change or a new client owner joins.

Should every small request be logged?

Yes. Logging takes seconds and shows the pattern. The team can still act immediately on a small request without turning it into a contract change.

Who decides whether work is in scope?

The catalog and contract decide, with the named owners interpreting the boundary. The team should escalate an unclear request rather than guess.

What if the client refuses to review scope?

Keep the log and show the capacity effect in the regular account review. A factual trend is easier to discuss than a one-time complaint.

Philippines staffing intake

Define the position before hiring begins.

Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.

Contact Us