Documents are the core content unit in ClearPolicy. Each document represents a policy, form, or any other content you need people to acknowledge or sign. A document holds a name, a default attestation type, and a complete history of its content through revisions.
What is a document?
A document is the parent record that ties everything together — its name, settings, revisions, and compliance history all live under a single document. When you create a document, you give it a name and choose a default attestation type: acknowledgment or signature. This default applies to new requests sent from the document, though you can override it per request.
Documents can be assigned to groups so that entire teams or departments are automatically included when you send requests.
What is a revision?
A revision is a versioned snapshot of your document’s content. Every document starts with a single revision, and you can create new ones at any time. Revisions exist in one of two states:
- Draft — the revision is being written or edited and is not yet ready to send.
- Published — the revision has been finalized and can be used for attestation requests.
Versioning matters because it lets you update a document without invalidating records already in flight. Each attestation request is permanently linked to the revision that was current when the request was sent — so older completions always reference the exact content the recipient saw.
Creating a document
When you create a new document, ClearPolicy starts a first draft revision for you. You can build out your content using any of three methods:
Rich text editor
PDF upload
Google Docs import
Write and format your content directly in ClearPolicy using the built-in rich text editor. This is the fastest way to get started, especially for shorter policies or forms you want to maintain inside ClearPolicy.
Upload an existing PDF to use as the document content. The uploaded file becomes the revision’s content and is stored for download and attestation.
Import a document from Google Drive. ClearPolicy connects to your Google account and pulls in the document content, making it easy to keep your existing authoring workflow.
Publishing a revision
A revision must be published before you can send attestation requests against it. Publishing finalizes the content and makes it available for distribution.
Finish editing
Complete your content in the editor or confirm your uploaded file is correct.
Publish the revision
Click Publish on the revision. ClearPolicy finalizes the content and makes it available for requests.
Send requests
From the document, send attestation requests to individuals or groups.
You cannot send attestation requests from a draft revision. Publish the revision first.
Downloading a published document
Every published revision has a downloadable PDF. You can download it directly from the document view for sharing, archiving, or review outside ClearPolicy.
Updating content with a new revision
When you need to update a document’s content — to reflect a policy change, correct an error, or add new information — create a new revision rather than editing the published one.
Once a revision is published, create a new revision to make changes. Requests already sent are permanently linked to their original revision, so recipients who completed an earlier version will appear as outdated when you publish an update. This gives you a clear picture of who has seen the latest content.
