The Permit That Expired on the Wrong Day
A municipal licensing office issued a business permit to Marlow Catering on March 3, valid for one year. The permit states it expires on 'the same date the following year.' On February 28 of the next year (a non-leap year), Marlow submits a renewal application by email at 4:55 p.m. The office's published policy says renewals must be received 'no later than the expiration date,' and that late renewals are treated as new applications requiring a 45-day review. The office closes at 5:00 p.m. An intake clerk timestamps the email March 1 at 9:10 a.m., claiming the server received it after hours. Marlow's owner has a delivery contract starting March 5 and needs continuous authorization. The office manager must decide whether to process the renewal as timely or as a new application, and whether any interim authority exists.
1. How should the manager determine the permit's actual expiration date, and what does that mean for the February 28 submission?
Read the worked answer
The permit says it expires 'the same date the following year,' which points to March 3. The manager should not silently convert that to February 28 or March 1. Two readings are possible: a calendar-date reading (March 3) and a 'last day of the month' reading sometimes applied where an anniversary date does not exist. Here March 3 exists in the following year, so the calendar-date reading is the natural one. That makes the February 28 email early, not late. Even on the stricter view that the term ends the day before the anniversary (March 2), the submission is still before expiration. The manager should state the operative date in writing, apply it consistently, and treat the February 28 email as timely. The timestamp dispute is then secondary: even if the server logged it after 5:00 p.m., the policy deadline is a date, not a business-hour cutoff, unless the policy says otherwise.
2. The clerk argues the email arrived after close and is therefore late. Evaluate that argument and identify what the manager should do about the timestamp.
Read the worked answer
The argument conflates two different rules. The published policy sets a date deadline ('no later than the expiration date'), not a close-of-business deadline. An email received at 4:55 p.m. or even 11:59 p.m. on a permissible date is within a date-based deadline. If the office wanted a 5:00 p.m. cutoff, it needed to say so, and applying an unwritten cutoff now would be an inconsistent, after-the-fact standard. On the timestamp, the manager should check the mail server log rather than rely on a manual re-timestamp the next morning. A manual timestamp records when a person opened the message, not when it arrived. The manager should document the server record, correct the intake log if needed, and note the correction. If the server genuinely shows delivery after midnight, the manager must then ask whether the date deadline had already passed, which loops back to the expiration-date analysis.
3. Assuming the renewal is timely, what should the manager do about the March 5 delivery contract and the gap in authorization?
Read the worked answer
Timeliness of the application does not by itself extend the permit. The manager should check whether the governing ordinance or the permit conditions provide for continuing authority while a timely renewal is pending. If they do, the manager should confirm in writing that the permit remains in effect during review and give Marlow a dated letter stating that. If they do not, the manager cannot invent interim authority; instead, the manager should expedite review, since a timely renewal should not be pushed into the 45-day new-application track. The 45-day track applies to late renewals, and this one is not late. The manager should also flag the operational risk: Marlow's March 5 contract depends on continuous authorization, so any gap should be minimized and communicated early. The decision should be recorded with the expiration date relied on, the server evidence, and the basis for interim authority or its absence.