> ## 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.

# TruBuild documentation

> AI-assisted tender evaluation for construction procurement teams: commercial bid leveling, technical scoring, tender queries, and award evidence in one governed workspace.

TruBuild is an AI-assisted tender evaluation platform for construction procurement. It gives you one governed workspace per tender package: contractor documents, commercial bid comparisons, technical scoring rounds, tender queries and clarifications, and the evidence behind the award recommendation.

AI accelerates the slow parts (extraction, bid leveling, draft scoring, query drafting), but evaluators review, override, and approve every output. The result is a decision record that stands up to committee review and audit, not a black box.

TruBuild is built for the people accountable for the tender outcome: procurement managers, quantity surveyors and cost consultants, technical evaluators, owner-side reviewers, tender query coordinators, and the administrators who control access.

## New to TruBuild?

<CardGroup cols={3}>
  <Card title="What is TruBuild?" icon="circle-info" href="/get-started/overview">
    The product in five minutes: the organization, project, and package model, and where AI fits.
  </Card>

  <Card title="Set up your account" icon="user-check" href="/get-started/setup-account">
    Sign in, create or join an organization, and get the right access.
  </Card>

  <Card title="Run your first package" icon="rocket" href="/get-started/first-project">
    A practical pilot path from package setup to your first evaluation round.
  </Card>
</CardGroup>

If you already have access, the path from sign-in to a working package is short:

<Steps>
  <Step title="Sign in">
    Enter your email and click **Continue**. Open the sign-in link from your inbox (it expires after 10 minutes), or use your company SSO if your organization requires it.
  </Step>

  <Step title="Create or join an organization">
    First user in your company? Enter the organization name and country, then click **Create Organization**. Otherwise, accept the invitation your administrator sent you.
  </Step>

  <Step title="Create a project">
    A project is the development or program. Click **Create Project**, name it, and set the country. Only organization owners and admins can create projects.
  </Step>

  <Step title="Create a package">
    A package is one tender package inside the project. Set the name, currency, and the technical/commercial weight split, add the contractors bidding, then click **Create Package**.
  </Step>

  <Step title="Upload documents">
    Add the RFP, BOQ or pricing basis, and contractor submissions to the right workflow. Each file shows **Pending** while it processes and **Ingested** when it is ready for evaluation.
  </Step>
</Steps>

See [Upload standards](/get-started/upload-documents) for accepted formats and how to structure BOQs and proposals for clean extraction.

## Choose your path

<CardGroup cols={2}>
  <Card title="Procurement managers" icon="briefcase" href="/get-started/enterprise-rollout">
    Set up the operating model for projects, packages, commercial rounds, technical rounds, access, and award evidence.
  </Card>

  <Card title="Owner and committee reviewers" icon="building-columns" href="/platform/award-readiness">
    Understand what a committee-ready award record should contain before a package is awarded.
  </Card>

  <Card title="Commercial evaluation teams" icon="calculator" href="/platform/commercial-eval">
    Level priced BOQs across bidders, review exclusions and unpriced scope, prepare commercial PTCs, and export the evaluation pack.
  </Card>

  <Card title="Technical evaluation teams" icon="list-check" href="/platform/technical-eval">
    Manage criteria, score contractor proposals, review clarification impact, and produce technical evidence.
  </Card>

  <Card title="Tender query coordinators" icon="circle-question" href="/platform/tender-queries">
    Import, assign, draft, approve, send, close, and report tender queries and clarifications.
  </Card>

  <Card title="Administrators and IT" icon="shield-halved" href="/get-started/roles-permissions">
    Manage members, roles, and team access governance, and coordinate sign-in policy (SSO, MFA) with TruBuild.
  </Card>
</CardGroup>

## Core workflows

<CardGroup cols={2}>
  <Card title="Enterprise rollout" icon="diagram-project" href="/get-started/enterprise-rollout">
    Recommended adoption path for multi-package programs and enterprise teams.
  </Card>

  <Card title="Evaluation governance" icon="scale-balanced" href="/platform/evaluation-governance">
    Controls for commercial and technical separation, rounds, clarifications, and human review.
  </Card>

  <Card title="Upload standards" icon="upload" href="/get-started/upload-documents">
    Document standards for BOQs, PTEs, RFPs, contractor proposals, PTC responses, and query imports.
  </Card>

  <Card title="Rounds and clarifications" icon="rotate" href="/platform/rounds">
    Package-level commercial and technical rounds, PTC cycles, revised submissions, BAFO-style rounds, and award locks.
  </Card>

  <Card title="Roles & permissions" icon="users" href="/get-started/roles-permissions">
    Map procurement, owner, commercial, and technical teams to TruBuild access levels.
  </Card>

  <Card title="Organization settings" icon="gear" href="/get-started/settings">
    Manage members, invitations, branding, archived projects and packages, and the activity log.
  </Card>
</CardGroup>

## Product modules

Each module can be used independently, but the strongest workflow combines them inside the same package: the commercial comparison, technical scores, and query register then all reference the same contractor list, weights, and documents.

| Module                                                            | Primary users                                                            | Decision evidence                                                               |
| ----------------------------------------------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
| [Commercial evaluation](/platform/commercial-eval)                | Commercial managers, QS teams, cost consultants                          | Bid totals, line-item comparison, exclusions, unpriced scope, commercial PTCs   |
| [Technical evaluation](/platform/technical-eval)                  | Technical leads, discipline evaluators, owner engineers                  | Criteria, scores, justifications, overrides, round-to-round impact              |
| [Tender queries](/platform/tender-queries)                        | Procurement coordinators, package leads, technical/commercial responders | Query register, draft responses, approvals, circulars, prior response knowledge |
| [Knowledge Hub](/platform/knowledge-hub) (part of Tender queries) | Procurement coordinators, package leads, responders                      | Searchable, reusable record of past tender query answers across packages        |
| [AI chat](/platform/chat)                                         | Any authorized project user                                              | Grounded answers over package context and uploaded documents                    |

<Note>
  Module availability is configured per organization by TruBuild. If a module does not appear in your sidebar, your organization admin can confirm what is enabled; to change it, contact TruBuild support.
</Note>

## Why the package structure matters

Tender evaluations go wrong in predictable ways: priced submissions compared on different scopes, technical scores influenced by prices, clarifications answered inconsistently across bidders, and award memos assembled from scattered spreadsheets. TruBuild's structure counters each one.

* **Weights are explicit.** Every package carries an agreed technical/commercial split, set before evaluation starts.
* **Commercial and technical stay separate.** Access roles keep pricing away from technical evaluators, so scores reflect quality, not cost.
* **Rounds preserve history.** Each commercial and technical round is a snapshot, so you can show what changed after clarifications and why.
* **Queries are a register, not an inbox.** Every question, response, and approval is tracked, and answers stay consistent across bidders.

For the full control model, see [Evaluation governance](/platform/evaluation-governance).