Category Archives for "DocRead"

How does DocRead differ from Information Management Policies?

How does DocRead differ from Information Management Policies?DocRead for SharePoint is the only policy management software that integrates straight into SharePoint and allows compliance professionals to distribute and track their policies and procedures. A question recently came up asking us to explain how DocRead was different from what you can achieve with standard ‘Information Management Policies’ in SharePoint. […]

Continue reading

Regulatory Compliance – Workflow

Regulatory Compliance – WorkflowSharePoint Workflow allows a set of activities to process in either sequential or parallel, more often than not, one or more of those activities involves human intervention such as ‘approve a document’, or ‘complete a task’ and so on. This in itself goes a long way to ensure regulatory compliance because the right information is […]

Continue reading

How does DocRead differ from Workflow?

How does DocRead differ from Workflow?DocRead for SharePoint is the only policy management software that integrates straight into SharePoint and allows compliance professionals to distribute and track their policies and procedures. We often get asked – why do we need DocRead when we can do it in a workflow? Here’s how DocRead differs from a workflow engine […]

Continue reading

Why is DocRead different from competing software?

Why is DocRead different from competing software?We are very often asked how DocRead differs from its competitors. Here’s a recent response we gave (slightly tweaked to protect the identity of the requestor!): Great question! Although we have a few competitors in the same area of ‘compliance’ – as far as we know – we don’t have […]

Continue reading

SharePoint Lessons Learned – Don’t forget to use proven design patterns and practices

SharePoint Lessons Learned – Don’t forget to use proven design patterns and practicesSharePoint should be seen as another layer in the technology stack that your code will interact with. But just because you are using this layer you should not forget to follow good and proven design practices. The following points describe some of the […]

Continue reading

Requirements, Requirements, Requirements…

Requirements, Requirements, Requirements…Those are the three most valuable artefacts of a project. Requirements should drive most (if not all) activities in a project. A project should be architectural centric and requirements driven… We have all heard these clichés before but how exactly does one manage requirements in an iterative process? How do we make sure […]

Continue reading
1 6 7 8