“Having a meeting where we can come together and look at one screen and the same real-time information is paramount,” says Lisa Villasmil, VP of People & Culture at Cauldwell Wingate. “Now when we’re collaborating on staffing we can just say ‘Check Bridgit. What does it say in Bridgit?’ That has really made us more efficient when having staffing discussions and has helped foster a more collaborative relationship between the project team and People Operations.”
Table of Contents
Villasmil is describing what happens when communication stops fragmenting across channels. Before, every staffing conversation required reconstructing information from multiple sources. Who said what to whom. What was decided and why. Whether the person being discussed even knows about the decision. Now there’s one place to look, and everyone sees the same thing.
Poor communication is the primary cause of one-third of all failed construction projects. Projects with effective communication show dramatically different outcomes: 71% finish on time, 76% stay within budget, and 80% meet their original goals. The difference isn’t that successful teams talk more. It’s that information reaches the people who need it, when they need it, with enough context to act on it.
The real cost of fragmented workforce communication
Communication inefficiency hides in plain sight. It doesn’t show up as a single dramatic failure. It shows up as small friction across hundreds of interactions: the five-minute conversation to track down who’s assigned where, the confusion when an update didn’t reach everyone, the decision made without context that existed somewhere but wasn’t accessible.
Time lost to information hunting
How much time do your operations people spend tracking down staffing information? Verifying who is assigned where. Finding out who communicated what to whom. Reconstructing decision history that was never documented in a findable place.
“We have weekly meetings for business development and operations, and we would spend the operations meetings talking about staffing, not the business,” says Jamie Miller, Director of Engineering Development at Sellen Construction. “We were too busy coordinating our different spreadsheets.”
Miller’s team was spending meeting time on information retrieval that should have been instant. Multiply that across every staffing conversation, every week, across every team in your organization. Conservative estimates suggest construction professionals spend 5-7 hours per week on information retrieval that better systems could eliminate. For a team of ten, that’s more than a full-time equivalent lost to communication overhead.
Mistakes from incomplete information
When critical information doesn’t reach people who need it, mistakes follow. Someone accepts an assignment not knowing a scheduling conflict exists. A project manager makes a decision unaware of a conversation that happened last week. An employee shows up at a site Monday morning only to learn their start date changed Friday afternoon, and nobody told them.
Each mistake requires time to correct. Some create downstream problems that compound: the project that’s now understaffed because someone was double-booked, the client relationship strained because the wrong person showed up, the employee who questions whether leadership has their act together.
Context that evaporates
Information shared verbally or through casual channels doesn’t persist. The context of why a decision was made, what factors were considered, what concerns were raised, evaporates once the conversation ends.
“Previously, there was a gatekeeper,” says Shawn Gallant, COO at Columbia Construction. “We would communicate project needs, and they would go back to their desk to figure it out. It was siloed. We had one person controlling our operations and did it that way for 20 years.”
When information lives in one person’s head, it’s inaccessible when that person isn’t available. And months later, when a similar situation arises, the context that would inform a better decision is gone. The organization starts from scratch every time.
Who needs to know what about assignment changes
The most frequent communication challenge is assignment updates: informing people about where they’ll work, when, and with whom. Getting this right means understanding who needs information and what they need to know.
The person being assigned
The assignee needs complete information: which project, what role, start date, reporting structure, special requirements. Incomplete communication forces follow-up questions that consume time on both ends. “What time should I be there?” “Who do I report to?” “Is there anything I should know before I start?” These questions signal that the initial communication was insufficient.
Their direct manager
Direct supervisors need visibility into their team members’ assignments without having to ask. When did assignments change? What does the upcoming schedule look like? Are there conflicts to address? If managers find out about their people’s assignments through the grapevine, something is broken.
The receiving project
The project receiving the resource needs to know someone is coming. What’s their background? When exactly will they start? What experience do they bring? Projects that receive assignees with attached context integrate them faster than those receiving people without context, wondering who this person is and why they were assigned.
Everyone affected by the change
Sometimes an assignment affects other people or projects. If moving someone leaves their current project understaffed, that team needs to know. Mapping these relationships and ensuring information flows to everyone affected prevents the surprise phone calls that damage trust.
Designing assignment alerts that actually work
Knowing who needs information is the first step. Delivering it effectively is the second.
Timeliness that enables action
Alerts should reach recipients while information is still actionable. Notification of a Monday start that arrives Friday afternoon gives little time to prepare. Notification weeks in advance allows proper planning, questions to be asked, and adjustments to be made.
“Now, with Bridgit, everyone’s putting that information in one platform,” says Daniel Barry, VP of Operations at Schimenti. “This helps for multiple reasons; you don’t have to get on the phone or email. You can pull up Bridgit on your phone or laptop and see where there are available resources.”
Completeness that prevents follow-up
Every alert should contain enough information to understand what’s happening without requiring a follow-up conversation:
- Who is being assigned
- Which project and what role
- When the assignment starts and ends
- Relevant context or special instructions
- Who to contact with questions
If recipients consistently need to ask clarifying questions after receiving alerts, the alerts aren’t complete enough.
Channels that match how people work
Different recipients may prefer different channels. Some want email for the record. Some want mobile alerts for immediacy. Field teams need push notifications they can receive on site. Communication features that centralize alerts work best when they route through channels people actually check, while maintaining a central record regardless of delivery method.
Project-wide announcements without the noise
Beyond individual updates, teams need mechanisms for broader communication: changes affecting multiple people, project-wide updates, organizational announcements that need to reach specific groups.
Broadcast communication done right
When information affects an entire project team, a single announcement reaches everyone simultaneously with consistent information. Weather delays, site shutdowns, safety updates, schedule changes that affect the whole team. One message, everyone gets it, no telephone game where the message changes as it passes from person to person.
“HR and Business Development both have access to Bridgit, and they can see the staffing changes as well as trends,” says Andy Sparapani, Project Technology Leader at The Boldt Company. “It leads to a conversation around business development and available resources and how that affects speeding up and slowing down in certain areas.”
Sparapani’s point matters: visibility into the same information enables conversations that couldn’t happen when information was siloed. HR sees what operations sees. BD sees what HR sees. Decisions happen faster because everyone starts from the same facts.
Avoiding communication overload
The flip side of broadcast capability is communication overload. If everything goes to everyone, people stop paying attention. The important update gets buried under routine notifications. Eventually, people start ignoring broadcasts entirely.
Establish criteria for broadcast-worthy communication. Use broadcast sparingly so recipients treat those messages as important. Route information only to people who need it. The goal isn’t more communication but better communication: targeted, complete, and retrievable when needed later.
Why context should live with profiles
Communication about a person should be findable when that person’s record is accessed. The alternative is context scattered across email threads, chat messages, meeting notes, and conversations that were never documented.
The problem with scattered notes
Notes accumulate everywhere except where they’re useful. The feedback from a project manager about someone’s performance lives in an email from six months ago. The development conversation about career interests happened in a meeting that was never documented. The constraint that should inform this person’s next assignment is in someone’s memory, and that person is on vacation.
“What happens when you don’t have a clear picture of your staff is you don’t see ‘John Smith’ is ready for a promotion,” says Villasmil at Cauldwell Wingate. “So you hire an outside senior PM instead of promoting internally and backfilling the open position.”
This creates information asymmetry that advantages some decision-makers over others based on personal history rather than what the organization actually knows collectively.
Profile-attached communication
The alternative is communication that lives with the person’s profile. Notes, observations, and discussions attach to the individual record rather than floating in separate channels. When anyone pulls up that person’s profile, they see the attached context. The supervisor who knows the employee well and the operations manager who has never worked with them access the same information.
What belongs in profile notes: feedback from project leadership about performance, development conversations and career interests, constraints or preferences relevant to assignments, historical context that might inform future decisions. Notes should not become a dumping ground. Establish norms about what goes in to maintain signal quality.
Moving from reactive to proactive communication
Reactive communication waits until someone remembers to share information. Proactive communication builds notification triggers into the system.
Automated notifications
Rather than requiring someone to remember to communicate, systems can trigger notifications automatically. Project approaching staffing deadline triggers alert to operations. Certification nearing expiration triggers an alert to HR and the employee. Assignment ending in 30 days triggers planning notification. The communication happens because the system knows it should, not because a person remembered.
Early warning signals
Proactive communication surfaces emerging situations before they become problems. Utilization dropping. Multiple projects competing for the same resource. Assignment gaps opening in the forecast.
“Bridgit has shifted us from siloed decision-making to a more inclusive, team-based approach,” says Shelby McEntire, Director of Human Resources at Skiles Group. “Focusing on taking the best possible care of our people matters to us, and Bridgit allows us to be more proactive rather than reactive.”
These early warnings let people respond while options remain available, before the problem requires emergency action.
Centralizing workforce communication
Fragmented communication becomes centralized through deliberate design and consistent practice. Designate one system as the authoritative source. Assignment alerts, team announcements, profile notes all flow through this primary channel. This doesn’t prevent using other channels for informal communication. It establishes where official information lives and where people should look when they need to know something.
The specific tool matters less than consistent use. What matters is that alerts reach the right people, context attaches to profiles where it can be found later, and everyone involved in workforce decisions can access the same information. Construction teams that communicate effectively don’t communicate more. They communicate strategically, and the information is there when someone needs it.
