If you build the same kinds of homes over and over, you should not be rebuilding the same scaffold every time. Templates are your own reusable starting points.

Save a project as a template

From a project you have already structured the way you like, choose Save as template and give it a name that describes the kind of build: Custom 2-Story, Coastal Ranch, Spec House Base.

What gets saved is the scaffold, meaning the sections, their order, and the item rows with their identity fields and units. What does not get saved is the project's client, address, or money. A template is a shape, not a copy of a job.

Create a project from one

On New project, pick a saved template instead of the default taxonomy. The new project comes up with your sections and your item list already in place, and you start editing rather than building.

Keeping templates useful

Templates go stale the same way paper checklists do. Two habits keep them honest.

Re-save after a job that taught you something. If you added three lines you keep forgetting, roll them back into the template rather than trying to remember next time.

Keep the item names generic. A template line reading "Kitchen faucet" survives; one reading "Kohler K-596 Simplice" is a selection, not a scaffold, and it will be wrong on the next house.

Templates and the library are different things

A template holds the structure of a project. The product library holds specific products you reuse. They compose: start from a template to get the rows, then insert products from the library to fill them.

Limits by plan

Saved templates are a paid plan feature, and the number you can keep goes up with the plan. See pricing for the current numbers.