Managing several jobs
How to track permit work across several small jobs
Keep each job’s next permit action, responsible person, confirmed dates and blocker clear when office work competes with time on site.
General workflow guidance
A contractor can remember the biggest issue on a large project and still lose track of a small permit action on another job. One application needs a document, another needs a status check and a third has two conflicting messages. When every item is labelled “permits pending”, the list hides the difference. A useful review makes the next action visible for each permit, without pretending that a tidy list settles an authority’s decision.
Start with the gaps
Before sorting the work, check whether the records are usable. Is the latest status actually checked? Does someone own the next action? Can that person find the supporting notice or submission record? An empty next-action field could mean the work is finished, or that nobody recorded what follows. Ask which is true instead of treating the blank as a reassuring sign.
Keep missing evidence and conflicting reports visible. “No response received” differs from “Nobody has checked for a response”. An older source may need a current check before the team relies on its instructions. These are suggested descriptions for company records, not new PermitLane statuses. The purpose is to show what needs clarification before a colleague plans around it.
Give each permit one clear next action
Start with the job and the particular permit. Write an action someone can perform or verify: obtain the missing document, check the authority record or clarify which response applies. “Handle permits” is too broad to hand to a busy colleague. Add the responsible person, the blocker and a link or reference to the evidence in your authorized workspace.
Keep a company follow-up target separate from a municipal deadline. If a deadline is stated in an authority notice, retain that notice and its date context; if the date is unclear, record the question. Do not manufacture a deadline from a crew booking or an expected response. Where several permits have open work, keep separate actions so progress on one does not hide the others.
Hypothetical example: three jobs, three different needs
Imagine a small contractor reviewing three fictional jobs before the team heads out. On the Cedar job, Morgan is waiting for a supplier document and has promised an internal follow-up on Tuesday. On the Birch job, Riley has a submission record but has not checked for a later response. On the Maple job, a saved email and a colleague’s note appear to describe different outcomes. This is an invented example, not a customer account.
Calling all three “waiting on the City” would hide work the company can do. Morgan can follow up with the supplier. Riley can check the current record. The Maple coordinator can preserve both messages and clarify the discrepancy through the appropriate channel. Tuesday is a company target in this scenario, not a municipal deadline. None of these entries establishes approval, refusal or permission to begin construction.
Choose the next check from recorded facts
Review supported deadlines and dependencies before choosing today’s work. A missing document with an agreed follow-up deserves a different action from an application whose latest record has not been checked. If two items compete for the same person, make the conflict explicit and agree what happens next. This is a company coordination practice, not a claim that PermitLane automatically ranks all jobs or makes scheduling decisions.
Keep the review small enough to repeat. Finish by naming the next check and who will report back, rather than opening every attachment in a meeting. If a record cannot be accessed or an update is not confirmed saved, keep that uncertainty visible and verify the saved record before relying on it. A confident verbal summary cannot replace missing evidence.
Keep company actions separate from municipal results
Calgary’s residential ePermit FAQ distinguishes applications with the City from records requiring applicant action. It identifies “pre-screen” and “project review” as submitted, while “revision” and “re-submission” require an applicant update before resubmission. These are descriptions for that specific portal. They illustrate why a generic waiting label can conceal the next task; they are not universal statuses or a decision about any particular property.
City of Calgary: residential ePermit submission and applicant-action statuses
A six-step company review checklist
Use these company practices to review several jobs. They do not replace municipal instructions or authorize construction.
- Identify the job and permit. Keep separate permits separate, and record any unresolved permit question.
- Write the next action. Describe something a person can do or confirm, with the supporting record nearby.
- Name the owner. Confirm who will act and who receives the update if that person is unavailable.
- Label the date. Separate a company follow-up target from a source-backed municipal deadline; leave unknown dates unknown.
- State the blocker. Keep missing information, outdated sources and conflicting records visible beside the action.
- Review what changed. Record completed company actions separately from external submissions and municipal outcomes, preserving earlier history.
Keep the review connected to the record
PermitLane organizes responsibilities, evidence and recorded permit history so teams can find the information behind their next action. Its AI determines permit applicability from the applied playbook and cited official-source revisions; an authorized person can override that determination. This does not decide a municipal outcome. Submission and review remain external, and PermitLane does not guarantee approval.
Official sources
Source checked October 3, 2026. The Calgary example concerns residential ePermit status descriptions only; confirm the current instructions and records for your application.