Published Updated

For an issuing team, a digital licence or permit file should connect the current issued document to the submission, evidence, and authorised decision behind it. It should also show later conditions, changes, expiry, and renewal work without rewriting the earlier record.
This guide follows a mobile-vendor permit. The applicant submits forms and certificates; officers check the evidence, record a decision, and issue the approved permit. The same file then supports condition monitoring and the next renewal review. Programme rules determine the required evidence, decision powers, and effects of expiry.
The case file is the continuing record. The permit is a particular output of an authorised decision, with a defined scope and validity period. A renewal, corrected document, or changed condition should remain traceable to its own decision and evidence.
Give the case, applicant, regulated activity or location, submission, decision, and issued document stable identifiers. Keep their relationships explicit. One applicant can hold several permits, and one permit file can contain several submissions or issued versions over time. For a change of operator, see transferring a permit to a new holder, including the recorded outcome, effective date and earlier holder context.
| Record | What it explains |
|---|---|
| Submission | What the applicant requested: the received form, declarations, attachments, amendments, and submission time. |
| Evidence and assessment | Which certificates, inspections, consultations, findings, and exceptions reviewers considered, and which evidence they accepted. |
| Decision | Who decided, under which authority, for what reasons, with which scope, conditions, and effective period. |
| Issued permit and notice | The exact approved output, its identifier and version, issue and validity dates, and the copy supplied to the applicant. |
| Later lifecycle events | Condition reports, renewals, corrections, transfers, expiry, or authorised suspension and revocation, with their dates and supporting records. |
A corrected certificate can satisfy a requirement without erasing the expired certificate originally received. Keep the replacement linked to the request that prompted it, its review, and the submission it supports. The incomplete-submission workflow guide explains the correction loop in more detail.
Record the applicant’s request and received documents. Assign missing information and replacement requests to an owner.
Link the assessment and authorised decision to the evidence actually considered, including outstanding conditions.
Generate and check the approved permit, record issuance and delivery, and connect later changes to that issued version.
Document version history and an issued decision serve different purposes. Identify the exact versions supporting each decision and the exact document issued from it. For the release distinction, see controlled revisions versus file versioning.
In this illustrative programme, mobile-vendor permit PER-1042 expires on June 30. The renewal requests a new term beginning July 1, but its insurance certificate is out of date. The programme requires accepted replacement evidence and an authorised renewal decision before a new permit can be issued. These are example rules, not a universal renewal timetable.
Keep the current permit, its validity dates, and the new renewal submission separately identifiable. The officer requests replacement insurance and the renewal remains incomplete.
The applicant supplies a current certificate. Record when it arrived, which requirement it addresses, and the officer’s review. Preserve the earlier submission and certificate alongside that history.
The authorised reviewer approves the renewal with a reporting condition. Generate the new permit and notice from the approved fields, check them, and record the issued version and copy supplied to the applicant.
Assign the reporting deadline and the next renewal action. If a report is missed, open the configured follow-up for an officer. Any change to permit status follows the programme’s rules and an authorised decision where required.
Keep a pending renewal, supporting-document expiry, and the permit’s own status as separate facts. Record how the programme handles each. This lets an officer explain what was valid at a particular date, what was still awaiting review, and which later decision changed the file.
A generated draft can still require an officer’s check. Record the approved decision, template version, input data, generated file, issuance action, and delivery outcome. Correcting an issued copy should preserve the earlier version and explain whether it was replaced, withdrawn, or left effective for an earlier period.
If a programme requires a particular signature, seal, service method, or notice wording, include it in the approved process and selected integrations. Retain the relevant evidence without assuming that producing a PDF alone completes issuance.
For a public register or QR-linked lookup, agree the permitted fields under the programme’s disclosure rules. The public view may show a permit identifier, type, status, validity period, and approved conditions. Decide separately whether holder or location details are public; private supporting evidence should remain behind its own access controls.
Have the public identifier resolve to that approved view instead of exposing the internal case file. Record the source and effective time of status changes, reconcile updates with the public service, and define what the lookup shows while data is unavailable or an update is delayed. A QR code supplies a route to the view; the service behind it determines what users can verify.
A useful permit file lets the issuing team explain what was requested, what evidence was accepted, who decided, and which document was issued. Preserve those relationships as conditions, renewals, and status changes accumulate, with programme rules controlling the next action.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.