Setting Up: Config, DAO Master, Roster

Three tabs get a DAO's Workbook ready before any work is tracked.

Config — the DAO’s settings and rules

Config holds the settings the rest of the file reads. To set it up:

1. Fill the DAO Config block: dao_code, dao_name, cohort, payment_model (per-task / pool / none), and seed_fund_usdt ($3,000).
2. Leave the scoring rules at their defaults unless your DAO has reason to change them — they set what counts as a Low / Mid / High band and when a phase is "cleared".
3. Fill the Event Catalog — one row per cohort event (kick-off, check-ins, syncs, submissions). Adding an event is a data entry, not a formula change; the Attendance Grid reads this list automatically.

Screenshot: the Config tab (DAO Config + Event Catalog). Source: the DAO Workbook template.

DAO Master — the one-page identity and directory

DAO Master is the page a newcomer or partner reads first. It carries the DAO's identity (pulled from Config), its KDF on-chain details (chain, treasury, vault/splitter/executor contracts, accepted token), a File Library of live links (Master Plan, each lane's Launch Kit, weekly reports, the Cashbook), and — for community-based DAOs — a Nodes / Partners directory. Fill the yellow cells once at onboarding; operator DAOs can leave the Nodes section empty.

Screenshot: the DAO Master tab. Source: the DAO Workbook template.

Roster — who is in the DAO

Roster lists the members. The green columns (person_id, name, email, returning?) come from the Hub — don't edit them. You type the blue columns: each member's Scope, Lane, Role, joined date, and status. The joined date matters: it's what keeps a late-joining member from being scored against events they were never invited to.

Screenshot: the Roster tab. Source: the DAO Workbook template.