How much of an architect's week is spent designing?

The honest answer, for most firms, is less than they'd like to admit. The rest is translation. Preparing exports for the structural consultant. Reformatting the model for the estimator's spreadsheet. Building presentation decks for the client meeting that's now three days away. Waiting for feedback that won't arrive until next week.

The drawing itself may take a day. Everything around the drawing took three weeks.

This is where the conversation about efficiency in architectural design goes wrong. The industry keeps trying to make the drawing faster. Faster CAD. Faster BIM authoring. Faster rendering. But the drawing was never the bottleneck. The bottleneck is the decision cycle: the time between a design move and the information needed to evaluate that move.

The real timeline of a design decision

Trace a single decision through a typical project.

The architect modifies a massing study. The new option looks promising. It maximizes the site, meets the program, and has an interesting relationship to the street. Now it needs to be evaluated.

• Step one: Export the model to the structural engineer. Reformat as needed. Send it over.

• Step two: While waiting for structural, prepare a cost estimate request. Export the model in a different format. Annotate assumptions. Send to the estimator.

• Step three: Prepare a client presentation. Take screenshots. Build a deck. Add annotations. Format the floor plans for print. Render a couple of views. Three days of a designer's time, minimum.

• Step four: Present to the client. The client has questions about cost. "We'll get back to you." The estimate isn't back yet.

• Step five: The structural feedback arrives. One column grid doesn't work. Revise the design. The cost estimate arrives a few days later, but it's based on the old geometry. Start over.

Total elapsed time for one design decision: three to six weeks.

The client is waiting too

This isn't only a problem for the design team. The client feels it acutely.

By the time the client sees the presentation, the design has already changed. The structural feedback forced a revision. The cost estimate prompted a scope adjustment. The presentation the client is reviewing is already outdated. They just don't know it yet.

So they give feedback on an old design. The team incorporates that feedback into the current design, which the client hasn't seen. The gap between what the client thinks is happening and what's actually happening widens with every presentation cycle.

And the time spent making those presentations is staggering. Ask any project architect how much of their week goes into formatting deliverables, building decks, and preparing materials for client meetings. The answer is usually 30% to 40% of their time. Not designing. Not solving problems. Formatting information for consumption.

This is a hidden tax on every project. The client pays for it in slower timelines. The firm pays for it in billable hours spent on non-design work. The design suffers because the best designers are spending their time in PowerPoint instead of in the model.

What "faster" should be

Faster should mean faster feedback loops.

When cost updates in real time as geometry changes, the two-week estimate becomes irrelevant. The cost implication of a design move is visible the moment the move is made. The architect doesn't need to wait for someone else to evaluate it. The evaluation is happening continuously, inside the design environment.

When the model is the presentation, the three-day deck-building exercise disappears. Stakeholders can see the live model. They can see the floor plans, the massing, the metrics, the cost data, all in the same environment, all current, all at once. No screenshots. No reformatting. No "let me prepare a package for Thursday."

When structural feedback is instant, the week-long wait evaporates. The designer modifies the floor plate and sees the structural implication immediately. No export. No handoff. No queue.

Each of these collapses a waiting period. And the waiting periods are where all the time goes.

The compounding effect

Here's what makes this so significant. Each handoff doesn't just add time. It adds sequential time.

A typical feasibility process has five or six handoffs. Structural review. Cost estimate. Energy analysis. Zoning compliance check. Client presentation. Owner feedback. Each one depends on the previous one finishing. Each one adds days or weeks.

Collapse each handoff from days to minutes, and a six-week cycle becomes a six-day cycle.

Not because anyone worked harder. Not because the CAD software got faster. Because the waiting is gone. The decision latency, the time between question and answer, shrinks from weeks to seconds.

A substantial share of rework traces back to decisions made with incomplete information during the design phase. Not bad decisions. Slow decisions. Decisions that were reasonable at the time but were made without the structural, cost, or compliance data that would have changed them.

What this looks like when the cycle collapses

Arcol collapses the decision cycle by embedding cost, structural, and compliance intelligence directly into the design model.

Modify the massing: cost per square foot updates. Adjust the floor plate: structural feedback is immediate. Change the building height: zoning compliance recalculates. The information the designer needs to evaluate a decision is available at the moment the decision is being made.

And the model itself is the presentation. Arcol's Boards feature lets teams present live design data to stakeholders without exporting, reformatting, or building a deck. The client sees the current design, with current data, in real time. Not a snapshot from three weeks ago.

This is Connected Constructible Design. The design, the data, and the presentation are one environment. The translation steps that consumed 70% of the project timeline don't exist.

The firms that feel slow aren't slow at designing

The most talented designers in the industry are spending their weeks waiting for information, formatting deliverables, and reconciling feedback on outdated presentations. The design itself happens in bursts between the bottlenecks.

Decision speed is not about the people. It's about whether the environment gives them the information they need, when they need it, in the context where they're working. When the answer to every design question requires an export, a handoff, and a waiting period, even the best team moves slowly.

The firms that will pull ahead are the ones that recognize the bottleneck for what it is. Not drawing speed. Decision speed. And decision speed depends on the environment, not the effort.

Rethinking that environment is a significant undertaking. It means changing tools, changing workflows, and changing habits built over decades. But the math is clear. When the decision cycle compresses from weeks to minutes, every other metric follows: more iterations explored, fewer surprises downstream, faster timelines, and clients who are looking at the current design instead of a three-week-old presentation.

The drawing was never the slow part. The deciding was. And that's a problem the industry can actually solve.