Skip to main content

Resource Price Book

The Resource Price Book holds unit rates for every material, labour category, and equipment type used in the project. The AI generates quantities and crew configurations โ€” it never sets prices. All rates come exclusively from the price book.


What a price book containsโ€‹

SectionExamples
MaterialsCement (50 kg bag), Reinforcement bar 10 mm dia (kg), Concrete C-25 ready-mix (mยณ)
LabourMason (day), Unskilled labourer (day), Carpenter (day)
EquipmentConcrete mixer 0.5 mยณ (hour), Tower crane (hour), Compactor (day)

Each resource has a name, unit, and unit rate.


Importing a price bookโ€‹

A price book is imported through the same Import Dataset drawer used for BOQ and rate tables, with the Resource Indexes dataset type selected.

  1. Go to Table Manager and click Import Datasets.
  2. Provide the source โ€” paste a Google Sheets URL, or click Browse for a local .xlsx/.xls workbook (unlike BOQ/rate tables, .csv is not accepted here โ€” a single CSV can't hold three separate tabs).
  3. Under Dataset Type, select Resource Indexes.
  4. Under Target Matching Scenario, choose the scenario this price book belongs to.
  5. Map each of Equipment Tab, Labor Tab, and Material Tab to the corresponding sheet tab.
  6. Click Ingest Dataset.

Import Dataset drawer with Resource Indexes selected, showing Target Matching Scenario and Equipment/Labor/Material tab selectors

There is no manual column-mapping step within each tab โ€” Name and Rate columns are detected automatically from the header row, and only the Material tab reads a Unit column (Equipment and Labor are always priced per hour). If your workbook only has some of the three resource types, leave the other tab selectors on -- Select Tab --.

Before you import

See Appendix E โ€” Accepted File Formats for the exact header keywords recognized per tab, and a gotcha worth knowing about: rows with a rate of zero are silently dropped, with no warning.


Setting the Active Price Bookโ€‹

When a scenario has multiple price books available (or when generating URAs for the first time), Conio needs to know which book to use. The Active Price Book is the project-wide default.

To set a book as active:

  1. In Table Manager โ†’ Project Resource Price Books, find the card you want.
  2. Click Set Active (star icon). This button only appears on price books that are not already active.

The active card shows an In use pill. Only one book can be active at a time.

The active price book is used automatically when:

  • Generating URAs for a scenario that has no resources loaded.
  • Pricing templates via Export as Rate Table โ†’ Priced.
  • Running Coverage Analysis โ€” an active price book is required before coverage can run at all.

Checking price book integrityโ€‹

Large price books imported from spreadsheets often contain near-duplicate resource names โ€” the same equipment entered twice with slightly different wording, or a stray typo. Conio can scan for these automatically.

  1. On the price book's card, click Preview.
  2. Click Check Integrity in the top-right of the preview.

Price Book Integrity panel showing the sensitivity slider, Clean/Needs Review chart, KPI cards, and items needing review

The Price Book Integrity panel opens on the right with:

  • A Sensitivity slider (default 90%) โ€” how similar two names must be to be flagged. Lower it to catch more borderline matches; raise it to only flag near-identical names.
  • A Clean vs. Needs Review doughnut chart.
  • Three counts: Exact Duplicates (identical normalised names), Close Matches (similar but not identical), and Suppressed (items already excluded โ€” see below).
  • An Items Needing Review list, each tagged Duplicate or Close match.
Grade suffixes are not duplicates

Names that differ only by a grade or class suffix โ€” e.g. "Operator II" vs "Operator III" โ€” are not flagged. The check assumes these are intentionally different resources, not typos.

Resolving flagged itemsโ€‹

Each row in the resource list (visible below the preview table) has three actions:

  • Edit (pencil) โ€” fix a typo or rename in place.
  • Suppress (eye icon) โ€” exclude the item from matching and coverage analysis without deleting it. Use this for a close match you're not certain is a true duplicate, or a resource you want to keep for reference.
  • Remove (trash) โ€” delete the row outright. Use this once you've confirmed it's a genuine duplicate.

After resolving items, click Check Integrity again (it re-runs with the current Sensitivity setting) to confirm the counts have dropped.


Resource match confidenceโ€‹

When the AI names a resource in a generated URA, Conio looks it up in the price book and reports how well the name matched:

BadgeMeaning
(no badge) โ€” exactThe AI-generated name matches a price book entry verbatim
~ โ€” fuzzyThe nearest substring match was used; review that the right resource was selected
โš  โ€” unmatchedNo match found; the rate for this row is 0

URA workspace showing an unmatched resource warning banner and a row with the โš  badge

A yellow zero-rate warning banner appears above the URA grid whenever any resource row is unmatched. Review the price book and add the missing resource, then re-generate the URA or manually enter the rate on the unmatched row.


Waste factorsโ€‹

Each material row in a URA carries a waste factor percentage (0โ€“20%). The effective quantity used in cost calculation is:

Effective quantity = quantity ร— (1 + waste_factor / 100)

The AI estimates waste within recommended ranges:

Material typeTypical waste factor
Concrete5โ€“10%
Masonry units (blocks, bricks)10โ€“15%
Reinforcement bar3โ€“5%
Timber, plywood5โ€“10%
Other materials2โ€“5%

You can edit waste factors manually in the URA workspace.


Next stepโ€‹

Build a URA manually โ†’