A lab moves its administrative collaboration and case-related documents into SharePoint. During the demo, the migration team shows off version history: open a document, pick an earlier version, restore it. It looks reassuring. Then the quality assurance manager asks, "Can we show everyone who had possession of this item, who exported it, and which copy went to the prosecutor?"
That question changes the project. Version history tracks saved changes to a file. Chain of custody documentation records who handled an item, when, and under what authority, across every transfer the lab's evidence procedures cover. A file-management feature can help protect integrity, but on its own it can't establish every transfer, handling event, authorization, or identity that record needs.
At a glance
- Version history shows how a stored file changed. A custody record shows who handled it, who released it, and under which procedure.
- Audit logs, permissions, case identifiers, transfer receipts, retention, and validation have to be designed together.
- Before moving evidence-related workflows, map your quality system to what the technology can actually prove, and write down the gaps.
Where the two records part ways
Picture a digital case file prepared for outside review. An analyst creates the document in an approved repository, and a supervisor reviews it. Someone downloads a copy, sends it to an outside party, and later restores an earlier version of the original. The SharePoint version list shows versions of the original document. So what records the transfer of the downloaded copy? Who approved the release? Did the outside reviewer get the intended version? Was the file changed after it left the controlled system?
These are ordinary questions. A quality manager, accreditation assessor, prosecutor, or defense attorney may ask any of them about the records behind a scientific conclusion. SharePoint can be a sound part of the workflow, especially for collaboration and controlled distribution. It just shouldn't be mistaken for a complete evidence-management system or a laboratory information management system (LIMS).
What version history and chain of custody documentation each answer
- What changed in this stored file?
- SharePoint version history: Can show versions and editors for supported changes
- Complete custody process: Records which changes matter to evidence handling
- Who had access?
- SharePoint version history: Permissions and audit records help, depending on configuration
- Complete custody process: Tracks authorized custodians and roles across the full lifecycle
- Was a copy exported or downloaded?
- SharePoint version history: Needs the right audit events; version history alone won't show it
- Complete custody process: Records the release, recipient, purpose, and transfer acknowledgment
- What happened outside SharePoint?
- SharePoint version history: Generally outside the version list's scope
- Complete custody process: Needs additional records from receiving systems and people
- Can the record be reconstructed later?
- SharePoint version history: Depends on license, retention, logging, and preservation
- Complete custody process: Defined retention and a verifiable process are part of the requirement
Microsoft Purview's audit log can record many SharePoint and OneDrive file actions, including access and downloads, depending on licensing and configuration. That's useful evidence. It still doesn't establish the off-platform chain, physical custody, approval context, or your quality manual's acceptance criteria. Audit retention also has limits, and Microsoft documents different defaults by license and workload. Labs need to set retention and preservation deliberately so they match the obligations that apply.
Write the custody question before choosing the tool
Start with the lab's SOPs, case workflow, and information classification. Separate evidentiary material from administrative records and collaboration copies. Not every document that mentions a case needs the same custody treatment, but blurry categories lead either to unsafe sharing or to procedures nobody can follow.
For each type of item, work through a short set of questions. What is the authoritative record, and where is it stored? Who can create, view, change, export, or release it? Which events need documented approval? How is the receiving party identified? What makes the record complete? What is the retention rule, and who can place a hold? What happens if a restored copy differs from the original?
The laboratory quality team should own the requirement. IT turns it into identity, permissions, logging, backup, and workflow design. Legal and accreditation representatives decide whether the procedure meets the lab's obligations. Technology can preserve records and bring them to the surface when they're needed. Whether evidence is admissible remains a legal determination.
Build a controlled sharing workflow
Name the case and the recipient
For a transfer to an outside agency or prosecutor, skip broad folders and anonymous, reusable links. Set a case identifier, a named recipient, the purpose of sharing, a defined access window, and an approved repository or transfer method. Where SharePoint fits, use authenticated sharing addressed to specific people instead of open "anyone" links. Keep in mind that a link expiration doesn't close every path. Guest membership, site permissions, and downloaded copies each need their own review.
Record release and receipt
A defensible workflow might include authorization by the designated lab role, a manifest of the exact items released, timestamps, cryptographic hashes where they help, recipient identity, and receipt confirmation. Hashes are good at confirming that the bytes match. They can't tell you who had custody, why a transfer was authorized, or whether the underlying method is reliable, so they belong alongside the custody record as supporting evidence.
Preserve both the data and the history
When an item is updated, restored, transferred, or deleted under an authorized procedure, keep the related records under the applicable retention and legal-hold rules. Test the logging configuration, the export format, and your ability to reconstruct a real sample case. Include service accounts and privileged administrators in the monitoring scope, and protect the audit system itself from unauthorized changes.
The FBI's CJIS Security Policy includes requirements for event logging and for protecting audit records in environments where it applies. Accreditation expectations, ISO/IEC 17025 obligations, local SOPs, state records rules, and court processes each need their own mapping. There's no universal setting labeled "CJIS and accreditation compliant."
Which workloads belong on-premises?
A common mistake is treating a Microsoft 365 migration as a decision to move every lab workload to the cloud. Many labs use Teams or SharePoint for administrative collaboration and approved external distribution while keeping LIMS, original evidence stores, and instrument data on separately controlled on-premises or private-cloud infrastructure.
At CTP, we design lab environments to be deliberately hybrid. The question for each record is where it has to live to protect performance, integrity, availability, and defensibility. Identity controls, cross-platform monitoring, immutable backups, and segmented networks then apply on both sides of that line. For most labs, the boundary between original evidence and collaborative working copies matters more than the product chosen for either side.
Test it before you migrate
Choose one representative, non-sensitive test case and run it through the full journey. Create an item, review it, share it with an authorized outside account, download it, revoke access, restore a previous version, and then try to reconstruct the history from retained records. Ask a QA reviewer who didn't run the test to find the authoritative original, the changed version, the recipient, and the release authorization.
Every step they can't explain becomes a design requirement. Sometimes the fix is a SharePoint setting or a Purview audit configuration. Sometimes it's an approval workflow, a LIMS integration, a dedicated evidence-transfer platform, or a revised SOP. Either way, you want to find the gap before real case material depends on it.
A more useful question
"Does SharePoint have version history?" Yes, it does. The question worth asking is this: if someone challenges this file's history two years from now, can we produce a clear, complete, and defensible account of what happened?
That question leads to a different architecture. It respects evidentiary systems, uses collaboration tools where they fit, and keeps a record of the controls that support the lab's quality process. If you're planning a migration and want to pressure-test the custody side first, see how we approach forensic and crime laboratory IT or start a conversation with our team.

