Help
Get practical support for RFPs, bids, documents, workforce, suppliers, project evidence, invoices, and network rooms.
Help detail
Complete a Bid Package
Walk through proposal, estimate, team, timeline, documents, review, amendment, and withdrawal states.
Help record
Complete a Bid Package
Walk through proposal, estimate, team, timeline, documents, review, amendment, and withdrawal states.
Bids
Available
Available
Open draft bids
Linked record context
This record is kept tied to its governing object so state, source, and next action remain clear.
Bids
| Field | Why it matters | Signal |
|---|---|---|
| Linked record | Primary object this record is tied to. | Bids |
| Record signal | The main amount, package, delivery, or capital signal to inspect. | Available |
| Status | Current visible state for this role. | Available |
| Next gate | Next allowed action or review step. | Open draft bids |
Help workflow
Review the record summary, status, related facts, evidence, and next gate before taking action.
Proposal narrative
Estimate
Team plan
Timeline
Document checklist
Final review
Evidence and source path
Evidence should stay near the decision it supports and remain visible to the right role only.
Proposal narrative
Estimate
Team plan
Timeline
Document checklist
Final review
Record packet
The record packet keeps the visible facts, source state, and allowed action in one place before the user moves deeper into the workflow.
Available
| Signal | Visible value | Why it matters |
|---|---|---|
| Linked record | Bids | Shows the governing object this record belongs to. |
| Record signal | Available | Highlights the main value, delivery, capital, or performance signal. |
| Next gate | Open draft bids | Clarifies what the user can inspect or do next. |
| Source state | Source-backed | Keeps placeholder, source-backed, and planned integration data separate. |
| Visibility | Permissioned Register view | Protects private bids, quotes, payments, and restricted diligence fields. |
Record lifecycle
This record follows a source-backed review path before any governed action is taken.
| Stage | Owner | Signal | State |
|---|---|---|---|
| Record opened | Register | Bids | Complete |
| Current state | User | Available | Available |
| Next action | User | Open draft bids | Next |
| Decision support | Reviewer | Evidence and source boundary | Pending |
| Outcome | Governed workflow | Human-controlled outcome | Planned |
Bid package steps
The guide explains the expected content for each bid step and what changes when a bid is returned for amendment.
Amendment support
Returned bids should be corrected in place so the contractor can address the precise request without creating duplicate package records.
Bid submission stepper
A bid is draft, returned, or ready for human review
Proposal, estimate, team, timeline, documents, and final review
BlueCrest must review before submission or resubmission
Record facts
Bid submission stepper
A bid is draft, returned, or ready for human review
Proposal, estimate, team, timeline, documents, and final review
BlueCrest must review before submission or resubmission
Governed action guardrail
Atlas may summarize this record, explain gaps, and draft questions. It cannot approve, deny, publish, pay, award, select, or execute the next governed action. Human owners remain responsible for every decision gate.