Project Life Cycle
The documents each stage needs and the outputs it produces. Start with an available job; the update and completion stages are not open yet.
01
Project start
Build your starting point
Starting documents
- Contract
- Bill of quantities — BOQ
- Specifications
- Drawings and models
- Other documents
Each job needs only its own inputs. You do not need to upload every document listed here.
Jobs and outputs
- Quantity take-offDrawings or a model
- BOQ pricingRequires PROAn unpriced BOQ
- Generate a scheduleBOQ and project dates
- Contract analysisRequires PROThe contract document
Opens a standalone job. Your plan and usage limits apply. A generated schedule is a candidate: it becomes the approved schedule only through a separate recorded approval.
Under development
- Material, labour and equipment lists
- Procurement plan
- Method statement
- Risk management plan
Planned. No engine has been built for these yet.
02
Updates
Track work as it happens
Progress and actuals
- Schedule update from your planning software — P6 or XER
- Work done and progress
- Actual costs
- Bills and invoices
- Petty cash
Jobs and outputs
Coming Soon
- Schedule update
- Progress dashboard — EVM
- Delay analysis
- Payment certificate — IPC
- Cost report
- Cash-flow forecast
These need verified progress, cost records and the right schedule version before they open.
Under development
- Invoice register
- Cash actuals
- Recovery or revised schedule
Planned. No engine has been built for these yet.
03
Project completion
Prepare for handover
Completion workspace
The final stage brings together handover documents and closeout work. Nothing in this stage runs yet.
Having an output does not mark a project stage complete or approved.
Your project documents, with TUT
The TUT library lets you upload and discuss project documents. Running a job from saved project files, and saving its output back automatically, is not available yet.