Forecast 26 Aug · baseline 22 Aug
Applications · Projects
The plan, the hours and the invoice, on one record.
Project plans with real dependencies and baselines, resource capacity you can commit against, timesheets that reach billing, and a status report assembled from what actually happened. Implementation, rollout, construction, campaign or client delivery: the same discipline.
plans · dependencies · baselinesCapacity & utilisationTimesheets to invoiceStatus from the record
One programme · baseline to authorityA changed API contract reaches milestone, capacity, margin and readiness before the plan changes.PR-038 · MS-21 · BL-219
09:18•••
Baseline v3 · contract v7 · team calendars
Margin remains illustrative and visible.
No plan, booking or milestone changed.
The delivery record carries the promise, the hours and the invoice consequence.
PR-038 is not a task list. It is a baseline, dependency graph, capacity commitment, margin view and named decision trail that finance and delivery can both read.
Commit what delivery means.
The saved plan keeps dates, dependencies and scope visible after the schedule changes.
Read progress from work.
Tasks, effort, blockers and approvals build status without a weekly reconstruction.
Model the cross-project trade.
BL-219 reaches MS-21, capacity and margin before a recovery path is proposed.
Retain the delivery commitment.
Kavya validates the evidence; Rohan decides the capacity move and its consequence.
What changes
Move from status assembly to evidence-backed recovery.
Task tools are cheap and everywhere. What they do not do is connect the plan to capacity, to cost and to the invoice, which is where projects are actually lost.
Planning
The SaaS playbook
→Boards and lists, with dates as decoration.
Rebuilt agentic
Work breakdown with real dependencies, critical path and a saved baseline, so slippage is measured against what you committed, not what you last edited.
Resourcing
The SaaS playbook
→Assignment by name, and hope about capacity.
Rebuilt agentic
Capacity by skill, role and calendar, with soft booking during pursuit and firm allocation on award: over-allocation is refused at the point of assignment.
Time & effort
The SaaS playbook
→A timesheet nobody fills, approved by nobody.
Rebuilt agentic
Time captured against the task on web and mobile, approved by the delivery lead, and carried straight into billing, utilisation and project cost.
Risks & issues
The SaaS playbook
→A RAID log, updated before the steering committee.
Rebuilt agentic
The risk-watch agent reads slippage, open dependencies and burn rate daily and raises the risk with the date it will become a delay.
Billing
The SaaS playbook
→A milestone spreadsheet, re-keyed into invoicing.
Rebuilt agentic
Fixed-fee milestones, time-and-material and retainer models compute from approved effort and trigger the invoice on the same record.
Status reporting
The SaaS playbook
→A deck built the night before the call.
Rebuilt agentic
The status brief is assembled from the record: progress, spend, risks, decisions pending, and the project manager edits rather than writes it.
Read the dependency, capacity and margin trade-off in one room.
The recovery brief is evidence-cited, but Kavya validates the path and Rohan retains the cross-project commitment.
Programme 360
DC-031 · authority dueCore rollout · Wave 2
Integration exit · 22 Aug → Integration exit · 26 Aug
MS-12 → MS-18
MS-18 → MS-21
MS-21 → MS-27
MS-24 → MS-27
MS-27 → MS-31
Wk 1 92% · Wk 2 118% · Wk 3 105% · Wk 4 84%
Wk 1 76% · Wk 2 94% · Wk 3 121% · Wk 4 88%
Wk 1 68% · Wk 2 87% · Wk 3 109% · Wk 4 98%
Farah Ali · MS-21 integration exit +4 days
Neel Shah · MS-24 rehearsal may lose one day
Rohan Desai · Go-live or 3-point margin trade-off
Schedule baseline v3 joined to current task progress
API contract delay linked through MS-21 to rehearsal
Team calendars and PR-041 allocations modelled
No project plan, booking, or milestone changed
One critical-path decision at the scale of the authority it carries.
Rohan sees the record, delay, evidence, downstream consequence, prepared route and named action without opening a miniature dashboard.
Core rollout · Integration exit
Vendor contract schema changed after baseline.
Rehearsal needs two days of recovery.
No cross-project booking is automatic.
09:185G
Baseline 22 Aug · BL-219 +4 days
Team calendars · margin model · dependency path
Current forecast margin 14% · illustrative.
Rohan Desai remains delivery authority.
What delivery gets.
Project templates carry your methodology: stage gates, deliverable types, approval points, so the second project starts from the first. Plan, capacity, cost, evidence and client approval remain joined to the commitment.
Work breakdown & plan
Multi-level task structures with dependencies, constraints, milestones, critical path and baseline versions.
wbs · dependency · baselineTemplates & stage gates
Reusable project templates with stage gates, mandatory deliverables and the approvals that release the next stage.
template · gate · releaseCapacity & allocation
Resource pools by skill and cost rate, soft and firm booking, leave-aware availability and utilisation targets.
pool · booking · utilisationTimesheets & approval
Task-level time on web and mobile, submission cycles, delivery-lead approval, and rejection with a reason.
cycle · approve · rejectBudget & cost
Effort, expense and procurement cost against budget with committed versus incurred, and variance by work package.
committed · incurred · varianceRisks, issues & decisions
RAID entries with owners and dates, decision log with the option chosen and why, and escalation into the steering forum.
raid · decision logClient collaboration
A branded workspace for the customer: deliverable review, approval with e-sign, and a shared document trail.
review · e-sign · sharedPortfolio view
Programme and portfolio roll-up with health, margin and delivery-risk ranking across every active engagement.
roll-up · health · marginGoverned delivery
A slipping dependency that raises the risk before the review.
A prepared recovery is not a revised baseline. The delivery lead validates evidence; the director records the cross-project commitment.
“which projects will breach their baseline this month and which dependency causes it”
Three agents on delivery. The commitment stays the lead's.
Agents assemble plans, surface dated risks and prepare status. The commitment remains with the lead and delivery authority.
Drafts the work breakdown from the template and the scope document, with dependencies and a first-cut resource ask.
delivery lead commits the planReads slippage, burn rate and open dependencies daily and dates the delay before it happens.
risks carry an owner, alwaysAssembles the weekly status from the record: progress, spend, risks, decisions pending, for the manager to edit.
no number without a drill pathChases missing time against the approval cycle and flags entries that will not survive a billing review.
approvals stay with the lead
Bring a live project plan. See it under governance.
A 90-minute working session: your project template, stage gates and billing model drafted as an FRS, approved, and generated to a staging tenant with a real plan loaded.
For your technical team
Projects are meta on the platform: the same customer and employee records, durable execution behind every stage gate, and timesheet approvals attributable down to the policy version that priced them.