TL;DR
- An architectural technology consultant should be engaged as a design-side professional – vendor-neutral, producing construction documents, and involved from schematic design through construction administration.
- The most important evaluation criteria are vendor neutrality, design-phase engagement model, scope of technology systems covered, and ability to coordinate with the full design team.
- Red flags include consultants who also sell or install the systems they specify, consultants who engage only after CDs are issued, and consultants who can't produce a complete Division 27 and Division 28 specification package.
- The questions architects and principals ask during evaluation determine whether they get a design consultant or a vendor in disguise.
- Technology design services should be scoped to match the project, from a single system type on a small project to a full Division 27 and Division 28 engagement on a complex campus or institutional building.
Why Should Architects Evaluate Technology Design Services?
Not every party that calls themselves an architectural technology consultant operates as a design professional. Some are integrators who have expanded their sales process to include design services. Some are manufacturers' representatives who specify products they distribute. Some are IT contractors who handle technology during construction but aren't equipped to produce coordinated design documents during schematic design and design development.
Getting this distinction wrong has consequences. A consultant who isn't truly vendor-neutral produces specs that favor their business relationships rather than the project's independent requirements, while a consultant who can't produce a complete construction document package leaves gaps in the bid set that contractors fill with assumptions.
Because architects don't work in technology day to day, defaulting to technology design firms that boast certifications can feel like a safe shortcut – but many of those certifications are built around idealized conditions that have little bearing on a live design-through-construction project. There’s a big difference between a consultant who knows technology and one who has lived and breathed a project from schematic design through closeout, who knows what tends to go wrong and heads it off before it becomes a problem.
In this blog, we'll explain why evaluating technology design services matters, the criteria that separate a design consultant from a vendor in disguise, and the questions to ask before assembling your next project team.
How To Evaluate Technology Design Firms: Technology Consultant Evaluation Criteria
What actually separates a design-side technology consultant from a vendor who has added "design" to their sales language? Use the criteria below to find the right fit for your technology design service needs before signing an agreement rather than during construction.
Vendor Neutrality
Vendor neutrality is the most important criterion for evaluating an architectural technology consultant. A vendor-neutral consultant has no financial relationship with any manufacturer or integrator, so their specs describe performance requirements that multiple qualified contractors can meet.
Make sure to ask if the consultant receives any compensation, referral fees, or preferred pricing from manufacturers or integrators. The answer should be unambiguous: a truly vendor-neutral consultant has no such relationships and can say so clearly.
At TMC, we don’t sell, install, resell, or commission the systems our consultants specify, and we hold no vendor relationships that pay us to put a given product in a specification. That independence means every recommendation carries an explanation of why it was made and what each design decision costs or saves, so the design team and owner can weigh options on the merits rather than on what a vendor happens to carry.
Design-Phase Engagement
A qualified architectural technology consultant engages during schematic design and runs through construction administration. If a consultant typically engages only at construction documents or later, they're operating in a reactive mode – identifying coordination problems rather than preventing them.
Ask when the consultant typically begins their engagement on a project and what their deliverables are at each design phase. A design-phase-focused consultant should be able to describe specific SD, DD, and CD deliverables: a technology program at SD, coordination drawings during DD, and vendor-neutral specifications at CDs.
Construction Document Capability
The primary deliverable of an architectural technology consultant is a set of Division 27 and Division 28 drawings and specifications that become part of the bid set. A consultant who can't produce complete construction documents – or who produces specs that are proprietary rather than performance-based – isn't operating as a design professional.
Ask to see examples of completed Division 27 and Division 28 specifications from past projects, and look for:
- Performance-based language
- Coordination with MEP drawings
- Completeness of scope coverage
If the specifications read like a product catalog rather than a performance spec, that's a red flag.
Systems Coverage
The scope of systems that a technology consultant covers should match the project's requirements. For instance, the primary scope on a commercial office project is structured cabling, AV systems, and network infrastructure, while Division 28 security scope is often the most coordination-intensive element when building a government facility.
Ask which technology systems the consultant covers and which they typically subcontract or refer out. A consultant who covers only one or two system types on a project with broader technology requirements will produce a fragmented construction document set – with coordination gaps at the boundaries of their scope.
References and Project Experience
Relevant project experience matters more than general technology credentials. A consultant who has worked on projects similar to yours – in terms of building type, technology complexity, and design team structure – can bring context that translates into better coordination during DD.
Ask for references from architects or owners on comparable projects, specifically about the consultant's coordination with the design team during SD and DD, the completeness of their construction documents, and the quality of their construction administration.
TMC works most often with architectural firms on technology-intensive projects like corporate campuses, healthcare environments, government facilities, stadiums, and airports. The feedback architects tend to give us centers less on the technology itself than on how the engagement felt to run:
- Coordination that stayed ahead of the schedule
- Questions answered before they became blockers
- Issues caught before they reached the field
- Consultants who protect the design team's standing with the owner
That last point comes up repeatedly, with the value showing up as problems that never materialized.
Frequently Asked Questions
What questions should I ask a technology design consultant?
The most important questions to ask an architectural technology consultant are:
- Are you vendor-neutral, and can you describe specifically what that means for your business?
- What are your deliverables at schematic design, design development, and construction documents?
- Can you show me a complete Division 27 specification from a past project?
- What technology systems do you cover, and which do you subcontract?
- What is your construction administration process?
- Do you have any financial relationships with manufacturers or integrators?
A confident answer draws on comparable projects by name, while a vague answer that substitutes a similar technology or a different industry for direct experience calls for a closer look.
What are the biggest red flags when hiring an architectural technology consultant?
The clearest red flags all point back to a consultant who isn't truly design-side. Watch for a financial relationship with a manufacturer or integrator, an inability to produce complete Division 27 and Division 28 construction documents from past projects, and specifications that read like a product catalog or rely on out-of-date templates.
On the working relationship, the warning signs are a consultant who has to be asked repeatedly for the deliverables a milestone set depends on, who doesn't know the questions to ask other disciplines, or who substitutes a similar technology or a different industry for direct, verifiable experience. Any of these suggests the project will inherit coordination gaps rather than avoid them.
What should technology design services include?
A complete technology design services engagement should include:
- Schematic Design Coordination: establishing the technology program and infrastructure requirements
- Design Development Coordination: equipment locations, conduit routing, equipment room layouts coordinated with the full design team
- Construction Document Specifications: vendor-neutral, performance-based Division 27 and Division 28 specifications
- Construction Administration: submittal review, RFI responses, site observation
The construction administration scope is worth confirming explicitly, since it's the phase most often left undefined in an RFP.
What is the difference between a technology design consultant and an integrator?
A technology design consultant is a design-side professional whose deliverable is a set of vendor-neutral construction documents: Division 27 and Division 28 drawings and specifications that become part of the bid set. An integrator is a construction-phase vendor whose deliverable is an installed, programmed, and commissioned system.
The distinction matters during evaluation because an integrator writing a specification tends to describe what they sell and install, which narrows competitive bidding and ties the owner to a single vendor. A design consultant specifies what the project requires in performance terms that multiple qualified contractors can bid.
TMC: The Vendor-Neutral Standard for Technology Design Services
Choosing the wrong architectural technology consultant rarely announces itself at the interview. It shows up months later, as a proprietary spec that killed competitive bidding, a coordination gap that wasn’t caught until rough-in, or a change order the architect has to explain to the owner.
TMC has worked as the vendor-neutral technology consultant on architects' projects for more than 35 years, across Divisions 25, 27, and 28, from schematic design through construction administration. We produce the coordinated drawings and performance-based specifications that hold up at bid, and we stay in the room through construction to protect the design intent and the design team.
If you're assembling a project team and want to see how a design-side technology consultant answers these questions, reach out to TMC today.
