This page sets out how we work, what falls inside a typical engagement, and where our responsibility ends. Read it so we both start from the same place.
We manage the delivery process, not the technical execution. Our coordinator keeps the schedule honest, tracks dependencies, and makes sure decisions get made. The actual build, configuration, or creative work stays with your internal team or chosen vendors.
We work inside the platform you already use, whether that is Microsoft Project, Smartsheet, Jira, or a well-structured spreadsheet. If your team has no central tool at all, we set up something lightweight first and migrate later if the need grows.
Weekly reporting is the default for active engagements. We produce a one-page status update that covers progress against milestones, open risks, and decisions needed from the steering committee. Monthly deep-dives are available for longer programmes where weekly detail adds noise.
We keep artefacts lean by design. A project charter fits on two pages, RAID logs stay current because they are reviewed in every session, and meeting notes capture decisions rather than full transcripts. If a document stops being useful, we retire it.
Our practice is built around teams in Gauteng and the Western Cape. Remote coordination works well for most engagements, but we do schedule in-person working sessions for kick-offs, steering committee reviews, and critical planning workshops when travel makes sense.
We do not supply permanent staff or backfill roles. Engagements are structured around outcomes, not hours. If your situation changes mid-project, we adjust the plan together and agree on any revised scope before the next cycle begins.
These points are meant to prevent misunderstandings, not to limit what we can do together. If your project sits outside these descriptions, bring it up in the discovery session. We will tell you honestly whether we are the right fit or point you toward someone who is.
Whether you are unsure if a PMO makes sense at your scale, or you already know the gaps and need a second opinion, the fastest way forward is a direct conversation. No sales script, no obligation — just a clear read on your delivery situation.
We work with teams in Gauteng and the Western Cape, so if you are in a different time zone or province, we can still arrange a call that suits your week.
890 Nicola Manor
Lake Nicoleneberg, KZN 2239
Visits are by appointment so we can keep the day focused on project work rather than walk-ins.
Best reached between 08:00 and 16:30 on weekdays. If we are in a steering committee session, leave a message and we will call back the same day.
info@planprojectmanagement.com
For project documents, RAID log templates, or a quick question about how we fit into your current tooling, email works well.
Reporting deadlines sometimes shift these hours during month-end closes. We will confirm anything unusual in advance.
Straight answers about how we work with your team, what the first steps look like, and what you can expect from a project coordinator.
We walk through how your team currently tracks work, where things slip, and which deliverables matter most to your sponsors. You leave with a clear picture of your delivery gaps and a short list of practical next steps. No obligation, no lengthy proposal document.
No. We work inside the tools you already use, whether that is Microsoft Project, Jira, Asana, or even a well-structured spreadsheet. The goal is to improve how you plan and report, not to force a platform migration on your team.
We keep it lean. A project charter, a RAID log, a milestone plan, and a weekly report are usually enough. If a document is not being updated or read, we cut it or simplify it. The point is to keep information flowing, not to create an archive.
Most of our work involves 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 adds the most value.
We prepare a weekly report that focuses on decisions needed, risks that have changed, and milestones at risk. The format is short enough to read in five minutes, so your steering committee can act quickly instead of wading through status updates.
It depends on the project. Some teams need support for a few months during a rollout, while others prefer a longer arrangement to build internal capability. We discuss this during the discovery session and structure the engagement around your timeline.