Staff hub¶
Everything a Guild administrator, bookkeeper, or contractor needs to do their work.
Operational links to vendor accounts (Cloudways, Klaviyo, Stripe, etc.) live in a separate internal credential vault per the break-glass procedure. This hub points to the procedural and policy documents in this repo.
My role¶
Administrator role
Full role description, including the systems-administrator scope and guardrails.
Bookkeeper role
Bookkeeper responsibilities, monthly close, vendor coordination.
Committee chairs
Chair responsibilities (for staff supporting committees).
Day-to-day finance¶
Reimbursement policy
Accountable-plan rules, approver matrix, submission steps.
Expense reimbursement form
Fillable form template — submit a reimbursement request.
1099 process
Year-end vendor 1099 issuance SOP.
Sponsorship tiers
Reference for sponsor outreach and renewal conversations.
Sponsorship agreement template
Sponsor contract template; counsel-reviewed before send.
Year-1 sample budget
Reference budget for planning conversations with the Treasurer.
Membership and member experience¶
Membership overview
The published tiers, dues, and what's included.
Member agreement
The standard member agreement.
Subscriber conversion FAQ
What to tell current ganjierguild.com subscribers about the transition.
Complimentary membership policy
Eligibility and approval workflow for comped memberships.
Scholarship and hardship waiver
Member-driven hardship pathway; application process.
Communications¶
Welcome email template
First touch for new members — fillable.
Press release template
House style for outbound press.
Sponsor outreach email
Cold outreach template for prospective sponsors.
Volunteer certification letter
Service-hours letter template for volunteers requesting verification.
Brand and media boilerplate
Approved Guild language for press contacts and partners.
Tech and systems¶
Systems inventory
Template for the tracked-systems list (account owner, billing, recovery contact).
Break-glass procedure
What to do if the sysadmin is unavailable and credentials are needed.
Migration plan
Pre-formation → post-formation systems migration sequence.