Scope
Define coaching services, deliverables, session frequency, participant eligibility, and any limits on activities. Precise scope prevents scope creep and clarifies what outcomes coaches are expected to support.
A Community Coaching Agreement clarifies expectations, reduces disputes, and protects participants and organizations by documenting roles, schedules, confidentiality, and data practices. It supports compliance with relevant laws and creates a clear basis for payment, supervision, and termination.
Organizations and individuals commonly use the Community Coaching Agreement to set expectations, document services, and manage liability.
Select clauses to match program scale, funding rules, and any required background checks or reporting obligations.
Define coaching services, deliverables, session frequency, participant eligibility, and any limits on activities. Precise scope prevents scope creep and clarifies what outcomes coaches are expected to support.
Specify stipend, reimbursement policies, expense caps, payment schedule, invoicing requirements, and conditions for withholding or termination of payments. Include tax treatment and whether the coach is an independent contractor or employee.
Require handling of personal and program data, specify permitted disclosures, require compliance with privacy laws, and list secure recordkeeping and destruction procedures to protect participant information.
Document session frequency, duration, location or virtual platform, rescheduling policy, notice periods, and maximum allowable cancellations to maintain program continuity and manage participant expectations.
Address insurance requirements, indemnification obligations, scope of liability, and whether the coach is covered under organization policies or must carry personal insurance. Include limits and proof of coverage requirements.
Specify grounds for termination, notice periods, cure opportunities, post-termination obligations, return of materials, and dispute resolution methods such as mediation or binding arbitration and effect on outstanding payments or deliverables.
| Field Name, Purpose, and Configuration | Configuration Setting and Recommended Value |
|---|---|
| Signer Authentication | Email link, SMS code, or KBA per risk level. |
| Signature Fields | Signature, initials, and date fields placed per role. |
| Reminders | Automatic reminder after X days; configurable cadence and limits. |
| Storage Location | Choose secure cloud storage with access controls and retention policy. |
Use an eSignature platform supporting PDF, Word, audit trails, and common integrations like Salesforce and Google Workspace.
Specify MM/DD/YYYY and contract length
Complete checks before first session
Provide proof at least 14 days before start
Net 30 or specific dates per calendar
Typically 14–30 days unless otherwise stated