Set a temporary worker's access end date before the card, fob, or code is issued, and write it down with the name of the person who sponsors the worker. Pick either a fixed calendar date or a defined event such as the contract closing. Decide whether the system or a person removes access, and agree on what an extension requires. A temporary credential with no end condition usually turns into a permanent one.
Why the end date belongs to the issuing decision
A temporary credential is easy to create and easy to forget. The job wraps up and the worker stops coming in. Nothing at the door tells anyone that the card still works.
Writing the end date before you issue the credential flips the default. With no end date, access continues until someone notices. With one, access stops unless someone asks for more time.
What to know before the credential exists
Two different sets of facts go into a temporary credential. One set defines what the credential opens. The other defines when it stops opening anything.
The scope comes from the worker's role, the doors and areas the work actually requires, and the days and hours the worker will be on site. A contractor working one floor on weekday mornings has no reason to hold a credential that opens the mechanical room overnight.
The end comes from how the engagement is defined. That might be a contract date, a last scheduled shift, or acceptance of finished work. The end also needs a sponsor, meaning the staff member who asked for the worker and answers for them. The sponsor owns the end date. If the sponsor cannot say when the work ends, the credential is not ready to issue.
Should temporary access end on a date or an event?
A fixed calendar date is the simpler choice. You know it on day one and can enter it when you create the credential. Its weakness is that work rarely ends on schedule. If the job finishes early, the card stays live until the date. If it runs late, the worker is locked out partway through the job.
An event-based end tracks the real job more closely. The event might be the contract closing or the sponsor accepting the work. The catch is that an event does not record itself in the system, so someone has to notice it and act. One workable approach uses both: a fixed date as the outer limit, with access ended sooner if the event comes first.
Next, decide who actually stops the access. If your access control system can hold an end date on the credential record, enter it at issue so the credential stops working without anyone stepping in. Removal by hand gives up that default, because a missed task leaves the credential working. If manual removal is your only option, put the date on one named person's calendar.
Then set the extension rule. A sensible rule lets only the sponsor request an extension, requires the request to name a new date, and has the administrator update the existing record instead of issuing a second credential. Write the rule down before the worker's first day.
The record to pass to the system administrator and door staff
The end date only helps if the people who run the system and the doors can see it. Keep a short record for each temporary credential with these fields:
- Worker's name and employer or agency
- Sponsor's name
- Credential type and number
- Doors and areas allowed
- Days and hours allowed
- End condition: a fixed date, an event, or both
- Who may request an extension
- Who confirms removal
Give the record to the system administrator and to whoever manages the doors day to day. When an end date changes, the sponsor, the administrator, and the door staff all need the new date.
To keep end dates current, add one question to an access review you already run. Does each temporary credential on the active list have an end condition that is still in the future and still accurate? Any credential that fails goes back to its sponsor.
For help setting up access control for temporary users on commercial doors, including short-term workers assigned to doors with commercial smart locks, call Atlas Integrated Security at (347) 357-0985.
Frequently asked questions
What if a temporary worker's job runs longer than planned?
When a temporary worker's job runs long, the extension request should come before the current end date passes, not after. If the date passes first, let the access lapse rather than quietly reactivating the old credential, and restore it through the normal extension request. The short gap is useful: it shows that the end date was reached and that someone made a deliberate decision to continue.
Should a temporary worker share a credential with a colleague?
A temporary worker should not share a credential. Each person on a crew needs their own card, fob, or code. With a shared credential, the access log cannot show who came through a door. It also ties two people to one end date. Ending one worker's access then either cuts off the other worker or leaves the first still holding working access.
Is a shorter end date better than a longer one?
A shorter end date for temporary access is not automatically better. An end date set too tight produces repeated extension requests, and frequent requests teach people to approve them without reading. Set the date at the planned end of the work with a small allowance for normal slippage. Then rely on the extension rule for real delays.
Who should confirm that a temporary credential has actually been removed?
Someone other than the sponsor should confirm that a temporary credential is removed. That is usually the system administrator or whoever runs access reviews. Confirmation means checking that the credential record shows as inactive, not just that a request was sent. Collecting a physical card or fob is a separate step worth recording. The record change is what stops the door from opening.
Tell us about the building.