Platform overview

TruBuild gives construction procurement teams one governed workspace per tender package. Commercial evaluation, technical evaluation, tender queries, and AI chat can each be used on their own, but they are strongest together because they share the same package context: one contractor list, one document set, one weighting, one award record. Commercial and technical rounds are tracked separately inside the package, so the cost team and the technical team each keep their own evidence history without overwriting the other. This page is the map. Each module has its own detailed guide linked below.

​

Find your way around

The sidebar is organized around the package hierarchy. Items only appear when the module is enabled for your organization and your role can see them. Inside a package, the header shows breadcrumbs (Projects > project > package), a Members button, and a Settings button, so you can always check who has access to what you are looking at.

​

Enterprise workflow map

​

The package is the center

A package is one tender package inside a project, such as enabling works, structure, MEP, or fit-out. Everything evaluators produce stays scoped to it: Keeping evidence at package level matters in practice: when the tender committee asks why a bidder’s Round 2 price moved, you can point at that package’s round history instead of reconstructing it from email and spreadsheets.

​

Modules

​

How the modules reinforce each other

The modules are useful alone, but the shared package context is where the compounding value shows up:

• Documents move between workflows. If RFP documents already exist in Tender Queries, technical evaluation setup offers Import to copy them across, so you never upload the same RFP twice.
• Past answers inform new responses. When you draft a tender query response, the consistency check compares it against the RFP and prior answers, and the query dashboard tracks the knowledge base match rate so you can see how much you are reusing.
• Chat answers from what is on screen. Chat with AI on a package, evaluation, query, or award page is grounded in that context, so “which bidder left the most scope unpriced” is answered from your actual round data.
• Both evaluations feed one award. The award record pulls the latest technical rank and score and the latest commercial rank and total bid into a single summary card, so the committee sees one consolidated position.

​

Who sees what

TruBuild scopes access at three levels, which lets you keep commercial and technical evaluations blind to each other where your governance requires it:

• Organization roles (Owner, Admin, Member) control who can create projects, invite members, and change organization settings.
• Project roles: Project Lead has full access, Commercial Lead sees only commercial workflows, Technical Lead sees only technical workflows, and Project Viewer can read both without editing.
• Package roles: Package Lead, Commercial Team, Technical Team, and Package Viewer mirror the project roles for a single package. Package membership takes priority; users without a package role fall back to their project access. Organization owners and admins always have full access.

Viewers see the same results as evaluators but every editing control is disabled, with a tooltip explaining the read-only access. See Roles & permissions for the complete mapping.

​

Evaluation rhythm

Commercial and technical evaluation follow the same review pattern, and each round shows its own status so you always know where it stands: Setup while you configure it, Analyzing while TruBuild processes the submissions, then Ready when results are open for review (or Failed with a retry option). Technical rounds add one more state, Review Complete, once an evaluator finalizes the score review; the award depends on it. For a deeper explanation of Round 1, PTC cycles, revised submission rounds, and BAFO-style final offers, see Rounds and clarifications.

​

What you can take away

Every module produces committee-ready exports, so evidence leaves the system in the formats tender boards expect: The commercial comparison and technical results workbooks both let you choose which vendors to include before download, which is useful when you circulate a shortlist analysis without exposing the full bidder field.

​

Where governance lives

Account-level controls sit above the modules: enterprise organizations can require single sign-on and multi-factor authentication, and sessions time out after 15 minutes of inactivity by default. See Enterprise rollout for the full control set.