Where a Permit Belongs

Every infrastructure project of any complexity requires permits. A construction permit from the municipality, an excavation permit from the utility, an environmental clearance, a road occupancy permit, sometimes all four for the same stretch of road. The permit is not optional. Work cannot legally begin until the permit is in hand, and the inspector who shows up afterward wants to see documentation that proves it was.

A permit gates the work. The people doing the work need to see it. The crew needs to know it cleared, the project manager needs to know when it expires, and the inspector needs to see the proof. When the permit lives beside the work, all three find it in one place.

When it lives somewhere else, permits get missed, expire unnoticed or clear after work has started, because the permit and the work drift apart.

What a Permit Needs

A permit needs four things from the system around it.

A place beside the work. The crew, the project manager and the inspector look for the permit where the work is.

Dates that raise their own alerts. An approaching expiry reaches the people responsible before it passes.

A history. Who changed the status, when, and on what evidence.

A link to the work it clears. When the permit changes, the work that depends on it shows the change.

Permits as Work Items

In Aptli, a permit is a work order. It sits under a job, is documented through a report and is validated through the same review as every other piece of field work.

A job is a unit of planned work: "Install fibre on Oak Street." Under it sit three work orders: one to obtain the construction permit, one for the installation and one for the post-installation inspection. The permit work order sits beside the construction work order in the same job, visible in the same project tree and tracked by the same progress.

The permit work order carries its details as fields: permit number, issuing authority, expiry date, conditions and application reference. They are searchable and filterable, and they appear in exports and reports.

The permit has a due date and notifications. A reminder or a rule on the record tells the people responsible as the expiry approaches, through the same notifications, in-app badges and calendar feed as any other work.

The permit goes through validation. When the permit is obtained, a report carries the permit document. A validator confirms it is the right permit, for the right location, with the right dates, and records any conditions as findings. The verdict is pass, fail or needs revision, and a validated permit issues its document with your letterhead.

The permit's status shows in the project. A project manager sees the permit work order's status beside the construction work orders in the same job, and the job's progress counts it.

Municipal Portals

Each municipality runs its own portal, forms and process.

A person checks the portal and records the permit's dates and reference numbers on the permit's work order.

From there, Aptli tracks the dates, notifies the people responsible and keeps the history an auditor asks for.

The Audit Trail Inspectors Ask For

When a regulatory inspector or a client auditor asks about permitting, they are asking three questions: Did you have the permit before work started? Was the permit valid for the location and scope of work? Can you prove it?

With the permit as a work order in the same system as the construction, the answers come straight from the record:

The permit work order carries its dates (created, completed, validated), and they compare directly with the construction work order's start.
The permit report holds the permit document, the validator's confirmation and any conditions recorded as findings. A validated report keeps its validated status.
Every material pickup on the construction work orders writes a timestamped transaction, and those timestamps compare with the permit's dates.
Everything exports to CSV, Excel, PDF or the audit log from one system.

An inspector looks for documentation that is consistent, timestamped and tamper-evident. With the permit and the work in one system, the records already agree.

Summary

A permit gates the work, and it belongs beside the work it clears.
A permit needs a place beside the work, dates that raise alerts, a history and a link to the work it clears.
In Aptli a permit is a work order under the same job as the construction, with the same planning, tracking, validation and audit trail.
Permit details (number, issuing authority, expiry date, conditions) are fields on the work order, searchable and filterable with the rest of the work.
A person records dates from the municipal portal, and Aptli tracks and notifies from there.
The audit trail inspectors ask for (the permit preceded the work, it covered the scope, the documents are tamper-evident) comes straight from the shared record.