Moodle can grade an assignment. It can't collect a signature.
For academic integrity statements, lab safety waivers, or enrollment agreements tied to a course, add the signing step Moodle skips.
Where this fits
- Moodle has no native e-signature — a "tick this box to agree" checkbox activity isn't a signed, attributable record
- Academic integrity statements, lab or field-trip safety waivers, and course enrollment agreements often need an actual signature, not a form submission logged in the gradebook
- Instructors managing this outside Moodle usually resort to printed forms or an emailed PDF with no consistent trail back to the course
- A cohort can be dozens or hundreds of students; collecting individual signed statements without a batch workflow is its own project
Who uses this
- Teams running on Moodle
- Or anything similar — the signing step works the same regardless of which one you use
Why Docracy
Docracy sits outside Moodle as the signing step you link to from the course page, not an installed Moodle plugin. Save the integrity statement, safety waiver, or enrollment agreement as a reusable template once per course, then post the signing link in the course itself or send it to the whole enrolled cohort at once with parallel signing. Each student signs with no account required, and a timestamped audit trail shows exactly who signed which version and when — useful if a program or accreditation review ever asks for evidence.
One template per course
Save the integrity statement or waiver once, reuse it every term.
Whole-cohort parallel signing
Send to an entire class roster at once instead of chasing individuals.
No student account needed
Students open a link and sign — nothing to register for in Moodle or Docracy.
Exportable audit trail
A dated signature record per student, separate from the Moodle gradebook.
Docracy has no Moodle plugin, block, or API integration — the signing link lives outside the course shell, shared manually or via Zapier (for example, when a Moodle activity is marked complete). There are also no education-specific features: no FERPA-specific claims, no gradebook integration, and no school or campus SSO. This is a general-purpose signing tool, not an LMS module.
Templates for this
Code of Conduct Acknowledgment
A signed record that an employee received, read, and agreed to follow the company's code of conduct.
Liability Waiver
A participant's signed release of claims against an organization for risks in an activity or event.
Acceptable Use Policy Acknowledgment
A short cover document where a user confirms they've read and will comply with your Acceptable Use Policy.
Frequently asked questions
Do the people I send documents to need a Docracy account?
No — only the sender needs an account, so document history, saved templates, and team access have somewhere to live. Whoever's signing opens a link and signs, no signup required.
Which documents can I send?
Ready-made templates for this include Code of Conduct Acknowledgment, Liability Waiver, Acceptable Use Policy Acknowledgment. You can also upload your own PDF.
How much does it cost?
Free for documents with up to 2 signers. Beyond that it's a flat $10/month — never priced per seat — which also unlocks reusable templates, team accounts, and the integrations mentioned above.
How fast can someone actually sign?
Under a minute in most cases: they open the link, review the document, and sign — no account to create, no app to install. WhatsApp delivery adds a phone-bound PIN step for extra assurance when that matters.
What doesn't Docracy do here?
Docracy has no Moodle plugin, block, or API integration — the signing link lives outside the course shell, shared manually or via Zapier (for example, when a Moodle activity is marked complete). There are also no education-specific features: no FERPA-specific claims, no gradebook integration, and no school or campus SSO. This is a general-purpose signing tool, not an LMS module.
See also
Ready to send your first document?
Try free — send a sample statement