Why I made this
Legal teams are under constant pressure to move faster while staying accurate, confidential, and consistent. That tension is exactly where onboarding often breaks:
- People learn Teams and SharePoint just enough to “get by,” then develop messy habits (duplicates, unclear sharing, bad naming).
- AI tools are exciting, but without guardrails, they can create risk, especially around confidentiality and work product.
- Training time is limited, so the material must be immediately usable, not theoretical.
This guide solves for those realities. It is designed to be used as a two-page handout plus a short live session, with language and structure that fits professional services.
Who this is for
- Professional Development and training teams in law firms
- Practice technology or IT enablement staff supporting attorneys and business services
- Anyone onboarding new hires into Microsoft 365 collaboration and AI-assisted workflows
What success looks like
If this is working, you should see:
- Fewer “Which file is the latest?” moments
- Less duplicate document sprawl
- Clearer access control habits (who can see what and why)
- AI usage that feels practical and policy-aligned, not chaotic or risky
- New hires who can operate independently faster
AI and Copilot-ready work habits (policy-aligned)
The mindset
AI can speed up drafting and summarizing, but it is not a source of truth. In a legal environment, safe usage starts with three principles:
- Confidentiality first
- Human review always
- Primary sources win
Before using any AI tool
Use this as your quick pre-flight checklist:
- Confirm the firm’s AI policy and which tools are approved for your role
- Do not paste client confidential information unless policy explicitly allows it
- Treat AI output as a draft, not an authority
- Verify key statements against the underlying source
Generally safe use cases (subject to firm policy)
These tend to be low risk and high value:
- Summarizing internal, non-confidential notes or meeting takeaways
- Rewriting internal emails for clarity and tone
- Creating checklists, agendas, training outlines
- Structuring a first draft for internal review using provided facts
High-risk use cases (avoid unless explicitly approved)
- Uploading or pasting client documents, privileged notes, or work product into unapproved tools
- Asking AI for definitive interpretations or legal advice
- Generating citations without verifying against the actual authority
Prompt patterns that actually work
The best prompts include constraints. Here are patterns you can reuse.
Summarize with uncertainty flags
“Summarize the text below in 7 bullets. Flag any assumptions. Do not invent facts. Text: …”
Extract action items
“List action items, owners, and deadlines from the text. If missing, mark as ‘unknown.’ Text: …”
Draft an internal email with structure
“Draft a concise internal email to [audience] about [topic]. Keep it factual, include next steps, and add a short FAQ.”
Rewrite for a busy attorney audience
“Rewrite for a busy attorney audience. Keep tone neutral and professional. Use headings and bullets. Do not add new facts.”
A 30-second quality check
Before you send or save anything:
- Did I include any confidential information that should not be in an AI tool?
- Are there invented facts or missing context?
- Did I verify the key points against the source?
- Does the output match firm tone and policy?
SharePoint Online habits that function like document management
SharePoint is not iManage, but many of the day-to-day habits that prevent chaos are the same: clear storage rules, disciplined naming, controlled sharing, and version hygiene.
Where to store what
- Team workspaces: SharePoint sites and document libraries
- Personal drafts: OneDrive until ready for collaboration
- Shared “source of truth”: a SharePoint library with consistent naming and versioning
Naming conventions that reduce confusion
Pick a pattern and stick with it. Example:
ClientOrMatter_DocType_Topic_v01_YYYY-MM-DD
Avoid “final_final2_reallyfinal” naming. If your team uses version history correctly, file names can stay stable.
Versioning habits
- Update the same file when iterating as a team
- Use version history instead of creating multiple downloads
- If approvals are required, follow the review workflow instead of emailing attachments
Permissions and sharing
- Prefer group-based access over individual permissions
- Apply least-privilege access
- Avoid external sharing unless explicitly approved
- When sharing links, use “Specific people” where available and appropriate
New hire checklist (first week)
- Confirm access to required SharePoint sites and Teams channels
- Learn where templates live and how to request access
- Review naming rules and sharing boundaries
- Join office hours or book a 1:1 for the first workflow you touch
Common issues and fast fixes
“I can’t find the latest file.”
Check version history. Confirm the library that is the agreed source of truth.
“I can’t access the library.”
Request access via the correct owner group, not ad hoc workarounds.
“There are too many duplicates.”
Consolidate into one source of truth, then archive older copies with clear labeling.
How to deliver this as a training session
Recommended session length: 30 minutes
This is intentionally short. You can repeat it frequently for new hires and rollouts.
Run-of-show
- 5 min: policy-aligned AI guardrails and confidentiality
- 10 min: prompt patterns, live examples, and “what good looks like”
- 10 min: SharePoint document habits, naming, versioning, sharing rules
- 5 min: Q&A and where to get help (office hours, 1:1, guides)
What to bring to the session
- A single example document or internal memo (non-confidential)
- A “bad” vs “good” file naming and sharing example
- Your escalation path (who handles access, who handles policy questions)
What to measure (lightweight, practical metrics)
You do not need a complicated analytics program to prove impact. Start with these:
- Attendance and completion rates for onboarding sessions
- Top recurring questions (to improve the handout iteratively)
- Reduction in common issues reported to IT/PD (duplicates, access requests, “latest version” confusion)
- Time-to-proficiency signal for new hires (self-reported confidence after week 1 and week 4)
Download and reuse
If you want the trainer-ready two-page version of this guide (Word or PDF), you can link it here: