09 / 14

Project Management & Automation

Plans that revise themselves when circumstances change.

A project plan ceases to be accurate the moment a dependency slips, but the system holding the plan is generally not informed. The consequence is that revised dates are communicated late, and usually by the party least responsible for the delay.

What changed this week?

ONESUITE

Three items. The interior package slipped four days, moving handover to the 22nd. Dependent tasks have been rescheduled and both owners notified. Client correspondence has been drafted and awaits approval.

Investigated, reasoned and prepared. Nothing is sent, paid or amended without your authorisation.

The working surface

onesuite / project-management-automationSchematic

Schedule

Dependencies

Owners

Tasks against dates, with dependent activities shown so that slippage is visible immediately. Layout shown for orientation; it is a wireframe, not the finished interface.

What it covers

  • Tasks, owners, dependencies, dates, documents and correspondence for each project
  • Current status, including what is blocked and by whom
  • Prior versions of the plan, retained for comparison
  • The effect of a given slippage on the completion date
  • Where capacity is over-committed, and where it is available
  • Projects at risk before the risk is formally reported
  • Reschedules dependent activities and notifies the parties affected
  • Escalates to the responsible party rather than to the whole team
  • Compiles status reports from the record

Matters reserved for you

Scope, sequence, and what is communicated to the client when dates move.

The same engine, configured to your industry — one of 446 verticals — and provided without licence fee for the first year.

Request a configuration for your industry