Too many hands in one file
On a project with dozens of subcontractors, updates arrive by email and spreadsheet and get keyed into P6 by one overloaded planner. Errors creep in and nobody can tell whose input is whose.
Know exactly what changed in your schedule, and why.
POKO runs every schedule update on top of Primavera P6. Each subcontractor updates only their own scope, logic changes wait for approval, and the analysis is ready the moment the period closes.
Activity Scope owner W1W3W5W7W9W11
Site mobilisation Main contractor
Excavation & shoring Earthworks sub.
Raft foundation Structural sub.
Superstructure L1–L8 Structural sub.
MEP rough-in MEP sub.
Façade installation Façade sub.
POKO doesn't replace Primavera P6. It controls how P6 gets updated.
- Your P6 schedulestays the single source of truth
- Scoped updates in POKOreviewed, approved, analysed
- One merged P6 scheduleready to share
Why schedule updates break down on large projects
The tools for planning are mature. The process for updating a shared schedule every month is not.
Changes hide in the logic
A shortened lag or a relationship switched from finish-to-start to start-to-start can absorb weeks of delay without a single date looking wrong. These edits are easy to make and hard to spot.
Analysis comes too late
By the time the update is merged, checked and analysed, the period is half over. Owners and main contractors end up reacting to last month's picture.
One update period, start to finish
The same six steps every period, with every input traceable to the person who made it.
- 1
Open the update period
The planning admin loads the current P6 schedule and sets a deadline.
- 2
Invite by scope
Each subcontractor and engineer gets an email with access to their own activities only.
- 3
Update progress
Actual dates, percent complete and remaining durations, entered where the work is done.
- 4
Review logic changes
Any change to a link, lag or relationship is flagged and waits for admin approval.
- 5
Close and analyse
S-curve, earned value and Monte Carlo forecasts run as soon as the period closes.
- 6
Merge back to P6
All approved updates are merged into one P6 schedule, ready to download and share.
Built for planning teams, not just planners
- Scope-based access
- Every user sees and edits only the activities they are responsible for, on the projects they are invited to.
- Change control with an audit trail
- Who changed what, when, and who approved it. Logic edits never reach the schedule unreviewed.
- S-curve and earned value
- Planned versus actual progress, SPI and CPI, recalculated for every update period.
- Monte Carlo risk forecast
- P50 and P80 finish dates based on the current schedule, so you can see how much float is left.
- AI-assisted actions
- Plain-language summaries of what changed and suggested follow-ups for late or slipping scopes.
Who uses POKO
Everyone in the update cycle works in the same place, each with the access their role needs.
-
Owners and employers
A schedule you can trust each month, with every change explained and approved.
-
Main contractors
One update cycle for all subcontractors, without retyping their input into P6.
-
Project management consultants
Independent visibility of progress, logic changes and forecast finish dates.
-
Subcontractors
A simple screen for their own scope instead of spreadsheets and email chains.
See POKO running on your own schedule
Send us a recent P6 schedule and we'll walk you through one full update period with your activities, your scopes and your subcontractors.