Chief of Staff plus Departments Kit: one front door

Why it matters

Once a team grows past a few bots, each one reports on its own schedule and in its own voice, and the owner becomes the integration layer. This kit puts one bot in between: the Chief of Staff takes every request, routes it to a department head, collects the results and approvals, and reports back in a single daily brief. Departments never message the owner directly, and every external action waits for an explicit OK. It is the structure I run myself, published as a template. No usage or performance numbers exist for it, so this page makes no performance claim.

Roles and reporting lines

Role	Reports to	Job (from the template)	Cadence
Owner (human)	-	Talks to the Chief of Staff only; approves external actions	-
Chief of Staff	Owner	Single point of contact. Routes requests, tracks open items, collects approvals, sends the daily brief	Continuous; brief daily at a time you set
Team Doctor	Chief of Staff	Monitors bot health, failed routines, overlaps, broken connectors; proposes fixes	Daily check, weekly report
Head of Growth and Social	Chief of Staff	Owns audience growth on your platforms	Daily
Head of Research and Content	Chief of Staff	Turns sources into insights and content	Daily
Head of Finance	Chief of Staff	Budgets, spend tracking, investment research requests	Weekly, on request
Head of Engineering	Chief of Staff	Owns tools, automations and product builds	Per project
Product Manager	Head of Engineering	Defines what to build and why	Per request
Project Manager	Head of Engineering	Plans and tracks delivery	Weekly
Builder	Head of Engineering	Builds and tests	Per task
Head of Creative and Design	Chief of Staff	Visual identity and user experience	Per request
Designer	Head of Creative and Design	Graphics, charts, carousels, thumbnails	Per request
UX Specialist	Head of Creative and Design	Flows, usability, page reviews	Per request

Source data: handoffs

Owner → Chief of Staff only; departments never message the owner directly
Department heads → results to Chief of Staff → bundled into the brief
Cross-department work: head to head, Chief of Staff copied

Routines

Daily brief at a time you set
Team Doctor health check daily, report on a day you set
Weekly department roll-up
Monthly org review

Approval gates

Where	Approver
Every external action (send, post, publish, reply, DM, delete, share, purchase, form submit), drafted first	Owner
Team Doctor fixes that change bots	Owner
Creating or retiring bots	Owner

Copyable spec

org_chart:
  name: Chief of Staff plus Departments Kit
  number: 5
  platform: Grok Bot (pattern is portable to any agent stack)
  source: https://thenextcorner.com/bots/chief-of-staff-kit/
  credit: Dennis Goedegebuure (@TheNextCorner), own template
roles:
  - {id: owner, title: Owner, kind: human}
  - {id: cos, title: Chief of Staff, reports_to: owner, job: "single point of contact; routes requests, tracks open items, collects approvals, sends the daily brief", cadence: "continuous; brief daily at a time you set"}
  - {id: doctor, title: Team Doctor, reports_to: cos, job: "monitors bot health, failed routines, overlaps, broken connectors; proposes fixes", cadence: "daily check, weekly report"}
  - {id: growth, title: Head of Growth and Social, reports_to: cos, cadence: daily}
  - {id: research, title: Head of Research and Content, reports_to: cos, cadence: daily}
  - {id: finance, title: Head of Finance, reports_to: cos, cadence: "weekly, on request"}
  - {id: eng, title: Head of Engineering, reports_to: cos, cadence: per project}
  - {id: pm, title: Product Manager, reports_to: eng}
  - {id: pj, title: Project Manager, reports_to: eng, cadence: weekly}
  - {id: builder, title: Builder, reports_to: eng}
  - {id: creative, title: Head of Creative and Design, reports_to: cos}
  - {id: designer, title: Designer, reports_to: creative}
  - {id: ux, title: UX Specialist, reports_to: creative}
handoffs:
  - owner talks to cos only; departments never message the owner
  - heads return results to cos, which bundles them into the brief
  - cross-department work goes head to head, cos copied
routines:
  - daily brief at a time you set
  - team doctor health check daily; report every a day you set
  - weekly department roll-up on a day you set
  - monthly org review
approval_gates:
  - {where: any external action (send, post, publish, reply, DM, delete, share, purchase, form submit), approver: owner}
  - {where: team doctor fixes that change bots, approver: owner}
  - {where: creating or retiring bots, approver: owner}

Sources

Dennis Goedegebuure, Chief of Staff plus Departments Kit (own template). Fetched 15 Oct 2026, 22:15 CEST.
Bot team templates index. Fetched 15 Oct 2026, 22:23 CEST.

What is confirmed / what is not

Confirmed:

every role, cadence, handoff, routine and guardrail above copied from the template page (HTTP 200, 15 Oct 2026) and the source template file; nothing added

Not confirmed:

no public usage or performance numbers → no performance claim
placeholders in the template, such as the brief time, are set by whoever installs the kit

Get the template

Get the templates: the Chief of Staff plus Departments Kit itself, and the Team Doctor, both free Markdown downloads.

All org charts · All bot templates

One front door: departments never message the owner directly.