Skip to content

Add director onboarding and offboarding checklists - #2

Open
shedquartersbot wants to merge 3 commits into
RevolutionVA:mainfrom
shedquartersbot:docs/director-checklists
Open

Add director onboarding and offboarding checklists#2
shedquartersbot wants to merge 3 commits into
RevolutionVA:mainfrom
shedquartersbot:docs/director-checklists

Conversation

@shedquartersbot

Copy link
Copy Markdown
Contributor

Summary

  • adds a public director onboarding checklist from candidate preparation through annual renewal
  • adds an offboarding checklist covering governance records, access revocation, responsibility transfer, and verification
  • places both documents under board/processes/

Notes

These checklists contain no credentials or private records. Completed internal copies and signed materials remain in restricted Google Drive storage. This PR is intentionally separate from #1 and can be reviewed independently.

Review checklist

  • Confirm the public/private records split
  • Confirm access-control and financial-system references
  • Confirm term-anchor and appointment language
  • Confirm alignment with the governance changes now being developed

@1kevgriff
1kevgriff requested review from lynnaloo and a lite review from Copilot August 15, 2026 16:37
@1kevgriff 1kevgriff mentioned this pull request Aug 8, 2026
6 tasks

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds two public-facing board process documents under board/processes/ to standardize director onboarding and role offboarding while keeping completed/signed internal records in restricted Google Drive storage.

Changes:

  • Adds a director onboarding checklist covering candidate preparation, appointment, access provisioning, orientation, verification, and annual renewal.
  • Adds a director/officer/volunteer offboarding checklist covering governance records, access revocation, responsibility transfer, and post-departure verification.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File Description
board/processes/director-onboarding-checklist.md New onboarding checklist from candidate prep through annual renewal and access auditing.
board/processes/offboarding-checklist.md New offboarding checklist including governance actions, access removal, transitions, and verification.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.


### Financial systems

- [ ] Remove or modify TowneBank access and signing authority when applicable.
- [ ] Place the appointment on a properly noticed board-meeting agenda or written-consent action.
- [ ] Consider and vote on the candidate individually rather than as part of a slate.
- [ ] Confirm that appointing the director receives a two-thirds vote of directors currently serving.
- [ ] For one of the first three rotating seats, confirm that both Kevin Griffin and Linda Nichols affirmatively approve the candidate, regardless of how many initial directors are already serving.
- [ ] Preserve relevant email, chat, documents, logs, financial records, and account history.
- [ ] Do not delete or alter records merely because the person is departing.
- [ ] Restrict sensitive departure records to people with a legitimate need for access.
- [ ] Coordinate with Pierce Legal or another qualified adviser when the departure is disputed, disciplinary, or legally sensitive.
### Financial oversight

- [ ] Cash-basis accounting and calendar fiscal year.
- [ ] TowneBank and QuickBooks Online workflows.
- [ ] Update Virginia corporate or charitable-registration records.
- [ ] Update registered-agent or principal-office records.
- [ ] Update IRS responsible-party or tax records when legally required.
- [ ] Update TowneBank authorized signers.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants