You're not alone
Most small life science companies start their quality management system in Google Drive. It's familiar, it's collaborative, and it's free. There's nothing inherently wrong with this — the FDA doesn't require a specific software platform for your QMS. What they require is that your system meets the standard.
The challenge isn't the tool. It's making sure the way you use it satisfies ISO 13485's requirements for document control, record keeping, and traceability.
What works about Google Drive for QMS
- Collaboration — Multiple people can review and comment on documents in real time
- Version history — Drive tracks changes automatically (though not in a controlled way)
- Accessibility — Your team can access documents from anywhere
- Search — Finding documents is fast
- Cost — Google Workspace is dramatically cheaper than eQMS platforms
For a small team with 20-50 QMS documents, Drive can work. The key is adding the right structure and discipline.
What doesn't work without help
- Document control metadata — Drive doesn't natively track document numbers, revision levels, effective dates, or approval status in a structured way
- Approval workflows — There's no built-in approval routing. You can use comments and sharing, but there's no formal record of who approved what and when
- Controlled copies — Anyone with access can download or print, with no way to mark copies as "uncontrolled"
- Periodic review — No system to flag documents that are due for review
- Training linkage — No way to connect a document revision to required training
These gaps are solvable — but they require intentional structure, naming conventions, and companion tracking (usually a spreadsheet or simple database).
Document control in Drive
A workable document control system in Google Drive needs:
Folder structure that maps to your QMS:
Quality Management System/
├── 01 — Quality Manual/
├── 02 — Management Responsibility/
├── 03 — Design Controls/
├── 04 — Purchasing Controls/
├── 05 — Production Controls/
├── 06 — CAPA/
├── 07 — Records/
└── 08 — Templates/Naming conventions:
SOP-XXX-Rev## — Document Title — e.g., SOP-003-Rev02 — Design Control Procedure
A document control log (spreadsheet) tracking:
- Document number and title
- Current revision
- Effective date
- Author and approver
- Review due date
- ISO 13485 clause reference
Version control and approval workflows
Google Drive's built-in version history is not sufficient for controlled documents. It tracks changes but doesn't distinguish between drafts and approved versions.
What to do instead:
- Keep approved documents as PDFs in a "Current" folder
- Keep editable drafts in a separate "Drafts" or "In Review" folder
- Record approvals in your document control log with dates and names
- Consider Google Workspace add-ons for approval workflows if your team is growing
Access control and permissions
ISO 13485 requires that only authorized personnel can modify QMS documents. Google Drive supports this through sharing settings:
- Set the QMS folder to "Viewer" access by default
- Grant "Editor" access only to document owners and the quality function
- Use Google Groups to manage access by role
- Review sharing permissions quarterly
Making it audit-ready
An FDA inspector or ISO auditor will want to see that your document control system is intentional and followed — not that you use a specific tool. To make your Drive-based QMS audit-ready:
- Have a Document Control SOP that describes how you manage documents in Drive (naming, numbering, approval, distribution, obsolescence)
- Keep your document control log current — this is the auditor's entry point to your system
- Be able to show version history for any controlled document
- Demonstrate access controls — show who can edit vs. who can only view
- Show training records linked to document revisions
When to upgrade — and when not to
Stay with Google Drive when:
- Your team is fewer than 10 people
- You have fewer than 100 controlled documents
- Your quality function can manage the document control log manually
- You're pre-revenue or early-stage
Consider a dedicated QMS when:
- Document control is consuming more than a few hours per week
- You're managing multiple product lines with different regulatory requirements
- You need automated approval workflows and training management
- You're preparing for a notified body audit (EU MDR)
The transition from Drive to a QMS platform is a project in itself. Don't rush it. A well-organized Drive is better than a poorly implemented eQMS.