How to Write a Monthly Training Administration BPO Scope of Work

A monthly fee is only useful when the buyer and delivery team can explain what it covers. “One administrator” says little about the request queue, the software permissions or the checks required before work can be accepted. A practical MTA BPO statement of work starts with the transactions and decisions the service must handle.

The method below is an original LyndonAI planning framework. It is not a market price study, a contractual template or a promise of a particular response time. Consulting and transition planning form part of the agreed BPO engagement; the final scope determines the actual responsibilities and commercials.

Build a workload register before estimating capacity

Choose a planning period and list requests by workstream. Use historical records where authorized and available. When records are missing, label the volume as an estimate and identify how the first operating cycle will establish a baseline.

The following entries are illustrative planning inputs, not a client workload or a capacity commitment.

Do not add these units together and treat the total as interchangeable work. A course-release check and an enrollment request can have different dependencies. Record the authorized input, typical exceptions, required checks and resulting evidence for each stream.

Define what starts and finishes a task

A useful service measure has an observable beginning and end. For an assignment request, the start might be the receipt of an approved audience list, valid learner identifiers and the authorized course version. The end might require the platform action, a representative check and an evidence reference.

Agree how missing information, rejected access and customer decisions affect the service clock. A paused request should show the reason, time, owner and next action. If an administrator can proceed with part of a batch, specify whether that creates a partial output or whether the whole batch waits.

Keep response and resolution separate. A ticket acknowledgment is not a fix. An issue referred to a software vendor may have a different owner and dependency from a routine administrative change. The report should reveal that distinction.

Record capacity and service windows explicitly

The scope should explain the planned workload, operating days, time zones, languages, priority rules and escalation route. For global programs, identify which deadlines belong to which business time zone rather than using an undefined “end of day.”

State how requests enter the queue and who can assign priority. If several stakeholders can request urgent work, identify who resolves conflicts. An escalation process is more useful than an unqualified promise that every request is urgent.

Review forecast peaks before they arrive. A launch may increase course changes, communications and support at different times. Agree the required capacity and any commercial change rather than assume a recurring fee absorbs every variation.

Separate administration from optional production

Course production needs its own units: asset type, length or complexity where relevant, review rounds, languages, source-file delivery and acceptance checks. Do not hide a new interactive course inside an allowance for catalog edits.

The relationship between the work packages still matters. Content approval supplies the permitted version for LMS release; publishing checks supply evidence for rollout; learner support may identify an issue that returns to the content owner. Define those handoffs so the combined service is coordinated without making its scope unlimited.

A wider Total Managed Training BPO engagement can include both packages. The monthly plan should still show their capacity and dependencies separately.

Build a review pack around decisions

Use a service review that can answer five questions:

1. What work entered the queue, and was it inside the agreed scope?
2. Which outputs were completed and checked?
3. What required rework, and what caused it?
4. Which requests remain blocked or await approval?
5. What change to capacity, procedure or scope should be agreed next?

Show source dates and reporting coverage. Learner completion rates belong in the learning report; administrative turnaround and release quality describe service execution. A course remaining incomplete does not, by itself, prove that administration failed, and a high learner completion rate does not prove every administrative check was performed.

Compare costs on a consistent basis

Compare the same tasks, volumes, service windows and acceptance requirements across options. Include delivery, supervision, checking, rework, transition and any incremental software or integration costs. Distinguish a new expense from an allocation of a subscription already paid for.

There is no reliable percentage saving to promise before that comparison. The useful output is a scoped proposal with assumptions, exclusions and a route for changes. Unknown inputs should remain visible rather than be converted into zero cost or unlimited capacity.

Make scope changes a visible decision

A new region, report or course format should trigger a review of the work it changes. Record the request, affected workstream, expected volume, dependency, approval and effective date. Update the service register after agreement so operators use the current scope.

Bring the register to the MTA service scoping discussion. It creates a better starting point than a broad request for “LMS support,” because both teams can inspect the work, the decisions and the evidence that will define acceptance.