MentorshipAgreements Early access
What they agreed to, as they agreed to it. A code of conduct, a commitment of hours, a safeguarding policy: versioned when you edit, and kept exactly as each person accepted it.
Write it once, per role. And let the version do the bookkeeping.
Attach agreements to the program (inline text or a document you already host) with a role, a required flag, and a version that steps forward on every edit.
- Write it inline, or point at a document you host
- Different agreements for mentors and for mentees
- Required, or offered (your call, per agreement)
- Edit the text and the version steps itself forward
- A new version asks everyone to accept again
Keep the acceptance honest. A snapshot, not a link.
Each acceptance captures the text as it stood, with the time, the address, the device, and whether it was accepted in the Hub or recorded by a coordinator.
- Accepted in the Hub, or recorded by a coordinator: marked which
- The exact text and version accepted is captured, not linked
- When, from where, and on what: kept with the acceptance
- Acceptances cannot be deleted, by anyone
- Outstanding requirements greet the participant, not the coordinator
No, and we say so plainly: it is click-to-accept with an audit trail (the exact text, the version, the time, the address and the device). Audit-defensible for a code of conduct; not a certified signing product for contracts.
The version steps forward and everyone is asked to accept the new one. The people who accepted version two keep their record of version two; publishing version three never rewrites it.
A coordinator can record the acceptance for them, and the record says a coordinator did: accepted-themselves and recorded-for-them are never blurred together.
The Hub shows a banner and a badge for any outstanding required agreement every time the participant visits, but it does not padlock the program: a safeguarding decision should be a person’s, made visible, not a lockout nobody notices.