Templates

Templates let you save a board layout — its lists and structure — so you don't have to rebuild the same project from scratch every time. Instead of recreating cards and lists for every laptop refresh or maintenance cycle, save the layout once as a template and spin up a new project from it whenever you need it. Boards opened from the Templates page are always in a safe "building mode": no notifications, mentions, or automations fire while you're editing the template itself.

How to use templates

1. Go to the Templates page under Stackr in your workspace.
2. Click New Template and give it a name. Choose a starting layout — pick a blank board or one of the built-in layouts to jump-start your structure.
3. Open the template and add, rename, or reorder lists until it matches the workflow you want to repeat.
4. When you're ready to run the workflow, click Use Template on the card, give the new project a name (a suggested name based on today's date is pre-filled), and confirm.
5. Metadot creates a new, fully live project from the template — cards, assignments, and automations all work normally from this point on.
6. Manage saved templates anytime from the card's menu: rename, or delete templates you no longer need.

In practice

An IT manager running quarterly laptop refreshes keeps a "Laptop Refresh & Onboarding" template with lists like Devices Ordered, Imaging, Ready for Pickup, and Offboarded — Wipe Pending. Each time a new hire class starts or a refresh cycle begins, they click Use Template, name it "Q3 Refresh," and have a ready-to-assign board in seconds instead of rebuilding the list structure each time.

A facilities manager at a K-12 district keeps a "Building Maintenance" template with lists for Reported, Scheduled, In Progress, and Completed. At the start of each semester, they spin up a fresh project per building from that template, so every school follows the same tracking process without any setup work.

Tips

• Keep templates generic (list names, not specific tasks) so they stay reusable across cycles.
• Use naming conventions like "Q3 Refresh" or "Fall Semester — Lincoln Elementary" when instantiating, so it's easy to tell projects apart later.
• Delete outdated templates regularly to keep the list clean for your team.