How the engagement is framed

A few clarifications so we start from the same baseline. These points shape how scopes are written, how reporting works, and where our responsibility ends and yours begins.

Scope boundaries

We work as an independent practice, not as a replacement for your internal project team. Our role covers the coordination and governance layer: charters, schedules, RAID maintenance, and steering committee packs. Execution of the actual deliverables, such as configuring your ERP or installing office furniture, stays with your team or your chosen vendors.

Tooling assumptions

Engagements run inside your existing stack. Whether that is Microsoft Project, Smartsheet, Jira, or a disciplined spreadsheet setup, we adapt to it. If your current tooling is creating more friction than structure, we will flag it early and suggest a migration path, but we do not push a proprietary platform.

Reporting cadence

Weekly reporting is built around your steering committee rhythm. If your committee meets fortnightly, we align the pack to that cycle. Reports are written for readers who need decisions, not for project management purists. We keep them short enough that sponsors actually open them, and we track whether actions from the previous meeting were closed.

Documentation philosophy

Documentation stays lean by design. If a register or log is not being updated by the people responsible for it, we treat that as a process problem, not a discipline problem. We simplify the format until it fits into the natural workflow, so the RAID log and the schedule remain living tools rather than artefacts for an audit.

What we do not cover

We do not provide legal advice, procurement services, or technical implementation of the systems being rolled out. Change management support is available as a separate workstream, but it is scoped explicitly rather than assumed. If your project requires those services, we will say so during the discovery session and help you find the right specialist.

Ways to Work With Us

Three engagement formats that match where your delivery actually is. Each one keeps documentation lean, works inside your existing tools, and gives your steering committee reporting it will read.

Project Coordination

For teams that need a dedicated coordinator to keep sponsors informed and unblock people daily.

  • Weekly status reports written for steering committees, not just for the project file.
  • RAID log maintenance with clear owners and follow-through on open items.
  • Milestone tracking and early warning when dates start slipping.

Best fit for marketing campaign launches and internal process automation where the work is clear but accountability is scattered.

Discuss your project

PMO Setup

For operations moving from ad-hoc task tracking to structured delivery without drowning in process.

  • Project charter templates and a simple governance model your team will actually use.
  • Milestone planning and resource levelling across your current workload.
  • Reporting rhythm set up so updates stay current without becoming a full-time job.

Built for ERP rollouts and office fit-outs where multiple workstreams need one consistent view.

Plan your PMO

Delivery Governance

For sponsors who need visibility and control without sitting in endless update meetings.

  • Steering committee packs that focus on decisions, risks, and what needs attention.
  • Escalation paths and decision logs so nothing gets lost between meetings.
  • Light-touch audits of existing project health and delivery gaps.

Useful when internal teams manage the work but external oversight keeps it honest.

Set up governance

Not sure which format fits?

Book a discovery session to map your current delivery gaps and we will recommend a starting point.

Book a discovery session
Cookie settings

We use cookies to keep the site reliable, remember basic choices, and understand which pages are useful. You can accept, reject, or review the settings before continuing.