> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trubuild.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Platform overview
> A map of every TruBuild capability: package setup, commercial and technical evaluation, tender queries, Knowledge Hub, AI chat, and the award record.
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.
| Sidebar item | What it opens |
| --------------------------- | ------------------------------------------------------------------------------------------- |
| **Overview** | Your dashboard landing page |
| **All Projects** | Every project in your organization |
| **Projects** > project name | One project, with its **Packages**, **Commercial**, **Technical**, and **Queries** sections |
| **Knowledge Hub** | Search and reuse past tender query answers |
| **Vendor Database** | Search and compare vendor records |
| **Brain** | Organization-wide patterns, lessons, and Agent Sam (owners and admins only) |
| **Settings** | Organization, project, package, member, and branding settings |
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
Name the package, set the currency, add contractors, and set the technical/commercial weighting with the slider (the two always total 100%).
Upload RFPs, BOQs, pre-tender estimates, criteria files, contractor submissions, and round responses into the correct workflow, filed against the correct contractor.
Run BOQ comparisons per asset, review pricing anomalies and unpriced scope, prepare commercial PTCs, and export the comparison workbook.
Define weighted criteria, score proposals with evidence, run PTC rounds, and track score movement between rounds.
Import, assign, draft, approve, and send tender queries, then generate tender circulars for amendments.
Combine the latest reviewed commercial and technical rounds into a decision-ready award record with comments.
## 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:
| Item | Purpose |
| ----------------- | ---------------------------------------------------------------------------------------------------------------- |
| Contractors | The bidders being evaluated |
| Technical weight | The agreed contribution of technical scoring to the award recommendation |
| Commercial weight | The agreed contribution of commercial evaluation, filled in automatically as the balance of the technical weight |
| Assets | Commercial splits such as towers, zones, or buildings, used for per-asset priced comparisons |
| Documents | RFPs, BOQs, pre-tender estimates, criteria files, contractor submissions, PTCs, and query imports |
| Commercial rounds | Priced comparison snapshots across submission and clarification cycles |
| Technical rounds | Scoring snapshots across the initial submission and PTC rounds |
| Tender queries | The register of bidder questions, responses, approvals, and circulars |
| Award record | The selected contractor, award comments, and the **Awarded** badge on the package dashboard |
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
| Module | Primary users | Best used for |
| -------------------------------------------------- | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| [Commercial evaluation](/platform/commercial-eval) | Commercial managers, QS teams, cost consultants | Compare priced submissions line by line, rank bidders, flag exclusions and unpriced scope, and prepare bidder-specific PTCs |
| [Technical evaluation](/platform/technical-eval) | Technical leads, discipline evaluators, owner engineers | Score proposals against weighted criteria with cited evidence and manage clarification-driven re-scoring |
| [Tender queries](/platform/tender-queries) | Procurement coordinators, package teams, approvers | Run a controlled query workflow from import through approval, sending, and response circulars |
| [Knowledge Hub](/platform/knowledge-hub) | Procurement coordinators, package teams | Search past tender query answers by category, region, and discipline, and generate Q\&A documents |
| [AI chat](/platform/chat) | Authorized project users | Click **Chat with AI** on package, evaluation, query, and award pages to ask grounded questions about that context |
| [Brain](/platform/brain) | Organization owners and admins | Explore patterns, lessons, and vendor history across all past packages, and ask Agent Sam organization-wide questions |
| Vendor database | Package creators, procurement managers | Search existing vendor records when adding contractors to a package |
Modules are enabled per organization by TruBuild. If a module is missing from your navigation even though your project access looks right, your organization admin can confirm what is enabled; to change it, contact TruBuild support. Brain is additionally limited to organization owners and admins.
## 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](/get-started/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.
Confirm the package setup, contractor list, access roles, and required documents. Wait for each upload to move from **Pending** to **Ingested** before running an evaluation; a **Failed** file shows the reason so you can re-export and re-upload it.
Start a commercial comparison with **Create and run evaluation**, or a technical scoring round from the technical setup wizard. Processing runs in the background and shows progress while you work elsewhere.
Evaluators inspect the AI output, check the cited evidence, correct or override values, and add notes. Nothing goes into the award record without human review.
Issue commercial or technical PTCs and collect the bidder responses for the next round. Tender queries from bidders are tracked separately in the query register. Decide per criterion or per line item what carries into the next round.
Complete the technical score review on the latest round, then open **Award package**. Pick the winner under **Select contractor**, check the summary card showing the technical rank and score next to the commercial rank and total bid, add **Award comments (optional)**, and click **Award package**. The contractor must rank in both the technical and commercial evaluations to be eligible.
For a deeper explanation of Round 1, PTC cycles, revised submission rounds, and BAFO-style final offers, see [Rounds and clarifications](/platform/rounds).
## What you can take away
Every module produces committee-ready exports, so evidence leaves the system in the formats tender boards expect:
| Deliverable | Format | Where to get it |
| ------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------ |
| Commercial comparison workbook | Excel | Commercial asset view, **Export Comparison**, with vendor, rate/amount, and PTE options |
| Commercial PTC questions | Excel | Commercial evaluation, exported per asset and round |
| Technical results workbook | Excel | Technical evaluation, **Export** then **Results (Excel)** |
| Technical evaluation report | Word | Technical evaluation, **Export** then **Report (Word)** |
| Tender query report | Excel | Query dashboard, **Export Report**, with SLA, response-time, and bidder analytics |
| Tender circular | Word | Query workflow, **Generate tender circular**, covering pending amendments |
| Query and answer documents | Word, PDF, or HTML | Knowledge Hub document generator, with Q\&A and summary templates and per-status query selection |
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
Controls for separation of duties, rounds, clarifications, audit history, and human review.
Checklist for committee-ready award evidence.
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](/get-started/enterprise-rollout) for the full control set.