Structured delivery for teams that are done with ad-hoc tracking

PlanProject Management is an independent practice helping mid-sized operations in Gauteng and the Western Cape move from scattered task lists to delivery that holds up under scrutiny. We handle project charters, milestone planning, RAID log maintenance, resource levelling, and weekly reporting your steering committee will actually read.

Typical engagements include ERP rollouts, office fit-outs, marketing campaign launches, and internal process automation. We work inside the tools you already use, and we keep documentation lean enough that people update it.

What a typical week looks like

A snapshot of the coordination rhythm we bring to an engagement, so sponsors stay informed and teams stay unblocked.

  • Monday: Milestone check-in

    Review what moved last week and what is at risk before it becomes a problem.

  • Wednesday: RAID log update

    Assign owners to new risks and issues, and confirm mitigations are actually moving.

  • Friday: Steering committee pack

    A concise report that highlights decisions needed, not just activity completed.

Want to see how this applies to your context? Read about setting up a PMO that sticks or keeping RAID logs alive.

What a dedicated coordinator actually does

Most teams don't need a heavyweight PMO. They need someone who keeps the plan honest, surfaces problems early, and makes sure the steering committee hears about them before they become crises. Here is the work we take on.

Project charters that set the rules

A one-page charter that names the sponsor, states the scope boundary, and lists what is explicitly out of scope. No ambiguity about who approves changes or what happens when the timeline slips.

Milestone planning with real dates

We break the work into milestones that mean something to your business, not just to the project file. Each one has an owner, a deliverable, and a date the team actually believes in.

RAID log maintenance

Risks, assumptions, issues, and dependencies tracked in a way people update. We review it weekly, assign owners, and make sure items don't sit there for months without a decision.

Resource levelling

When two initiatives need the same person in the same week, we spot it early. We adjust the plan, talk to the people involved, and show the trade-offs to sponsors before they become surprises.

Weekly reporting that gets read

Steering committees don't need a 40-slide deck. They need a clear status, what changed, what's blocked, and what decision is required. We write reports that respect their time.

Working inside your existing tools

We don't force a new platform on your team. If you run on Excel, Google Sheets, or a tool like Asana, we adapt to that and keep the documentation lean enough that people actually maintain it.

Typical engagements: ERP rollouts, office fit-outs, marketing campaign launches, internal process automation.

See how engagements are structured

Common questions about how we work

Straight answers about what a project coordinator actually does, how we fit into your existing setup, and what to expect when we start.

Do we need to change our project management software?

No. We work inside whatever you already use, whether that is Microsoft Project, Smartsheet, Jira, or a well-maintained spreadsheet. The point is to make your current tooling more structured, not to add another platform your team has to learn and maintain.

What does a typical engagement look like in the first month?

We start by mapping your current delivery gaps and identifying who needs what information and when. From there we set up the core artefacts: a project charter, a realistic milestone plan, and a RAID log with clear owners. You get a weekly report that summarises progress, risks, and decisions needed, so your steering committee can act rather than just review.

How much documentation will we have to maintain?

As little as possible. We keep documentation lean and practical, so people actually update it. If a template or log is not earning its keep, we cut it. The goal is a lightweight structure that supports delivery, not a filing system that slows everyone down.

Which types of projects do you typically support?

Most of our work falls into ERP rollouts, office fit-outs, marketing campaign launches, and internal process automation. These projects usually have multiple stakeholders and tight deadlines, which is where a dedicated coordinator who keeps sponsors informed and teams unblocked makes the biggest difference.

How do you handle resource conflicts across departments?

We do resource levelling at the planning stage and revisit it as the project moves. When two pieces of work compete for the same person, we surface the trade-off early and give you options with clear implications, so the decision is made with full context rather than discovered late.

What is the difference between a PMO setup and ongoing coordination?

A PMO setup is about putting the right governance in place: charters, reporting rhythms, RAID processes, and clear roles. Ongoing coordination is the day-to-day execution of that structure, keeping schedules current, chasing actions, and preparing steering committee packs. We can do either or both, depending on where your team needs the most support.

Still unsure whether this fits your situation? Read more about how we support teams during an engagement or reach out directly with your specific context.

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.