First-task training

Move one task from observation to a checked independent sample.

Use this plan when a new offshore teammate is learning one repeatable task. Name what they can watch, practice, try with review, and repeat independently. Keep owner-only actions visible at every stage.

Plan fields10

The details for one bounded training cycle.

Fictional examples2

CRM cleanup and customer-support drafts.

Data savedNone

The template stays in your browser.

This is a training record, not legal, financial, tax, security, privacy, HR, safety, or compliance advice. It does not grant access, provide authority, expand scope, or approve work. Keep customer, money, access, legal, security, privacy, clinical, and regulated-work decisions with qualified authorized owners.

Ten fields

Map the first training cycle before the task repeats.

A good first sample is bounded. The learner watches, practices safely, shows one small sample, and gets a check before the same work comes back.

Shadow plan field

Task and result

Name one repeatable task and the result a reviewer can check.

Shadow plan field

Learner, observer, and reviewer

Name who is learning, who demonstrates the task, and who gives feedback.

Shadow plan field

Source SOP and approved example

Link to approved instructions and one safe example. Do not paste credentials or confidential records.

Shadow plan field

Observe

State what the learner watches and which questions they should capture.

Shadow plan field

Guided practice

Name a safe historical or test item the learner can prepare with feedback.

Shadow plan field

Supervised sample

Set the small live sample, evidence to save, and review before the task repeats.

Shadow plan field

Held actions

List decisions and actions that stay with an authorized owner.

Shadow plan field

Feedback and correction

Record the reviewer, one specific correction, and the SOP or example to update.

Shadow plan field

Repeat check

Name the next sample or check before the task can repeat under the same rule.

Shadow plan field

Safe-stop trigger

Say when to pause and who owns the next decision.

Fictional examples

One admin task and one support task, bounded by an owner.

Every company, person, case, date, rule, and outcome below is fictional. Scroll the table horizontally on a small screen to see every field.

Fictional training plans that keep the source, sample, owner, and stop route visible.
Task and resultLearner, observer, and reviewerSource SOP and approved exampleObserveGuided practiceSupervised sampleHeld actionsFeedback and correctionRepeat checkSafe-stop trigger
Fictional CRM Cleanup: add approved source notes to five existing contact records.Fictional assistant learns; fictional CRM owner observes and reviews.Fictional CRM-note SOP v3 and a fictional approved record example.Watch the owner open the saved view, compare a submitted form, and add a source note without changing the contact owner.Prepare source notes on two historical training records. The owner checks both before any live work.Add notes to one live five-record batch. Save the safe record references for the owner to inspect.Merging, deleting, changing ownership, changing consent, or enrolling a contact in outreach stays with the owner.The owner names one missed source link, updates the SOP example, and asks for one corrected note.The owner checks the next five notes before another batch is assigned.Pause if records disagree, consent is unclear, or a merge is requested. Send the record reference to the fictional CRM owner.
Fictional customer support: prepare routine order-status reply drafts from an approved status source.Fictional support assistant learns; fictional support lead observes and reviews.Fictional reply guide v4, fictional carrier-status reference, and an approved draft example.Watch the lead match a ticket to an approved reply category and hold an exception instead of making a new promise.Draft replies for two historical tickets. The lead compares each draft with the approved wording.Prepare one small set of live drafts. The lead reviews every draft before anything is sent.Sending, refunds, compensation, order changes, firm delivery promises, threats, and policy exceptions stay with the authorized owner.The lead marks one line to rewrite, points to the approved example, and records the correction in the guide.The lead checks one more routine draft before allowing the same narrow preparation step to repeat.Pause when the status is missing, a customer asks for an exception, or the approved wording does not fit. Route the ticket to the fictional support lead.
Copy-ready blank plan

Start with safe references, not copied records.

Keep credentials, customer records, payment details, and confidential attachments in the approved system. The plan should point to them, not repeat them.

OFFSHORE TRAINING SHADOW PLAN

PLAN CONTROL
Task lane:
Plan owner:
Learner:
Observer or trainer:
Feedback reviewer:
Source SOP and approved example:
First review date:
Next check date:

TASK AND CHECKABLE RESULT:
OBSERVE: what the learner watches and questions to capture:
GUIDED PRACTICE: safe historical or test work and feedback point:
SUPERVISED SAMPLE: small live sample, evidence to save, and reviewer:
HELD ACTIONS: decisions and actions that stay with an authorized owner:
FEEDBACK AND CORRECTION: one rule or example to use next time:
REPEAT CHECK: next sample or review before the task repeats:
SAFE-STOP TRIGGER AND DECISION OWNER:
REFRESH TRIGGER: process, system, access, scope, reviewer, or policy change:

Use approved references instead of credentials, customer records, payment details, or confidential attachments. This plan records training and feedback. It does not grant access, expand scope, approve customer, money, legal, security, privacy, clinical, regulated, or policy decisions, or replace a contract, policy, or written approval rule.

The full plan stays visible and selectable. Nothing is uploaded or saved.

One task at a time

Turn one first sample into a written learning record.

A good first sample gives you something specific to check. If the task changes, update the SOP, example, boundary, and stop rule before the next batch.

  1. Choose one narrow task with a written result, a named reviewer, and a safe source reference.
  2. Let the learner observe the normal path, then practice on historical or test work before touching a live sample.
  3. Review one small supervised sample against the SOP and approved example. Record one correction instead of giving broad feedback.
  4. Choose whether to repeat the same narrow task under review, revise the plan, or keep the task held with the owner.
Pause and clarify

The plan cannot fix missing authority or missing evidence.

Stop when the task reaches a held decision, an approved rule does not fit, or the person who owns the next choice is not clear.

  • The task has no approved SOP, example, reviewer, or safe source reference.
  • The learner is asked to send a customer message, change access, move money, make a legal, security, privacy, clinical, or policy decision, or handle an unusual exception.
  • The plan mixes several task lanes, owners, systems, or results into one first sample.
  • Feedback says only that the work needs to be better and does not name the rule, example, or correction.
  • The task, system, access, reviewer, or scope changes but the plan still uses an old example.
Need a second set of eyes?

Review the first-task plan before the work spreads.

Bring the task, safe reference, example, and owner question. OutsourcedU can help locate the missing rule or the risky handoff.