Skip to main content
Back to the blog

Scheduling and permit records

How to schedule one job with two open permit records

Keep each external record separate, then decide what your company can commit to while a permit question is still open.

General workflow guidance

A site calendar is useful when it tells the crew where to be and what to do. It can also hide uncertainty. If one renovation has two permit records and a calendar entry just says “permits confirmed”, nobody can tell which record was checked or whether the update covers the work in that booking. Before turning a tentative slot into a commitment, connect the activity to the specific records and questions your team needs to resolve.

Keep the records separate

Give each external record its own entry, even if both share a job name or address. Record the application or permit reference, the scope described in the available material, the last observed status and when someone checked it. Keep a link to the relevant evidence in a place your authorised team can reach. If the record is missing or you have only a verbal summary, write down what is missing and who will check it.

On the company schedule, name the activity you are trying to confirm and the question that affects the booking. A note like “crew date subject to clarification about the changed work on record B” gives the office something to follow up on. A generic “permit pending” label leaves the crew guessing about the part of the job in question and what evidence would resolve it.

A hypothetical crew booking with an open permit question

Imagine a fictional renovation where Mina is coordinating the schedule. Her team has an issued document on file for record A. On record B, the latest message requests revised material. A trade can hold a Tuesday slot, but the office has yet to establish how the work planned for that slot relates to the two records. The crew leader sees the document for A and asks whether Tuesday is firm.

Mina keeps Tuesday tentative and writes the exact scope question beside the booking. She names the person who will obtain clarification and sets Monday morning as the company’s check-in. If the answer is still outstanding then, the scheduler can release the hold and tell the trade why. If clarification arrives, Mina records which reference and activity it covers before updating the crew. In this example the schedule change is a company decision about a booking. Any authority decision remains with the authority.

Check the status against the right reference

For Calgary applications tracked in VISTA, the City’s instructions explain how to check an application’s status using its Job Access Code. When documenting an update, keep the application reference with the observation and note when it was checked. Keep access codes and credentials in authorised channels rather than copying them into a broad schedule or crew message.

A status observation is one piece of evidence. If its connection to a planned activity is unclear, record the question and ask the appropriate authority or professional to clarify it. Keep the answer with the activity and record it actually addresses.

City of Calgary application tracking instructions for VISTA

Make the handoff about the booking

A useful message to the crew gives the date, the work under discussion, whether the booking is tentative or confirmed by the company, and who will send the next update. The office can keep the underlying evidence in the job file. That way the field team receives a usable instruction without needing to sort through external messages or infer what a document covers.

When something changes, add the new observation and its date to the record. Keep the earlier note so the next coordinator can see why the team held the slot and what changed. Update the people relying on the old plan, particularly if a trade has already reserved time or a homeowner has arranged access.

A six-step check before confirming a slot

Use this as a company scheduling check and take scope or authority questions to the appropriate source.

  1. List each external record and its own reference. Keep any missing or disputed reference visible.
  2. Write down the last observed status, source and date for each record.
  3. Name the exact activity in the booking and the unresolved question that affects it.
  4. Give one person the follow-up and agree when the company will check in again.
  5. Tell the trade and affected colleagues whether the slot is tentative or confirmed by the company.
  6. When clarification arrives, preserve its scope and date, update the booking and contact the people relying on it.

Keep the evidence with the permit work

PermitLane organises permit work and records human-observed external submissions and review outcomes. When it can validate an AI applicability decision against the exact official-source revision in the applied playbook snapshot, PermitLane records and applies that decision automatically. An authorised person can override it. When a decision cannot be made, applicability stays unconfirmed. The AI decision carries no municipal authority and offers neither professional advice nor a guarantee of approval. Submission and review take place outside PermitLane. The company still needs to connect each scheduling commitment to its evidence and obtain clarification where the scope is uncertain.

Official sources

Reviewed November 9, 2026. The Calgary reference covers application tracking in VISTA. The scheduling checklist is suggested company practice.

Explore how PermitLane organizes permit work