The Hidden Margin Leak in Small Design Firms: Unscoped Coordination Time

Fixed-fee projects feel safe until they do not. The scope is agreed, the fee is set, and then the project starts moving — and so does a category of work that was never really priced.

Selection calls with vendors. Follow-up emails on lead times. Redline cleanup after a contractor marks up the drawings. Status summaries for a client who wants a weekly update. None of these feel large on their own. Together, they can quietly consume the margin that made the project look profitable on paper.

The issue is not that coordination work is avoidable. Most of it is not. The issue is that it is invisible inside a fixed fee unless someone is tracking it.

Why Coordination Time Is Easy to Miss

Coordination work does not look like design work, but it lives inside the same project budget. It happens between the visible milestones — after the concept is approved and before the drawings are issued, or after the drawings go out and before the contractor responds.

Because it fills the gaps, it rarely gets logged. It feels like overhead. It feels like the cost of doing business. And in small firms, where the principal is often the one making the calls and writing the follow-up emails, it rarely gets questioned.

The result is a project that feels busy and productive but lands with thinner margin than expected. The work was real. The hours were real. They just were not scoped.

The Four Coordination Categories Worth Watching

Not all coordination work carries the same risk. These four categories tend to accumulate quietly in fixed-fee projects:

None of these categories is inherently out of scope. But when they grow beyond what was assumed at the time of pricing, the project absorbs the cost silently.

Here is how that growth tends to look in practice. A client selects a tile that gets discontinued mid-project. The designer sources three alternatives, sends samples, gets client feedback, confirms availability, and updates the spec. That substitution cycle — which was not in the original scope — can easily consume three to four hours across a week. On a fixed fee, those hours disappear into the project with no record and no conversation.

The same pattern shows up on the contractor side. If the drawing set has gaps or ambiguities, the contractor routes questions back through the designer. Each clarification feels small. Across a project with a less experienced contractor or a more complex scope, those clarifications can add up to a meaningful block of unscoped time.

The Simple Habit That Reveals the Problem

The fix does not require a new billing model or a complicated time-tracking system. It requires one habit: tagging coordination hours separately from design hours, even informally.

This does not mean billing every email. It means knowing, at the end of a project, how many hours went to coordination versus design. That number tells you something useful.

If a project was priced assuming ten hours of coordination and it took twenty-five, that gap is information. It might mean the scope was underestimated. It might mean the client needed more hand-holding than expected. It might mean the contractor required more support than the drawings should have required. It might mean the vendor situation was unusually complicated.

Without the tag, you cannot tell. The project just feels like it ran long.

One useful addition to this habit: note the reason when coordination hours spike. A single note — "substitution cycle, client-driven" or "contractor RFIs, drawing gap" — takes thirty seconds and makes the pattern visible across projects. After three or four projects, you will know whether your coordination load is a scoping problem, a client-type problem, or a documentation problem upstream.

When Coordination Stays Inside the Fee — and When It Should Not

Not every coordination task should be billed separately. Some coordination is part of the design relationship and should stay inside the fee. The question is whether the volume was anticipated when the project was priced.

A simple way to think about it:

The threshold is not a fixed number of hours. It is whether the coordination grew beyond what a reasonable reading of the scope would have included. When it does, the options are to absorb it, adjust the fee for the next project, or have a direct conversation with the client about what the additional work costs.

Some studios handle this by building a coordination allowance into every fixed fee and tracking against it. When the allowance is consumed, additional coordination becomes a change order conversation. Others scope coordination as a separate line item from the start, especially on larger or more complex projects. Either approach works. What does not work is absorbing the hours without knowing they are there.

You Cannot Protect Margin You Do Not Measure

The firms that stay profitable on fixed-fee work are not necessarily the ones with the highest fees. They are the ones who know where their hours go.

Coordination time is not a problem to eliminate. It is a category to understand. Once you can see it, you can price it, scope it, or have a clearer conversation about what it costs when it grows beyond what was planned.

It is also worth noting that some coordination growth is a documentation problem, not a client or contractor problem. When drawings are incomplete, specs are ambiguous, or vendor communication lacks structure, reactive coordination fills the gap. Cleaner production upstream — better-organized drawings, tighter submittals, more consistent documentation — tends to reduce the volume of coordination that lands back on the designer's desk.

A simple time-tagging habit — even a rough one — is usually enough to start. The goal is not perfect tracking. The goal is enough visibility to stop absorbing hours you never agreed to carry.

For studios looking to reduce the coordination load itself, offloading parts of the production and documentation process can help. When drawings are cleaner and vendor communication has more structure behind it, the volume of reactive coordination tends to drop. That is part of what Creo's production support is built to do — not to replace the design relationship, but to reduce the friction that turns coordination into a margin problem.

Learn more about how Creo supports design studios