DEI Council Workspace
A DEI Council workspace template for chartering initiatives, planning events, tracking metrics, and publishing reports. It gives the council a clear operating rhythm so roles, decisions, and follow-through stay visible.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Technology · Healthcare · Financial Services · Education · Nonprofit
Overview
This DEI Council Workspace template gives a council one place to run chartered work, coordinate initiatives, plan events, track metrics, and publish reporting. It is organized around the actual flow of council work: kickoff, day-to-day coordination, decisions, retrospectives, and metrics reporting. That makes it easier to separate discussion from action and to keep the council’s outputs visible to the right people.
Use this template when a DEI council has recurring responsibilities, multiple contributors, and a need to report progress back to leadership or stakeholders. The included milestones help the council move from charter approval to initiative planning, event delivery, and first reporting. The task lists are stage-based, so work can move from intake to delivery without getting buried in chat. The hill chart gives the council a simple way to see which initiatives are uphill, which are nearing completion, and where attention is needed.
Do not use this template as a generic team workspace or as a place to store unrelated HR content. It works best when the council has a defined scope and a clear DRI for each workstream. If your group is still informal, start with the charter and roles canvas first. If you do not plan to track metrics or publish reports, a lighter workspace may be enough. The value of this template is in turning council activity into a repeatable operating system, not just a shared folder and chat space.
What's inside this template
Members
This section defines who participates in the council by role, which keeps ownership clear as the workspace evolves.
Channels
These channels separate kickoff, execution, decisions, retros, and reporting so each type of conversation has a clear home.
-
#council-kickoff
Intake for new chartered initiatives, scope alignment, and launch planning.
-
#day-to-day
Working channel for active tasks, blockers, coordination, and follow-ups.
-
#decisions
Channel for approvals, policy recommendations, and formal council decisions.
-
#retros
Channel for post-event, post-campaign, and quarterly reflection notes.
-
#metrics-reporting
Channel for KPI review, dashboard updates, and recurring reporting drafts.
Check ins
The check-ins create a predictable operating rhythm for weekly coordination, biweekly review, and monthly reporting.
- Weekly Monday Council Check-in
- Biweekly Initiative Review
- Monthly Metrics and Reporting Check-in
Milestones
Milestones mark the council’s key outputs so progress is visible from charter approval through reporting.
-
Council charter approved
Governance, scope, and success criteria are approved.
-
Initial initiative plan finalized
Workstreams, owners, and timeline are confirmed.
-
First engagement event delivered
Council-sponsored event or listening session is completed.
-
First metrics report published
Council report is reviewed and shared with stakeholders.
Task lists
The task lists organize work by stage, making it easier to assign DRIs and move initiatives from intake to delivery.
-
Initiative Intake and Chartering
Capture new ideas, define scope, and confirm sponsorship before work begins.
-
Project Planning and Delivery
Plan milestones, owners, and execution steps for approved initiatives.
-
Events and Engagement Coordination
Plan council-sponsored events, listening sessions, and engagement activities.
-
Metrics, Reporting, and Insights
Track council metrics, summarize outcomes, and prepare recurring reporting.
Hill charts
The hill chart shows which initiatives are still climbing and which are close to done, helping the council focus attention.
-
Council Initiative Portfolio
Track the overall progress of chartered DEI initiatives across planning, execution, and reporting.
Default apps
Default apps connect the workspace to the tools the council uses most often for documents, metrics, and scheduling.
Integrations
Integrations keep Slack, Drive, Sheets, and Calendar tied to the council’s actual workflow instead of scattered across tools.
- Slack
- Google Drive
- Google Sheets
- Calendar
Pinned resources
Pinned resources give the council immediate access to the charter, roles canvas, dashboard, reporting template, and event checklist.
- DEI Council Charter
- RACI and Roles & Responsibilities Canvas
- Metrics Dashboard
- Reporting Template
- Event Planning Checklist
How to use this template
- 1. Add the council’s role-based members, confirm the DRI for each workstream, and publish the charter in the pinned resources.
- 2. Use #council-kickoff to align on scope, milestones, and the first initiative plan before any work starts.
- 3. Move active work into the stage-based task lists and assign each item to a single DRI with clear due dates and dependencies.
- 4. Run the weekly Monday council check-in to review blockers, decisions, and next actions, then capture outcomes in #decisions.
- 5. Use the biweekly initiative review and the hill chart to assess progress, reprioritize work, and close out completed items.
- 6. Update the monthly metrics and reporting check-in with dashboard inputs, publish the report, and record retrospective learnings in #retros.
Best practices
- Keep the Members section role-based so the workspace can be reused when council membership changes.
- Assign one DRI to every initiative, event, and reporting task so ownership is never ambiguous.
- Use #decisions only for approved outcomes, not open discussion, so the channel stays easy to scan.
- Tie each check-in to a specific output such as a decision, a milestone update, or a published report.
- Store source documents in Google Drive and link them from the pinned resources instead of attaching duplicates in chat.
- Review the hill chart during the biweekly initiative review so the council can see which work is still uphill.
- Keep metrics definitions stable from month to month so reporting trends are comparable over time.
- Close each retrospective with one or two concrete process changes, then assign a DRI to follow through.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this DEI Council Workspace template for?
This template is for a DEI council that needs one shared workspace to manage chartered initiatives, event planning, metrics, and reporting. It is built around council work rather than general team chat, so the channels, check-ins, milestones, and task lists all map to that workflow. Use it when the council has recurring responsibilities and needs a repeatable operating rhythm. It helps keep decisions, action items, and reporting artifacts in one place.
Who should run this workspace day to day?
The workspace is usually run by the Council Chair, Program Manager, or another DRI assigned to coordinate the council. The template is designed so roles can be mapped in the Members section using placeholders like Project Manager, People Ops Lead, or Engineering Lead rather than individual names. That makes ownership easier to transfer when council membership changes. The DRI for each task list should be explicit so follow-up does not drift.
How often should the check-ins happen?
The template includes three cadences: a weekly Monday council check-in, a biweekly initiative review, and a monthly metrics and reporting check-in. That cadence works well when the council is balancing active projects with reporting obligations. If the council is smaller or less active, you can reduce the biweekly review without losing the weekly operating rhythm. The key is to keep each check-in tied to a decision or output.
What kind of work belongs in the task lists?
The task lists are stage-based: intake and chartering, planning and delivery, events and engagement, and metrics and insights. Put work in the list that matches its current stage, then assign a DRI and any consulted roles. This keeps the council from mixing early ideas with active execution or reporting. If a task cannot be placed in a stage, it may need a clearer owner or a better-defined milestone.
How does this template handle roles and accountability?
It is built to support a RACI-style structure and a Roles & Responsibilities Canvas, which helps the council distinguish who is Responsible, Accountable, Consulted, and Informed. That is especially useful when multiple functions contribute to DEI work and decisions need clear ownership. The template also fits Conway’s Law by mirroring the council’s actual workflow in its channel and task structure. That reduces confusion about where decisions happen and who needs to be looped in.
Can this workspace be customized for different DEI council scopes?
Yes. You can tailor the milestones, task lists, and pinned resources to match your council’s charter, whether it focuses on employee engagement, learning programs, policy review, or representation metrics. You can also add or remove channels depending on how much decision-making and reporting the council does. Keep the structure stage-based so the workspace still supports intake, execution, and reporting. The template is meant to be a starting point, not a fixed process.
What integrations are most useful with this template?
The template includes Slack, Google Drive, Google Sheets, and Calendar because those tools support the council’s core workflow. Slack handles day-to-day coordination and decisions, Drive stores the charter and planning docs, Sheets supports metrics tracking, and Calendar keeps check-ins and events on schedule. If your organization uses other tools, you can swap them in as long as the integration touchpoints still support the same workflow. The goal is to avoid scattered reporting artifacts.
What are the most common mistakes when adopting this template?
A common mistake is leaving the workspace too generic, such as using one catch-all channel for every topic. Another is listing members by name instead of role, which makes the template harder to reuse when council membership changes. Teams also sometimes skip the monthly metrics check-in and then lose the reporting rhythm. The best rollout is to assign DRIs, publish the charter, and confirm what belongs in each channel before the first meeting.
How is this better than running the council through ad hoc docs and chat threads?
Ad hoc docs and chat threads often blur decisions, action items, and reporting into one stream, which makes follow-through harder. This template separates kickoff, day-to-day coordination, decisions, retros, and metrics reporting into distinct channels and task lists. That structure makes it easier to see what is in flight, what is approved, and what still needs input. It also gives the council a repeatable way to publish reports and review progress over time.
Related templates
Ready to use this template?
Get started with MangoApps and use DEI Council Workspace with your team — pricing built for small business.
