Working with co-consultants: practical solutions to delays, unresponsiveness, and friction

If you, as an architect, have never had complaints about co-consultants you’ve worked with, you’re either very organised or very lucky.

“Coordinating with consultants” (1), “unresponsive consultants” (2), “being on the hook for consultants’ delays” (3), “getting thrown under the bus by consultants” (4) are some of the most common complaints architects have about their experience with co-consultants.

Of course, this isn’t universal, but the trend is clear. Some architects learn to manage co-consultants effectively with time. We’ve worked with hundreds of architects and heard many horror stories while building PlanMan.

That’s why one of the main features of PlanMan is our co-consultants module designed to help you avoid these issues. 

Let’s go over some of the best practices you could use to get a better experience working with co-consultants.

Organizing your work with co-consultants

Working effectively with co-consultants (designers, structural engineers, MEP engineers, landscape architects and so on) on architectural projects requires clear communication, mutual respect, and proactive coordination. 

Here is a checklist for productive collaboration:

Vet everyone you work with

First things first, make sure you do at least some due diligence before starting to work with a co-consultant. 

We’ve put together a guide on vetting your contractors and co-consultants, so check it out.

Don’t be cheap

Underpriced co-consultants are the ones that get all the bad rep, because they take on an unrealistic amount of projects while doing all the work the night before deadline. 

This approach rarely lets them actually meet the deadlines, and if you’re working with several of those your project (and your reputation) can suffer.

Instead, work with co-consultants that charge enough to be comfortable, because you get what you pay for. Their timely and high-quality deliverables will make up for the potential minor savings.

Establish clear roles and expectations early

At the project kickoff, define each consultant’s scope, deliverables, and deadlines. 

Use a responsibility matrix (e.g., RACI chart) to clarify who is responsible, accountable, consulted, or informed for each task.  

Agree on project goals, timelines, and communication protocols to align everyone.

Communicate regularly and transparently

Schedule recurring coordination meetings (weekly or bi-weekly) to review progress, address issues, and align on next steps.  

Use the collaborative power of PlanMan for real-time updates and document sharing.

Each project has a built-in chat room for real-time updates and discussions, allowing co-consultants to communicate instantly without relying on external tools like email. 

Tagging (@) notifies specific team members so you get a timely and personalised response.

This centralised communication minimises miscommunication, especially for remote teams or those in different time zones.

Be proactive in sharing design updates or changes to avoid surprises that could derail other consultants’ work.

Use standardised tools and processes

Agree on file formats, naming conventions, and software (e.g., Revit, AutoCAD, BIM 360) so the team can exchange and use files.  

Implement Building Information Modeling (BIM) for integrated design coordination, allowing all consultants to work within a shared model to catch clashes early.

Anticipate and mitigate delays

Build buffer time into schedules for unforeseen issues, especially for complex tasks like structural or MEP (mechanical, electrical, plumbing) designs.  

Request interim deliverables or progress updates to monitor consultants’ work and catch potential delays early.  

Keep responsibilities clear by addressing delays diplomatically but promptly, focusing on solutions rather than blame.

Build strong relationships

Treat co-consultants as partners, not adversaries. Understand their constraints and priorities to find mutually beneficial solutions.

Encourage open feedback and listen to their expertise, as engineers or contractors may offer practical insights that improve the design or execution.

Acknowledge good work to build trust and goodwill, and establish yourself as a leader, and not just a customer.

Resolve conflicts constructively

Address disagreements quickly through direct discussions or mediated meetings, focusing on project goals rather than personal differences.  

Use the contract or project charter as a reference to clarify disputes over scope or responsibility.  

If conflicts escalate, involve the client or a neutral third party (e.g., project manager) to mediate.

Document everything

Keep detailed records of agreements, meeting minutes, and correspondence to avoid misunderstandings. Our document management module helps you keep it all in one place.

Use version control for drawings and documents to ensure everyone is working from the latest information.

The co-consultant module supports tracking co-consultant deliverables (e.g., structural calculations, and cost estimates), helping you stay on top of project milestones.

Every project visualises timelines and dependencies, keeping co-consultants aligned.

With PlanMan’s set of permissions, co-consultants can access the latest project documents (e.g., drawings, specifications) securely. No more scattered files across emails or third-party hosting sites.

Version control and global search features help co-consultants quickly find and work with the most current files, reducing errors from outdated information.

Once you set a collaborative tone, maintain open lines of communication, and use appropriate tools, you will minimise friction and ensure co-consultants work together efficiently.

There are some further small, specific, and fun practical tricks you can implement in your practice to manage co-consultants more effectively, e.g.:

• Gamify deadlines with fun titles or monetary bonuses.
• Schedule 10-minute “flash sync” calls mid-week for co-consultants to share one critical update or blocker.
• Create a shared “mood board” for inspiration  – it could be a shared folder in PlanMan for co-consultants to drop images, sketches, or ideas that inspire their work.
• Drop quick, specific thank-yous in PlanMan’s chat for co-consultants’ efforts.

Dealing with unresponsive co-consultants

Dealing with unresponsive co-consultants can be a major bottleneck for architects, stalling project progress and coordination. 

Below are some specific, practical strategies to address unresponsiveness using the PlanMan’s co-consultants module and general project management tactics. 

These approaches are professional, direct, and designed to re-engage consultants efficiently while maintaining positive relationships.

• Use the chat nudges in PlanMan – send a concise message in PlanMan’s chat, tagging the consultant (e.g., “@StructuralEng, need your input on beam layout by EOD tomorrow”). If no response within 24 hours, follow up with a direct email referencing the PlanMan message and CC the project manager or client (if appropriate).
• When assigning tasks or requesting input in PlanMan’s task tracker, include a specific response deadline (e.g., “Please confirm receipt of this task by 5 PM tomorrow”). Use PlanMan’s notifications to auto-remind consultants 24 hours before the deadline.
• If a consultant remains unresponsive after two attempts, schedule a 10-minute one-on-one call via PlanMan’s chat or a calendar invite, framing it as a “quick sync to align on the next steps.”
• If unresponsiveness persists, post a neutral update in PlanMan’s project-wide chat, visible to all consultants (e.g., “Awaiting structural input to proceed with the design phase, @StructuralEng, please advise status by tomorrow”). As a last resort, loop in the client or senior stakeholder via email, citing the project impact.
• Log every attempt to contact the consultant in PlanMan’s chat or task comments (e.g., “Emailed @MEPEng on 4/20, no reply; followed up 4/22”). This creates a paper trail for accountability and protects you if disputes arise.  
• Structural engineers may go silent due to complex calculations or competing projects. If they’re unresponsive to broad requests, send a yes/no or multiple-choice question in PlanMan’s chat.
• In your outreach, mention a prior successful interaction (e.g., “@StructuralEng, your input on the last project’s beams was spot-on—need your thoughts on this slab by Friday”). Post this in PlanMan’s chat to keep it visible.
• Break large requests into smaller, actionable tasks in PlanMan’s task tracker (e.g., instead of “Complete MEP plans,” assign “Confirm duct routing for Level 1 by Wednesday”). Tag the MEP engineer and set notifications.  
• If they’re silent on a decision, suggest a default option in PlanMan’s chat (e.g., @MEPEng, no reply on HVAC placement, so we’ll proceed with Option A unless you advise by EOD”).  
• At the project kickoff, agree on response times (e.g., 24-48 hours) and preferred channels (PlanMan chat, email). Document this in PlanMan’s project folder.

Use PlanMan’s co-consultant tools to keep contact details, conversations and shared files linked to the project. 

They address unresponsiveness by combining urgency, clarity, and respect, tailored to each consultant’s workflow.

Get your PlanMan trial today and see how it can help you manage co-consultants!