The site photo arrives while the electrician is waiting. The specified nightstand will hide one outlet unless the electrician moves it. The local project lead can see the problem, the trade is ready, and the principal designer is between meetings in another city.
The electrician needs one person to own that call.
Remote projects slow down when the people on-site have to ask about every adjustment. They become risky when local authority extends to a choice the principal would have made differently. Assign authority by asking what happens if the call is wrong. Use that consequence to decide who can respond, who needs to know, and when trades should pause for approval.
A recent Business of Home roundup shows why this matters. Seven designers describe local partners, responsibility matrices, scheduled visits, and detailed documentation as routine parts of remote work. The roundup explains who is involved and how they stay connected. It leaves one practical question open: what can each person decide when something changes?
Give every decision one of three routes
A list of responsibilities leaves a local partner exposed. A trade may propose a substitution, discover an obstruction, or need an answer before the principal can review the full context. “Coordinate the trades” gives that person a task without enough authority to perform it.
Use three routes:
| Route | What happens | Suitable decisions |
|---|---|---|
| Local call | The named site lead decides and records the outcome. | Reversible adjustments inside an approved detail, with negligible budget and schedule effect. |
| Notify | The site lead chooses within an agreed boundary and alerts the principal for visibility. | Choices that affect sequencing, use a defined allowance, or alter a detail the principal should see before the next milestone. |
| Stop for approval | Work pauses on that item until the principal decides. | Irreversible, expensive, client-visible, contract-changing, or design-defining choices. |
The middle route is easy to miss. Without it, studios tend to choose between asking permission for everything and hearing about important changes after they have happened. Notification lets the team continue while the principal still has time to intervene before the next connected decision.
Test the consequence of each decision
A studio can write a long list of choices reserved for the principal and still miss the one that matters. Projects create new combinations. A familiar material appears in an unfamiliar location. A small dimension change affects custom millwork. A low-cost substitution alters the color temperature across a room.
A five-test framework covers the new combinations that appear during a project.
Check whether it can be reversed
Ask what it would take to undo the decision after the next trade acts on it. Moving a loose accessory is easy. Moving a junction box after the wall is closed is a different class of choice. A decision belongs higher up the route when the next step turns it into demolition, remaking, or a visible patch.
Count the full cost
Set a project-specific allowance for local decisions before work begins. The number should account for the contract, contingency, and the client’s approval rights. Cost includes the price of the choice and the labor it could add elsewhere. A modest electrical adjustment can become expensive when it changes millwork, lighting control, and installation.
Protect the client-approved promise
Some details matter because the client was promised them plainly. A locally sensible substitute can still break the presentation the client approved. Mark those promises in the drawing set and procurement schedule so the site team can recognize them without reconstructing every client conversation.
Identify the choices that define the room
The principal should define the few elements that establish the room’s point of view. They may be the stone, a sight line, a custom profile, the lighting composition, or the relationship between two materials. Price alone will not identify them. A cheap change can flatten the entire idea.
Keep urgent decisions with their approved owner
Urgency changes the response route, though it never lowers the consequence. Give every escalation a response window and a fallback. The fallback may be to continue unrelated work, protect the area, or reschedule one trade. Keep irreversible calls with their approved owner even when a contractor is waiting.
When a contractor is waiting, the approved owner still decides.
Let the highest consequence decide
A decision can look local under four tests and still require approval under the fifth. Use the highest result.
Suppose the specified stone arrives with damage. The supplier has an available alternative, and accepting it would protect the installation date. The substitute fits the allowance and can arrive quickly. It still changes a surface the client approved and one of the materials the principal identified as central to the design direction. That puts it on the stop route.
Now take the outlet behind the nightstand. The local lead has the approved furniture plan, the wall remains open, and the revised position stays within the electrical intent. The move has negligible cost, preserves the client-approved layout, and prevents a usability problem. That can be a local call if the kickoff rules grant that authority.
A third issue appears during installation: the workroom needs to adjust an unseen fastening detail inside a window treatment. It preserves the approved appearance and uses the agreed allowance, though it changes the installation sequence. That is a notify decision. The local lead can keep the work moving and alert the principal before the room’s next milestone.
All three examples concern execution on-site. The studio assigns different owners because the cost of getting each one wrong is different.
Set the rules before anyone on-site needs an answer
Build the escalation page during kickoff, when the principal, project manager, and local lead can discuss awkward cases without a trade waiting nearby.
For each route, name:
- the person authorized to decide;
- the project’s cost or allowance boundary;
- the client promises and design-defining elements;
- the response window for the principal;
- the fallback when that window expires; and
- the evidence required with an escalation, such as a marked-up photo, drawing reference, options, cost, and schedule effect.
Keep the page short enough to use from a phone on-site. The supporting project record can remain detailed elsewhere. This page exists to answer a narrower question: where does this decision go now?
Use one sentence: “This choice is irreversible after drywall, changes the approved elevation, and needs an answer before the electrician leaves.” A good escalation names consequence, evidence, and timing.
Keep accountability with the principal
The principal remains accountable after delegating a route. She defines the boundaries, makes the reserved decisions, and checks completed decisions against the design intent. Local authority works because it is bounded and visible.
Review the first few decisions together. If routine calls keep rising to the principal, the local boundary may be too narrow or the documentation may be incomplete. If changes arrive as surprises, the notify route needs a lower threshold. If the same category repeatedly stops work, decide it earlier in the next project.
A working system is easy to recognize on-site. The local lead can answer the outlet question, the team pauses the stone decision for the principal, and every trade knows which is which before picking up a tool.
