Skip to main content

Template Library

The Template Library stores pre-verified resource breakdowns (materials, labour, equipment) for known work types. Templates are the backbone of consistent, scalable URA generation โ€” once a template exists for a work type, every future item of the same type can be built from it rather than generated cold from scratch.

Templates are project-level (global). A template seeded in one scenario is immediately available to all other scenarios in the same project.


Accessing the Template Libraryโ€‹

Go to Settings โ†’ Recipe Library. The library lists all templates with their name, unit, keyword string, and creation date.

Template Library table showing all templates with export dropdown and selection checkboxes


How templates are used at generation timeโ€‹

When you generate a URA for a BOQ item, Conio looks up the Template Library and selects how to use the best matching template based on a Jaccard score:

ScoreTierHow the template is used
1.0 (definitive link)DefinitiveTemplate adopted verbatim โ€” no AI call. Resources re-priced from the current price book only.
โ‰ฅ 0.65BaselineAI keeps the resource makeup; adjusts quantities, crew sizes, and usage factors only
0.30 โ€“ 0.65Starting pointAI uses the closest recipe as a starting point; may add, remove, or substitute resources
< 0.30ColdNo template is close enough; AI generates from scratch

The Baseline and Starting point tiers ensure the AI adapts an existing recipe rather than inventing a new one. The Definitive tier (score = 1.0) is produced when the matched rate row was exported from the Template Library โ€” see Exporting.


Writing good keywordsโ€‹

Template keywords are the primary signal for template matching. Generic, trade-level terms that appear in any BOQ description for that work type โ€” regardless of project-specific wording โ€” produce the best cross-project coverage.

Too specific (raw phrase)Broadly matchable (generic)
Excavation in hard rock by blasting m/crock excavation, blasting, hard rock, ripping
C-25 concrete for columns using drum mixerconcrete, c-25, columns, drum mixer, in-situ
Cement sand plaster 1:3 to wallsplastering, cement plaster, sand render, wall, ceiling

Keywords generated by AI Refine during the seeding workflow are already generic by design. If you promote a URA manually (without going through seeding), you may need to edit the keywords.

Editing keywordsโ€‹

  1. In the Template Library, click the edit icon on a template row (or click the row to open the edit modal).
  2. Find the Keywords field.
  3. Enter a comma-separated list of generic trade terms.
  4. Click Save.

Template edit modal showing the keywords field with current and suggested terms


Importing templates from CSVโ€‹

If you have a set of verified URA templates from a previous project or a standard library, you can import them directly:

  1. In the Template Library toolbar, click Import โ†’ Templates (JSON or CSV).
  2. Select your file. The required columns are: name, unit, keywords, materials, labour, equipment.
  3. Rates are zeroed on import โ€” they are resolved from the current project's active price book at generation time.
Starter template packs

Before starting a new building project, import a standard template pack covering the most common work types (Concrete, Formwork, Reinforcement, Masonry, Plastering, Earthworks). This gives the Coverage Analysis a head start and reduces the number of templates that need seeding from scratch.


Exporting templatesโ€‹

Templates can be exported as JSON for sharing between projects:

  • Click Export โ†’ Templates (JSON) in the toolbar.
  • Rates are zeroed in the export. The receiving project resolves rates from its own price book.

To export templates as a Rate Table (with optional pricing), see Exporting.


Next stepโ€‹

Run Coverage Analysis and seed templates for your BOQ โ†’