Who's Actually Running the Job

Picture yourself two weeks into your first job, a mid-rise apartment renovation, as a newly hired project engineer. A wall in front of you doesn't match the drawing you were handed this morning, and three different people seem to have three different answers about who actually gets to decide what happens next: the superintendent, someone from the architect's office who stopped by yesterday, and a person the owner keeps calling "our rep." Figuring out who actually has the authority to make that call, and who you're even supposed to ask, turns out to be one of the most useful things a new hire can learn, and it rarely gets explained directly. Start with the three parties who exist on almost every project, no matter how small. The owner is the person or organization paying for the project and ultimately receiving it; every decision eventually traces back to what they want and are willing to pay for. The architect designs the project and, on most traditional jobs, also administers the contract during construction, reviewing submittals, answering RFIs, and certifying that the work actually matches what was designed. And the general contractor holds the main contract to actually build it, coordinating the trades who perform the physical work. Three parties, three very different jobs, and only one of them is directly hiring the people swinging a hammer. That "administers the contract" phrase covering the architect is worth pausing on, because it surprises a lot of newcomers. The architect isn't just handing over a set of drawings and walking away; on most traditional projects, they're also acting as a kind of referee during construction, interpreting what the drawings actually mean when a question comes up. That dual role is exactly why the person from the architect's office had an opinion about your wall.

Here's the part that actually resolves the "who do I ask" question: contracts, not job titles, decide who can tell whom what to do. The owner has one contract, the prime contract, and it's with the general contractor, not with any individual subcontractor. The general contractor, in turn, signs a separate subcontract agreement with each subcontractor, one for electrical, one for drywall, one for concrete, and so on, each one written to "flow down" many of the same obligations the GC itself agreed to with the owner. That's why an owner, however frustrated, generally can't walk over to an electrical sub's foreman and start issuing directions: there's no contract between them, no privity, and no legal footing for that instruction to mean anything binding. That isn't bureaucratic caution for its own sake. If instructions could flow around the GC, changes could pile up that nobody priced, nobody tracked, and nobody's clearly responsible for once something goes wrong. Keeping direction flowing through the contract chain is what keeps one party, the GC, accountable for the whole job, instead of the owner discovering too late that six different people all thought they were helping and nobody actually owns the outcome. Most of the specific rules for how that chain is supposed to work day to day live in the general conditions, often a standard form like AIA A201, covering things like how RFIs and change orders get handled and what happens when there's a dispute. Because no single standard form fits every project perfectly, owners commonly add supplementary conditions on top, tailoring those default rules to a specific project's insurance requirements, local regulations, or payment terms. If you ever want the actual rule for a specific situation on a job, rather than what everyone assumes it is, these two documents are where it's actually written down.

Most owners aren't in the construction business full time, which is exactly the gap the Owner's Representative role exists to fill. Hired directly by the owner, and working only for the owner, an Owner's Rep sits in design and construction meetings translating technical issues into decisions the owner can actually make, and reviews change orders and pay applications from the owner's side of the table. It's a meaningfully different role from the GC or even the architect: both of those parties are ultimately managing their own contract and scope too, while an Owner's Rep has no other job on the project except protecting the owner's interests. On the paperwork side of that same chain sits the Contracts Administrator, the person who actually drafts and manages the prime contract and every subcontract underneath it, making sure the terms are consistent, insurance and bonding requirements are met, and that changes to scope or price get documented in a way that holds up if a dispute ever lands in front of a lawyer. When a subcontract quietly leaves out a term that was in the prime contract, that gap usually surfaces at the worst possible moment, mid-dispute, which is exactly what a good contracts administrator exists to prevent in the first place. One more piece worth understanding: risk doesn't just flow through the chain as instructions, it flows through as liability too, via indemnification clauses. A subcontractor typically agrees to cover claims arising from their own work, protecting the GC, who in turn protects the owner, from getting pulled into a lawsuit over something they didn't actually cause. It's the same chain of contracts doing double duty: directing the work, and assigning who's on the hook when something goes wrong.

Everything so far assumes the traditional structure: one owner, one prime contract, one GC coordinating every subcontractor underneath it. That's common, but it isn't universal. Under multiple prime contracting, the owner contracts directly with several prime contractors, a general prime, a mechanical prime, an electrical prime, instead of funneling everything through one GC. It sounds like it could save money by cutting out a layer, and sometimes it does, but it also hands the owner, or whoever they hire to coordinate, often a construction manager, the job of resolving conflicts between primes who have no contractual authority over each other. Ask a mechanical prime why they can't just tell the electrical prime to move a conduit, and the honest answer is the same one from earlier: no contract between them, no authority. Whichever structure a project uses, someone has to actually keep track of who asked what, who approved what, and which version of a drawing is current, especially once dozens of RFIs and contract changes start moving at once. That's the Document Control Specialist role: maintaining the submittal and RFI logs, distributing the current drawing revisions, and making sure nobody on site ends up building off information that's already been superseded. It's easy to overlook until the one time an outdated drawing gets used by mistake, at which point the value of that role becomes obvious to everyone on the job at once.

Go back to that new hire staring at the mismatched wall. The actual answer to "who do I ask" was never really about who seemed most confident or showed up most often. It was about the contract chain: the architect's office answers questions about what the design intends, often formally, through an RFI, the GC, through your own supervisor, decides how the work actually proceeds on site, and the owner, or their rep, gets informed and weighs in on anything that changes cost, schedule, or scope. Nobody on that list can bypass the chain and give a binding answer that isn't really theirs to give. Understanding this chain is also exactly what separates someone who's merely worked around construction from someone who actually understands how a project runs. It's why the Owner's Representative, Contracts Administrator, and Document Control Specialist careers all exist: three different jobs, all built around keeping this same structure of authority and accountability from breaking down on a real project. If any of that sounds like the kind of problem you'd enjoy untangling for a living, it's worth a serious look. If you remember only one thing from this lesson, make it this: on a construction project, who can tell whom what to do is never a matter of who's loudest or most senior-sounding on site, it's a matter of who actually has a contract with whom. Learn to trace that chain, and a huge share of the confusion that trips up newcomers simply stops being confusing.