The Tender Compliance Audit
Check your draft response for gaps before submission
You have written a tender response but you are unsure if you have addressed every mandatory requirement. Missing a single compliance point can disqualify your entire bid.
That is the gap this drop closes. It is a sales & leads skill built for Kimi, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Bid managers and proposal writers who already have a draft tender response
How it works
The skill file does five things, in this order.
1. Extract all mandatory requirements. Ask Kimi to list every mandatory, must-have, and shall statement from the tender document with section references.
2. Map requirements to your response. Give Kimi your draft and ask it to identify where in your response each mandatory requirement is addressed.
3. Flag missing or weak coverage. Request a list of requirements with no clear answer or only partial coverage in your draft.
4. Review word count and format compliance. Ask Kimi to verify your response meets page limits, word counts, and formatting rules specified in the tender.
5. Generate a compliance matrix. Have Kimi produce a table showing requirement reference, location in your response, and compliance status for submission as an appendix.
What comes back
A checklist of coverage gaps and a compliance matrix ready to include with your tender submission
The mistake to avoid
Run this audit 48 hours before the deadline, not on the final day. Many procurement authorities in the UAE require a separate compliance statement and this matrix serves as evidence.
Running it
Paste the prompt block into a new Kimi chat and attach your files in the same message. Kimi's long context means you should upload everything at once rather than in batches, splitting the input is what causes it to lose cross-references between documents.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are a tender compliance auditor. I will provide you with two documents: a tender or RFP document and our draft response.
First, extract from the tender document:
- Every mandatory requirement marked with shall, must, or required
- All evaluation criteria with assigned weightings
- Formatting requirements including page limits, font, section order, and appendices
- Submission requirements including certifications, declarations, or supporting documents
Present these as a numbered list with the exact section reference from the tender.
Second, review our draft response and for each mandatory requirement identify:
- The section and page number where we address it
- Whether coverage is complete, partial, or missing
- Any language mismatch where we use different terms than the tender
Third, produce a compliance matrix in table format with these columns:
Requirement ID | Requirement Summary | Tender Section | Response Section | Status | Notes
Finally, list any requirements we have not addressed and any formatting rules we have not followed.
Tender document:
{tender_document_text}
Our draft response:
{draft_response_text}
If the tender specifies evaluation criteria weightings, note which requirements carry the highest scores so we can strengthen those sections.