Rubric deep-dive: communications assessment (Pillar 04).

Twenty-five percent of the pillar. We give the team a synthetic engagement scenario and ask for a 500-word async update. What we grade is not grammar or idiom. It is structure. Does the update start with the lede (the thing the client most needs to know). Are the decisions named. Are the asks unambiguous. Is any risk buried, or stated up front.

A grammatically flawless update that buries the actual blocker in paragraph four scores lower than a technically imperfect update that leads with the blocker in the first sentence. The reference set the sample is calibrated against is not a set of well-written business emails. It is a set of updates the panel has seen resolve or escalate client engagements in production.

Twenty percent of the pillar. Functional English on the call, on the page, and (critically) under disagreement. Rehearsed answers that fall apart when the reviewer asks a follow-up are the primary red flag. A team can prepare intros and pitches. They cannot prepare their way through a real conversation that goes off script.

The bar is not native or near-native fluency. The bar is that comprehension and expression are not the bottleneck of the conversation. Teams can score well here with heavy accents, non-native word choice, and grammatical variance. What they cannot score well with is inability to follow up on a question they did not expect. That is the reveal.

Twenty percent of the pillar. Stated SLA for async response, plus a one-week observation window during which we send three test messages and log turnaround. First response within stated SLA on all three. Substantive response within one business day.

The red flag we score hardest is emoji acknowledgments with no substantive follow-up. A thumbs-up on a technical question, or a "will do" that is not followed by the actual doing, indicates a team that has learned to appear responsive without being responsive. A specific failure mode we see often enough to name.

Twenty percent of the pillar. Can the team scope realistically and push back on a request that does not fit. We give them a synthetic intake (a client asking for something they should not get) and record the transcript.

The bar: team narrows scope, names trade-offs, proposes a smaller first delivery. The red flags: team agrees to whatever the buyer proposes without pushback. Team quotes a price without asking a single clarifying question. Both are failure modes we see across the offshore market, and both are learned behaviors that hurt every downstream engagement.

Expectation-setting is where the difference between vendor and partner is decided. Vendors agree. Partners narrow. Every team that scored high on this criterion in the last year, on review, described the same pattern. They lost more small deals than they won, and won more big deals than they should have on paper.

Fifteen percent of the pillar. We roleplay a scenario where the team has to tell the client something the client does not want to hear. A slip, an overrun, a quality issue. The reviewer plays the client. Notes are structured.

The bar: issue stated plainly, with impact, options, and a recommended path. The red flags: bad news softened with so many qualifiers the actual issue is unclear, and news only surfaced after the client asks directly. The second pattern is the more dangerous one. A team that only shares bad news reactively will produce reference calls that recount "unexpected invoices" and "surprise slips" a year later.

Every criterion in this pillar exists domestically too. Every domestic vendor can also be graded on writing, responsiveness, and bad-news delivery. The stakes are higher offshore for a specific reason. The buyer cannot walk down the hall and get a read on the team's mood. All the signal has to come through written and scheduled channels. Which means the written channels have to carry more information, more accurately, than they would for a co-located team.

An offshore team that writes well can compensate for a lot of other gaps. An offshore team that writes badly (buries risk, sends emoji-only responses, softens bad news to the point of illegibility) will lose the account even if the underlying work is excellent. Communications is load-bearing infrastructure, not a soft skill.