Free CRM for accountants & bookkeepersFree for two months (60-day trial) · no per-user fees
Quality assurance & review
How to Share SOPs and Procedures With an Outsourcing Team
The best place to share an SOP is inside the work, not next to it
Built by a practising Chartered Accountant · Unlimited users · Free for 60 days
Quick answer
SOPs shared with an outsourcing team as a static document in a shared drive get read once and then forgotten. Sharing them by attaching the actual steps to task and subtask templates keeps the procedure visible every time the work is done, not just at onboarding. Remindoo supports this by letting you attach procedures to templates as subtask steps.
Why don't SOPs shared as documents actually get followed?
A document shared once, however well written, competes with dozens of other things in someone's memory by the time they're actually doing the work weeks or months later.
Most firms that outsource have SOPs somewhere — a shared drive folder, a Google Doc, maybe a PDF sent during onboarding. The documents themselves are often perfectly good. The problem is where they live: separate from the actual task, requiring someone to remember to go and check them.
An SOP that's genuinely followed is one that shows up at the point of doing the work — as steps on the task itself — rather than one that has to be actively recalled and looked up from a folder nobody's opened in weeks.
What goes wrong when SOPs live separately from the work
A firm builds a thorough set of SOPs covering how each recurring service should be prepared and shares the folder with its offshore provider during onboarding. Everyone signs off that they've read it.
Six months later, a new offshore team member joins and is pointed at the same folder, but with a growing list of other priorities, actually working through unread documents falls to the bottom of their list. They learn the job informally from a colleague instead, picking up whatever habits that colleague has drifted into.
The firm only discovers the SOP was never properly read when a specific step — a client-specific exception documented in the SOP — is missed on a live job, causing a client complaint that traces straight back to a document nobody actually consulted while doing the work.
Signs you've lost control
- SOPs exist in a shared drive that nobody references during actual work
- New starters are pointed at a folder rather than shown the procedure in context
- You have no way of knowing which staff have actually read a given SOP
- SOPs haven't been updated in longer than you'd expect the work to have changed
- Different offshore staff describe the same procedure differently when asked
- Errors trace back to a documented step that was simply never seen
How to share SOPs so they actually get used
- 1
Audit your existing SOPs for what's actually used
Some documents are outdated or duplicated — start from what's genuinely current.
- 2
Break each SOP into individual, checkable steps
The same detail level as a task checklist, not prose paragraphs.
- 3
Attach the steps to the relevant task or subtask template
So the SOP appears at the point the work is actually done.
- 4
Keep a single source SOP document for reference too
Useful for context and training, alongside the task-embedded steps rather than instead of them.
- 5
Update the template, not just the document, when a procedure changes
The template is what staff actually interact with day to day.
- 6
Ask new starters to work through a real task using the template
Rather than just reading the document in isolation, as their first exposure to the SOP.
Who owns each step of an outsourced job?
1. Assign
UK office
The task is created from a template with the relevant SOP steps already attached.
2. Prepare
Offshore team
The preparer follows the SOP steps directly on the task, not from a separate document.
3. Review
UK reviewer
The reviewer checks the SOP steps were completed as part of the review checklist.
4. Approve
UK partner
The partner can see the SOP was followed, recorded step by step, before final sign-off.
5. Send
UK office
Work reaching the client reflects the current SOP, not an outdated version someone half-remembered.
How does Remindoo help you share SOPs with an offshore team?
Remindoo lets you attach procedures to task templates and add them as subtask steps, so your SOPs show up exactly where and when the work is actually done, rather than sitting in a shared drive folder that's easy to forget about. Because these are subtasks on the template itself, updating the SOP means updating the template once, and every future task created from it reflects the change automatically. Notes on the task let staff flag anything unclear about a specific step, creating a live feedback loop back to the UK office rather than a static document nobody can query. Client portal and document sharing gives you a place to keep the full reference SOP document too, alongside the task-embedded steps, for anyone who wants the fuller context. Employee reporting and task breakdown let you see whether particular SOP-driven job types are taking longer or shorter than expected, a useful early signal that a procedure might need revisiting.
Task and subtask templates
Checklists that make every job consistent.
See featureService templates
Repeatable structures for every service.
See featureClient portal and document sharing
Share requests and documents securely, not by email.
See featureEmployee reporting
Capacity, productivity and deadline performance.
See featureEmployee task breakdown
Balance work before deadlines bunch up.
See featureCustom fields and data tokens
Capture and reuse the data your firm needs.
See featureWhat changes when you move off email and WhatsApp?
| Area | Email, WhatsApp and spreadsheets | Remindoo |
|---|---|---|
| Where SOPs live | Shared drive folder | Attached to the task template as steps |
| When staff see the SOP | Once, at onboarding | Every time they do the work |
| Updating an SOP | Edit a document, hope it's re-read | Update the template, applies automatically |
| Feedback on unclear steps | No obvious route | Notes on the task back to the UK office |
| New starter training | Reads a document alone | Works through a real task using the template |
| Reference material | Only place SOPs exist | Kept via the client portal alongside embedded steps |
See your offshore set-up working
A 30-minute walkthrough of teams, roles, time budgets and review steps.
Should we keep a central SOP library as well as task-embedded steps?
Yes — a central library remains useful as reference and for training, but it should feed the task templates rather than being the only place staff are expected to look.
Think of the central SOP document as the source of truth and the task-embedded subtasks as how that truth actually reaches the person doing the work. When they're kept in sync — updating the template whenever the source document changes — you get both a defensible written record and a practical mechanism that keeps procedures followed day to day.
- Keep one current version of each SOP document, dated and version-controlled
- Break it into subtask steps on the matching task template
- Update both together whenever the procedure changes
- Use the document for training and audits, the template for daily work
Frequently asked questions
Do we still need a written SOP document if it's built into the task template?
Yes, as a reference and training resource and for anyone auditing your procedures — the template is how it gets followed day to day, the document is the source it's built from.
How do we make sure the SOP document and the task template stay in sync?
Treat updating both as one action whenever a procedure changes, and assign responsibility for that update to one named person so it doesn't get missed.
What if our SOPs are too long to turn into subtasks?
That's often a sign the SOP itself needs simplifying — break it into the essential checkable steps and keep supporting detail in the reference document instead.
Can offshore staff suggest edits to an SOP?
Yes, and it's worth encouraging — route suggestions through notes on the task back to the UK office to review before updating the template.
Should client-specific exceptions be in the main SOP or somewhere else?
Record client-specific exceptions on the client record via custom fields or notes, and reference them from the task rather than creating a separate SOP per client.
How do we know whether an SOP is actually being followed?
Because it's built into subtasks, the reviewer can check completed steps as part of QA, and reporting can flag jobs where steps are consistently skipped or rushed.
Is this different from the general 'follow procedures' approach?
It's the practical mechanism for it — sharing SOPs this way is how you make sure a procedure actually gets followed rather than just documented.
Ready to run a calmer practice?
See Remindoo with your own clients, or start free for 60 days with unlimited users.
Sources
Last updated: . General guidance.
Why knowing what each employee is working on matters
In a growing practice, the partner can no longer hold every job in their head. Clear ownership and visible workload are what stop deadlines slipping when someone is on leave, busy or new.
Clear ownership
Every client and task has a named person, so nothing sits unassigned and clients get consistent answers.
Balanced workload
Seeing tasks per person helps managers move work before one person is overloaded and another is waiting.
Cover for absence
When work, notes and history live in one system, a colleague can pick up a job without starting from scratch.
Controlled access
Roles and permissions keep sensitive client and AML data visible only to people who need it.
Practical tips from UK practice
- Group people into teams around services or client portfolios, and name a Team Lead for each.
- Review the employee task breakdown weekly, not only when a deadline is missed.
- Give new starters a limited role first, then widen access as they are trained.
- Use bulk reassignment when someone leaves or goes on holiday, rather than moving tasks one by one.
Related Remindoo features
Written and reviewed by Waqas Sagar ACA FCCA FMAAT, Chartered Accountant with 18+ years in practice. Founder and MD of Accotax, an ICAEW, ACCA and AAT regulated London practice that has served over 5,000 clients, and founder of Remindoo. Guidance is general; check current GOV.UK and professional body guidance for your firm.
What UK practices say about Remindoo
Read all reviews on Trustpilot“With Remindoo, everything from the first enquiry to onboarding and ongoing client management is tracked in one place… It saves us hours and gives me, as a practice owner, complete visibility of where the firm stands.”
“The biggest benefit is having clients, tasks, deadlines, workflows, proposals and communication all organised in one place.”
“During my trial, the team were absolutely amazing. They helped onboard my clients, set up my settings and made sure everything was ready for me to use… they made the whole process completely stress-free.”
“It brings client information, tasks, recurring deadlines, workflows and reminders together in one place, giving us much better visibility across the team.”
