When a Bid Addendum Never Reaches Three Subcontractors

The preconstruction manager noticed the pattern only affected subs on hosted Microsoft plans, mostly smaller shops without any dedicated IT support of their own. Larger subcontractors running enterprise Google or Microsoft accounts had no trouble receiving anything at all. That split is common: smaller mailboxes run stricter default filtering than a large enterprise tenant with its own configured allow lists and administrators, so a marginal sender reputation tends to show up there first, well before anyone else notices a thing.

Rather than simply resend the addendum and hope it landed the second time, the team ran a placement check across the specific mail providers their subcontractor list actually used, mostly Microsoft-hosted small business accounts and a handful of Gmail addresses. The addendum and the standard weekly bid-list newsletter, both sent from the same domain, were landing in spam at several of those providers. That confirmed it wasn't one unlucky email; it was the domain itself, and it had likely been building for a while without anyone noticing until a document with a hard deadline needed to arrive on time.

The newsletter went out to every sub the company had ever worked with, including subs from projects two or three years prior who'd stopped opening anything from the firm entirely. That large inactive segment had been quietly dragging the domain's reputation down for months without anyone noticing, and it only became visible once a genuinely time-sensitive addendum needed to land instantly instead of eventually, the way a newsletter usually can afford to.

Because bids were due within the week, waiting for organic reputation recovery simply wasn't a realistic option. The team brought in InboxAlly to actively rebuild trust with the affected providers while they separated the weekly newsletter's inactive segment out of the main list at the same time. Once placement stabilized across the providers that mattered, they kept Mailreach running to check before every major bid package goes out from then on, since preconstruction has too many genuinely time-sensitive sends to find out about a filtering problem only after the fact.

The general and operations manager role that typically owns bid communications earns a median of $105,770 a year nationally¹, and a meaningful share of that role's time on a live, active bid goes to chasing down whether subs actually saw an addendum in the first place, usually by phone once trust in email has broken down. A placement check that costs a few hundred dollars a month is genuinely cheap against the hours spent re-confirming numbers one call at a time, not to mention the underlying risk of a bid that goes out priced entirely against outdated drawings.

After the recovery, the team added a placement check as a fixed line item on the preconstruction schedule template itself, sitting right next to the deadline for issuing addenda, rather than treating it as a one-off fix after a near miss. That way it survives staff turnover on the project and doesn't depend on whoever happens to remember the incident two years later, when the person who traced the original problem has likely moved to a different project entirely.

The schedule now also flags any subcontractor added to the bid list from a domain the firm hasn't emailed in over a year, since a stale relationship is exactly the kind of address that can quietly sit on the newsletter list without anyone noticing until it matters on a live bid. A short standing rule, confirm a sub's current email before adding them back to an active bid list, catches most of what would otherwise become next year's version of the same Friday afternoon problem, and it costs the estimator a two-minute phone call instead of a weekend spent rechecking every number on the job.

Fixed placement checks on a preconstruction schedule include:

• A placement check as a fixed line item on the schedule template, next to the deadline for issuing addenda.
• Placement tests against the mail providers the subcontractor list actually uses, including Microsoft-hosted small business accounts.
• Bid communications kept on a domain separate from marketing content such as the weekly newsletter.
• A phone call to confirm receipt for anything time-critical while a domain rescue is still working.