Built by people who have sat through the survey.
We turned three decades of hand-built survey prep into software any team can start for free.
in survey and inspection preparation
facilities taken through survey
survey pass rate across those facilities
record, from the first report to the audit packet
Track record from PharmPro's compliance consulting practice. Figures describe that practice, not IncidentKit software customers.
The binder is the problem.
Before a survey, someone builds a binder. Reports sit in a drawer, actions in a spreadsheet, QAPI minutes (CMS's quality program) in a folder. The one person who knows how it fits is on vacation.
After thirty years of that week, the pattern was clear. The incident is the unit of proof. If one record holds the report, the investigation, the fix and the check, the binder builds itself.
So we built the kit around that record, with an assistant at the front door so a report takes ninety seconds. It is free, so the smallest site can start. We charge for a BAA, a covered AI and packets that hold up.
Five principles that guide what we ship.
The report is the easy part.
Most programs fail after the form is filed. The investigation stalls, the fix has no owner, and nobody checks that it worked. We build for the whole loop.
A person signs.
AI can draft a report and suggest causes. It cannot be accountable for them. Lauren drafts, and a named person approves every report and investigation.
Compliance should be a by-product.
When the record is complete at close, the QAPI summary, survey packet and OSHA log are an export, not a project.
Safety tools should be free to start.
A near miss logged on a free plan can prevent an injury. We charge for assurance, not access.
Say what is real.
We mark what is live and what is rolling out. We say when a competitor fits better. We cite a source for every regulatory claim.
How we write what you read.
- Primary sources first. We cite the CFR, CMS manuals, OSHA and accreditors, not blogs.
- Dated and reviewed. Every page shows its last review date and changes when the rule does.
- Unknown is not no. In comparisons, if a vendor is silent, we write unknown and date it.
- Rolling out means rolling out. Anything not in every account is labeled, on every page.
- Corrections welcome. Email support@incidentkit.ai and we will fix errors and say so.
- Not legal advice. Guides explain rules in plain words. Confirm with the issuing body or your counsel.
About us, answered.
Something we missed? Ask us, and a person answers.
Who is behind IncidentKit?
The compliance team behind PharmPro's consulting practice: 31 years in survey and inspection prep, and 250+ facilities taken through survey. The forms, routing rules and packets are the ones we built by hand for clients.
Is IncidentKit part of PharmPro?
IncidentKit is a separate product from the same team. PharmPro is the consulting practice. IncidentKit makes that practice's incident, QAPI and survey work repeatable for any team.
Who writes the guides and compliance pages?
The compliance team, from primary sources: the Code of Federal Regulations, CMS manuals, OSHA and accreditor publications. Each page lists its sources and review date. See our editorial policy.
How do I report an error?
Email support@incidentkit.ai with the page and the error. We fix factual errors quickly and note the change on the page.
Where is the company based and how do I reach you?
We are a remote team in the United States. Use the contact page or email hello@incidentkit.ai.
See thirty years of survey prep as software.
Create your kit in about ten minutes and report the first incident the same day. Free to start, no card.