Seven Months, One Building: What Design-Build Is Worth On A Landmarked Pre-War Renovation

TABLE OF CONTENTS

• An Experiment Nobody Set Out to Run
• The Thread: Anatomy of a Seven-Month Coordination Breakdown
• What Actually Went Wrong
• The Same Window, Side by Side
• How Design-Build Changes The Conversation
• One Team, Many Specialists
• What The Delay Costs An Owner
• Questions Worth Asking Before You Assemble a Team
• The Part That Stays With Us
• FAQs About Working With A Design-Build Firm For Your NYC Renovation

This is the story of two apartment renovations in one building. One was ours. The other, a floor above, belonged to a neighbor who hired a separate team and, over seven months, watched a finished ceiling end up marked for demolition without anyone able to say quite how it got there.

Same pre-war building, same board, same calendar. Both projects leaned on a quiet assumption that someone was minding the details. A consultant figured the architect was filing the plans. The architect waited on the engineer. The engineer waited on a drawing that never came. Everyone stayed busy, the calendar kept turning, and the ceiling came down.

‍

‍

We had a rare seat for the neighbor's renovation, a floor above, and watching it unravel reminded us how renovation schedules rarely come apart at a single dramatic moment. They come apart in the small spaces between scopes. Here is where those spaces opened, and what a single accountable team does differently.

‍

‍

[#1]An Experiment Nobody Set Out to Run[#1]

Renovation comparisons are usually unfair. No two projects share a building, a board, an era of infrastructure, and a scope at the same time, so a claim that one delivery model outperforms another tends to rest on assertion rather than evidence. Occasionally the variables cooperate.

Gallery KBNY was engaged for a full renovation of an apartment in a landmarked pre-war building in Lower Manhattan. The apartment directly above was under renovation on the identical calendar and in the same building line, before one board, within a single Landmarks jurisdiction, governed by matching alteration agreements, and staffed by an entirely separate team. Building conditions and regulatory path were identical on both sides. Over seven months the two projects separated by a wide margin, for reasons that had little to do with the quality of anyone's design work.

How We Ended Up Inside Another Team's Process

Our client wanted central air. The building had spent years declining condenser placements, and the objections arrived in a predictable order that began with the facade, moved to the roof, invoked precedent, and closed on the prospect of every shareholder asking for the same accommodation.

While working the approval, we learned that the unit above was stuck on the identical question with its own roster of consultants. Two applications pressing the same institutional resistance on separate tracks handed the building an easy posture: treat each as an isolated request and defer both. We proposed the obvious remedy. The two owners aligned their applications, coordinated the engineering behind a single roof placement, and presented one technical answer in place of two competing favors. That reframing broke the deadlock, and approval came through for both units (a story for another time and a different blog).

The byproduct was months of our team copied on the neighbor's internal correspondence: the architect of record, the mechanical and fire-protection engineer, the expediter, the general contractor, the sprinkler subcontractor, and the owner. We watched a coordination problem develop in real time, from the first question to the moment finished ceilings had to come down.

‍

‍

[#2]The Thread: Anatomy of a Seven-Month Coordination Breakdown[#2]

The correspondence below comes from the project record. Names, email addresses, firm identities, phone numbers, the building address, and the unit number have been redacted.

‍

‍

The architect's project manager writes to the mechanical engineer with two questions ahead of a final sprinkler inspection: whether a 39-square-foot bathroom requires a head, and whether the in-ceiling air handlers need a second drip pan. The engineer answers that afternoon. Dwelling-unit bathrooms under 55 square feet are exempt, and the Department of Buildings requires one drip pan beneath each unit, with any pan internal to the equipment disregarded. A colleague confirms the threshold the following Monday. One clean exchange, resolved inside a business day.

‍

‍

Ten weeks later, the sprinkler subcontractor wants confirmation on whether heads can be omitted in two small closets. The engineer answers with the code thresholds, heads required in closets above 12 square feet and omission permitted below that in non-combustible construction, and adds an assumption in passing: revised architectural drawings will be needed to update the engineering set for a Post Approval Amendment. The architect replies that the condenser location remains under negotiation with the board, so mechanical items may still change.

An assumption about who will produce the revised drawings sits in the engineer's reply. The architect's response lands on a separate subject, and the task goes unassigned.

The thread then goes quiet for fourteen weeks.

‍

‍

Building approval for the roof condenser lands. The architect asks the engineer to prepare a sprinkler PAA matching the contractor's as-built drawings, attaches the construction plan and CAD backgrounds, and asks how the engineer would like to bill for the work.

Approval follows fourteen weeks of silence. The request to prepare the amendment opens on scope and closes on billing.

‍

‍

The engineer reviews the markups and concludes the pipe modifications are minor enough to skip a PAA. He also flags that several heads marked for elimination are in fact required, including one in a space that houses mechanical equipment. Two hours later the architect responds that the expediter disagrees and considers the amendment necessary.

Within two hours, two consultants on one project reach opposite conclusions about whether a filing is required, and neither holds authority over the other.

‍

‍

The engineer learns for the first time that updated reflected ceiling plans exist and asks for the CAD. The architect sends a download link with an apology that the file is messy after so long a project. By mid-afternoon the engineer has reviewed it and reports new soffits, several ceiling heights in areas his drawings showed as one flat plane, and a relocated laundry room. His conclusion: the approved sprinkler layout no longer works and a full redesign is required to comply with NFPA 13, which also means the contractor's as-built cannot be accurate.

Six months after installation, the engineer opens the current ceiling plan for the first time and finds a building that no longer matches his stamped design.

‍

‍

The architect's project manager explains that he inherited the project the previous December and had understood the living-room ceiling to have always carried varying heights. He observes that the ceiling changes should have reached the engineering team when they were made.

Project history that lived in one person's memory, on a job that changed hands mid-course.

‍

‍

The engineer confirms the changes are not minor and that additional heads may be needed at the exterior soffit. A site meeting to review conditions in person is the architect's proposal. Eyeballing distances will not yield reliable measurements, the engineer counters, and he asks for the sprinkler contractor's shop drawings. The only set in the architect's files appears not to be drawn to scale.

One party wants to solve it in the apartment. The other holds out for documentation that was never produced. Both positions hold up, and a month passes.

‍

‍

The architect sends the current reflected ceiling plan with head locations marked from the foreman's recollection, whose account holds that the only deviation was rerouting branch lines around obstructions. The engineer replies in thirteen minutes: heads will need to be added and relocated in several places, and the original layout could not have been followed if the floor plan changed. From there the exchange turns toward fault. The architect calls it unfortunate that the engineering team lacked the accurate ceiling layout, and the engineer answers that shop drawings submitted per the contract documents would have surfaced the discrepancy before anything was installed.

‍

‍

The architect states the problem plainly: the sprinkler system is already in. The engineer's corrected layout works for the space, though building it means tearing out finished drop ceiling and rerouting branch piping. Protecting below the exterior soffit from the interior side is impossible, the engineer confirms, so ceilings will have to open regardless. He raises cost allocation, taking the position that the contractor installed without approved shop drawings and should absorb the correction.

Finished ceilings have to come down, and the conversation moves to which contract absorbs the cost.

Nineteen days pass between the engineer's markup and the architect's next round of questions.

‍

‍

Four exchanges over three days, one of them spent entirely on an email sent without its attachment.

‍

‍

The engineer returns a layout and asks that the contractor review and confirm the work will be installed as drawn before the amendment is filed.

Seven months in, the amendment still waits on a confirmation from a contractor who has already built the work once.

Seven months after the first email, the PAA sits unfiled and the ceilings still have to open, with no party yet agreed on who pays for the correction.

‍

‍

[#3]What Actually Went Wrong[#3]

It's tempting to go looking for the one person who dropped the ball. But that is not really what happened here. Everyone did the job their contract asked them to do. The problem is that the work fell into the gaps between those jobs, where it was nobody's to catch.

‍

‍

How The Coordination Broke Down

The Submittal Loop Stayed Open

The sprinkler subcontractor installed a design set that no longer described the ceiling. Shop drawings, which exist precisely to catch that condition before pipe goes in, were never produced for review, and every party in the chain assumed someone else owned that step.

A Design Change Never Reached the Engineer

Soffits went in and ceiling heights changed. The engineer who had stamped the sprinkler layout found out roughly six months after installation, and only because an unrelated amendment forced the current drawings open.

Institutional Memory Left With A Person

The architect's project manager took over in December, midway through a multi-year design and approval process(also a story for another time and a different blog), and the reason for the ceiling configuration lived nowhere he could retrieve it.

‍

‍

How The Decisions Stalled

Two Consultants Read Filing Strategy Differently

The engineer treated the situation as needing no amendment, while the expediter considered one necessary. With neither holding authority over the other, the question was resolved by deferral.

Every Round of Coordination Reopened a Fee Conversation

The request to prepare the amendment arrived alongside a question about billing, so work that would sit inside a single team turned into a scoping negotiation between firms.

The Site Walk Never Happened

The architect wanted to solve it in the field, while the engineer held that a visit would not produce measurable data and that documentation should come from the contractor. Both positions were defensible, and the result was a month of drawings passed back and forth in place of an hour in the apartment. Each professional did precisely what his agreement required. The difficulty lived in the space between those agreements, where no one was paid to look.

‍

‍

[#4]The Same Window, Side by Side[#4]

‍

[#5]How Design-Build Changes The Conversation[#5]

Under a fragmented model, a common project exchange sounds like this:

• "Did the engineer submit the plans?"
• "I thought the architect was incorporating them."
• "Is the expediter filing this as an amendment?"
• "We were told the mechanical consultant was handling it."
• "Should we wait for the other application?"
• "Can the contractor confirm what is being installed?"

Every question generates another email, another handoff, and another opening for the project to pause. 

Under design-build, the same moment reads as a single directive: building approval is in hand, so confirm the filing path, coordinate the architectural and mechanical sets, respond to agency comments, and prepare the construction team for permitting. The individual tasks remain. Someone still produces the architectural drawings, completes the mechanical design, prepares the applications, answers agency objections, and installs the system. Those tasks now run as one sequence held by one accountable team.

That accountability is what closes the specific gaps this project exposed.

Field Changes Have One Destination

When a ceiling height changes, the person who decided it and the person who drew the sprinkler layout answer to the same project record, so a soffit cannot sit in one set of drawings and stay absent from another for six months.

Submittal Review Has An Owner

Shop drawings get reviewed because a single party carries the consequence of skipping them, and no interval goes to determining whose fee covers the review.

Filings Are Prepared By The People Carrying Construction Responsibility

The party signing the application also owns what happens when it meets the field, which removes an entire category of amendment.

Disagreements Reach a Decision

A question such as whether an amendment is required goes to someone with authority over both the filing strategy and the schedule.

Cost Allocation Stays Quiet

With design, coordination, and installation under one contract, there is no productive argument about which firm absorbs a correction. Across our portfolio, more than 70% of projects close with zero change orders, and the remainder land under 5% overage, figures that follow directly from gaps closing before they can open.

The pre-construction phase of our comprehensive design-build process runs fifteen defined steps and usually takes eight to twelve weeks. It moves quickly because none of those weeks go to establishing whose job something is.

‍

‍

[#6]One Team, Many Specialists[#6]

Design-build sometimes gets read as a way to do without specialists. A well-run design-build project depends on them. Architects handle architecture, engineers design the mechanical systems, expediters carry agency procedure, project managers hold the schedule and the decisions, and the contractor runs execution. The value comes from one organization owning how all of that fits together. Integration connects expertise and puts it on a single track.

‍

‍

[#7]What The Delay Costs An Owner[#7]

Time in a New York City renovation converts into money along several channels at once. An owner carrying rent alongside maintenance or common charges pays for every additional month. In this case the correction also carries direct construction cost: opening finished ceilings, rerouting branch piping, and refinishing work that was already complete and paid for. Contractor pricing has a shelf life, and a set that stalls long enough gets re-bid at current numbers rather than the numbers that justified the budget. 

Board composition turns over, and approval momentum is perishable. Buildings run capital projects on fixed windows, so a roofing or facade program that opens while an approval is unresolved can close access for a full season. Consultant fees, meanwhile, accrue per exchange whether or not the exchange produced a decision, and a thread that runs seven months to an unfiled amendment has been billable throughout.

‍

‍

A lower professional fee at the outset buys a smaller invoice on day one. The final project cost depends far more on how cleanly the work moves from design to permit to installation.

‍

‍

[#8]Questions Worth Asking Before Assembling A Team[#8]

If you are weighing how to structure a renovation in a co-op or condo, the useful questions are about accountability rather than credentials.

• Who reviews shop drawings before the trade installs, and what happens if that review never occurs?
• When a design change is made in the field, who is responsible for pushing it to every consultant whose work depends on it?
• Who is the applicant of record, and does that same party carry responsibility for building the work?
• When two consultants disagree on whether a filing is required, who decides?
• If a coordination failure produces rework, whose contract absorbs it?
• What happens to the schedule the first time the answer is "that falls outside my scope"?

The final question carries the most weight. Inside a fragmented team, "that falls outside my scope" is an accurate and costly sentence. Under a design-build structure, it has nowhere to land.

[#9]The Part That Stays With Us[#9]

Two owners in one building wanted the same result, presented to one cautious board, and hired credentialed professionals on both sides. One of them is entering permit phase. The other is scheduling demolition of a ceiling that was finished last year, while three firms discuss who should pay for it. Design-build describes where responsibility sits, and in a landmarked pre-war building in front of a cautious board, that turns out to govern nearly everything else.

‍

‍

[#10]Frequently Asked Questions About Working With A Design-Build Firm For Your NYC Renovation[#10]

Does a single design-build contract weaken competitive pricing on the construction side?

Price tension is preserved through the pre-construction phase rather than through a lump-sum bid war after drawings are complete. Trade scopes are competitively bid to qualified subcontractors, the numbers are presented in an open-book format, and the structure is typically a guaranteed maximum price with shared savings. The owner sees the subcontractor quotes behind each line, so the discipline that a hard bid is meant to create is applied earlier, when the design can still respond to it.

In a landmarked building, what actually governs whether a rooftop condenser is approvable?

The controlling test is visibility from the public right of way, assessed against the significance of the facade and roofline. Equipment set back behind a parapet or screened out of sightlines can often clear at the staff level, while anything readable from the street tends to draw a full Commission review or a request for relocation. Existing non-compliant conditions on the roof complicate the picture, since a new placement that enlarges a visible condition is harder to defend than one that resolves into an already-approved zone.

When does a field change force a Post Approval Amendment rather than folding into the existing filing?

A PAA is triggered when the built condition departs from the approved plans in a way that affects code compliance, egress, mechanical layout, or anything an examiner relied on, which is exactly what a changed ceiling plane and relocated heads produce. Minor pipe adjustments that hold the approved design intent can sometimes be reconciled at inspection, and the judgment call on which path applies is precisely the kind of question that benefits from a single party holding both the filing and the construction risk.

For a complex pre-war alteration, does professional certification serve the owner better than standard plan examination?

Professional certification compresses the schedule by allowing the applicant of record to self-certify compliance, which is attractive on a project fighting a long timeline, though it carries audit exposure and places the full weight of accuracy on the certifying professional. Standard plan examination adds calendar time but puts a Department examiner between the drawings and the permit. The right choice depends on the filing's complexity and on how much confidence there is that the drawings match what will actually be built, which again points back to whether design and construction are coordinated under one roof.

With the architect and the builder under one firm, who preserves the owner's advocate role?

Single accountability and independent judgment coexist when the design-build firm carries professional obligations in its own name and reports transparently on cost, schedule, and code exposure. The check that a separately retained architect is meant to provide comes instead from open-book pricing, a defined pre-construction scope the owner approves before construction commits, and a contract that assigns rework and correction cost to the party that owns coordination. The owner keeps the ability to bring in independent review at any milestone, and the integrated structure removes the incentive for one firm to point at another when a condition surfaces.

‍