Writing to Persuade, Not Just Inform: Lessons for Mauritian Tender Submissions

#Blog 7

Many tender submissions read as inventories of fact rather than arguments for selection. This distinction, between informing an evaluator and persuading one, is often what separates a submission that scores adequately from one that scores strongly.

Information alone rarely wins

Stating that a business "has ten years of experience in facilities management" informs an evaluator. It does not, by itself, persuade them the business is the right choice for this specific contract. Persuasion requires connecting that experience explicitly to the outcomes the contracting authority is seeking.

Every claim needs a "so that"

A useful discipline is to follow each factual claim with its implication for the client. Not simply "our team is ISO-certified," but "our team is ISO-certified, so that quality is assured without requiring additional oversight from your organisation." The second version does the evaluator's reasoning for them.

Specificity persuades; generality does not

"We deliver high-quality service" persuades no one, since every competitor claims the same. "In our most recent comparable engagement, response times averaged under four hours across a twelve-month period" gives an evaluator something concrete to weigh.

Address the evaluator's likely concerns directly

Strong submissions anticipate what might cause hesitation, capacity, continuity, risk, and address it before it becomes a doubt in the evaluator's mind, rather than leaving gaps for assumptions to fill unfavourably.

The Mauritian context

In a market where many businesses compete for the same public contracts, technical capability is often broadly comparable across bidders. Persuasive writing, communicating that capability convincingly rather than simply listing it, is frequently what determines the outcome.