Board templates

Creating a board means picking a template. The template decides what's pre-created — groups, columns, views — and it keeps shaping the board's behaviour afterward, not only at creation.

deckgauge · New board
Development
👥Recruitment
Blank board

The three templates.

The three templates

Development

The default when you don't choose otherwise. Pre-creates a Size status column, the engineering-intelligence dashboard view, and a Roadmap view sized from your issues. No groups or extra columns are seeded — connect Jira, GitHub, Azure DevOps, or GitLab afterward to populate it.

Recruitment

A candidate pipeline. Pre-creates five stage groups — New / Sourced, Interviewing, Offer, Hired, Not moving forward — and five columns: Role (Text), Interview date (Date), Salary expectation (Number), Target start (Date), and Decision (Status, with Pending/Pass/Hold/Fail options). No Size column, dashboard, or roadmap.

Blank board

Rows and the status column, nothing else — no groups, no extra columns, no dashboard, no roadmap. Shape it however you like.

How the kind keeps shaping the board

A board's template choice becomes its permanent kind, and that kind gates behaviour well after creation — it isn't only a one-time seed. The clearest example: the Onboard control, which turns a candidate row into an org-tree employee, only appears in the item detail panel on recruitment boards. A development or blank board never shows it.

If it looks wrong

SymptomCauseFix
No Roadmap tab on a new boardThe template you picked doesn't seed one (only Development does)Create a standalone roadmap instead, or start from Development
Can't find the Onboard controlThe board isn't a Recruitment-kind boardOnboarding only appears on boards created from the Recruitment template
Template's seeded columns are missingColumns are seeded once, at creation, per templateAdd matching columns by hand — templates don't retroactively apply

Related

Last updated