Templates
Reusable project starting points. What they capture, when to use them, and how to keep your library healthy.
A template is a saved starting point for a new project. Instead of starting from a blank workspace, you start from a previous project's structure: same units, same column setup, same starter rows. Then you swap in the new build's specifics.
What a template captures
| Captured | Notes |
|---|---|
| Project type | Stamped onto the new project. |
| Units | The unit list with names, in order. |
| Sheet structure | Every spec sheet (per category, with its scope). |
| Items | Item names, groups, classifications, notes, and pre-filled attribute values. |
| Custom columns | Any column customizations the source project had. |
What a template does not capture:
- The customer's name and address, those are project-specific.
- Status and completion timestamps, a fresh project starts in Draft.
- Image attachments, items come over without their images.
- Comments and audit history, those belong to the source project.
When to save a template
After you finish a project that's representative of a build type. If the next duplex you sell will be roughly the same shape, save the current one as a template. Common patterns:
- One template per build type (Duplex, Triplex, Single-family).
- One template per option package (Standard Duplex, Premium Duplex).
- One template per architect or developer if their builds repeat.
When to not save a template
- One-off custom builds that won't repeat.
- Projects mid-flight, wait until the structure has stabilised.
- Ultra-minimal projects, the workspace already ships with starter content from the category schemas.
The standard library
Specbook ships with a small set of standard library templates seeded into your workspace. They cover common build types out of the box. Treat them as a starting point, you'll usually save your own once you've adjusted them to your team's conventions.
