Briefs and source materials
Review outside instructions before they can steer research, drafting, recommendations or project setup.
Document security for client work
Scan client documents before they enter AI-assisted work.
Check briefs and outside source materials before they enter the AI systems you build or operate for clients. Follow each version’s decision and retrieve the current Approved copy as the work develops.
- Outside exact versionClient document
- Organise the recordChoose a Collection for the workflow
- Completed Standard ScanCheck and route
Three destinations
- ApprovedLibrary → current eligible version → Client project
- Needs reviewInvestigate, replace or recheck
- QuarantineKeep this exact version out
The Collection keeps all three outcomes organised. Membership does not grant approval or retrieval.
No decision: The scan could not complete, so no security decision was made. Retry is available and no new scan credit is consumed.
The client-work problem
Give each incoming brief a clear route into the project.
Client documents may arrive through email, shared drives, portals or third parties. They can contain hidden, active or instruction-like document content that deserves review before AI-assisted drafting or analysis.
Check the file before it influences a draft, and keep track of which version you used when the client sends an update.
See the supported scan areasConsistent handling
Apply the same checkpoint across the engagement.
The document type may change, but the decision about what enters project context should remain visible.
Hidden and active surfaces
Supported document features or machine-readable content may deserve review before AI-assisted work begins.
Revised deliverables
Treat a changed or newly returned file as a new intake decision rather than relying on an earlier scan.
Your document workflow
Put document admission before project use.
Make the checkpoint part of the handoff whenever external files enter AI-assisted work.
- 1Receive the client brief or third-party source material.
- 2Confirm permission, confidentiality and handling requirements for AI use.
- 3Explicitly choose the Collection for the client or project, then check the supported exact version before drafting.
- 4Follow Approved, Needs review or Quarantine, and keep the record organised in its Collection while you act on the decision; membership never grants retrieval.
- 5Use only the current eligible Approved exact version from the Library at the next stage of authorised work.
- 6Submit a revised client attachment as a replacement that needs its own scan before it can be retrieved.
An accepted replacement supersedes the earlier version immediately, with no fallback while it is pending or held. .mdSiren supports document review but does not grant permission to use client material with an AI service. Pro API access supports document submission, status checks and retrieval of eligible current Approved exact-version copies under the same rules.
Before client work
Keep authority, privacy and scan findings in view.
A document-security check is one part of responsible client handling, not a substitute for the engagement’s rules.
- Confirm that the document is authorised for the intended AI-assisted use.
- Assign it to the Collection for the client or project.
- Scan the exact version before it enters project context.
- Review findings without copying document content into support emails.
- Check coverage and resolve anything that needs attention.
- Check the replacement whenever the source document changes.
This checkpoint supports the document decision but does not grant permission for AI use. Do not send client documents, credentials or sensitive content to the website contact address.
Related resources
Before documents become AI context
Make outside client files a deliberate intake decision.
Check incoming client documents, follow each version’s decision and retrieve the current Approved copy for authorised AI workflows.