DocRead Knowledgebase – Tutorials & Technical Guides https://www.collaboris.com/category/knowledgebase/docread-kb/ We make compliance simple Fri, 28 Nov 2025 15:28:11 +0000 en-GB hourly 1 https://www.collaboris.com/wp-content/uploads/2016/07/collaboris_favicon.png DocRead Knowledgebase – Tutorials & Technical Guides https://www.collaboris.com/category/knowledgebase/docread-kb/ 32 32 The Hidden Costs of Poor Policy Management in Microsoft 365 https://www.collaboris.com/m365-policy-management-hidden-costs/ Fri, 28 Nov 2025 15:28:11 +0000 https://www.collaboris.com/?p=1379478 .thrv_text_element{overflow-wrap: break-word;}.tcb-post-list.masonry article{flex-basis: unset;position: absolute;}.tve_editor_page .tcb-post-list.masonry article{transition: none;}article{box-sizing: border-box;transition: opacity 1s ease-in-out;width: 100%;}article.thrv_wrapper{margin-bottom: 0px;margin-top: 0px;padding: 0px;}body:not(.tve_editor_page) .tcb-post-list[data-disabled-links="1"] article{position: relative;}body:not(.tve_editor_page) .tcb-post-list[data-disabled-links="1"] article > .tve-article-cover,body:not(.tve_editor_page) .tcb-post-list[data-disabled-links="1"] article .tve-article-cover a{position: absolute;width: 100%;height: 100%;top: 0px;left: 0px;cursor: pointer;z-index: 12;}.tcb-article-cover-link,.tcb-post-list .tve-article-cover a{line-height: 0 !important;font-size: 0px !important;color: rgba(0,0,0,0) !important;}.tve-loading article{opacity: 0.4;}.notifications-content-wrapper.tcb-permanently-hidden{display: none !important;}.tcb-permanently-hidden{display: none !important;}.tar-disabled{cursor: default;opacity: 0.4;pointer-events: none;}html.tve-o-hidden.tve-hide-overflow.tve-l-open{overflow: hidden;}html.tve-o-hidden.tve-hide-overflow.tve-l-open:not(.bp-th){height: auto !important;}body.tve-o-hidden.tve-hide-overflow.tve-l-open{overflow: hidden;}body.tve-o-hidden.tve-hide-overflow.tve-l-open:not(.bp-t){height: auto !important;}.tve_p_lb_overlay{opacity: 0;}.tve_p_lb_background{text-align: center;position: fixed;top: 0px;right: 0px;bottom: 0px;left: 0px;z-index: 999992;padding: 10px;}.tve-l-open.tve-o-hidden .tve_p_lb_background{overflow: hidden;}.tve-l-open.tve-o-hidden .tve_p_lb_background.tve-scroll{overflow-y: auto;}.tve_p_lb_background .tve_p_lb_overlay{position: absolute;top: 0px;left: 0px;right: 0px;opacity: 0;background: rgb(0,0,0);transition: opacity 0.3s ease-out;min-height: 100%;}.tve_p_lb_background.tve_lb_closing .tve_p_lb_overlay{transition: opacity 0.3s ease-out;opacity: 0 !important;}.tve_p_lb_background.tve_lb_closing .tve_p_lb_content{opacity: 0;}.tve_p_lb_background.tve_lb_opening .tve_p_lb_overlay,.tve_post_lightbox .tve_p_lb_background .tve_p_lb_overlay,.tve_p_lb_background.tve_lb_open .tve_p_lb_overlay{opacity: 0.8;transition: opacity 0.3s ease-out;}.tve_p_lb_background .tve_p_lb_content{border-radius: 6px;position: relative;background-color: rgb(255,255,255);padding: 15px;width: 100%;max-width: 650px;text-align: left;overflow: visible;box-sizing: border-box !important;margin: auto !important;}#tve_current_event_settings .tve_p_lb_background .tve_p_lb_content{box-shadow: rgb(0,0,0) 0px 0px 6px -2px;background-color: rgb(255,255,255);}.tve_p_lb_background .tve_p_lb_content .tve_p_lb_inner{max-height: none !important;}.tve_p_lb_background .tve_p_lb_content .tve_p_lb_close{z-index: 99;position: absolute;top: -10px;right: -10px;display: block;width: 22px;height: 22px;line-height: 20px;text-align: center;border: 1px solid rgb(255,255,255);background: rgb(0,0,0);color: rgb(255,255,255);text-decoration: none;font-size: 12px;transition: 0.1s;border-radius: 22px;}.tve_p_lb_background .tve_p_lb_content .tve_p_lb_close:hover{transform: scale(1.1);}.tve_p_lb_background .tve_p_lb_content .scon .btn{display: block;width: auto;}.tve_p_lb_background .tve_p_lb_content .out{margin-left: 0px;margin-right: 0px;}.tve_p_lb_background.tve_lb_anim_instant .tve_p_lb_overlay{opacity: 0.8;}.tve_p_lb_background.tve_lb_anim_instant.tve_lb_closing{display: none !important;}.tve_p_lb_background.tve_lb_anim_zoom_in .tve_p_lb_content{transform: scale(0);}.tve_p_lb_background.tve_lb_anim_zoom_in.tve_lb_opening .tve_p_lb_content,.tve_p_lb_background.tve_lb_anim_zoom_in.tve_lb_open .tve_p_lb_content{transform: scale(1);transition: 0.5s ease-out;}.tve_p_lb_background.tve_lb_anim_zoom_in.tve_lb_closing .tve_p_lb_content{transform: scale(0);transition: 0.3s ease-out;}.tve_p_lb_background.tve_lb_anim_zoom_out .tve_p_lb_content{transform: scale(1.8);}.tve_p_lb_background.tve_lb_anim_zoom_out.tve_lb_opening .tve_p_lb_content,.tve_p_lb_background.tve_lb_anim_zoom_out.tve_lb_open .tve_p_lb_content{transform: scale(1);transition: 0.5s ease-out;}.tve_p_lb_background.tve_lb_anim_zoom_out.tve_lb_closing .tve_p_lb_content{transform: scale(1.8);transition: 0.3s ease-out;}.tve_p_lb_background.tve_lb_anim_rotate .tve_p_lb_overlay{transition: opacity 0.5s;}.tve_p_lb_background.tve_lb_anim_rotate .tve_p_lb_content{transform: scale(0) rotate(500deg);}.tve_p_lb_background.tve_lb_anim_rotate.tve_lb_opening .tve_p_lb_content,.tve_p_lb_background.tve_lb_anim_rotate.tve_lb_open .tve_p_lb_content{transform: scale(1) rotate(0deg);transition: 0.6s ease-out;}.tve_p_lb_background.tve_lb_anim_rotate.tve_lb_closing .tve_p_lb_content{transform: scale(0) rotate(500deg);transition: 0.7s ease-out;}.tve_p_lb_background.tve_lb_anim_slide_top .tve_p_lb_content{transform: translateY(-100%);}.tve_p_lb_background.tve_lb_anim_slide_top.tve_lb_opening .tve_p_lb_content,.tve_p_lb_background.tve_lb_anim_slide_top.tve_lb_open .tve_p_lb_content{transform: translateY(0px);transition: 0.5s ease-out;}.tve_p_lb_background.tve_lb_anim_slide_top.tve_lb_closing .tve_p_lb_content{transform: translateY(100%);transition: 0.5s ease-out;}.tve_p_lb_background.tve_lb_anim_slide_bottom .tve_p_lb_content{opacity: 0;transform: translateY(1400px);}.tve_p_lb_background.tve_lb_anim_slide_bottom.tve_lb_opening .tve_p_lb_content,.tve_p_lb_background.tve_lb_anim_slide_bottom.tve_lb_open .tve_p_lb_content{opacity: 1;transform: translateY(0px);transition: 0.5s ease-out;}.tve_p_lb_background.tve_lb_anim_slide_bottom.tve_lb_closing .tve_p_lb_content{transform: translateY(-1400px);transition: 0.7s ease-out;}.tve_p_lb_background.tve_lb_anim_lateral .tve_p_lb_content{opacity: 0;transform: translateX(-100%);}.tve_p_lb_background.tve_lb_anim_lateral.tve_lb_opening .tve_p_lb_content,.tve_p_lb_background.tve_lb_anim_lateral.tve_lb_open .tve_p_lb_content{opacity: 1;transform: translateX(0px);transition: 0.3s ease-out;}.tve_p_lb_background.tve_lb_anim_lateral.tve_lb_closing .tve_p_lb_content{transform: translateX(100%);transition: 0.3s ease-out;}html{text-rendering: auto !important;}html body{text-rendering: auto !important;}.thrv_wrapper{margin-top: 20px;margin-bottom: 20px;padding: 1px;}.thrv_wrapper div{box-sizing: content-box;}.thrv_wrapper.thrv_text_element{margin: 0px;}p{font-size: 1em;}.tve_p_lb_background .tve_p_lb_content.pattern1{background: rgb(41,128,185);}.tve_p_lb_background .tve_p_lb_content.pattern2{background: rgb(192,57,43);}.tve_p_lb_background .tve_p_lb_content.pattern3{background: rgb(46,204,113);}.tve_p_lb_background .tve_p_lb_content.tve_brdr_none,.tve_p_lb_background .tve_p_lb_close.tve_brdr_none{border-style: none !important;}.tve_p_lb_background .tve_p_lb_content.tve_brdr_dotted,.tve_p_lb_background .tve_p_lb_close.tve_brdr_dotted{border-style: dotted !important;}.tve_p_lb_background .tve_p_lb_content.tve_brdr_dashed,.tve_p_lb_background .tve_p_lb_close.tve_brdr_dashed{border-style: dashed !important;}.tve_p_lb_background .tve_p_lb_content.tve_brdr_solid,.tve_p_lb_background .tve_p_lb_close.tve_brdr_solid{border-style: solid !important;}.tve_p_lb_background .tve_p_lb_content.tve_brdr_double,.tve_p_lb_background .tve_p_lb_close.tve_brdr_double{border-style: double !important;}.tve_p_lb_background .tve_p_lb_content.tve_brdr_groove,.tve_p_lb_background .tve_p_lb_close.tve_brdr_groove{border-style: groove !important;}.tve_p_lb_background .tve_p_lb_content.tve_brdr_ridge,.tve_p_lb_background .tve_p_lb_close.tve_brdr_ridge{border-style: ridge !important;}.tve_p_lb_background .tve_p_lb_content.tve_brdr_inset,.tve_p_lb_background .tve_p_lb_close.tve_brdr_inset{border-style: inset !important;}.tve_p_lb_background .tve_p_lb_content.tve_brdr_outset,.tve_p_lb_background .tve_p_lb_close.tve_brdr_outset{border-style: outset !important;}body.tve-lightbox-page .tve_p_lb_overlay{position: fixed;top: 0px;right: 0px;bottom: 0px;left: 0px;background: rgb(0,0,0);opacity: 0.8;}body.tve-lightbox-page .tve_p_lb_background{top: 32px;padding-top: 150px;}body.tve-lightbox-page .tve-spacer{height: 40px;width: 100%;}:not(#_s):not(#_s) .tcb-conditional-display-placeholder{min-height: var(--tcb-container-height-d,100px) !important;position: relative;}:not(#_s):not(#_s) .tcb-conditional-display-placeholder.thrv-page-section{box-sizing: border-box;margin: 0px;}:not(#_s):not(#_s) .tcb-conditional-display-placeholder.thrv-content-box{box-sizing: border-box;}:not(#_s):not(#_s) .tcb-conditional-display-placeholder .tve-page-section-out,:not(#_s):not(#_s) .tcb-conditional-display-placeholder .tve-content-box-background{box-sizing: border-box;position: absolute;width: 100%;height: 100%;left: 0px;top: 0px;overflow: hidden;}@media (max-width: 1023px){:not(#_s):not(#_s) .tcb-conditional-display-placeholder{min-height: var(--tcb-container-height-t) !important;}}@media (max-width: 767px){html{overflow-x: hidden !important;}html,body{max-width: 100vw !important;}:not(#_s):not(#_s) .tcb-conditional-display-placeholder{min-height: var(--tcb-container-height-m) !important;}}@media only screen and (min-device-width: 375px) and (max-device-width: 736px){html.tve-o-hidden.tve-hide-overflow.tve-l-open:not(.bp-th){height: 100% !important;}body.tve-o-hidden.tve-hide-overflow.tve-l-open:not(.bp-t){height: 100% !important;}}@media screen and (max-device-width: 480px){body{text-size-adjust: none;}}

The Hidden Costs of Poor Policy Management in Microsoft 365(And Why Agencies Keep Paying for a Problem They Think They Already Solved)FDA 21 CFR Part 11 Compliance: How DocRead Helps Organizations Stay on Track Most organizations—especially in law enforcement—assume that because their policies “live” in Microsoft 365, they’re covered. SharePoint has a folder. Teams has […]

The post The Hidden Costs of Poor Policy Management in Microsoft 365 appeared first on Collaboris.

]]>

The Hidden Costs of Poor Policy Management in Microsoft 365

(And Why Agencies Keep Paying for a Problem They Think They Already Solved)

The Hidden Costs of Poor Policy Management in Microsoft 365

FDA 21 CFR Part 11 Compliance: How DocRead Helps Organizations Stay on Track

Most organizations—especially in law enforcement—assume that because their policies “live” in Microsoft 365, they’re covered. SharePoint has a folder. Teams has a channel. Someone emailed a PDF last year.
But here’s the reality:


Storing a policy is not the same as proving that people read it.
And that gap is where agencies quietly bleed time, money, and credibility.


And one thing has always been consistent:
Microsoft 365 is powerful—but it does not solve policy acknowledgment, audit readiness, or legal defensibility on its own.

The Hidden Costs No One Accounts For

1. Wasted Time

When policies are scattered across SharePoint sites, Teams chats, and email attachments, your people waste hours hunting for “the latest version.” Multiply that by every officer, supervisor, or admin—and the cost spikes fast.

Agencies think they have a document system. What they really have is digital clutter.

2. Failed Audits

Auditors don’t care where your policies are stored. They care about proof:

  • Who read the updated use-of-force directive?
  • Who acknowledged the new evidence-handling procedure?
  • Can you show me a timestamped record?

Without this, an agency walks into an audit already on the defensive.

3. Legal Exposure

If an employee says, “I never saw that policy,” and you can’t prove otherwise, the agency is exposed. In law enforcement, that’s not a minor risk—it’s a direct liability in court, in IA investigations, and in regulatory reviews.

Storage is not compliance. Storage is storage.

Tired of reminding staff to read your company policies?

DocRead makes compliance simple

Where Collaboris Fits In

This is exactly the gap we built DocRead to close.

Think of it as the missing operational layer Microsoft 365 never provided:

  • Targeted policy distribution

  • Mandatory acknowledgments

  • Reliable, audit-ready tracking

  • Version accuracy

  • Reporting built for oversight

DocRead doesn’t replace your Microsoft 365 investment—it makes it defensible. It turns policies from passive files into actionable, trackable compliance events.

For agencies like the ones we serve—sheriff’s departments, police services, and public-sector teams—the difference is night and day. Less manual follow-up. Fewer audit surprises. Stronger legal posture.

Are your policies read on time and by the right people?

DocRead makes compliance simple

Why This Matters

If your agency relies on Microsoft 365 without a structured policy-management layer, you’re paying for inefficiency you don’t see and assuming compliance you don’t actually have.

The fix isn’t more training or more meetings. It’s better tooling.

And that’s where Collaboris steps in.

If you’re wrestling with policy acknowledgment chaos—or if you’ve already felt the pain during an audit—I’m happy to share what agencies are doing now to close the gaps.

Just reach out.

Get your free Standard Operating Procedures guide

Creating Standard Operating Procedures for your organisation doesn't have to be complicated. This guide will introduce you to the whole lifecycle from creation to training and distribution.

You may also like:

The post The Hidden Costs of Poor Policy Management in Microsoft 365 appeared first on Collaboris.

]]>
How Collaboris Helps Law Enforcement Agencies Achieve ISO 9001 Certification https://www.collaboris.com/iso-9001-police-accountability/ Wed, 01 Oct 2025 20:50:53 +0000 https://www.collaboris.com/?p=1379461 How Collaboris Helps Law Enforcement Agencies Achieve ISO 9001 Certification For law enforcement, consistency and accountability are non-negotiable. Citizens expect professionalism, regulators demand compliance, and courts require proof that procedures are followed. ISO 9001, the global standard for Quality Management Systems (QMS), helps agencies demonstrate that their operations are structured and reliable.But certification isn’t just […]

The post How Collaboris Helps Law Enforcement Agencies Achieve ISO 9001 Certification appeared first on Collaboris.

]]>

How Collaboris Helps Law Enforcement Agencies Achieve ISO 9001 Certification

For law enforcement, consistency and accountability are non-negotiable. Citizens expect professionalism, regulators demand compliance, and courts require proof that procedures are followed. ISO 9001, the global standard for Quality Management Systems (QMS), helps agencies demonstrate that their operations are structured and reliable.
But certification isn’t just about having policies—it’s about showing that every officer and staff member has received, understood, and applied them. That’s where Collaboris’ DocRead solution comes in.


The challenge? SOX compliance isn’t just about finance teams — it touches HR, IT, and operations. And while many organizations focus on controls, they often overlook one key piece: ensuring people actually read, understand, and follow those controls.

Why ISO 9001 Matters for Law Enforcement

ISO 9001 helps agencies strengthen public trust, reduce liability, and maintain courtroom credibility.
 
For example:


  • Riverside Sheriff’s Office could use ISO 9001 and DocRead to ensure that updated field procedures, like pursuit protocols or evidence handling, are quickly distributed and acknowledged across hundreds of deputies.

  • Brantford Police Service might leverage DocRead to keep accurate training records for use-of-force or community engagement programs, ensuring every officer’s training is logged and audit-ready.

  • North Wales Police could streamline document control by using DocRead to distribute operational directives, making sure staff always work from the latest version—an essential part of ISO 9001 compliance.

Tired of reminding staff to read your company policies?

DocRead makes compliance simple

How DocRead Supports ISO 9001


DocRead directly addresses common compliance challenges:


  • Procedure Adherence: Distribute updated policies (e.g., arrest protocols, body-worn camera use) and track acknowledgments.
  • Training Records: Centralize proof that officers are trained in required processes.
  • Document Control: Ensure staff always work from the latest version of manuals and directives.

Are your policies read on time and by the right people?

DocRead makes compliance simple

Real-World Impact


Instead of scrambling to prove compliance during audits, agencies like Riverside, Brantford, or North Wales Police can show complete records of who acknowledged what, when, and how they were trained. This saves time, reduces risk, and strengthens public and legal confidence.


Collaboris’ Role


ISO 9001 in law enforcement is about more than certification—it’s about trust. By embedding DocRead, agencies build a sustainable system where accountability, training, and quality management are all audit-ready.

With ISO 9001, agencies commit to quality. With Collaboris and DocRead, they prove it.

Get your free Standard Operating Procedures guide

Creating Standard Operating Procedures for your organisation doesn't have to be complicated. This guide will introduce you to the whole lifecycle from creation to training and distribution.

You may also like:

The post How Collaboris Helps Law Enforcement Agencies Achieve ISO 9001 Certification appeared first on Collaboris.

]]>
SOX Compliance with Collaboris and DocRead: Making Governance Practical https://www.collaboris.com/sox-compliance/ Tue, 23 Sep 2025 12:21:17 +0000 https://www.collaboris.com/?p=1379454 SOX Compliance with Collaboris and DocRead: Making Governance Practical The Sarbanes-Oxley Act (SOX) remains one of the most critical frameworks for companies that want to maintain investor trust. It ensures that financial reporting is accurate, internal controls are sound, and corporate disclosures are reliable.The challenge? SOX compliance isn’t just about finance teams — it touches […]

The post SOX Compliance with Collaboris and DocRead: Making Governance Practical appeared first on Collaboris.

]]>

SOX Compliance with Collaboris and DocRead: Making Governance Practical

SOX Compliance

The Sarbanes-Oxley Act (SOX) remains one of the most critical frameworks for companies that want to maintain investor trust. It ensures that financial reporting is accurate, internal controls are sound, and corporate disclosures are reliable.


The challenge? SOX compliance isn’t just about finance teams — it touches HR, IT, and operations. And while many organizations focus on controls, they often overlook one key piece: ensuring people actually read, understand, and follow those controls.

This is exactly where Collaboris and DocRead bridge the gap.

1. Code of Conduct: Setting the Tone at the Top


Every SOX-compliant company must have a documented code of conduct and ethics policy. But having a code isn’t enough — regulators expect evidence that employees have reviewed and acknowledged it.


Example:

A publicly traded retailer used DocRead to distribute its updated ethics policy to more than 20,000 employees worldwide. Within 30 days, they achieved a 96% acknowledgment rate — complete with a digital paper trail for auditors.

Tired of reminding staff to read your company policies?

DocRead makes compliance simple

2. Internal Control Procedures: Distributing the Right Information


SOX Section 404 requires management to document and test internal controls over financial reporting. DocRead allows organizations to assign relevant procedures to specific roles, ensuring that only the right employees are asked to review them — reducing noise and improving compliance rates.


Example:


A global logistics company used DocRead to target specific internal control procedures to finance managers, system owners, and IT admins. This kept everyone aligned on their responsibilities and reduced instances of control failures caused by miscommunication.


3. Audit Trail and Accountability

When auditors ask for proof that employees were informed of financial control changes, DocRead delivers. Its reporting capabilities make it easy to demonstrate not just that controls exist, but that they were communicated, read, and acknowledged by the right people.

Example:


A tech company undergoing its first SOX audit was able to present clean, timestamped acknowledgment reports for every control procedure — reducing audit time and earning commendation for their documentation maturity.

Are your policies read on time and by the right people?

DocRead makes compliance simple

Bottom Line:


SOX compliance is about more than financial statements — it’s about culture, governance, and accountability. Collaboris and DocRead make compliance a proactive, well-documented process rather than a last-minute scramble.

Get your free Standard Operating Procedures guide

Creating Standard Operating Procedures for your organisation doesn't have to be complicated. This guide will introduce you to the whole lifecycle from creation to training and distribution.

You may also like:

The post SOX Compliance with Collaboris and DocRead: Making Governance Practical appeared first on Collaboris.

]]>
ISO 27001 Compliance Made Simple with Collaboris and DocRead https://www.collaboris.com/iso-27001-with-collaboris-docread/ Tue, 23 Sep 2025 11:25:24 +0000 https://www.collaboris.com/?p=1379447 ISO 27001 Compliance Made Simple with Collaboris and DocRead ISO 27001 is no longer just a "nice-to-have" for organizations — it’s quickly becoming a baseline expectation for doing business in an interconnected world. The standard establishes a framework for building an Information Security Management System (ISMS) that doesn’t just check compliance boxes but actively protects […]

The post ISO 27001 Compliance Made Simple with Collaboris and DocRead appeared first on Collaboris.

]]>

ISO 27001 Compliance Made Simple with Collaboris and DocRead

ISO 27001 Compliance

ISO 27001 is no longer just a "nice-to-have" for organizations — it’s quickly becoming a baseline expectation for doing business in an interconnected world. The standard establishes a framework for building an Information Security Management System (ISMS) that doesn’t just check compliance boxes but actively protects sensitive data, reduces risk, and improves resilience.


But let’s be honest: implementing ISO 27001 can be overwhelming. Between drafting policies, educating staff, and gathering audit evidence, the process often stalls not because of technology gaps, but because of execution. That’s where Collaboris and DocRead come in — turning what could be a documentation nightmare into a structured, auditable, and easy-to-manage process.

1. Policy Acknowledgment: Closing the Loop


ISO 27001 requires documented policies — but having policies is not enough. Employees must read, understand, and acknowledge them. DocRead automates this process by pushing critical documents like the Acceptable Use Policy, Access Control Policy, and Incident Response Plan to the right people at the right time.


Example:


A mid-sized healthcare provider rolled out ISO 27001 and used DocRead to ensure all clinical and administrative staff acknowledged the updated Data Handling Policy. Within two weeks, leadership had a 100% acknowledgment rate across 3,500 employees — a task that previously took months of chasing signatures.


2. Awareness Training: Evidence of Culture


Training employees on information security responsibilities isn’t just good practice; it’s a control requirement under ISO 27001. DocRead allows organizations to distribute security awareness materials, track completions, and store that data for future audits.


Example:


A financial services firm used DocRead to deliver phishing awareness training and monitored completion rates in real-time. This not only satisfied ISO 27001 requirements but also led to a measurable drop in phishing-related incidents — proving that compliance efforts can deliver business value.

Tired of reminding staff to read your company policies?

DocRead makes compliance simple

3. Version Control: Staying Current

Policies aren’t static — they evolve with threats and business needs. ISO 27001 auditors expect to see a controlled process for maintaining and communicating updates. DocRead ensures the latest versions are automatically distributed and acknowledged, reducing the risk of employees acting on outdated guidance.


Example:


A manufacturing company updated its BYOD (Bring Your Own Device) policy following a security incident. With DocRead, they quickly distributed the new version to all impacted teams and had full acknowledgment logs within days — something that could have taken weeks without automation.


4. Audit Evidence: No Scramble, No Stress


Audits shouldn’t mean a last-minute scramble for spreadsheets and email receipts. With DocRead, you can produce detailed acknowledgment reports instantly, showing auditors exactly who has read which documents and when.


Example:


During a certification audit, a SaaS provider used DocRead’s reporting dashboard to show a complete history of policy acknowledgments, impressing auditors with their level of control and traceability — saving both time and credibility.

Are your policies read on time and by the right people?

DocRead makes compliance simple

Bottom Line:


ISO 27001 isn’t just about documentation — it’s about building a culture of security. Collaboris and DocRead give organizations the tools to do just that, in a way that is scalable, auditable, and sustainable.

Get your free Standard Operating Procedures guide

Creating Standard Operating Procedures for your organisation doesn't have to be complicated. This guide will introduce you to the whole lifecycle from creation to training and distribution.

You may also like:

The post ISO 27001 Compliance Made Simple with Collaboris and DocRead appeared first on Collaboris.

]]>
DocRead vs PowerDMS: Policy & Training Tools Comparison https://www.collaboris.com/docread-vs-powerdms/ Tue, 09 Sep 2025 22:33:52 +0000 https://www.collaboris.com/?p=1379426 DocRead vs PowerDMS: Policy & Training Tools Comparison Many organizations already pay for Microsoft 365 and use SharePoint for document management. DocRead (plus DocSurvey) builds on SharePoint to deliver policies, track acknowledgements, and add quizzes—without adding a new platform.PowerDMS is a standalone suite that requires separate licenses, employee training, and ongoing admin support. Total cost […]

The post DocRead vs PowerDMS: Policy & Training Tools Comparison appeared first on Collaboris.

]]>

DocRead vs PowerDMS: Policy & Training Tools Comparison

DocRead vs PowerDMS

Many organizations already pay for Microsoft 365 and use SharePoint for document management. DocRead (plus DocSurvey) builds on SharePoint to deliver policies, track acknowledgements, and add quizzes—without adding a new platform.

PowerDMS is a standalone suite that requires separate licenses, employee training, and ongoing admin support.

Total cost for PowerDMS can run into six figures, while DocRead/DocSurvey typically costs under $10K for most organizations.

Feature

PowerDMS (standalone)

Office 365/SharePoint (with DocRead/DocSurvey)

Document repository & versioning

Centralized cloud library: Policies, procedures and records are stored in one secure site with version control and granular access rights.

Uses existing SharePoint/OneDrive libraries with built-in permissions and version control. DocRead works with existing document libraries without altering files. No file migration needed.

Policy distribution & assignment

Upload and assign policies by role/team. Mobile apps & email notifications deliver updates.

Target policies to groups directly in SharePoint. Deadlines & reminders show up in users’ dashboards (“Compliance Cockpit”).

Acknowledgement tracking

Built-in attestation: managers require employees to e-sign or check a box on policy updates. E-signature or checkbox tracking with audit trail.

Tracks read-status in real time. Data can flow into Power BI for dashboards and compliance reports.

Training & Quizzes

Built-in training module with videos, tests, and automated recertification.

DocSurvey attaches quizzes to documents/videos. Supports pass/fail scoring. Can combine with Teams, Forms, or Stream for full e-learning. Real-time reports show answers and scores.

Certification tracking

Dedicated module for tracking licenses/certifications, with auto-renewal reminders.

Use SharePoint lists or Planner/Power Automate workflows to record certification dates and send renewal alerts.

Reporting & analytics

Pre-built dashboards for compliance rates, training completion, and audit logs.

Power BI templates and custom reports show acknowledgements and quiz results. Flexible, fully integrated analytics.

Integration & platform

Separate web platform, integrates with Office apps but requires training for staff.

Native to Office 365: runs entirely within SharePoint/Teams. No extra integration needed. DocRead “preserves your documents” and metadata within SharePoint.

Tired of reminding staff to read your company policies?

DocRead makes compliance simple

Key Takeaways:

  • Lower Cost: DocRead/DocSurvey is under $10K for most orgs vs. six figures for PowerDMS.

  • No New System: Runs inside SharePoint/Teams—no new platform, training, or user logins required.

  • Flexible & Extensible: Combine with Power Automate, Power BI, and Teams for workflows, reporting, and e-learning.

  • Same Core Features: Delivers policy distribution, acknowledgements, quizzes, and reporting—covering the bulk of what PowerDMS provides.

Are your policies read on time and by the right people?

DocRead makes compliance simple

By using SharePoint plus DocRead/DocSurvey, an organization leverages tools it already owns instead of buying a separate platform. For example, DocRead “seamlessly integrates” with existing SharePoint libraries and tracks who reads each policy, while PowerDMS offers similar signature-tracking and living-policy features in its ecosystem. 
In short, if you have Office 365, you can often mimic PowerDMS features (distributed policies, quizzes, reminders, reporting) with DocRead/DocSurvey and other Microsoft services – avoiding the cost of a new, standalone system.

Get your free Standard Operating Procedures guide

Creating Standard Operating Procedures for your organisation doesn't have to be complicated. This guide will introduce you to the whole lifecycle from creation to training and distribution.

You may also like:

The post DocRead vs PowerDMS: Policy & Training Tools Comparison appeared first on Collaboris.

]]>
How does DocRead deal with Reading Tasks when versioning is enabled on a document library? https://www.collaboris.com/how-does-docread-deal-with-reading-tasks-when-versioning-is-enabled-on-a-document-library/ Mon, 15 Dec 2014 06:55:37 +0000 http://collaboriscom.wpengine.com/?p=502 How does DocRead deal with Reading Tasks when versioning is enabled on a document library?The way that DocRead deals with libraries with versioning enabled is: DocRead will not touch any documents in draft stage. Documents will only be processed by DocRead once they are published and approved. When DocRead generates reading tasks for Documents the […]

The post How does DocRead deal with Reading Tasks when versioning is enabled on a document library? appeared first on Collaboris.

]]>

How does DocRead deal with Reading Tasks when versioning is enabled on a document library?

The way that DocRead deals with libraries with versioning enabled is:

  1. DocRead will not touch any documents in draft stage. Documents will only be processed by DocRead once they are published and approved. When DocRead generates reading tasks for Documents the task will always point to the latest version of a document.
  2. When the task gets completed DocRead will register the version of the document at the point that the task was marked as completed. DocRead will also register the document version on the reading receipt that is automatically generated when the reading task gets completed.
  3. When a new version of a document is published DocRead will not automatically re-issue reading tasks to users that have already acknowledged that they have read the document. If you want to force those users to read the document again then you need to select “Reset tasks” on the document properties. This will clear all tasks (even the ones that have already been completed) and re-issue new tasks to everyone ( even to the users that have already read the document).

The post How does DocRead deal with Reading Tasks when versioning is enabled on a document library? appeared first on Collaboris.

]]>
How to free up DocRead user licenses in DocRead version 3 https://www.collaboris.com/how-to-free-up-docread-user-licenses-in-docread-version-3/ Mon, 07 Dec 2015 16:26:31 +0000 http://collaboriscom.wpengine.com/?p=1561 How to free up DocRead user licenses in DocReadNote: The information in this post relates to DocRead for on-premises SharePoint only. If you need to free up some DocRead licences, because you have users that no longer work in your organization, then follow the steps outlined here. Before we explain how to free up licenses, it's important to […]

The post How to free up DocRead user licenses in DocRead version 3 appeared first on Collaboris.

]]>

How to free up DocRead user licenses in DocRead

Note: The information in this post relates to DocRead for on-premises SharePoint only. 

If you need to free up some DocRead licences, because you have users that no longer work in your organization, then follow the steps outlined here.

Before we explain how to free up licenses, it's important to understand how DocRead processes new tasks :

How DocRead Task Processing Works

When you configure a document to be sent to a "Required Audience" with DocRead this will be done in a batch, so the following process will occur ...

  • DocRead will count the number of users in the Group(s) that need be given Reading Tasks for that document.
  • DocRead will also count the number NEW users that currently have no Assigned, Completed or Overdue Tasks for ANY document.
  • Finally, DocRead will test to see if the number of new user licenses will exceed the permissable license allocation. If it does then NONE of the tasks will be created for that group.

As an example, imagine this scenario:

CURRENT NUMBER OF USER LICENSES : 495
TOTAL LICENSE COUNT ALLOWED : 500
NUMBER OF LICENESES REMAINING : 5

- A DocRead Publishers assigns the "Health and Safety Policy" to "Finance Group".
- The Finance Group contains 10 users; 4 of which already take up 1 license each and 6 are NEW and will need a new license.

When DocRead attempts to process the "Health and Safety Policy" it calculates that there are 5 (500 - 495) available licenses remaining, but it needs 6 (10 - 4) to proceed. This results in a license shortfall of 1 license, which causes none of the Reading Tasks for that document to be created.

As a final point, if you remove all of a users Tasks, but that user is still in a group assigned to a document, then DocRead will create a new Reading Task causing the user to take up 1 more license again.

Step 1 : Temporarily disable the timer jobs in Central Administration

Go to : Monitoring > Review Job Definitions

Find the 5 jobs starting with DocRead and click on each one. When you see the disable button, click it.

Repeat this step for all 5 jobs to ensure the DocRead timer jobs are disabled and will not run.

Step 2 : Review and amend User details

In this step, you will need to ensure that the user has been removed from any SharePoint Group / Audience or Active Directory group that has been used to assign DocRead Tasks. Note: Failure to do this will mean that DocRead will recreate tasks for the user once AD synchronisation occurs.

To find out what groups the user is a member of, visit the User Management section within the Collaboris Settings menu in SharePoint Central Administration. This will initially show a list of all of the users who have currently been assigned a DocRead licence.

Select the user you are interested in and then User Audiences

This will display all the audiences and groups that the specified user is a member of. You will need to visit each group and remove the user from that group.

Note: If the Audience Type states "User" then this means the user has been selected individually for one or more DocRead tasks. The user needs to be removed from all of the individual DocRead tasks before their DocRead licence can be reused. A DocRead administrator should be able to use the DocRead reports for the user to find out what has been assigned to them and remove them from the relevant audiences.

Check this screen again to make sure that the user has been successfully removed from all Audience Types before continuing.

Step 3 : Delete user account from DocRead

Revisit the user details in the User Management screen and select 'Delete Account'.

This will delete the user account and all related tasks from DocRead (reading receipts will not be deleted). This will release the user license associated with the user and enable someone else to take the licence.

Step 4 : Re-enable the timer jobs (IMPORTANT)

You need to re-enable the jobs that were disable in step 1 - failure to do this will result in no tasks being processed.

At this stage you will need to wait until the audiences synchronisation job as run once, followed by the Readership Processing job. These two jobs will cause the user to be removed from DocRead and then allows you to re-allocate the license to another user.

You can check the number of available licenses by looking at the licensing screen in Central admin as follows. The 'Remaining Users' count should have increased by this stage.

Please note : Even though all the tasks have been removed – receipts are left in place so that you have still have an auditable history.

The post How to free up DocRead user licenses in DocRead version 3 appeared first on Collaboris.

]]>
Why can’t the “Domain Users” AD group be used in a DocRead audience https://www.collaboris.com/why-cant-the-domain-users-ad-group-be-used-in-a-docread-audience/ Fri, 10 Apr 2015 10:37:34 +0000 http://collaboriscom.wpengine.com/?p=103 Why can’t the “Domain Users” AD group be used in a DocRead audienceNote: The information in this post relates to DocRead for on-premises SharePoint only. DocRead uses the SharePoint API to identify the members of SharePoint and Active Directory (AD) groups (more specifically we use the SPUtility.GetPrincipalsInGroup method), unfortunately this API does not seem to support the “Domain Users” AD group […]

The post Why can’t the “Domain Users” AD group be used in a DocRead audience appeared first on Collaboris.

]]>

Why can’t the “Domain Users” AD group be used in a DocRead audience

Note: The information in this post relates to DocRead for on-premises SharePoint only. 

DocRead uses the SharePoint API to identify the members of SharePoint and Active Directory (AD) groups (more specifically we use the SPUtility.GetPrincipalsInGroup method), unfortunately this API does not seem to support the “Domain Users” AD group (there are several people reporting this problem: https://social.msdn.microsoft.com/Forums/office/en-US/594b8f59-526e-4624-97b7-6dd5acaa98e4/getting-users-from-ad-group?forum=sharepointdevelopment). Because of this the special AD “Domain Users” group cannot be used inside of a DocRead audience.

As an alternative, if you have DocRead Professional or Enterprise and you use SharePoint Standard edition or above you can use SharePoint audiences to target all users in your organisation. For more information on how to create and use SharePoint audiences please check this post: how-to-create-a-sharepoint-audience.

You may find some of our other posts interesting:

The post Why can’t the “Domain Users” AD group be used in a DocRead audience appeared first on Collaboris.

]]>
Types of audiences that can be used by DocRead https://www.collaboris.com/types-of-audiences-that-can-be-used-by-docread/ Fri, 16 Mar 2018 11:19:51 +0000 https://www.collaboris.com/?p=1202442 Note: The information in this post relates to DocRead for on-premises SharePoint only. DocRead uses the SharePoint API to get the list of users that have been assigned to a DocRead audience. Because of limitations with this API DocRead audiences can only contain individual windows users, SharePoint Groups, ASP.Net roles, standard Windows security groups and SharePoint audiences. […]

The post Types of audiences that can be used by DocRead appeared first on Collaboris.

]]>
Note: The information in this post relates to DocRead for on-premises SharePoint only. 

DocRead uses the SharePoint API to get the list of users that have been assigned to a DocRead audience. Because of limitations with this API DocRead audiences can only contain individual windows users, SharePoint Groups, ASP.Net roles, standard Windows security groups and SharePoint audiences. Active Directory Universal security groups and distribution lists are not supported.

Also please be aware that, if you configure DocRead to support SharePoint Audiences on a specific site, you will only be able to assign SharePoint Audiences and SharePoint groups to DocRead Audiences on that site, windows users and Active Directory groups would need to be nested inside SharePoint groups. This is due to limitations with the SharePoint audiences control used by DocRead (People Picker).

You may also be interested in:

The post Types of audiences that can be used by DocRead appeared first on Collaboris.

]]>
Amend the Owstimer.exe.config to support DocRead under FBA https://www.collaboris.com/amend-the-owstimer-exe-config-to-support-docread-under-fba/ Mon, 15 Dec 2014 06:58:06 +0000 http://collaboriscom.wpengine.com/?p=458 Amend the Owstimer.exe.config to support DocRead under FBAIf you choose to use a different authentication mechanism such as FBA that requires a ‘Role’ and ‘Membership’ provider specified in your web.config then you will also need to copy these entries to your owstimer.exe.config file. Here’s an example of a working owstimer.exe.config file that is set-up to use Extradium. […]

The post Amend the Owstimer.exe.config to support DocRead under FBA appeared first on Collaboris.

]]>

Amend the Owstimer.exe.config to support DocRead under FBA

If you choose to use a different authentication mechanism such as FBA that requires a ‘Role’ and ‘Membership’ provider specified in your web.config then you will also need to copy these entries to your owstimer.exe.config file.

Here’s an example of a working owstimer.exe.config file that is set-up to use Extradium. (Extradium is an identity management solution that allows you to make your SharePoint accessible externally and works really well with DocRead). If you don’t do this, then the DocRead timer jobs will not be able to access the FBA database causing the SharePoint API to return empty groups. This will result in tasks being removed, so it’s vitally important you copy the entries from your web.config.

Example :

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
 <startup useLegacyV2RuntimeActivationPolicy="true">
 <supportedRuntime version="v4.0.30319" />
 </startup>
 <runtime>
 <NetFx40_LegacySecurityPolicy enabled="true" />
 <appDomainManagerAssembly value="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
 <appDomainManagerType value="Microsoft.SharePoint.SPAppDomainManager" />
 </runtime>
<system.web>
 <membership defaultProvider="i">
 <providers>
 <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
 <add name="ext" type="RioLinx.Extradium.Providers.ExtradiumMembershipProvider, RioLinx.Extradium.Providers, Version=3.0.0.0, Culture=neutral, PublicKeyToken=ee2f606d34db8cb1" />
 </providers>
 </membership>
 <roleManager defaultProvider="c" enabled="true" cacheRolesInCookie="false">
 <providers>
 <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider, Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
 <add name="extg" type="RioLinx.Extradium.Providers.ExtradiumRoleProvider, RioLinx.Extradium.Providers, Version=3.0.0.0, Culture=neutral, PublicKeyToken=ee2f606d34db8cb1" />
 </providers>
 </roleManager>
</system.web>
</configuration>

The post Amend the Owstimer.exe.config to support DocRead under FBA appeared first on Collaboris.

]]>