Inspections

A compliance visit or an internal audit only creates value if its findings actually get fixed, and that depends entirely on whether anyone can find, months later, what was found and what happened next. Edsyft builds inspections as versioned templates: a compliance checklist, an internal audit, or a classroom observation, cloned and activated for each cycle so last year's version stays exactly as it was even after this year's gets edited.

Every report moves through a deliberate, one-directional status path: draft, submitted, under review, reviewed, and finally published, and that transition is driven entirely by the organization side; a school can fill in and submit its own responses, but it cannot push a report from reviewed to published itself. Scoring can be weighted by section or averaged as a rating, and specific items can require evidence before they're considered answered at all.

A finding that needs to be fixed becomes an action item with an assignee, a severity, and a due date, not a line buried in a PDF. The school responds with notes and evidence, and the organization then explicitly accepts that response or rejects it with a reason, in which case the school can respond again. Nothing about the finding actually closes without that back-and-forth being resolved, on the record.

Visibility is deliberately its own decision, separate from status. A report can be fully published and still invisible to the school it's about, until the organization takes the specific extra step of sharing it, so a report can move all the way through review internally before anyone at the campus ever sees a finding attached to their name. Every one of these transitions, shares, and responses is written to an event log that can't be edited after the fact, which is what makes a compliance review a search through history instead of a scramble to remember what was agreed.