DLR Group’s McFarlane deal puts science and tech programming closer to the architect, and it will show up first in lab and data center schedules

DLR Group has acquired McFarlane Architects, adding a science and technology-focused design shop to its platform, according to Building Design+Construction (BD+C). For enterprise owners, the headline isn’t corporate org charts. It’s where technical requirements get written, and how early the project team has to be right about power, cooling, vibration, clean construction, and commissioning.

The deal lands in a market where mission-critical and high-tech facility work is pulling design teams toward tighter integration. BD+C’s separate reporting this week argues that data center volume is changing risk allocation across designers and contractors, while the AIA/Deltek Architecture Billings Index (ABI) coverage points to softer billings in July. Put together, the signal is operational: projects with complex performance requirements are becoming the work that rewards firms with deeper in-house technical programming, and penalizes ambiguous scope boundaries.

What DLR Group is buying in practical terms: earlier technical definition

BD+C describes McFarlane as a science and technology design firm. That label matters because S&T work is heavy on decisions that become expensive once drawings are “done”: adjacencies that drive contamination control, structural stiffness that affects sensitive equipment, and MEP capacity that either supports future load growth or forces retrofits.

When that capability sits inside the prime architect, owners can push for a more coherent chain from early programming to design development to commissioning criteria. That doesn’t automatically reduce risk. It changes where it lives. Fewer handoffs can mean fewer gaps, but it can also mean owners must be more explicit about deliverables and acceptance tests, since fewer third parties are naturally checking one another.

Data center growth is forcing contract clarity around integration points

BD+C’s Aug. 20 data center piece frames the boom as a risk reshaper for designers and contractors. The practical translation for operators is that the usual “architect vs. engineer” split doesn’t map cleanly to modern mission-critical scopes. Electrical one-lines, cooling topology, controls sequences, and commissioning plans now drive business continuity as much as the floor plan does.

That shows up fastest in delivery method decisions. For owners leaning into design-build or fast-track schedules, an architect with embedded S&T expertise can bring more of the technical narrative under one roof. The procurement side of that choice is diligence: confirm which party is responsible for performance criteria, who signs off on basis-of-design assumptions, and how late changes to IT loads or redundancy targets get priced.

Soft July billings is a staffing signal, not a green light

BD+C reports that architecture firm billings “remained soft” in July, citing the AIA/Deltek Architecture Billings Index. ABI is widely used as a forward-looking read on design activity. Softness can mean more competition for near-term work and potentially more availability on calendars. It can also mean firms are managing utilization tightly, which affects who gets assigned and how long they stay.

For enterprise capital programs, ABI is less a macro trivia point and more a scheduling checkpoint. If a project’s critical path depends on high-scarcity roles, lab planners, electrical designers with mission-critical experience, commissioning authorities, the contract should name the resourcing plan. Staffing volatility becomes a delivery risk when the project relies on tacit knowledge carried by a few specialists.

Where this lands in owner playbooks: requirements, long-leads, and acceptance

The near-term impact of consolidation moves like DLR Group’s acquisition tends to show up in front-end project documents. Owners and operators will see pressure to lock more decisions earlier: basis of design, redundancy targets, equipment heat loads, and commissioning scope. That can help when the supply chain for electrical gear and cooling components is the schedule driver, because earlier definition supports earlier procurement.

It would matter most for organizations with repeatable technical programs, hospital systems expanding lab footprints, manufacturers building R&D capacity, cloud and colocation providers, and universities scaling research space, where the operating model depends on predictable turnover, uptime, and maintenance access. The shared constraint across those environments is that “late” design changes often cascade into procurement re-bids, controls rewrites, and re-commissioning.

Questions to put in the RFP before a lab or mission-critical project goes fast-track

• Which party owns the basis-of-design assumptions for IT load, redundancy, and future growth, and how will changes be governed after design development? Ask for the change-control workflow in writing.
• What is the commissioning scope, including functional performance testing, controls sequences, and integrated systems testing, and who authors each deliverable? Require a responsibility matrix that includes the controls contractor and owner’s IT team.
• How will long-lead procurement be handled for electrical and cooling equipment (switchgear, generators, UPS, chillers), and what early packages are planned? Confirm who holds vendor coordination responsibility and how submittal cycles affect the design schedule.
• If key personnel change, what is the continuity plan and what documents capture their decisions? Require named leads for S&T programming and mission-critical MEP, and specify replacement qualifications.