Check the exact document in its SharePoint library before assuming the edit was lost. A saved change to a checked-out file is separate from checking that file in. Where a library uses draft versions or content approval, those settings can also affect what a colleague sees. These are possible explanations to verify, not a diagnosis of every missing revision. Microsoft explains save and check-in; its versioning guide explains draft visibility.
Which document and revision are you both looking at?
Ask the editor and reviewer to identify the library item they opened and describe one expected change. An approved synthetic test might use a revised section heading. For a real assignment, keep document details inside the firm-approved workspace. Do not paste matter content into an outside troubleshooting service.
For law firms, good case file organization starts with a clear record of the document location, expected revision, time of the observation and each person’s role in the handoff. Avoid collecting passwords or making one person sign in as another. The reviewer can report what they see from their own authorized account.
What should the assistant check in the library?
Inspect the item in the browser with the access already assigned. Microsoft notes that a synced local folder does not display SharePoint’s checkout state. Its guidance also identifies required metadata and an initial check-in as possible issues for newly uploaded files in a library requiring checkout. Read Microsoft’s checkout questions.
Use the table to record what you observed and who should resolve it. Follow the firm’s approval process before changing the library.
| Observed issue | Evidence to capture | Next owner |
|---|---|---|
| The update exists only in the editor’s downloaded copy. | Which file was edited and whether an upload is confirmed. | The authorized editor checks the intended destination. |
| The library item shows a checkout owner. | The exact item and displayed owner/status. | That editor or the library owner resolves the handoff. |
| A draft or pending state is displayed. | The visible version/state and intended reviewer’s observation. | The library owner identifies the applicable review process. |
| The mismatch remains unexplained. | Expected change, observed result and checks already completed. | The firm’s technical owner investigates. |
How do saving, uploading and checking in differ?
For a checked-out document, Microsoft describes editing and saving as steps before check-in. If someone downloaded the document to edit locally, the edited file must be uploaded before check-in. Check-in then makes the changes available to people with the relevant permissions. The actual library’s version and approval rules still matter. See the documented check-in sequence.
The assistant should follow the firm’s instructions for the assigned file, not change checkout requirements to force a result. If another person owns the checkout, record that fact and route the issue. Do not discard their work, overwrite a competing copy or disable a review control as a shortcut.
Why might an authorized reviewer still see an older version?
A library can track major and minor versions and restrict who sees draft items. Microsoft explains that a reader without permission to see drafts can receive the last approved or major version instead. Not every library uses these settings. Check the versioning and draft-visibility guidance.
Content approval is another configured condition. Pending does not always mean hidden: draft-security settings can allow different groups to view the item. Ask the library owner which rules apply rather than treating the status label alone as proof of the colleague’s access. Microsoft describes approval and draft security.
What would a useful revision handoff look like?
Fictional exercise: an assistant changes a heading in a synthetic document index from “Documents received” to “Documents received for review.” The editor sees the new wording; a reviewer reports the earlier wording. No actual client or matter is involved.
The assistant records the item location, expected heading, displayed checkout or version state, and the reviewer’s observation. The responsible editor or library owner completes any authorized next action. The reviewer then confirms the wording they can actually see. The exercise is complete when the handoff records that confirmation or identifies the unresolved issue and its owner. A button click alone is not the proposed acceptance test.
Keep technical visibility separate from permission to send the document outside the firm. The attorney or designated firm reviewer still decides whether the content is ready for its intended use.
What education and experience should I look for?
For Microsoft 365 legal admin outsourcing, review the proposed person’s relevant education, document-management training and actual platform experience. A legal qualification does not establish SharePoint expertise. Ask for a clear explanation of a revision problem and a synthetic work sample that tests observation, written communication and appropriate escalation.
When evaluating a virtual legal assistant for this Microsoft 365 workflow, ask whether their handoff lets someone else locate the exact item and understand what remains unresolved. Confirm individual qualifications and the scope of the assigned role before granting access.
What else should my firm know about revision visibility?
Does every SharePoint document need to be checked in after editing?
No. The documented check-in process applies to checked-out files. Confirm the item state and the library’s actual configuration before deciding what action is needed.
Does Pending mean nobody else can see the file?
No. Visibility depends on the library’s draft-security settings and the viewer’s permissions. Ask the library owner to confirm the applicable rule rather than guessing from the label.
Can an assistant use the reviewer’s password to confirm the result?
Do not share credentials for this check. Ask the reviewer to read back what their own authorized account displays, or use a firm-approved test arrangement with the technical owner.
Does this check approve the document for filing or external release?
No. It addresses a revision-visibility problem. Content approval for the intended legal or business use remains a separate decision for the responsible firm reviewer.
How can I discuss support for this workflow?
Discuss the document handoffs your firm needs through remotelegalteam.com’s Legal Software & CRM Administration or Legal Document Preparation & Management service. Define the permitted tasks, access and reviewer before assigning work. Book A Strategy Call.
This article provides general operational information, not legal advice or an assessment of your firm’s SharePoint configuration.
