First-week review

Check the first week before offshore work spreads.

Use this template after a provider, assistant, or offshore team starts. It turns day-one access, day-three quality patterns, and day-five scope decisions into one clear review.

This is a planning template, not legal, security, HR, tax, or compliance advice. Keep sensitive decisions with qualified owners.

Review points3

Day 1 access, day 3 pattern check, day 5 keep/tighten/pause decision.

Sample rule20-30%

Check enough low-risk work to see repeated misses before expanding scope.

Scope rule1 lane

Prove one task lane before adding tools, customers, or higher-risk decisions.

Review map

Use day one, day three, and day five for different checks.

Do not wait 30 days to learn that the SOP was unclear or access was too broad. Use small checks early while the scope is still easy to fix.

When
Focus
What to check
Example
Day 1
Access and first safe sample
Confirm tools, MFA, SOP links, blocked actions, and one low-risk task sample before wider work starts.
Review 5 tagged tickets, 5 cleaned CRM records, or 3 drafted replies before anything customer-facing goes out.
Day 3
Pattern check
Look for repeated questions, missing examples, access friction, and quality misses across a small batch.
Sample 20% to 30% of completed work and write the top 3 fixes in the SOP instead of sending scattered chat notes.
Day 5
Keep, tighten, or pause
Decide whether the work lane is ready to repeat next week, needs tighter rules, or should stay owner-reviewed.
Keep inbox labels independent, tighten refund-escalation rules, and pause any export, billing, or admin-setting request.
Scorecard

Score what happened, not how busy the provider looked.

A first-week review should compare real output with the handoff. These six checks keep the conversation practical.

Access

Good: Named accounts work and MFA is active.

Fix: Tool gaps, shared logins, or broad admin rights are still unresolved.

SOP clarity

Good: The assistant can follow examples without guessing.

Fix: The same question appears twice or the finished-result example is missing.

Quality

Good: Routine output matches the sample standard.

Fix: Errors repeat across labels, fields, replies, formatting, or source links.

Speed

Good: Turnaround is realistic for the agreed hours.

Fix: The role is blocked by approvals, missing inputs, or too many task types.

Risk

Good: Money, legal, account, refund, and customer-risk work stays reviewed.

Fix: The provider is being asked to decide things that still need an owner.

Next scope

Good: One lane can repeat next week with spot checks.

Fix: More examples or a smaller scope is needed before adding work.

Copy-ready recap

Send one short recap after each review point.

The recap should name what repeats, what gets fixed, and what stays blocked. That keeps the provider from guessing and gives your manager a record.

  • Day-1 recap: "Access is ready for [tools]. Today we tested [sample task]. Keep [what worked]. Hold [risky action] for owner review."
  • Day-3 fix note: "The same issue appeared in [number] of [sample size] items: [issue]. Update the SOP with [rule/example] before the next batch."
  • Day-5 decision: "Next week, repeat [lane]. Spot-check [percentage or count]. Keep [blocked actions] with the owner until we have two clean weeks."
Source notes

Use a review template because access, roles, and examples need rules.

This page uses outside references for role clarity, small-business management, and access safety. The template stays conservative and does not claim a provider outcome.

Before week two

Do not expand the offshore role until the first batch is clear.

OutsourcedU can help turn early provider work into a safer next-week plan with tighter SOPs, cleaner access, and a practical review rhythm.

Build your handoff system

Ready to plan your first offshore role?

Use OutsourcedU to write the role, SOPs, onboarding steps, and weekly review before you hire more people.

Request the plan