Dates and follow-up
A company target is not a municipal deadline
Separate your team’s follow-up dates from published estimates and source-backed authority deadlines, and keep missing or conflicting information visible.
General workflow guidance
A date beside a permit task can mean several things. Your company may have promised to check a missing document, a municipality may publish an estimated review time, or an authority communication may state a deadline for your application. Each date needs its own label and supporting record. Otherwise, a useful planning target can become an unsupported promise.
Start with what the date means
A company follow-up target describes an action your team intends to take: ask for a drawing, check a record or send a progress update. A published processing estimate describes an expected duration within the scope of its source. A deadline recorded from an authority communication belongs with that communication and the particular permit. These entries may sit beside one another, but they answer different questions.
Make the distinction readable wherever colleagues encounter the date. “Company follow-up: Friday” is more useful than “Due Friday” when the task is an internal check. Keep an estimated duration labelled as an estimate. Do not turn it into a promised decision date by adding it to a submission date, especially when the source has qualifications you have not checked.
Leave missing and conflicting dates visible
If no authority deadline has been confirmed, say so and record the next company check separately. A blank field does not establish that there is no deadline. An old screenshot may no longer reflect current instructions, and a copied calendar entry may have lost the explanation that made it useful. Preserve the earlier record and assign someone to check the current information.
When two records show different dates, keep both and ask the appropriate authority to clarify the discrepancy. Do not quietly select the later date or overwrite the earlier message. Identify the unresolved question and the person following it up. If you cannot access the supporting record or confirm an update was saved, keep that uncertainty visible until the saved record can be checked.
Hypothetical example: Friday is a company target
Imagine a fictional renovation company preparing documents for one permit on its Cedar job. Morgan needs a revised drawing from a supplier and sets Friday as the company follow-up target. A colleague adds Friday to a shared job summary without the label. Another teammate reads it as the date the permit will be ready and mentions it during a homeowner update. This is an invented scenario, not a customer account.
The repair starts with the wording and the supporting record. The summary should identify the permit, Morgan’s action, the missing drawing and the company target. The teammate can correct the update: Friday is when the company will follow up, while an authority decision date has not been confirmed. Moving that internal target later would not establish an extension to any municipal deadline.
A published timeline is not a promise
On its secondary-suite permit costs and timelines page, Calgary states that the indicated timelines are not guaranteed. It identifies application volumes, completeness and timely applicant replies to requests for more information as factors. This qualification belongs to that page’s processing guidance. It does not set a deadline for a particular application or support promising a homeowner that approval will arrive on a chosen date.
Keep the date and its context together
Copy a stated calendar date clearly, including the year, and retain any time or time-zone context actually supplied by the source. If the instruction gives only a date, do not invent a midnight cut-off. If wording about days or timing is unclear, record the question and seek clarification rather than calculating a legal deadline from this article.
Record what happened separately from what should happen next. The date your team sent a response is an event; the next company check is a plan. Keep the response evidence and earlier instructions when plans change. During a handoff, read back the action, owner, date label and unresolved point together so the next person receives the meaning as well as the number.
A six-step company date checklist
Use this company recordkeeping checklist alongside current instructions for the application. It does not calculate deadlines or authorize construction.
- Identify the project and permit. Keep each permit’s dates with its own records.
- Label the date. State whether it is a company follow-up target, a published estimate or an authority deadline.
- Keep the supporting source. Retain the authority communication or official page and the date it was checked.
- Name the next action and owner. Say who will check, respond or obtain the missing information.
- Show the blocker or uncertainty. Leave missing dates unknown and preserve conflicting instructions.
- Record changes clearly. Keep earlier records and explain why the company target or recorded date changed.
Keep dates connected to their records
PermitLane organizes responsibilities, evidence and recorded permit history. Its AI determines permit applicability from the applied playbook and cited official-source revisions; an authorized person can override that determination. A software determination is not a municipal decision or professional advice, and does not establish a decision date. Submission and review remain external, and PermitLane does not guarantee approval. Clear company records help the team explain its next action without turning a planning date into an authority’s promise.
Official sources
Source checked October 6, 2026. The Calgary example concerns the qualification on published secondary-suite processing timelines; it does not establish a deadline for your application.