Pilot brief
What a PermitProof pilot involves.
A practical summary of scope, inputs, timeline, governance and success measures for a municipal pilot. Written to be shared with review, legal, privacy and IT stakeholders.
01Pilot scope
- One commercial permit stream, one review team, and a bounded set of rules the municipality already applies.
- Parallel operation: PermitProof supports the existing process; it does not replace the authority’s system of record during the pilot.
- Bilingual delivery (English and French) across every screen, export and notification.
02What we need from you
- A representative set of past submissions with drawings, revisions and reviewer notes.
- The applicable ruleset and any local amendments, with the version currently in force.
- Named reviewers, supervisors and oversight contacts for role and access mapping.
03Indicative timeline
- Weeks 1–2 — process mapping, ruleset intake and access provisioning.
- Weeks 3–6 — supervised reviews on live-equivalent cases with reviewer feedback each week.
- Weeks 7–8 — evaluation against the agreed measures and a written findings report.
04Governance and boundaries
- Engine findings, reviewer actions and competent-authority decisions remain separate records at all times.
- The assistant is decision support only: it explains stored findings with citations and cannot change a finding or approve a permit.
- Access is invitation-only and role-scoped, with case-level assignment enforced on the server.
05How we measure success
- Time spent locating documents and prior findings before a reviewer can begin.
- Share of findings that arrive with a complete evidence trail on first read.
- Repeatability: identical inputs must produce identical result hashes on rerun.
- Reviewer and supervisor confidence in explaining a decision to an applicant or auditor.
This brief describes a proposed pilot. It does not claim certification, legal validation or approved production status, and all figures shown in the product are representative demonstration data.