This starter kit is for CA, IT services, law, company secretary, and agency practices roughly 10–100 people. Write lightly. Improve from incidents. Avoid policy novels.
Principles before templates
- One page per SOP unless regulators force more
- Trigger + steps + owner + definition of done
- Links to live tools (where the record lives), not only prose
- Review date every six months or after a painful miss
- No SOP for rare edge cases until the common path is stable
SOPs exist to reduce rework and silence, not to impress auditors, unless you are actually under audit.
The six SOPs worth writing first
1. Intake / new request
Trigger: client asks for work (email, call, WhatsApp, portal). Steps: capture client, request summary, commercial shape, owner, next date; decide propose / accept / defer. Done: request visible in CRM or engagement draft with owner and next date, not only in chat.
2. Kickoff
Trigger: commercial yes or signed letter. Steps: confirm scope boundary, owners, channels, first milestone, billing contact; file kickoff summary. Done: engagement active in the project system with milestone and summary attached.
3. Weekly engagement health
Trigger: weekly cadence. Steps: owners update status and blockers; managers read exceptions; decisions written back. Done: every active engagement has a fresh next action or an explicit hold reason.
4. Change / scope note
Trigger: request outside agreed inclusions. Steps: write impact on fee/timeline; partner or named approver decides; client confirmation stored. Done: no out-of-scope work starts without a written note.
5. Billing & collections handoff
Trigger: milestone reached or retainer period start. Steps: confirm deliverable evidence; invoice correct entity; send; run chase cadence if unpaid. Done: invoice number linked to engagement; overdue items have an owner.
6. Access offboarding
Trigger: employee or contractor exit. Steps: remove SaaS access, files, email groups, devices within one business day; confirm with checklist. Done: signed checklist with timestamp. (Operational care with client data, not legal advice on DPDP.)
How to introduce the kit without mutiny
- Draft with the people who do the work; partners approve only the commercial and risk edges.
- Pilot on one service line for three weeks.
- Put SOPs where work happens (intranet is fine; unread PDFs are not).
- Reference the SOP in reviews when something breaks, “which step did we skip?” beats blame.
- Retire conflicting tribal rules explicitly.
Template skeleton you can copy
For each SOP, use the same headings:
- Name & owner
- Trigger
- Steps (numbered, verbs first)
- Definition of done
- System of record (where evidence lives)
- Escalation (who decides grey areas)
- Last reviewed
Print or pin the six skeletons during busy season. People follow what is visible.
What not to SOP yet
Exotic exception paths, every email template, and full quality manuals can wait. First make intake, kickoff, weekly health, change control, billing handoff, and offboarding boringly reliable.
Where Workplate fits
SOPs stick when the “link to live tools” points at records people already open. Workplate provides modular Projects, CRM, eSign, Invoice, and AI Chat under one login, account, and bill for Indian professional services. Shared account is live; deeper automation is roadmap. Aadhaar eSign covers suitable commercial documents; not DSC/MCA statutory filings. Use SOPs to define behaviour; use the system to hold the evidence.
Soft next step
Write the six one-pagers this fortnight, imperfect is fine. Run them on one team. Fix wording where people stumble. When your operating checklists should sit beside the same engagements you deliver and bill, explore Workplate at workplate.io.