Scope
Define who the contract covers and which activities are subject to the rules. Specify whether it applies to events, online forums, meetings, or all interactions to avoid ambiguity and surprises.
A clear Social Contract reduces misunderstandings, supports consistent moderation, and documents what community members agree to. It helps leaders apply rules fairly, encourages participation, and can improve trust among members when expectations are explicit and accessible.
Communities of all sizes use this document to set behavioral norms and operating expectations before disputes arise.
Use it as an onboarding and reference document to keep community standards visible and consistent over time.
A community leader or authorized administrator signs on behalf of the organizing body and is responsible for enforcing the contract, communicating amendments, and maintaining the official record of the agreement.
Individual members sign to acknowledge understanding and acceptance of the community norms and any listed consequences; signatures establish mutual recognition but do not automatically create binding commercial obligations.
| Field | Configuration |
|---|---|
| Signature type | Click-to-sign or drawn signature permitted |
| Authentication | Email link default; SMS or multi-factor where stronger identity is needed |
| Reminder cadence | Automatic reminders at 3 and 7 days after first invite |
| Audit retention | Attach a signed audit trail and export to PDF/A |
Confirm the signing platform supports secure, timestamped audit trails and flexible signer authentication before sending the contract.
Define who the contract covers and which activities are subject to the rules. Specify whether it applies to events, online forums, meetings, or all interactions to avoid ambiguity and surprises.
Include a short list of core values that guide decisions (for example, respect, safety, inclusivity). Concrete examples help moderators interpret and apply standards consistently across cases.
List permitted and prohibited behaviors with clear examples and thresholds for escalation. Avoid vague language and provide samples so members know what actions cross a boundary.
Describe steps for addressing breaches, from informal warnings to temporary suspension. Include timelines and who conducts investigations to ensure transparency and procedural fairness.
Set a clear process for proposing, reviewing, and adopting amendments, including notice periods and voting rules where applicable so the contract can evolve responsibly.
State how signed contracts and incident records will be stored, who can access them, and retention durations to meet privacy and compliance expectations.
Allow 7–21 days for community review and feedback.
Recommended 14–30 days to collect member signatures.
Provide 14 days' notice before adopting substantive changes.
Publish final signed contract within 7 days of closing signatures.
Review storage annually for access and compliance.
Finalize language and attachments before community review.
Collect feedback and incorporate agreed edits.
Distribute and gather electronic signatures with audit logs.
Store signed copies and publish a read-only community version.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by region | Trial available | Trial available | Trial available |
| Bulk Send | Yes | Yes | Yes | Yes | Yes |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
The association drafted a short code emphasizing respect and quiet hours
A volunteer-run forum published a clear moderation policy linked in registration