01 Cover Letter

Cover Letter

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

Use When

• Use this skill to draft or revise the proposal cover letter or transmittal letter.
• Load it after identifying the proposer profile and the applicable procurement context.

Do Not Use When

• The task is unrelated to the cover letter or submission sheet.
• The user only needs supporting domain knowledge rather than this section.

Required Inputs

• The ToR, RFP, advert, or submission notice.
• The selected proposer profile and any signature details.
• Any client-specific differentiators, past-project evidence, and validity requirements.

Workflow

Stop or block the workflow when a required input, permission, or acceptance basis is missing. Recover by revising the scope, obtaining evidence, or returning the narrowest qualified draft before proceeding.

1. Read the assignment materials and confirm what the cover letter must signal to the evaluator.
2. Load the proposer profile and any relevant procurement framework before drafting.
3. Identify the evaluator's first concern: fit, credibility, value, risk, compliance, or price confidence.
4. Use the structure below to draft a client-specific letter rather than generic boilerplate.
5. Cross-check the letter against the rest of the proposal for consistency of tone, facts, and commitments.
6. Verify signatory details, validity statements, and any submission-sheet requirements.
7. For premium or high-stakes submissions, run the premium commercial writing quality gate so the first impression signals value, proof, service quality, and risk control.

Quality Standards

• Keep the letter specific, courteous, and evaluator-aware.
• Use British English and East African professional tone unless the bid format requires otherwise.
• Prefer concrete relevance and measurable evidence over generic claims.

Anti-Patterns

• Releasing the section with an unresolved mandatory input. Fix: block release and name the evidence owner.
• Hiding a contradiction with another proposal section. Fix: reconcile the source sections before drafting resumes.
• Treating an unavailable check as passed. Fix: mark it not assessed and return a qualified draft.
• Do not open with generic boilerplate that could fit any client.
• Do not contradict the proposer profile, the proposal body, or the procurement instructions.
• Do not omit mandatory validity, enclosure, or signatory details.
• Do not invent authority or a signature. Fix: identify the authorised signatory and leave execution to them.
• Do not add new commitments. Fix: reconcile every promise with methodology, work plan, and price.

Outputs

Evidence Produced

Capability and Permission Boundaries

Read and search are required; any edit or external action remains within the explicit authority and permission boundary stated below. Read and draft only. Do not sign, send, submit, or represent authority without explicit authorisation.

Degraded Mode

If the tender pack or signatory details are unavailable, provide a marked draft and missing-input register. Do not infer validity or authority.

Decision Rules

Worked Example

A compliant letter names the tender reference, confirms enclosures, states the verified validity period, and leaves signature execution to the authorised director.

References

• Proposal skills router for repository-wide routing and mandatory quality gates.
• ../profiles/SKILL.md for proposer selection and voice.
• ../sectors/SKILL.md for procurement and sector routing.
• ../proposal-storytelling-and-evaluator-journey/SKILL.md when the cover letter needs a stronger first-impression narrative.
• ../premium-commercial-writing/SKILL.md for premium first-impression polish, proof-led positioning, and evaluator-friendly commercial writing.
• ../premium-client-proposal-strategy/SKILL.md and ../premium-pricing-and-value-defense/SKILL.md for premium, executive, enterprise, high-ticket, or value-defence proposals.
• ../references/ethical-persuasion-and-evaluator-psychology-gate.md for ethical persuasion checks.
• Root references/ files for persuasion and proposal-wide positioning.

The cover letter is the first thing an evaluator reads. It must be personal, specific to the client, and demonstrate that the firm has already understood the assignment — before the proposal body is read.

What to Gather Before Writing

• Client name and the name of the specific contact person or procurement officer
• Exact title of the tender or assignment as stated in the RFP or EoI notice
• Submission date
• Firm name, address, and signing authority (name and title)
• Two or three past projects directly comparable to this assignment
• The firm's three or four strongest differentiators for this bid

Structure

Opening — Client-Focused Hook

Do not open with "We are pleased to submit…" or "We refer to the above."

Open with a statement that shows understanding of the client's situation. Reference the specific challenge, reform agenda, or mandate the client is responding to.

Why Us — Two to Three Paragraphs

• State the firm's name and core positioning in one sentence
• Name two or three directly comparable past projects with measurable outcomes
• List three or four differentiators that matter for this specific assignment

Scope Confirmation — One Paragraph

• Confirm the proposal addresses all requirements in the ToR
• State validity period (typically 90 days)
• Note that a separately sealed financial proposal is enclosed, if applicable

Closing

• Express genuine interest in the assignment
• Provide primary contact name, phone, and email
• Sign off with "Yours faithfully" (unknown recipient) or "Yours sincerely" (known recipient)

Relationship Signals

The cover letter is the first impression of service quality. It should signal:

• Genuine understanding — name the client's specific problem, not generic language. Reference a specific detail from the ToR or context that shows you have studied their situation.
• Measurable-results orientation — even in the cover letter, hint at quantified value: "Our experience in similar engagements suggests [X% improvement] is achievable."
• The TRUST framework (Wickham): Truthful (honest about what is achievable), Responsive (acknowledge the ToR's specific concerns), Uniform (consistent with the tone of the full proposal), Safe (mention confidentiality and data protection if relevant), Trained (one sentence of quantified credential).
• Compatibility signal — demonstrate cultural awareness and alignment with the client's values and operating context.
• Service confidence — where the assignment includes support, maintenance, implementation, or digital service delivery, signal responsiveness, follow-through, and clear escalation without overpromising.

Tone Rules

• One page maximum
• Never use boilerplate that could apply to any client
• Name the client's specific challenge — not a generic sector description
• Quantify past project outcomes where mentioned ("reduced processing time by 40%")
• Polite and formally courteous throughout, following east-african-english standards

Submission Sheet

After the cover letter, include the Technical Proposal Submission Sheet. This is a standard form:

TECHNICAL PROPOSAL SUBMISSION SHEET

We offer to provide the services described in the Terms of Reference, in accordance
with the terms and conditions stated in your Request for Proposals.

We confirm that we are eligible to participate in public procurement.

We undertake to abide by the Code of Ethical Conduct for Bidders and Providers.

Validity period: Ninety (90) Days from the submission deadline.

Separately sealed financial proposal enclosed: [Yes / No]

Authorised By:

Signature: ___________________  Name: [NAME]
Position:  [TITLE]             Date:  [DATE]

For and on behalf of: [FIRM NAME]
Address: [ADDRESS]