Five Conversations on an Owner's Side
Most descriptions of this job list deliverables — schedule governance, cost review, risk, reporting. Those are real, and they're all downstream of something simpler. An owner's agent is a person standing in the middle of five conversations that are happening at the same time, where each group is answering a different question and none of them can see the whole picture.
Get one of those five wrong and the program doesn't fail loudly. It just starts to drag, and everyone develops their own explanation for why.
1. The owner
What the owner is really asking is not is everything on track. It's is the date real, and can I trust the person telling me. Those are different questions, and the second one is the harder one to answer honestly, because the answer sometimes costs you the relationship with the delivery team.
An owner who has never read a G702 and an owner on their fourth building present the same title and need completely different things from you. The first needs to be walked through what the documents actually commit them to. The second already knows, has red-lined the contract before your first call, and wants to argue about the schedule logic instead. Meeting both where they actually are is most of the work.
The failure mode here is agreement. A representative who nods through a meeting and never surfaces the uncomfortable question is not being diplomatic. They are deferring a decision that will be more expensive later, and they are spending the owner's trust to do it.
2. The designer
Design teams walk in protecting something, and it is rarely just cost. It's design intent, scope, liability, and a project that goes on their website for the next decade. If you arrive carrying only the owner's budget concerns, the drawings will come back exactly the way they were — and you will have spent the relationship getting there.
The useful move is to find out what is actually sacred before you start trading. Which parts of this design does the team care about? The ceiling plane, the material palette, the way the light lands in the lobby. Once you know what matters, you can help the owner trade around it instead of stepping on it.
And you have to know the designer's contract as well as the owner's. Owners ask designers for things that were never in scope, constantly. A representative who can see that line, hold it, and get the design team paid properly when the owner genuinely wants the extra service is worth more than one who simply pushes.
3. The contractor
This is the conversation most people picture when they hear "owner's representative," and it is the one that most often goes wrong.
The contractor's real need is unglamorous: answers, quickly, in writing. When an owner takes two weeks to approve a finish substitution, that delay does not stay with the owner. It becomes the contractor's schedule problem, then the subcontractor's, and then a variance the owner pays for. Nothing in that chain announces itself as an owner-side failure, which is why it gets to keep happening.
Twenty years on the government side taught me what happens when a reviewer's default answer is no. The submittals still got approved. They just took longer, cost more to process, and by the third month the contractor had stopped bringing anything to the table early — because there was no upside in it. A representative whose instinct is resistance does not read as rigorous. They read as a cost, and the team quietly routes around them.
That doesn't mean going easy. It means being strict where the contract matters and practical where it doesn't, and being consistent enough that the contractor can predict which one they're getting. When something is genuinely wrong, cite the paragraph and have the conversation. When something is close enough, say so, and mean it.
4. The trades
Subcontractors build the job. Every decision made in a conference room is really a decision about whether the trades can do their work, and the trades are the group with the least ability to say so politely.
Managing them is not the owner's agent's job — that belongs to the general contractor. But making sure the path in front of them is clear is, and so is noticing when it isn't. Coordinated drawings. Complete scope. Requests for information that get real answers before the steel arrives on Tuesday rather than after.
There is a harder version of this. When a legitimate change order sits unanswered for two months, or a pay application gets cut without a reason anyone will put in writing, that is not only a contractor problem. Subcontractors who are not paid leave. Subcontractors who are squeezed stop caring as much about quality. Subcontractors who believe nobody is watching out for them do not come back for the next bid — and on a campus program, the next bid is often the one that decides the second building.
Asking about that is not taking over. It is making sure the project is being run the way the contract says it should be.
5. The people who inherit the building
Everyone in the meeting will move on to another program. The operations team will run this one for fifteen years.
The easiest decisions to make on a data center program are the ones that save capital and cost money for a long time afterward. A chiller plant specified to the lowest first cost that then runs its entire life at a worse efficiency. A maintenance strategy written for a crew the facility will never actually staff. A commissioning record complete enough to satisfy a check box and not complete enough to let an operator diagnose the plant at two in the morning.
Nobody on the program is paid to run that arithmetic except the person retained by the owner. The owner measures the project on the day it opens. The operator lives with it for a decade. An owner's agent is the only seat at the table whose job includes both.
A program rarely fails in a single dramatic moment. It fails in a sequence of small deferrals that everyone believed was someone else's call.
The thing nobody else at the table is paid to do
Each of those five groups has a legitimate interest and a set of incentives that follow from it. The contractor wants the change order. The designer wants the design kept. The program manager wants the schedule it published. The operations team wants a building that works. None of them are being dishonest — they are simply answering the question their position asks them to answer.
Holding all five at once is not a skill anyone is hired for except you. And it isn't a personality trait. It's a consequence of having been in the room often enough to know what each group hears when you say a sentence.
Which is exactly what independence buys
You cannot hold five conversations honestly if you are selling something to one of them.
If there is scope waiting for you on the other side of a question — a design to defend, a contract to award, a schedule you published — then the conversation with that party stops being a conversation and becomes a negotiation with a foregone conclusion. Independence is not a virtue in itself. It is the thing that makes the other five possible, because it means the answer costs you nothing.
That is the whole argument for retaining someone directly, and it is the reason the engagement has to be structured that way from the first day rather than arranged later. A representative who can be believed by the contractor, the designer, and the utility — as well as by you — is worth considerably more than one who can only be believed by you.
Hendrik Schoeman, PE, PMP, is a data center construction executive and independent owner's agent. He has led owner-side delivery of hyperscale campuses, 1.3 GW of utility and substation program scale, and 20+ years of mission-critical infrastructure delivery including the U.S. Navy Civil Engineer Corps, where he spent two decades administering contracts from the government side of the table.