Stop CC-ing your SMEs
The 48% SME-bottleneck stat has held steady for five years. Most teams treat it as a people problem. It is a workflow problem. Replace the CC chain with a ticketed ask that has a deadline and a single owner.
Qorus reported that 48% of proposal teams cite SME collaboration as their top challenge — and that number has held steady for five consecutive years. Five years. Roughly half of every proposal team you’ll meet, with the same complaint, sustained across enough industry change that the cause is structural and not circumstantial.
The cause is structural, and most teams are working on the wrong layer of it.
The wrong layer is “we need better SME engagement.” Engagement programs, lunch-and-learns, recognition for proposal contributors, internal newsletters about the bid pipeline. These are fine. They do not move the number. The number has not moved while a thousand teams have run engagement programs. The cause is not that SMEs aren’t engaged. The cause is that proposal asks are unstructured.
The right layer is the ask itself. Replace the CC chain with a ticketed ask that has three properties:
- A specific deliverable. Not “your input on the security section.” A specific question or a specific paragraph for the SME to review. If the SME has to figure out what you want, they will deprioritize the figuring out.
- A deadline that’s earlier than you actually need it. Build the buffer in. The SME’s calendar is not yours; the deadline you give them is the deadline that competes with their billable work, and your real deadline is two days later than the one you put on the ask.
- A single owner on the proposal team. Not a CC. One named person who handles the SME’s questions, follows up, escalates to a manager if the deadline is at risk. The SME’s reply lands with that owner, not in a thread of seven names.
Three properties. A ticket. Not an email.
Lohfeld Consulting wrote about the same pattern — proposal managers spend more time chasing SME responses than building strategy. The chase is a CC chain. The chase is a workflow problem with a workflow solution.
What “ticketed” means in practice
You don’t need software for this. The discipline can run in a shared doc, a Linear or Jira project, a Slack canvas, or a dedicated channel. What matters is that each ask has a unique identifier, a status (open, in progress, blocked, closed), an owner on each side, and a due date.
When you have ticketed asks, three things stop happening. SMEs stop receiving the same question from three different threads in different states of staleness. Proposal managers stop wondering whether the SME saw the message. And the rest of the team stops wondering which version of the answer is current — there’s a ticket, the ticket has a single answer, and the answer is the source of truth.
What an SLA looks like
For a typical seven-to-fourteen-day proposal cycle, a workable SLA is: simple verification questions, 24 hours; full draft reviews, 48 hours; new content authoring (which you should be minimizing in favor of KB content), 72 hours.
These are the deadlines you put on the ticket. They are not the deadlines you commit to your customer. The proposal cycle is buffered: SME deadline first, then drafting and integration, then review, then submission. If your SME asks slip, the integration phase eats the slip; if you don’t have an integration phase, the slip becomes a submission risk.
What this is not
It is not a way to make SMEs work harder. It is a way to make their effort efficient. A 30-minute well-defined ticket from a proposal manager is less expensive for an SME than three back-and-forth emails over a week that converge on the same answer. The SLA is for both sides — the proposal team commits to a clear ask, and the SME commits to a clear turnaround.
It is not a substitute for SME judgment. If the right answer requires the SME to think hard for an hour, the ticket should reflect that and the deadline should accommodate it. The point is not to compress thinking; the point is to compress the friction around getting to the thinking.
The short version
The 48% SME-bottleneck number is steady because the CC chain is steady. Replace the CC chain with a ticket. Build a buffer. Name an owner. Five years of unchanged data is a long time to keep doing the same thing and expecting it to start working.