Onboarding & systems reliability for a small law firm with no dedicated IT staff.
This is a sample case study based on IT support work performed in a corporate role, adapted here to illustrate how I’d approach a similar freelance engagement. The firm and scenario are illustrative; the skills, process, and approach are real.
Ashford & Pine is a small law firm handling client-sensitive work with a lean team and no dedicated IT staff. Whenever someone new joined, laptop setup and account access were handled ad hoc, sometimes taking days to get right. Shared drives and client folders had grown organically over time, with no consistent structure to permissions, meaning some staff had access they shouldn’t, and others were locked out of files they needed.
The core problem: no reliable system for managing devices, accounts, or access, creating both productivity friction and a genuine confidentiality risk in a field where client data control matters.
Zero onboarding delays, permissions risk resolved, critical issue fixed before a filing deadline.
| Before | After |
|---|---|
| New hires waited days for proper access | Full setup completed same day |
| Shared drive permissions were inconsistent | Role-based, audited permissions structure |
| No fast, reliable point of contact for tech issues | Remote troubleshooting resolved same-day, including under deadline pressure |
| IT problems handled reactively | Documented process the team can follow independently |
Build a standard checklist for new hire setup covering device configuration, account creation, and role-based access, so every new starter is ready on day one.
Review shared drives and client folders, identify inconsistent or excessive access, and restructure permissions around actual roles.
Set up a fast-response process for technical issues, with remote access tools configured and tested in advance so fixes don’t stall on access problems.
Write short, plain-language guides for common issues and the onboarding checklist itself, so the process doesn’t depend on me being available every time.
This approach draws directly on hands-on experience managing device setup, M365 administration, and troubleshooting in a corporate IT support role, applied here to how I’d structure the same work for a freelance client.
A law firm running on borrowed time from whoever happens to be free that day isn’t sustainable. When onboarding takes minutes instead of days, and permissions are actually mapped to who’s on which case, that borrowed time goes back to billable work.
Remote IT support for small businesses without an in-house IT team.