Keep every approval tied to the plans it approved.
A permit is granted against a specific set of drawings, on a specific day, by someone with the authority to grant it. Months later, in another system, an inspector has the permit but no way to prove which drawings it was for. Rootz keeps that link attached to the record.
The document version is part of the decision.
A permit workflow can involve revised drawings, land records, engineering reports and several departments. An approval is useful only when a recipient can establish which version and conditions it covers.
Rootz connects those exchanges to signed evidence. The municipality and its appointed reviewers retain the authority to assess and approve. This is a proposed integration design.
Follow one permit referral
Register the submission
Bind the applicant’s request to a versioned manifest of drawings and supporting documents.
Check required evidence
Record the source, age and completeness of the records required by the municipality. AI can assist with extraction and completeness checks.
Refer the exact revision
A signed instruction names the assessment, its scope and the document version the department must review.
Return the assessment
The reviewer signs the assessment under the appropriate authority. Binder connects the result to the referral and available process measurements.
Authorize the permit
The designated official or authorized process issues the permit with its conditions and references to the approved revision.
Support inspections and amendments
Inspectors verify the applicable record and status. A changed plan requires its own recorded review and authorization.
A focused first delivery
| In the first workflow | Owned by the wider program |
|---|---|
| Submission completeness and one departmental referral | The full permitting application and land-record systems |
| Version binding and signed assessment | Engineering judgment, planning policy and statutory approvals |
| Verifier integrated into the receiving application | Field devices, user training and citizen-service channels |
| Documented exceptions and evidence export | Appeals, amendments, retention schedules and operational support |
Build on the digital services already taking shape.
Rwanda’s Building Permits Management Information System is a public example of permitting that spans submissions, reviews and inspections. It illustrates the breadth of the workflow; it is not presented here as a Rootz customer.
Our proposed contribution is the verifiable relationship among the request, the document revision, the reviewer’s authority and the returned decision.
Test a changed drawing, not just a successful approval.
The acceptance exercise includes a valid referral and a substituted plan revision. The recipient must detect the mismatch and follow the municipality’s exception process.
See the technical approachChoose one department and one referral.
A small, well-defined exchange can establish the evidence pattern for the rest of the permitting service.
Plan the workshop