Owner's Representative Questions, Answered Straight

Short answer: I carry the owner's interest through a program — scope, budget, schedule, contracts, risk, and the decisions in between. In practice that's running the owner-side operating rhythm, testing what the delivery team reports, chairing the meetings where money and dates get committed, and telling you the truth about the date — including when that truth is unwelcome.

It's a role, not a task list. What it looks like week to week depends on the phase, and it shifts as the program moves from planning through buyout, construction, energization, commissioning, and turnover.

Fair question — the titles do get used interchangeably, which is exactly why owners get confused. The distinction that matters isn't the title — it's who employs the person and whose interest they're paid to protect.

An owner's project manager is usually an employee of the owner, embedded in your own organization. An owner's representative is retained from outside, and that's what makes it possible to stay independent of the delivery organization and to say an unwelcome thing without a career consequence inside the project team. A well-run program can use either. What it can't use is someone whose loyalty is ambiguous.

Happy to draw the line. A construction manager manages construction. On a CM-at-risk engagement they also hold the trade contracts and carry a commercial position on the cost of the work — which means they're one of the parties you need to be able to verify.

An owner's representative covers the whole program rather than the construction phase alone: pre-construction and design coordination, procurement and contract structure, the utility and power path, commissioning and operational readiness, and the reporting that ties them together. Where the two roles overlap on schedule and cost, that overlap is fine. Where it matters is that these two roles stay in different hands. If one party is both setting the number and checking it, you have no independent read on your own project — and that's the part worth protecting.

No, and that's deliberate. The strongest engagements make your in-house team more effective, because the representative carries the integration work that normally falls between departments — schedule against contracts, construction against commissioning, power against occupancy.

What it does replace is the assumption that a report is accurate just because it came from inside the project. Someone has to be able to test it.

The owner — and only the owner. It sounds obvious, and it's the thing that quietly goes wrong most often — usually without anyone setting out to mislead you. It's common for a firm described as an owner's representative to also hold a contract with the contractor, the designer, or the program under review. When those two interests meet, the fee usually decides, and you'd never spot it from the outside.

Ask directly, and ask for it in writing: does your firm hold, or expect to bid on, any contract with my contractor, my design team, or any subcontractor on this program? Then check the answer against the org chart — who signs their invoices, and who else that firm is billing on the same project.

The strongest form of independence is a single-purpose engagement: retained by you, working only for you, with no downstream scope waiting on the other side of the project. If the answer comes back vague, that tells you something — I'd treat it as a no.

Short answer: it's hard to make that work credibly on a CM-at-risk or design-build job, and here's why. The same party would be setting the budget it then reports against, and reviewing its own change orders. Some owners accept that because it's simpler and cheaper. It's a decision about how much verification you want, and it should be made deliberately rather than by default.

No, and the difference is worth knowing, because the two are often sold the same way. A staffing firm is paid to place a person into your program, and is paid for the placement. An owner's representative is retained to deliver an outcome and is accountable for it, with no placement revenue underneath the advice.

If the proposal is priced like a placement and the deliverable is a person rather than a result, you're buying staff, not representation. Staff can be the right answer. Just know which one you're buying.

Earlier than most people think, and here's the reason. The decisions that decide the outcome are made earliest and are cheapest to change earliest: the basis of design, the sequence, the contract structure, the delivery method, and the power strategy. That's where a good representative earns the fee.

The practical rule I'd use: bring one in before contracts are awarded. If you're past that point and something feels wrong with the date, bring one in anyway — the value shifts from shaping decisions to testing the ones already made.

No, it's not too late. What changes is the work. Mid-stream the job is to establish a baseline you can actually trust, find out which commitments are real, and rebuild the reporting so you're looking at one integrated schedule instead of several compatible-looking ones.

That's often uncomfortable, because the first honest version of the picture is usually worse than the last reported one. That isn't a reflection on you or your team — it's simply what the picture looks like once somebody tests it. It's still much cheaper to learn it early.

Honest answer: you have someone delivering, and the real question is whether you have someone verifying. A general contractor is contracted to build, and their schedule and cost reporting is the primary evidence you get about how it's going. That's a legitimate structure — thousands of projects run on it — but it means there's no independent test of the date.

The gap widens on design-build and CM-at-risk, where one party owns both the design and the construction position and your only counterweight is the internal capability you have in-house.

The other half of that question is whether an independent representative slows your job down. Independence isn't opposition — it's verification. Because I sell nothing on the other side of a question, I can be straight with your contractor, your designer and your utility, and they can take it. A representative whose default answer is no doesn't read as rigorous; they read as a cost, and by the third month the team has stopped bringing anything to them early. Decisions get documented and issued in writing, most within two business days, because a decision you're sitting on becomes your contractor's schedule problem and then yours.

Maybe not a full engagement — but probably a second opinion, and here's how to think about it. Scale changes the shape of the engagement, not the value of the second opinion. A single-building project doesn't need a full-time representative for three years. It may well need a small number of high-consequence reviews: the contract structure, the schedule logic, the power and commissioning path, and the point where the first change orders land.

Bounded advisory work exists for exactly this. It's priced to a deliverable rather than an ongoing role.

Sooner, always — and the reason is arithmetic rather than preference.

A construction contract is a clock. It starts the day it's signed and it runs to the last day of the project, and every day lost inside that clock is a calendar day of cost. Not a working day — a calendar day. Once lost time starts colliding with other activities and eating the critical path, the cost stops being linear and starts compounding: the same week that looked survivable in month two is a claim in month eight.

That's why indecision is expensive. It's not a neutral position. It's an unpriced decision that somebody else will eventually invoice you for, and delay is the one line item on a project that never gets cheaper by waiting.

Signals that say call now rather than at the next report:

• The date has held for three or more consecutive reports while the float quietly disappeared.
• Someone has started explaining the schedule instead of showing it.
• The same open item appears on the log each month with a new close date.
• Change orders are arriving after the work rather than before it.
• The utility, the authority having jurisdiction, or an equipment vendor has gone quiet.
• You are being asked to decide something whose consequences are described as "to be determined".

None of those on its own is proof a project is failing. But all of them are proof that nobody independent is testing it — which is precisely the condition that gets more expensive the longer it holds.

Fair question, and the honest answer is that there's no menu price — the fee tracks the risk being carried rather than a task list. Two projects of identical construction value can need very different levels of owner-side presence, depending on delivery method, phase coverage, complexity of the power path, and how much of the schedule is already committed.

Any published range you see is a range for a category, not a price for your program. I'd be skeptical of any proposal that gives you a number before it has understood the risk.

Here's how it usually works. Four models cover almost everything, and they behave differently:

• Percentage of construction cost — simple to compare, and it aligns the fee with the value being protected. It also grows when the budget grows, which is worth noticing.
• Monthly retainer — predictable to budget, and it rewards a long schedule. Ask what happens if the program extends by six months.
• Fixed or lump sum — best when the scope is genuinely bounded and both sides know what "done" means.
• Hourly or advisory — right for a defined decision, a second opinion, or a review that should not turn into a standing role.

A few things, and they're worth knowing up front. Duration, phases covered, how much of the work needs on-site presence, the delivery method, the number of interfaces — utility, controls, network, operations — and the level of independence required. Complexity of the power path is a big one on data center programs, and it's usually underestimated at proposal stage.

Good question — the price is only one line, and here's what I'd weigh alongside it.

• Who will actually be in your meetings — and what they have personally delivered.
• Which phases the fee covers — and which ones turn into change orders.
• Whether they have held the kind of contract they are being asked to review.
• How they will report — a single integrated schedule with named dependencies, or a weekly narrative you have to interpret.

The lowest fee on a program whose date is drifting isn't the cheapest option. It's the most expensive one, bought in installments.

Happy to answer this one, because it comes up a lot. The deciding factor isn't how long the engagement runs. It's whether you're buying an answer or a period of time.

A consultant is bought for a question: is this schedule credible, is this estimate sound, why did this fail, is this claim defensible, is this design adequate for the load. The deliverable is a finding. The engagement ends when the finding arrives, and the consultant is accountable for the quality of the analysis.

An owner's representative is bought for a stretch of time in which your interest has to be carried — pre-construction and buyout, energization, commissioning and turnover, a recovery. The deliverable is the state of the program, and the representative is accountable for it while they hold it. That includes the unglamorous part: saying no to the contractor in the room, repeatedly, for weeks.

The test I would use is this. If a perfect report arrived tomorrow, could your staff act on it without further help? If the answer is yes, buy the consultant. If it's no, the report won't survive contact with the program, and what you need is someone to carry it.

There's a real limit here, and it's worth being honest about it. Standing takes time to earn. Someone who arrives for three weeks has to establish the authority to challenge a contractor who has been on site for eighteen months, and they may not get there before the engagement ends.

That's why the sensible minimum unit is one phase, not one week. Anchor the work to a boundary everyone already recognizes — buyout, energization, commissioning and turnover — and the mandate is obvious on day one. Buy it by the week and you're buying the calendar rather than the authority.

Cost is counter-intuitive for the same reason. A consultant is usually cheaper over the same weeks because you're buying analysis. Representation costs more because you're buying presence and availability, including the hours spent in meetings where nothing appears to be produced. That's not padding. It's the product.

The expensive mistake runs both ways. A consultant brought in to solve a representation problem produces a correct report and nothing changes. An owner's representative brought in to answer one narrow technical question is an expensive way to get an opinion — and a good one will tell you to go and hire a specialist instead.

Yes, and this is a large part of what I actually do. Rates can be agreed up front and drawn down only as the project needs them, remotely or on site or a mix of the two. There's no minimum engagement.

That covers one meeting, one review, one negotiation, one phase, or a person placed inside your program for as long as the problem lasts. If you need a cost controller to walk a GMP with you, a scheduler to rebuild the logic before a recovery board, or someone across the table through a heavy negotiation, that's a defined piece of work — not a program-length commitment.

What it doesn't need to be is permanent. Most owners don't need representation every week for three years. They need it at the four or five points where the money is still moveable, and they need to be able to call someone competent for everything in between.

Yes — and there's no catch. Tell me the issue — a scope, a schedule, a bill, a solicitation, a negotiation, or a team you don't have. I'll tell you what it needs, whether I'm the right person for it, and what it would cost. If the answer is that you need someone else, I'll say so, and that costs you nothing but the call.

Less than you'd expect, and none of it has to be tidied up first. Four things make a first review actually useful:

• The contract itself — plus amendments, the schedule as most recently issued, and the current cost report or GMP.
• Whatever your team is reporting. The dashboard, the minutes, the last three monthly reports. I want the version you're being shown, not a cleaned-up set prepared for me. The gaps between those two are often where the answer is.
• The one thing that prompted the call. A date that moved, a number that doesn't feel right, a claim, a solicitation, or a conversation whose shape you didn't like.
• Thirty minutes on the phone. Most of it comes out there anyway.

If the documents are confidential or carry handling restrictions, say so before you send them and we'll agree how they travel first — the next answer covers how I handle that.

It depends what you hired me for, but on a standing engagement the shape of the first month is predictable.

• Week one — read and listen. The contract, the schedule, the cost position, and several months of meeting minutes. Conversations with your team, the designer, the contractor, and the utility. Nobody is told there's a problem, because I don't yet know that there is one.
• Week two — test it. Does the schedule logic hold? Do the commitments in the minutes exist in the contract? Is the power path real, and does the utility agree with the date on your schedule?
• Week three — the honest picture. One integrated view: what's on plan, what's drifting, who owns each open item, and what each recovery would cost. Written for you rather than for the delivery team.
• Week four — where the decisions are. The items waiting on you, ranked by what they cost to delay, each with a recommendation. Plus the reporting and escalation rhythm you'll have from then on.

On a shorter piece of work — a review, a claim, a proposal — the equivalent is the deliverable itself, in writing, with what I relied on and what I haven't seen stated plainly.

If the honest picture in week three is worse than what you've been shown, that's a finding rather than a failure. It's usually why you called.

Yes, and it's all available à la carte — a defined question and a defined answer, with no program-length commitment attached.

That includes reviewing a proposal before it goes in, working a change order through with a government agency or a commercial owner and keeping it on entitlement rather than goodwill, reading what the contracting officer is actually after rather than what the letter says on its face, and applying the Federal Acquisition Regulation to a specific situation.

The useful part of twenty years administering contracts on the government side isn't knowing that the regulation exists. It's knowing how the person on the other end of the request is likely to read it, and what has to be in front of them for them to say yes.

Here are five that do most of the work.

1. Who will sit in my meetings, and what have you personally delivered?
2. Do you hold any contract, or expect to, with my contractor or design team?
3. What have you done on this project type rather than this project size?
4. Show me a real monthly report from a past program, redacted.
5. When would you recommend against your own scope?

That last one is the most informative. Someone who can't describe a situation where they're the wrong answer has either never thought about it or won't say it.

Good question, and it's usually a list of absences rather than one loud red flag — which is exactly why it's easy to miss in the moment, and why it's worth knowing what to listen for. Expertise described as categories rather than projects. A schedule discussion that never reaches logic, float, or the utility's actual commitment. Commissioning mentioned as a phase rather than as a set of design and procurement prerequisites. No clear story about how a risk gets escalated and who decides. And a report that's a narrative rather than one integrated view.

None of those are stylistic complaints. Each one predicts a specific way the program will get into trouble.

Happy to spell it out. Five things, and I would want all of them in front of me:

• One integrated schedule across construction, commissioning, utilities, and operations — with dependencies named, not four compatible-looking charts.
• Open items with an owner and a close date for each.
• Decisions waiting on you, ranked.
• Cost position against the current budget.
• An honest date, with the specific risks that would move it.

If you can't tell from the report what would have to go wrong for the date to slip, it isn't doing its job.

Because the failure modes are specific, and mostly invisible from outside the discipline. The power path runs on a third party's schedule. Commissioning prerequisites are decided in design and procurement, long before commissioning starts. Operational turnover is a construction deliverable, not a handover conversation. A representative who hasn't delivered mission-critical infrastructure tends to discover all three at the point where they can no longer be compressed.

By treating readiness as a series of decisions rather than an outcome, and by making sure those decisions are tracked from the start: integrating systems designed to be tested together, prerequisites closed early enough to matter, and a turnover package that operations can actually accept.

On a compressed program the whole difference is one operating rhythm — one integrated schedule, escalation while it's still cheap, and an owner-side voice allowed to be accurate about the date rather than supportive of the plan.

Making sure you're tracking the utility's actual commitment rather than an internal assumption about it. Interconnection agreements, service agreements, substation scope, and medium-voltage distribution rarely fail because construction did something wrong. They fail because a milestone was reported from the submittal instead of from the utility, and the gap surfaced when it could no longer be closed.

Yes, and that's an honest answer, not a sales one. The operating discipline — one integrated schedule, early escalation, independent verification, decisions with named owners and close dates — transfers to any capital program. What doesn't transfer is the depth of domain knowledge about the specific systems. On a program I don't know well, I'll tell you that rather than learn on your schedule.

Yes. Twenty years administering contracts on the government side of the table, including NAVFAC and U.S. Navy programs — writing solicitations, developing RFPs, reviewing proposals, building and defending cost estimates, running source selection, and awarding to contractors. That work is available to you on data center and mission-critical programs of any kind.

Yes, and this is the side of the process most people don't have access to. Proposal response development, cost and price volume preparation, technical narrative input, and review against what the evaluating agency actually scores rather than what the solicitation says on its face.

Having sat on the evaluating side of that process, the difference between a compliant proposal and a competitive one is usually not the price. It's whether a reviewer scoring against the criteria can find the evidence they're looking for without interpreting for you. I know how that scoring works because I have done it.

Yes, and this is exactly the kind of work I do. Request for equitable adjustment (REA) development, time impact analysis on a schedule in dispute, delay and disruption analysis, and the entitlement narrative that has to hold together in front of a contracting officer or a board. Written to withstand a reviewer rather than to win an argument.

Both, and that's a deliberate choice. Some clients want one senior person on one problem. Others need a team for the duration and don't have the time or the background to work out what that team should be — the right number of planners, cost controllers, schedulers and project controls people, for how long, doing what.

That's a service in its own right. I'll work out what you actually need across scope, schedule and cost, write the strategy that gets you there, and then help assemble and staff the team. If the answer is a full-time scheduler for eight months, that's what gets built — and the strategy behind it stays with someone accountable to you.

No — and it's worth being plain about it. Nothing on this site, and nothing provided in an engagement, is legal, financial, tax or accounting advice. I'm not an attorney, I'm not a member of any bar, and I don't represent anyone in court or in any legal capacity. Nothing here creates an attorney–client relationship.

What I provide is experience-based: practical approaches to navigating government construction contracting, drawn from twenty years of administering those contracts on the government side, plus professional opinion and analysis of whatever the facts are. That's a consultant relationship, not a legal one.

On anything genuinely legal or financial you should consult your own independent attorney or adviser. Where a matter does need an attorney, part of the job is saying so early — and helping you work out when that line has actually been crossed, because the alternative is paying legal rates for a question that never needed them.

The honest split: for problems that don't require a lawyer or a legal team to draft something, this approach costs a fraction of legal services. Knowing which of the two you have in front of you is where the money is actually saved.

It's a professional consulting service. The deliverable is analysis and judgment: what the facts are, what the contract says, what the other side is likely to do, and what I would do in your position.

What I will not take on:

• Anything requiring a licensed attorney. If a matter is legal in nature, or is already in litigation, I can't work on it. I'm not a licensed attorney and I'm not a member of any bar.
• Work that requires an engineering seal where I am not licensed, or where the honest answer is that it needs a firm with different licensure and insurance. I am a licensed Professional Engineer, and that cuts both ways.
• Means and methods, or design authorship. How the work gets built is the contractor's to decide, defend, and stand behind — a representative who starts directing it has taken on liability you never agreed to buy. I'll review constructability and sequence all day, and I won't take the designer's pen.
• Anything where I would be the wrong person. If that's the case you'll hear it on the first call, and it costs you nothing.

Beyond those lines the limit is scope rather than category — what the problem actually needs, which is usually a narrower piece of work than people expect.

No outcome is guaranteed, and I'd rather say that up front than bury it in terms. A guarantee would tell you I'd stopped thinking — no adviser controls the utility, the market, or the other party.

What I control is the quality of the analysis and the honesty of the recommendation: the facts I was given, what I tested them against, and what I would do in your position. What nobody controls is the other party, the market, the weather, the utility, the authority having jurisdiction, or the decisions other people make.

In practice that means three things. I state what I'm relying on and what I haven't seen. Recommendations go in writing, so there's a record of what was actually advised. And I say when a matter has moved outside my lane — into legal, or into something that needs a different specialist.

The commercial terms — scope, fees, and the limits of responsibility — are set out in writing before any work starts. Where those terms and anything published on this site differ, the engagement terms govern.

Carefully, and with the arrangements agreed before anything moves rather than after. Most of what I'm asked to look at is commercially sensitive — contract terms, claims, pricing, a schedule you don't want circulating. Some of it carries handling restrictions on top of that.

• Nothing goes anywhere without your say-so. Your material isn't published, presented, discussed, or reused as a reference or an example.
• Mutual NDA before documents. Send yours, or ask me for one. It gets signed before anything confidential is transmitted.
• Your handling rules, not my assumptions. If material is export-controlled, security-sensitive, or carries a government marking, tell me the rules and I'll work to them — including declining the work if I can't meet them properly.
• Confidential material doesn't travel. It isn't shared beyond what the work requires, and where the work needs something more, you'll know before it happens rather than after.

Your name, your project and your numbers don't appear on this site or in anything I publish. It's also why the track record above is deliberately unnamed — you can't offer discretion as a service and then use your clients as the proof of it.

Based in the United States, and that's where the depth is — particularly on US government construction, where the framework (FAR, NAVFAC, the Army Corps of Engineers) is inherently domestic.

Beyond that, the work travels. I'm set up to work remotely with owners and contractors anywhere, and to come to site by arrangement for the parts that have to be done in person — a recovery board, a heavy negotiation, a pre-award review, a commissioning push. Data center and mission-critical programs are increasingly international, and I'm glad to work on one.

Two honest caveats. Where a country requires local licensure or a locally licensed firm for a particular activity, that constraint is real and I'll say so rather than work around it. And where on-site presence is needed, visas, permits and travel are simply part of the scope rather than a surprise.

Directly:

• Contact form — the contact section on this page, or the same form on any other page. Nothing is stored on your device and nothing is sent until you press Send.
• Book a call — calendly.com/navycec/new-meeting

The first conversation is free, and it's a real conversation rather than a sales call. Tell me the project, the phase, and the decision you're trying to get right — or send the one-page version if you're not yet sure there's a problem worth a call. A fair amount of what I do is telling people which of their three problems is actually the expensive one.

If I'm not the right person for it, I'll say so and point you at who is.