---
title: "Contractor access: agree the end date before work starts"
id: "1499"
type: "post"
slug: "contractor-access-end-date-review-record"
published_at: "2026-11-17T09:12:19+00:00"
modified_at: "2026-11-17T09:12:19+00:00"
url: "https://optytech.com/contractor-access-end-date-review-record/"
markdown_url: "https://optytech.com/contractor-access-end-date-review-record.md"
excerpt: "A practical contractor access record: agree the scope and end date, identify who approves extensions, and keep separate confirmation for each closure action."
taxonomy_category:
  - "Blog"
  - "Services"
---

OPTYTECH BLOG

# Contractor access: agree the end date before work starts

November 17, 2026

*OpTyTech editorial guide · Security. Prepared with AI assistance and checked against the linked primary sources. The record and example below are planning aids. The cover photograph is illustrative and does not identify an OpTyTech site or project.*

Put an access end date, an extension approver and a closure owner into a contractor’s work request before access is arranged. Then keep the request open until the responsible team confirms the outcome. A date in a document needs an owner who will act on it.

This is a practical way to prepare an access review when a supplier needs to enter a workplace or use a business system for a defined task. It gives the people approving the work a place to record what remains necessary as the assignment changes. The responsible security and IT teams still determine the controls for the actual environment.

## Describe the work and the access it needs

Start with the task. Identify the supplier and the internal person sponsoring the work, then describe the area or service involved. “Access for maintenance” leaves questions unanswered. A request can instead name the agreed work area and refer the authorised team to the relevant job record.

The UK National Cyber Security Centre’s supply chain guidance recommends that supplier access to systems, information and premises is controlled, reviewed periodically and removed when no longer required. It also discusses matching requirements to the engagement. [Read the NCSC’s guidance on establishing control.](https://www.ncsc.gov.uk/collection/supply-chain-security/principles-supply-chain-security/ii-establish-control)

Use that planning principle to ask what access is needed for this assignment. Record any uncertainty for the person who can resolve it. Keep passwords, entry codes and detailed security configurations out of a general work request; refer to the organisation’s approved records instead.

## Copy this access review record

The following is an editorial template for coordinating a request. It does not issue a pass, change an account or establish that access has been withdrawn.

| Record | What to capture |
| --- | --- |
| Work reference | Link the agreed task and identify its internal sponsor. |
| Access scope | Describe the relevant area or service at an appropriate level of detail. |
| Timing | Record the intended start, end and next review date. |
| Extension decision | Identify who may approve a revised requirement and where the decision is recorded. |
| Closure owner | Name the team responsible for confirming the access outcome. |
| Completion evidence | Refer to the approved record showing what was checked or completed. |
| Open questions | Record missing information, its owner and the follow-up date. |

Adapt the fields to the organisation’s existing process. Where separate teams manage building entry and business accounts, give each its own closure action. One team’s completed action does not confirm that another team has finished.

NIST’s Cybersecurity Framework 2.0 describes access permissions being defined, managed and reviewed. It also includes managing physical access according to risk. These are high-level outcomes; the framework does not prescribe how to achieve them. [See PR.AA-05 and PR.AA-06 on printed page 20, and the introduction.](https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf#page=25)

The UK and US sources are used here as general planning references. The template is not a statement that a particular access system meets a standard or that a business has completed a security assessment.

## When the assignment runs into another day

Imagine a supplier’s workplace visit finishing later than expected. The supplier needs to return, but the original access period is about to end. This is a hypothetical coordination example, not an OpTyTech project or a description of a real site.

The internal sponsor could record the revised work requirement and ask the authorised approver to decide on the extension. Until that decision is recorded, the request would say “extension requested”, with an owner and follow-up date. It would not describe the extension as approved.

Once the responsible teams have acted, the record can point to their confirmation. If one action remains open, keep it visible. A completed job and a completed access review are separate entries, even when they concern the same visit.

## Bring the unresolved access questions to the right team

Before the next visit, identify the request whose end date or ownership is unclear and send it through the organisation’s authorised process. Ask for a recorded decision on the specific gap. Keep any change to the access system with the people authorised to make it.

For help framing a workplace security requirement, explore [OpTyTech Security](https://optytech.com/security/)
 or [contact OpTyTech](https://optytech.com/contact-us/)
. Bring the purpose of the work, the operating context and the questions still to be agreed.

[← Back to the blog](https://optytech.com/blog/)

## OpTyTech contact and useful links

- [Email info@optytech.com](mailto:info@optytech.com)
- Telephone: +353896069735
- [LinkedIn](https://www.linkedin.com/company/optytech)
- [Home](https://optytech.com/)
- [Services](https://optytech.com/services/)
- [About](https://optytech.com/about-2/)
- [Contact](https://optytech.com/contact-us/)
- [Policies](https://optytech.com/policies/)
- [Blog](https://optytech.com/blog/)
- [Insights](https://optytech.com/insights/)
- [Privacy policy](https://optytech.com/policies/#DataProtectionPolicy)
