Review, approve and assemble regulated documents
Protocols, lab reports and batch records move between scientists, quality and regulatory teams. Each of them reviews, comments and signs off in the same viewer, on the files they already use.
Comments · 2
3
formats in one viewer: PDF, Word and Excel
20+
markup, signing and page tools
0
uploads to a third-party service
MIT
licence: free for commercial use
Use cases
Where DocuVerse fits in life sciences & pharma
Review study documents
Protocols and reports open as PDF or Word; reviewers highlight, comment and reply in threads with names and times.
Learn more| A | B | C | D | |
|---|---|---|---|---|
| 2 | Region | Q1 | Q2 | Q3 |
| 3 | North | 18,240 | 21,075 | 24,310 |
| 4 | South | 12,900 | 11,480 | 15,060 |
| 5 | East | 9,615 | 13,230 | 12,775 |
| 6 | West | 16,420 | 17,905 | 20,140 |
| 7 | Total | 57,175 | 63,690 | 72,285 |
Check lab data in workbooks
Results stay in Excel: formulas recalculate, conditional formatting flags values out of range, and the sheet prints to PDF.
Learn moreAssemble submission packages
Merge reports and appendices, reorder and rotate pages, and flatten reviewed marks before the package is filed.
Learn moreThe workflow
From first draft to the final file
- 1
Draft
Authors write in Word and Excel, as they do today.
- 2
Review
Quality and reviewers comment, highlight and request changes, in threads with names and times.
Approve
Approvers stamp Reviewed or Approved with name and date; the final PDF is assembled.
Capabilities
What teams need, and how DocuVerse covers it
Comment threads
Every annotation records its author and time; replies stay with the comment they answer.
Approval stamps
Reviewed, Approved, Final, or your own stamp text with a name and date line.
Office files stay native
Comments and marks are saved into the .docx and .xlsx, where Word and Excel show them.
Batch processing
Stamp, flatten and merge documents with the Node.js or .NET engine on your servers.
Privacy and security
Documents stay where your users are
Study data and patient information are opened and edited on the reviewer’s device. Your application decides what is stored, and where.
- Documents open inside the browser, on the user’s device
- Encrypted PDFs open with the user or owner password
- Your application chooses what is saved, and where
DocuVerse places visual signatures and approval stamps. Certificate-based digital signatures are not supported yet.
only when your app sends it
Build it
This workflow in a few lines
The same engine behind JavaScript and .NET, so the result is identical wherever it runs.
const doc = viewer.getDocument(); // flag every out-of-specification result for the reviewerfor (const hit of doc.search('out of specification')) { doc.addAnnotation(hit.page, { type: 'Highlight', quadPoints: hit.quadPoints, color: '#ff2201', contents: 'Open a deviation', author: 'QA' });}doc.addAnnotation(0, { type: 'Stamp', rect: [400, 720, 560, 770], stampText: 'REVIEWED\nQA, 8 Nov 2026' });The SDKs
Client side, server side, and soon mobile
Private by design
Documents are processed where your users are: in their browser, or on your servers.
Same result everywhere
Every SDK gives the same result, so a file looks and saves the same on every platform.
Free under MIT
Every feature, unlimited users and servers, no licence keys or per-document fees.
Other industries
See it with your own documents
Free under the MIT licence, for PDF, Word and Excel, in the browser and on your servers.
Comments · 3