Does your Project Manager really need to be in the office?
Updated: Sep 8
The question isn't where your Project Manager sits. It's whether they have the visibility, authority and capacity to keep the project moving.
IN THIS INSIGHT…
For many organisations, the idea of a Project Manager still conjures an image of someone sitting in the same office as the team they manage. But does physical presence actually determine whether a project is well managed?
In this Insight, you'll discover:
Why physical presence and effective project management aren't the same thing
What a Project Manager actually needs to keep a project moving
When being physically present genuinely adds value
Why the right working model should be determined by the project, not the job
DOES A PROJECT MANAGER NEED TO BE IN THE OFFICE?
It's a reasonable question.
If you're paying someone to manage an important project, you might expect them to be visible, available, and closely connected to the team delivering it.
For some projects, that may genuinely mean being in the office. But for others, it may not.
The important distinction is between physical presence and effective project leadership.
A Project Manager provides structure, coordination and accountability. They need enough visibility to understand what is happening, authority to act when something isn't going to plan, and access to the people and decisions that affect delivery.
None of those responsibilities automatically requires them to be in the same building as the people involved.
Technology makes many aspects of project coordination possible across locations, but technology alone doesn't create effective project management.
That doesn't mean the office is irrelevant. It means the office is one possible way of supporting project delivery, rather than a requirement that should automatically apply to every project.
PRESENCE ISN'T THE SAME AS PROGRESS
One of the easiest assumptions to make is that if a Project Manager is physically present, they must have better visibility of the project. Sometimes they will. But being in the office doesn't automatically create good communication, clear priorities, or effective decision-making.
A Project Manager can spend every day surrounded by the project team and still struggle to get timely decisions from leadership.
They can attend every meeting and still lack clarity about changing organisational priorities. They can be physically close to colleagues while important risks remain hidden.
Being present is not the same as being close to the things that matter. A Project Manager can be physically close to the team while being disconnected from the decisions, information or organisational priorities that actually determine delivery.
Equally, a remote Project Manager can maintain strong visibility when the project has clear governance, reliable communication and timely access to the right information.
This is particularly important for organisations where project teams are already distributed across locations.
If staff, partners, suppliers, trustees, funders, or other stakeholders aren't all based in one place, insisting that the Project Manager is office-based doesn't necessarily solve the underlying coordination challenge.
The question becomes less about where the Project Manager works and more about how the project is managed.
REFLECTION:
If your Project Manager is physically present every day, what specific project outcome does that presence improve?
And if they weren't in the office, which part of their role would genuinely become harder?
WHEN DOES BEING IN THE OFFICE ADD REAL VALUE?
There are certainly projects where physical presence matters.
physical environments — such as facilities, equipment or operational sites
close engagement with people — particularly frontline teams or people affected by significant change
high-value face-to-face activity — such as difficult conversations, complex workshops or major project launches
These are legitimate reasons to value office or site presence. But notice what they have in common. The requirement comes from the needs of the project. It isn't simply because "Project Managers should be in the office". That distinction matters.
There isn't a universal answer because there isn't a universal project.
WHAT DOES A PROJECT MANAGER ACTUALLY NEED?
If physical location isn't the defining factor, what is?
An effective Project Manager needs:
Visibility — access to accurate information about progress, risks, actions and dependencies
Authority — sufficient ability to challenge, escalate and act
Access — to the decision-makers and people who influence delivery
Clarity — about objectives, priorities and what success looks like
Capacity — enough time and resource to actively manage the project
These conditions can exist in an office, remotely or through a hybrid arrangement. The location matters only when it affects the Project Manager's ability to do the job effectively.
And the Project Manager cannot create these conditions alone. Leadership still needs to provide direction, decisions need to be made, stakeholders need to engage and resources need to be available. Good project management is an organisational capability, not something that can be delegated entirely to one person.
Moving the Project Manager into the office doesn't automatically resolve any of those issues. Better project management does.
REFLECTION:
If you're considering making a Project Manager office-based, what specific project problem would physical presence solve?
If the answer is unclear, are you solving a delivery requirement — or using physical presence as a proxy for visibility, trust or accountability?
THE RIGHT MODEL DEPENDS ON THE PROJECT
Once the project requirements are clear, the organisation can consider how best to provide the capability.
That might mean a permanent internal Project Manager. It might mean part-time, fractional or contract support. It might mean an external Project Manager for a defined period. It might mean additional support alongside an existing team.
The important decision comes first: what capability does the project need, and for how long?
None of these models is inherently better. The right choice depends on what the organisation actually needs.
Consider a charity launching a new service. It may need experienced project leadership for nine months, but have no long-term requirement for a dedicated Project Manager once implementation is complete. A permanent appointment might still be appropriate. But it might also be worth considering whether a fixed-term, contract, or external Project Manager provides a more proportionate way of accessing the capability required for that period.
Project management requirements can also change during a project's lifecycle, so the appropriate level of support may not be the same from start to finish.
THE RISK OF STARTING WITH THE JOB DESCRIPTION
Sometimes the decision is made in the opposite order. An organisation decides it needs a Project Manager, writes a job description, specifies full-time and office-based working, and only then considers what the project actually requires.
By that point, the organisation is recruiting for a working model rather than first defining the capability it needs.
That can unnecessarily narrow the field and create a longer-term commitment than the project requires. The better approach is to understand the capability required first, then decide how best to provide it.
This doesn't mean organisations should remove office requirements or avoid permanent recruitment. If there is a genuine reason for either, they should absolutely remain part of the decision.
The point is simply to understand why they are there. Is the Project Manager required to be physically present because the project genuinely benefits from it? Or because that's how the role has traditionally been designed? Those are very different questions.
REFLECTION:
If you removed the words "office-based" and "full-time" from your current Project Manager role, what capability would you actually need to replace them with?
REMOTE DOESN'T MEAN DISCONNECTED
Remote working isn't automatically better. A remote Project Manager still needs to build trust, understand the organisation and maintain strong relationships. Poorly managed remote projects can suffer from communication gaps, delayed decisions and weaker relationships.
Some teams also benefit from regular face-to-face contact. The objective, therefore, isn't to make a project remote for the sake of it. It is to create the conditions in which the Project Manager can manage it effectively.
Good project management adapts to the circumstances of the work.
START WITH THE PROJECT, NOT THE LOCATION
The question of where a Project Manager works is worth asking. But it probably shouldn't be the first question.
Start with the project:
What outcome are you trying to achieve?
How complex is the work?
Who needs to be involved?
What risks, dependencies and decisions need active management?
What project management capability already exists internally?
What level of project management capability is actually required?
Where would physical presence genuinely improve delivery?
Once those questions are answered, the working model becomes a consequence of the project requirements rather than an assumption made in advance.
THE BEST MODEL IS THE ONE THAT SUPPORTS DELIVERY
There is no prize for having a Project Manager in the office five days a week. There is also no prize for making a project remote simply because remote working is possible.
The measure of success is whether the project has the leadership, coordination, visibility and accountability it needs to achieve its intended outcome.
Physical presence, flexibility, independence and specialist experience are different considerations — not competing ideologies.
CONCLUSION
The question isn't whether your Project Manager should be in the office. It's whether you're providing the right project management capability, in the right way, for the project you actually need to deliver.
Every organisation delivers projects differently. The right solution might be dedicated Project Management, additional capacity, specialist expertise or temporary support to get an important project back on track.
At RootRise, we provide practical Project Management support shaped around the needs of the organisation — whether that's working alongside an internal team, providing additional capacity, or supporting a defined project or period of change.
If you're considering what level and type of project management capability your organisation actually needs, we'd be pleased to have an initial conversation.
There's no obligation — just an opportunity to understand what you're trying to deliver and whether the way you're currently providing project management capability is helping you get there.
