Independent Owner's Agent Representation

What "independent" means here

On most programs the owner is represented at the table by people who are also being paid to deliver something else. The general contractor wants the change order. The designer wants the design kept. The program manager wants the schedule it published. None of them are lying to you — they are simply answering a different question than the one you are asking.

Independent owner's agent representation means the person in the room is retained by the owner and owes the owner a straight answer. No delivery incentive, no downstream scope, no relationship to protect with the parties being measured. That is the whole value, and it only holds if the engagement is structured that way from the start.

Independent does not mean adversarial. The reason I can be straight with your contractor, your designer, and your utility is that the answer costs me nothing — there is no scope waiting for me on the other side of the question. That is what makes independence useful rather than merely clean. A representative the rest of the table cannot believe is not protecting the owner; they are slowing the job down and handing you an argument you did not ask for. Twenty years on the government side taught me what happens when a reviewer's default answer is no. The submittals still got approved — they simply took longer, cost more to process, and by the third month the contractor had stopped bringing anything to the table early. A representative whose instinct is resistance does not read as rigorous. They read as a cost.

Where an owner's agent earns its keep

These are the points on a data center or mission-critical program where money, schedule, and credibility are actually decided — and where an owner who is relying on the delivery team for its own report tends to learn about the problem too late.

1. Scope and constructability, before the buyout

Whether the sequence is buildable, whether the power path is real, and whether the basis of design survives contact with the site. Catching this before contracts are awarded costs a review. Catching it afterward costs a claim.

2. Power and utility coordination

Service agreements, substation scope, medium-voltage distribution, long-lead equipment, and the utility's actual schedule rather than the one in the submittal. Energization drives Day-1, and it is almost never a construction problem — it is a coordination problem.

3. Contractor and consultant accountability

Clear acceptance criteria, GMP and change review, and the uncomfortable conversation that happens at a point where it can still change the outcome — not in a post-mortem.

4. Commissioning and operational readiness

Commissioning readiness is a design, procurement, and turnover discipline, not a phase at the end. An owner's agent keeps the end state visible from the beginning, so turnover does not become a negotiation.

5. Independent reporting to ownership and lenders

One honest dashboard: what is on plan, what is drifting, what it will cost to recover, and what decision belongs to the owner. Written for an executive who has three other things on their desk.

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.

Year seven, not the ribbon cutting

The easiest decisions to make on a data center program are the ones that save capital and cost money for the next fifteen years. A chiller plant specified to the lowest first cost, that then runs its entire life at a worse efficiency — the saving appears once, in a buyout, and the penalty arrives every month of every year after it. A maintenance strategy that assumes 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 project is paid to run that arithmetic except the person retained by the owner. An owner measures a program 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 — which is why the commissioning and turnover discipline described above matters well before the turnover date appears on a schedule.

Strict about the contract. Practical about the method.

These are not two positions to alternate between — they are the same position, applied honestly. Where the contract matters, I will cite the paragraph and have a real conversation about it. Where a thing is close enough, it is close enough, and saying so is part of the job rather than a lapse in rigor. A representative who is strict about everything is not more rigorous than one who is strict about what counts. They are just slower, and eventually they are ignored.

The clock is part of the deliverable. A decision the owner is sitting on does not sit still. It becomes the contractor's schedule problem, then the subcontractor's, then a variance the owner pays for. So decisions are documented and issued in writing — most within two business days. Where a decision genuinely needs longer than that, you get the date it will be made rather than silence.

How an engagement is shaped

The engagement follows the project, not a fixed product. Three shapes cover most of what owners actually need:

Using me for one issue, or one short stretch

You do not have to retain me for a program to use me on one. Rates can be agreed up front and drawn down only as the project needs them — remote, on site, or a mix of the two. There is no minimum engagement, and no requirement to take a program-length commitment to get a senior person onto one problem.

That covers a single meeting, a review, a negotiation, a phase, or a person placed on your team 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 to sit across the table through a heavy negotiation, that is available as a defined piece of work.

There is also an arithmetic argument for calling early rather than late. On a construction contract the clock starts the day it is signed and runs to the last day of the project. Every day lost is a calendar day of cost — and because it is a calendar, it does not stop. Once activities begin to collide and the loss starts eating the critical path, the same week that looked survivable in month two is a claim in month eight. Delay is the one cost on a project that never gets cheaper by waiting. Indecision is not a neutral position; it is an unpriced decision that someone else will eventually invoice you for.

Discrete services

Beyond standing representation, these are the specific pieces of work I am retained to do — on government work and on commercial data center programs alike.

Schedule and delay analysis

Independent schedule verification and logic review, time impact analysis on a schedule in dispute, delay and disruption analysis, and recovery planning a program can actually execute. Written to withstand a reviewer rather than to win an argument.

Cost, commercial and claims

Cost estimate review and validation, guaranteed maximum price (GMP) walkthrough, change order and claim review, request for equitable adjustment (REA) development, and heavy negotiation support and strategy — including someone standing across the table when the number matters and the room is not friendly.

Proposals and source selection

Response development against a government project RFP, cost and price volume preparation, and proposal review against what the evaluating agency actually scores rather than what the solicitation says on its face. On the other side of the same process: vendor and contractor selection, evaluation criteria design, and award recommendation support.

Team assembly and delivery strategy

Working out what you actually need across scope, schedule and cost, writing the strategy that gets you there, and then assembling and staffing the team for the duration — planners, cost controllers, schedulers, project controls. If the answer is a full-time scheduler for eight months, that is what gets built, and the strategy behind it stays with someone accountable to you.

Contract, change and federal acquisition support

À la carte support when a contract question needs an answer rather than a program. Reviewing a proposal before it goes in. Working a change order through with a government agency, or with a commercial owner, and keeping it on entitlement rather than on goodwill. Reading what the contracting officer is actually after rather than what the letter says on its face. Applying the Federal Acquisition Regulation to a specific situation and telling you what the position actually is.

Twenty years administering contracts on the government side means the answer comes from having been the person sitting on the other end of the request — which is usually the difference between an argument and a resolution.

Federal and government contracting

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 experience is available to owners on data center and mission-critical programs of any kind — and to the teams responding to a federal solicitation who need to know what the evaluating office is looking for before they start writing.

Both directions in one person is unusual. Most people who have run source selection have not delivered hyperscale data centers, and most data center executives have never sat inside a government evaluation.

What I do not do

A short list matters more than a long one here, because the failure mode of an owner's agent is claiming more than one person can hold. I do not design — I review constructability and sequence, and I do not take the designer's pen. I do not own means and methods: how the work gets built is the contractor's to decide, defend, and stand behind, and a representative who starts directing it has taken on liability the owner never agreed to buy. I do not provide legal advice, and I do not represent anyone in a legal capacity. I do not take on matters already in litigation.

Outside 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. Where the honest answer is that a matter needs a firm with different licensure, different insurance, or a specialist I am not, you will hear it on the first call, and it costs you nothing.

Background

Professional Engineer, PMP, and U.S. Navy Civil Engineer Corps veteran with 20+ years leading the planning, delivery, and integration of complex mission-critical infrastructure, including owner-side delivery of hyperscale data center campuses, 1.36 GW of utility and substation program scale, 1M+ square feet of hyperscale building scale delivered, and 80+ federal and commercial projects.