TruBuild gives enterprise procurement teams a governed workspace for each tender package. Commercial, technical, tender query, and chat workflows can be used independently, but they are strongest when they share the same package context, contractor list, documents, and award record. Commercial and technical rounds are tracked separately inside the package so each evaluation team can preserve its own evidence history.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.
Enterprise workflow map
1. Set up the package
Define the package, currency, contractors, technical/commercial weighting, and access model.
2. Control the documents
Upload RFPs, BOQs, PTEs, contractor proposals, round responses, and query documents into the correct workflow.
3. Evaluate commercial submissions
Run BOQ comparisons, review anomalies, prepare commercial PTCs, and export evidence.
4. Evaluate technical submissions
Manage criteria, score proposals, review clarification impact, and preserve round history.
5. Manage clarifications
Import, assign, draft, approve, send, close, and report tender queries and circulars.
6. Prepare award evidence
Combine commercial, technical, and query evidence into a decision-ready award record.
The package is the center
Each package contains:| Item | Purpose |
|---|---|
| Contractors | The bidders being evaluated |
| Technical weight | The agreed contribution of technical evaluation to award recommendation |
| Commercial weight | The agreed contribution of commercial evaluation to award recommendation |
| Assets | Commercial scopes or asset splits used for priced comparisons |
| Documents | RFPs, BOQs, PTEs, proposals, PTCs, query imports, and uploaded context |
| Commercial rounds | Package-level commercial snapshots across submission and clarification cycles |
| Technical rounds | Package-level technical snapshots across initial and post-clarification cycles |
| Tender queries | The register of questions, responses, approvals, duplicates, and circulars |
| Award fields | Selected contractor and award comments |
Modules
| Module | Primary users | Best used for |
|---|---|---|
| Commercial evaluation | Commercial managers, QS teams, cost consultants | Compare priced submissions, find exclusions/unpriced scope, and prepare bidder-specific PTCs |
| Technical evaluation | Technical leads, discipline evaluators, owner engineers | Score proposals against criteria and manage clarification-driven re-scoring |
| Tender queries | Procurement coordinators, package teams, approvers | Run a controlled query workflow from import through response circular |
| AI chat | Authorized project users | Ask cited questions over the package and evaluation context |
Feature availability is controlled at organization level. If a module is not visible, ask your TruBuild administrator to check the organization’s feature entitlements.
Access model
TruBuild separates users by project and package scope:project_leadandpackage_leadcan coordinate across disciplines.commercial_leadandcommercial_teamwork in commercial workflows.technical_leadandtechnical_teamwork in technical workflows.project_viewerandpackage_viewercan review without editing.
Evaluation rhythm
Every evaluation area follows the same review pattern:Clarify
Issue commercial or technical PTCs, import responses, and decide what changes the next round.
Where governance lives
Evaluation governance
Controls for separation of duties, rounds, clarifications, and human review.
Award readiness
Checklist for committee-ready award evidence.