Working with a remote AEC team: how Blend integrates into your firm
Written by: José Rossi

A Job Captain's field notes on visibility, control, and what actually breaks down when your team is remote.
There's a specific moment I've lived more than once, and last week was no exception.
It's Monday morning. The weekly client meeting is Thursday. I open the model — not because something feels off, but because that's the routine. Every week, before anything else, I check three things: the model, the drawings, and the Decision Log.
Everything looks fine on the tracker. Documentation at 75%, coordination on track, no flags. But the model tells a slightly different story. A change the client had requested — mentioned during a Teams call two weeks prior — wasn't reflected in the model. Not a crisis. But exactly the kind of thing that quietly grows into one.
That's the nature of client decisions on remote projects. They come in through email, through a side comment in a meeting, through a message on Teams. If nobody captures them formally, they live in someone's memory until they don't.
What's worked best for me is the decision log, a running record of every change the client wants to implement at the model level, from minor adjustments to decisions that reshape entire deliverables. I called a quick team meeting with our architectural coordination team, pulled up the log, and we had what we needed to course-correct before Thursday. By the time the client meeting happened, the picture was accurate. That's the goal.
Remote doesn't break projects. Invisible problems do.
I've worked on projects where the team was spread across three countries and delivery was tight and clean. I've also worked on projects where half the team was in the same building and things quietly fell apart for weeks before anyone caught it. The difference was never geography. It was always visibility.
Being in the same office doesn't guarantee it. You can sit ten feet from someone and still not know that their deliverable is blocked, that a decision was made in a side conversation that never got documented, or that the model hasn't been updated in three days. Proximity creates the illusion of visibility. It doesn't create visibility itself.
What actually works — remote or not — is building visibility deliberately. Documents that allow you to track the health of the project holistically, align the entire team, consolidate it, and that everyone takes as a reference source.
The thing nobody tells you about being the person in charge
When you're leading a remote BIM project, there's a failure mode that's easy to fall into and hard to notice until it's too late. You get pulled into the technical work, because it's interesting, and you're good at it, and while you're deep in one problem, something else starts drifting. A dependency that wasn't flagged. A decision that needed to be made two weeks ago and wasn't, because nobody was sure whose call it was.
The leader's job isn't to do the most complex work. It's to see around corners. BIM management means knowing, at any given moment, not just what got done this week but where the project actually stands and what's quietly accumulating.
Follow-up isn't a management formality. It's how you find out that a task marked "in progress" hasn't been touched in five days because the person doing it was waiting on a file that never arrived.
Culture is the system underneath the system
The teams that handle remote work well aren't the ones with the best tools. They're the ones where it's safe to say "I marked this done but I'm not sure it's actually done", where honesty about the gap is normal, not an admission of failure.
At Blend, we've spent years building that foundation, not just the workflows, but the culture underneath them. That's what makes it possible to open a model together and be honest about what we see. That's the part no toolkit can replace. But once you have it, everything else, the decision log, the tracker, the weekly rhythms, actually works.
I want to share the decision log I use to keep track of every decision the client makes throughout the project. It's simple, but essential for working with remote teams and keeping everyone aligned. Download it for free!
Ready to Blend With Us On Your Next Project?
José Rossi
Job Captain at Blend AEC. Experienced in BIM coordination, technical documentation, code application, and quality control for international architectural projects. He supports multidisciplinary teams through efficient production workflows, client interaction, and collaborative problem-solving across complex project environments.