Skip to main content

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.

Use your first package to prove the operating model, not every edge case. Pick one active tender package with a small group of evaluators, real contractor documents, and a procurement manager who can make decisions quickly.

​
Pilot outcome

At the end of the first package, you should have:
  • A project and package with correct weights and contractor list
  • Commercial documents uploaded against the right asset or package
  • Technical documents uploaded against the right contractors
  • A query register for bidder questions or internal clarifications
  • At least one commercial or technical round
  • A clear award-readiness gap list

​
1. Create the project and package

1

Create the project

Use the real program or development name. Set the country so regional defaults are clear.
2

Create the package

Add the package name, currency, technical weighting, commercial weighting, and at least two contractors.
3

Assign access

Add the procurement manager as project_lead or package_lead, commercial users as commercial_team, technical users as technical_team, and owner reviewers as viewers.

​
2. Choose the first workflow

Pick the workflow with the cleanest available documents.

Commercial-first pilot

Best when you have a clean Excel BOQ and contractor priced submissions.

Technical-first pilot

Best when the RFP criteria and contractor proposals are ready.

Queries-first pilot

Best when bidder questions are already arriving and the team needs control.

Chat-first pilot

Best when the team wants fast cited answers over package context.

​
Commercial-first pilot

Use this path when the commercial team has the reference BOQ or PTE and contractor priced submissions.
1

Upload the reference basis

Upload the BOQ, PTE, or commercial template in the commercial workflow.
2

Upload contractor submissions

Upload each priced submission against the correct contractor.
3

Create a commercial round

Use a clear name such as “Commercial Round 1 - initial pricing”.
4

Run the comparison

Review totals, unpriced scope, exclusions, deviations, arithmetic checks, and high-spread areas.
5

Prepare commercial PTCs

Edit the contractor-specific clarification rows and export the comparison for review.

​
Technical-first pilot

Use this path when the technical team has criteria or an RFP plus contractor technical submissions.
1

Upload criteria or RFP

Use an existing matrix where available. If not, use the RFP as the source of criteria.
2

Upload contractor proposals

Keep files linked to the correct contractor.
3

Create the first technical round

Use a clear name such as “Technical Round 1 - initial scoring”.
4

Run scoring

Let TruBuild prepare draft scores and justifications.
5

Review and override

Evaluators inspect the AI draft, make judgment calls, and record changes.

​
Queries-first pilot

Use this path when the immediate pain is managing bidder questions and response approvals.
1

Open package queries

Start from the package query register.
2

Import questions

Upload the Excel, PDF, or Word query document you received.
3

Categorize and assign

Assign each query to technical, commercial, contractual, or general owners.
4

Draft and approve

Use AI draft, RFP context, and consistency checks where useful, then send responses through your approved channel.
5

Close the loop

Mark sent and closed statuses, and capture any amendment requirement.

​
Chat-first pilot

Use this path when the team wants to test AI assistance against real package context.
1

Upload representative documents

Add an RFP, BOQ, technical submission, or query document.
2

Open chat

Ask scoped questions such as “Which package risks remain open?” or “Summarize Contractor A’s commissioning approach.”
3

Verify citations

Use chat to find and summarize evidence, then verify important claims against source documents or structured evaluation screens.

​
Pilot review

After the first package, review:
QuestionWhy it matters
Were roles scoped correctly?Prevents commercial/technical leakage and overbroad access
Which documents caused extraction issues?Improves bidder instructions before wider rollout
Were round names and evidence clear?Makes committee and audit review easier
Did evaluators understand overrides?Confirms AI is being used as draft evidence, not final judgment
Are open queries blocking award?Keeps the package from moving ahead with unresolved risk

​
Next

Evaluation governance

Turn the pilot into a repeatable control model.

Award readiness

Check whether the package evidence is committee-ready.