Compliance checklist form template
Work through a fixed list of controls and produce a dated, signed record that you did.
11 fields. Free to start. No card, and nothing to install.
Who uses it
Quality managers, food safety officers, pharmacy and clinic leads, and internal auditors. It fits any standard where the evidence of the check matters as much as the check.
The problem it solves
The checklist is done properly and then filed in a binder that an auditor cannot search. Six months later nobody can produce the Tuesday in March that the auditor happens to ask for.
How this handles it
Every control is a yes, no, or not applicable answer, which is the only vocabulary an audit trail needs. The three-way answer is a real option rather than a blank, so a skipped control is distinguishable from a control that did not apply. Each completed run is a separate dated submission with the signer attached, so producing one specific day is a search rather than an archaeology project.
This run
Controls
Exceptions
Photograph any exception, and the corrective action once it is done.
For agents
What an agent does with this form
A compliance agent watches for a run that is missing on a day the schedule expects one, and escalates before the gap becomes an audit finding. It reads only the answers and the dates, so it can flag a pattern of no answers on one control across a quarter.
The template is published as JSON at
/templates/compliance-checklist.json.
Read it to learn every field id, then post values keyed by those ids.
A field id is stable. A label is not.
{
"values": {
"cc_date": "2026-09-09",
"cc_checker": "Jordan Ellery",
"cc_area": "kitchen_and_preparation",
"cc_temp": "yes",
"cc_clean": "yes"
},
"idempotency_key": "compliance-checklist-2026-09-09-001",
"agent": {
"name": "your-agent"
}
}Authorization: Bearer ifk_submit_…. Or connect over MCP at /mcp.Questions about compliance checklist forms
Why offer not applicable at all?
Because forcing a yes or no on a control that genuinely did not apply teaches people to lie on forms. A distinct third answer keeps the record honest and tells an auditor the difference between skipped and irrelevant.
Can the checklist change without breaking the history?
Yes. Old submissions keep the questions and answers as they stood when they were filed. Adding a control affects future runs only, which is the behaviour an auditor expects.
How is a missed run detected?
By absence, which the form cannot see on its own. Query submissions by date through the API on a schedule and alert on the gap, or use a webhook to tick off an expected run in your own system.
Is a drawn signature acceptable to an auditor?
In most quality regimes it is, because it is attributable, timestamped, and stored with the record it signs. Check your specific standard, since a few regulated sectors demand a validated electronic signature system.
Create this form in your own workspace.
The template loads as a draft. Change every field, or send it as it stands.
Create this form