The quiet drag on architectural practice is not always a lack of work. Often, it is work repeated: another meeting, another transfer between systems, another drawing revised before the decisions beneath it are settled.

What if the biggest threat to your firm's profit isn't the work you're missing, but the work you're quietly doing more than once?

When did doing things twice become part of doing business?

In architecture, repetition rarely announces itself as waste. It arrives looking like diligence. A meeting is added so no one feels left out. A spreadsheet is updated because the project-management system does not speak to the accounting platform. A drawing is developed early to keep a submission moving, even though the decisions that support it are still in motion. Each action seems reasonable on its own. Together, they consume the time firms need for design, mentoring, coordination and thoughtful judgment.

The problem is not that architectural work changes. Design is iterative by nature, and construction requires adjustment. The problem is avoidable repetition: work that must be recreated because information was incomplete, poorly sequenced or trapped somewhere the next person could not use it.

That distinction matters. Efficiency is often misunderstood as a demand for thinner drawing sets, fewer conversations or faster production. None of those outcomes is inherently better. The real opportunity is to protect necessary work by removing the unnecessary work around it.

When the same information moves through repeated meetings, revisions, and disconnected processes, the cost is rarely visible on a single timesheet.

The cost of looking busy

Most firms can describe the meetings that accumulate around a project: owner meetings, site meetings, consultant coordination sessions, contractor check-ins, internal reviews and management updates. Some are essential. Others continue because they have always been scheduled, or because attendance has become a substitute for access to information.

The cost is larger than the hour shown on the calendar. Eight people in a one-hour meeting represents eight hours of professional time, before anyone prepares, travels, takes notes or translates the discussion into actions. If half the room is there only to stay informed, the meeting is functioning as an inefficient distribution system.

Collaboration doesn't mean everyone needs to be in the room. It means everyone needs access to the right information.

That may still require a meeting, but it changes how the meeting is designed. The people needed for a decision participate. The context is available before they arrive. Decisions, responsibilities and unresolved questions leave the room in a form that others can understand without convening the same conversation again.

Effective collaboration depends on the right people participating and the right information reaching everyone else.

The lesson is sequence, not speed

More than a century ago, Ford Motor Company and its engineers reorganized automobile production at the Highland Park plant. The moving assembly line was not created from a single flash of invention. It developed through experiments with components, the subdivision of labour and the deliberate movement of work between stations. By 1913, that thinking had expanded to the automobile chassis.

Architectural practice is not an assembly line. Every site, client, program and building brings its own conditions, and professional judgment cannot be reduced to a repeating industrial task. But the underlying lesson remains useful: complex work improves when its sequence is considered deliberately.

Ford didn't ask workers to move faster. He changed how work moved between them.

That is an editorial observation, not a quotation attributed to Henry Ford. It describes the shift documented in Ford's own history and by The Henry Ford: instead of repeatedly moving workers, parts and unfinished assemblies through a stationary process, Ford's team organized tools, people and components around the order in which work needed to occur.

The automobile assembly line demonstrated the value of organizing work into a deliberate sequence. Historical Ford production photograph supplied by the author; original archive and reproduction rights should be confirmed before publication.

The comparison is not an argument for standardizing buildings. It is an argument for examining handoffs. Where does information stop? Where is it re-entered? Which decisions arrive too early, and which arrive too late? Where does the next person begin by reconstructing what the last person already knew?

Drawing before the design is ready

Consider a familiar production problem. A team begins modelling interior elevations in Revit because the next submission date is approaching. The floor plan is not fully resolved, but starting the elevations feels productive. Then a wall moves. Millwork dimensions change. Door locations shift. The reflected ceiling plan responds. Notes, tags and dimensions that were correct yesterday have to be reconsidered today.

Some of that change is unavoidable. Design develops through testing, and better ideas should not be rejected simply because a drawing has already begun. But when detailed production repeatedly outruns the decisions it depends on, iteration becomes rework.

The answer is not to wait for absolute certainty; architecture never offers it. The answer is to recognize dependencies and establish reasonable thresholds. A floor plan does not need to be perfect before an elevation begins, but the team should agree on what is stable, what remains provisional and what should not yet be detailed. That shared understanding is more valuable than a drawing percentage that gives the appearance of progress.

When detailing begins before the underlying design is resolved, the same work can be repeated through successive revisions.

Detail is not the enemy

Arguments about efficiency can become careless when they imply that architects simply draw too much. Under a stipulated-sum contract, documentation must establish scope clearly enough for contractors to price the work and for the parties to understand what has been included. Ambiguity does not disappear because the drawing set is smaller; it usually reappears later as a question, assumption, change or dispute.

Imagine that the design intent calls for a granite countertop, but the material is not identified clearly in the contract documents. One bidder carries laminate, another carries quartz, and a third includes an allowance. The design team may still expect granite, but expectation is not scope. The missing decision has not saved time. It has merely moved the work into tender clarification or construction, where it becomes more expensive and harder to resolve.

Detailed drawings matter. Specifications matter. Coordination matters. The issue is not the level of information required to deliver a building. It is the number of times that information is interpreted, transcribed, corrected and rediscovered before it reaches the people who need it.

The price between the subscriptions

Architectural firms now rely on specialized software for proposals, scheduling, drawing production, visualization, markups, construction administration, email and document management. Each tool may solve a real problem. The difficulty appears in the spaces between them.

A project number is created in one system and typed again in another. Milestones move, but the staffing plan does not. A marked-up drawing becomes an email attachment, then a task, then a meeting agenda item. Someone maintains a spreadsheet because it is the only place where information from several platforms can be seen together. The visible subscription fees are easy to calculate. The labour required to keep the systems aligned is not.

Each tool may solve an individual problem while creating additional work between systems.

This is why adding another isolated application can make a firm feel less organized even when the application itself is excellent. Every new boundary creates another handoff. Unless information remains connected across that boundary, people become the integration layer.

Half an hour becomes a year of capacity

Small inefficiencies become significant when they are repeated across a firm. Consider a deliberately simple hypothetical example: a 25-person practice in which each employee spends an average of 30 minutes a day on avoidable duplication. Across 220 working days, that amounts to 2,750 hours. At an assumed blended labour cost of $75 per hour, the annual value of the staff capacity consumed is $206,250.

A hypothetical 25-person firm losing 30 minutes per employee per day would spend 2,750 hours a year on avoidable duplication—$206,250 in staff capacity at an assumed blended labour cost of $75 per hour.

These figures are not an industry statistic. They do not represent guaranteed savings, lost profit or revenue that could automatically be recovered. Not every reclaimed hour becomes a billable hour, and no practice operates without some administrative friction. The calculation simply makes the scale of repeated time visible.

What could a firm do with even part of that capacity? It might reduce overtime before a submission. A senior architect might spend more time mentoring an intern instead of reconciling two tracking systems. A project team might complete a more considered coordination review. The practice might take on additional work without immediately adding overhead. In a difficult market, retained capacity could even help protect positions that would otherwise be vulnerable.

The financial question is therefore not only, “How much does this software cost?” It is also, “How much professional time does this process require us to spend around the software?”

Better systems protect better work

The goal is not to strip architectural practice down to the smallest possible number of actions. Redundancy can be useful when it protects life safety, quality or accountability. Independent review is not waste. Checking a critical dimension is not waste. A second professional perspective can prevent an expensive mistake.

The challenge is to distinguish verification from duplication. Verification tests the work for a reason. Duplication repeats the work because the system failed to carry it forward.

That distinction provides a practical way to review a process. If a piece of information is entered twice, ask whether both entries serve a different control. If a meeting has ten attendees, ask which decisions require each person. If a drawing is repeatedly revised, ask whether the changes reflect healthy design development or whether production began before its dependencies were understood. If staff maintain a parallel spreadsheet, ask what the primary system is failing to show.

The most effective improvements are often modest. A clearer handoff, a shared source of current information, a decision recorded with its context, or a task connected to the drawing that prompted it can remove hours of later reconstruction.

One project, carried through every phase

This is the problem Project Arc is intended to address. A project should not have to rebuild its identity as it moves from proposals into design, bids and tenders, construction administration and closeout. The participants and responsibilities will change, but the record should continue.

Connected information does not mean every person sees everything or works in exactly the same way. It means that appropriate project information can move with the work: a pursuit becoming a project, a design decision informing tender, a tender clarification remaining visible during construction, and a construction record supporting closeout.

Project Arc is still being developed, and the ambition is not to promise that software can eliminate every meeting, revision or manual task. It cannot. Architecture will remain a human practice shaped by judgment, negotiation and change. The opportunity is narrower and more useful: reduce the avoidable repetition created when project information and project processes become disconnected.

The profession does not need to move faster for the sake of speed. It needs to spend its time where professional attention creates value: resolving the design, coordinating the work, mentoring people, supporting clients and delivering buildings with care.

If you could eliminate everything your firm does twice, what would your people finally have space to do?