Define the scope
Import an Excel WBS and organize packages, cost lines, dates and system tags.
Capital projects · Cost control · Ready to operate
Run rig projects on one set of numbers.
Control scope, schedule, cost, risk and handover in one project record, from reactivations and surveys to upgrades and new builds.
One connected project record
From approved scope to handover.
Every module uses the same workscope, budget and schedule, so the forecast stays current as work changes.
Track delivery
Compare progress with the baseline, milestones, schedule and project risks.
Control cost
Follow budget, commitments, actuals and earned-value forecasts together.
Prove readiness
Close check sheets, punch items and readiness gates for RTO handover.
Portfolio control
See what needs attention across every project.
Management gets the portfolio view. Each project team gets the controls and decisions for its own work.
- 01Cost and forecast
Compare approved budget, actual spend and estimate at completion.
- 02Schedule and progress
See baseline slip, earned progress and upcoming milestones.
- 03Risks and decisions
Surface exposure, pending approvals and actions needing attention.
How the work moves
One clear path from scope to sail-away.
Keep the project team, approvals and handover tied to the same controlled record.
01 · Build the workscope
Start with the WBS you have.
Map spreadsheet columns, review the hierarchy and connect work packages to systems and equipment.
02 · Control changes
Route decisions to the right person.
Change requests carry their cost and schedule impact, with approvals set by delegated authority.
03 · Complete handover
Know what stands before sail-away.
Track equipment checks, punch-list close-out and readiness gates through to the RTO certificate.
Project-scoped access
The right people see the right work.
Customer data stays separate. Project assignments determine what each person can see and change.
Clear ownership, with a full record.
Directors see the portfolio. Project teams work within their assignments, and client representatives can follow progress without internal cost access.
- Each role edits its assigned project controls.
- Approval limits route changes to the right authority.
- Changes and exports stay in the audit history.
Built for project teams
One project, one accountable team.
Assign roles, dates and approval limits to each project team member.
Common questions
A few things teams ask.
Can we import our existing work scope?
Yes. Import an Excel or CSV WBS, review the mapped columns and work-package hierarchy, then connect it to schedule and cost controls.
How does ProjectOS calculate the forecast?
Planned value comes from the baseline, earned value from reported progress and actual cost from spend. These feed CPI, SPI, estimate at completion and variance at completion.
How are changes approved?
Requests include cost and schedule impact. Project managers approve within their assigned limits; requests above those limits route to the project director.
Can clients see project progress?
Yes. Client representatives can be given project-scoped access to follow progress without viewing internal cost information.
Does ProjectOS support production-platform projects?
Yes. Configure project types, workscope, controls and readiness checks for fixed platforms or floating production units.
Start with your project
See ProjectOS on your own work.
Choose a reactivation, survey or upgrade. We’ll walk your team through the scope, controls and handover that matter.