Help
Get practical support for RFPs, bids, documents, workforce, suppliers, project evidence, invoices, and network rooms.
Help detail
Run a Project Workspace
Understand how approvals, workforce, suppliers, progress evidence, invoices, and Atlas groups connect to a project.
Help record
Run a Project Workspace
Understand how approvals, workforce, suppliers, progress evidence, invoices, and Atlas groups connect to a project.
Projects
Available
Available
Open projects
Linked record context
This record is kept tied to its governing object so state, source, and next action remain clear.
Projects
| Field | Why it matters | Signal |
|---|---|---|
| Linked record | Primary object this record is tied to. | Projects |
| 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 projects |
Help workflow
Review the record summary, status, related facts, evidence, and next gate before taking action.
Approval roadmap
Workforce demand
Supplier dependencies
Evidence files
Invoice milestones
Network room
Evidence and source path
Evidence should stay near the decision it supports and remain visible to the right role only.
Approval roadmap
Workforce demand
Supplier dependencies
Evidence files
Invoice milestones
Network room
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 | Projects | Shows the governing object this record belongs to. |
| Record signal | Available | Highlights the main value, delivery, capital, or performance signal. |
| Next gate | Open projects | 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 | Projects | Complete |
| Current state | User | Available | Available |
| Next action | User | Open projects | Next |
| Decision support | Reviewer | Evidence and source boundary | Pending |
| Outcome | Governed workflow | Human-controlled outcome | Planned |
Project workstreams
The project workspace is the anchor for delivery activity. Related pages should not become standalone records detached from the awarded project.
Evidence habit
Keep documents, inspection notes, delivery proof, and invoice support close to the project so payment and closeout reviews have context.
Awarded project workspace
Contract acceptance or kickoff preparation
Approvals, workforce, suppliers, documents, invoices, and network rooms
Keep every workstream tied back to the project and next action
Record facts
Awarded project workspace
Contract acceptance or kickoff preparation
Approvals, workforce, suppliers, documents, invoices, and network rooms
Keep every workstream tied back to the project and next action
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.