User Guide
10.2 · Templates

Creating a Template

You can create a template from scratch, from a selection, or by duplicating an existing template.

From a Selection (Most Common)

  1. In Direct Costs (or Overheads, Resources, Carbon), select rows.
  2. Right-click → Save as Template.
  3. Enter Name, Description, Category, Scope.
  4. Tick Embed Resources if you want the resources to travel with the template.
  5. Save.

The service methods behind this:

  • SaveDirectCostsAsTemplateAsync
  • SaveOverheadsAsTemplateAsync
  • SaveResourcesAsTemplateAsync
  • SaveCarbonAsTemplateAsync
  • SaveDirectCostBreakdownsAsTemplateAsync
  • SaveOverheadBreakdownsAsTemplateAsync
  • SaveResourceBreakdownsAsTemplateAsync

From Scratch

  1. Open Templates → New Template.
  2. Choose a Target Type.
  3. Add line items manually; the grid looks like a mini direct-cost / overhead view.
  4. Each line supports Qty, Unit, Resource (by name), Rate, Formula.

Fields You'll Fill In

FieldPurpose
NameRequired.
DescriptionShown in preview cards.
CategoryGroup templates in the picker.
TagsAdditional filtering.
Target TypeDirectCosts / Overheads / Resources / etc.
ScopePrivate / Project / Organisation / Global.
StatusDraft while editing; Active once ready.
SpecificationsOptional — link to AS3600, NCC2022, etc.
Embed ResourcesSave resource snapshots alongside line items.

Line Items

Each ItemTemplateLineItem carries the same structure as a real item:

  • LineNumber, WBS, ParentId, IndentLevel (0–6), SortOrder.
  • Item, Description, Notes.
  • Quantity, Unit, ResourceRate, Total.
  • ResourceName, ResourceType — strings, no FK (so templates port).
  • Formula — supported and preserved on apply.
  • Status — typically all Draft in templates.
  • Formatting fields.

Duplicate

Templates → Duplicate copies an existing template. Ownership defaults to the current user.

Publishing

  • Active status makes the template pickable on Apply.
  • Promote a template to Organisation scope via Templates → Scope → Organisation (requires admin permission).
  • Promote to Global scope is typically done by your organisation's TX1 administrator.

Versioning

Version number on the template. Bump it when you make a breaking change so linked projects know to sync.

Tips

  • Keep templates small and composable — one template per trade, not "the whole project".
  • Name with a verb + noun pattern: "Install — Site Services", "Price — Standard Preliminaries".
  • Use Tags for cross-cutting filters (e.g. "Civil", "Fit-out").