“They have a clearance” sounds reassuring. But your team still has questions to answer. What information do they need? Where can they go? Who approves the visit?
For organizations with a facility clearance (FCL), clear visitor procedures help teams work through those decisions before granting access. This guide covers classified visits, CMMC visitor requirements, and the records you’ll need afterward. Let’s jump in.
What is a facility security clearance?
A facility security clearance, usually called a facility clearance or FCL, confirms that an organization is eligible to access classified information at a specific level. It applies to the organization, not just the building.
Employees and visitors still need the appropriate personnel clearance and a need-to-know before they can access classified information. An FCL alone doesn’t grant that access.
An FCL is one part of the picture. The requirements below address different types of information and who can access it.
Organizations that handle both classified information and CUI must meet the requirements for each. Having an FCL does not satisfy CMMC or NIST SP 800-171 requirements for protecting CUI.
What must happen before a classified visit?
The NISPOM Rule’s visits provision, 32 CFR 117.16 applies when classified information is expected to be disclosed during a visit for an authorized U.S. government purpose.
Before sharing classified information, the contractor must confirm that the visit requires it, check the visitor’s identity and clearance, and confirm their need-to-know. Under the NISPOM Rule’s visitor requirements, visitors can only access classified information needed for the visit.
The person sharing the information is responsible for confirming need-to-know. An invitation, signed NDA, or identity check alone isn’t enough.
The host contractor checks clearance through a government-designated database or a visit authorization letter (VAL) from the visitor’s employer. If the database is unavailable, the letter needs to include clearance confirmation, visitor and employer details, who they’re visiting, why, and the dates covered.
Visitor registration can help organize the visit, but clearance checks still need to happen through the approved security process.
Build a visitor process your staff can follow
Use these steps to put the requirements into practice. Your FSO can tailor them to your contract, government guidance, and site procedures.
1. Establish what the visitor needs to access
Before confirming the visit, identify the host, purpose, requested areas, and whether classified information or controlled unclassified information (CUI) could be involved.
A maintenance contractor, delivery driver, and cleared program visitor may all arrive at the same entrance, but their access decisions will differ. An unclassified visit should be planned so the guest isn’t exposed to classified information.
Be sure to give hosts a clear way to flag changes, such as a room change or added tour, since they can alter what information a visitor might encounter.
2. Put security review ahead of entry
Assign the FSO or designated security staff responsibility for required clearance verification and visit authorization. Define who confirms need-to-know and who approves the physical areas the visitor may enter.
If your organization uses DISS, authorized security staff can use its visit functions to help manage visit requests. DCSA prohibits printing or taking screenshots of DISS screens, so keep clearance verification within the approved security process instead of adding screenshots to visitor records.
Front desk staff need a clear instruction when approval is missing: whom to contact and where the visitor should wait.
3. Match the person to the approved visit
At arrival, follow the site’s identification procedure and confirm that the person, date, host, and access requested match the authorization. If the visitor isn’t the person who was approved, or they ask to go somewhere that wasn’t approved, send it back for review.
Adding an escort doesn’t fix a mismatch. Any change still needs approval before the visitor goes in.
Once everything matches, explain badge, escort, device, and photography rules before the visitor proceeds.
4. Make escort responsibilities explicit
Make sure escorts are trained on what they’re responsible for, including where visitors can go, what they shouldn’t see or hear, and when to call security.
When a visit requires an escort, name the person responsible and confirm they’re available before the visitor enters the area. Make sure the escort knows the approved route and what to do if the visitor asks to go somewhere else.
Define how handoffs work when the escort takes a break or the meeting moves. Listing a host in your visitor system helps staff coordinate the visit, but it doesn’t prove anyone escorted the visitor. If you need proof that a visitor was escorted, record who escorted them and when.
5. Close the visit as carefully as it began
Make sign-out, badge return, and temporary access removal part of departure. Confirm access removal in the relevant access control system according to its configuration and your procedures.
Record exceptions that need follow-up, such as a missing badge or an unapproved change in route. A scheduled credential expiration and a visitor’s actual departure are different events, so keep the records clear about what each timestamp represents.
CMMC and NIST 800-171: Visitor escort and access log requirements
CUI is unclassified, but it still requires protection. A company can have CUI obligations without holding an FCL.
CMMC Level 2 is based on NIST SP 800-171 Revision 2. Although Revision 3 is available, CMMC hasn’t automatically switched to it. Check which requirements apply to your contract and what your assessment covers.
The relevant Revision 2 physical protection requirements include:
These are just some of the physical protection requirements. Review the full set for the systems, spaces, and equipment covered by your assessment.
A visitor badge doesn’t replace an escort
Under NIST SP 800-171 Revision 2, people with credentials granting permanent physical access aren’t considered visitors for requirement 3.10.3.
For those who are visitors, issuing a badge or notifying a host isn’t enough. Staff still need to escort them and monitor their activity, with records that help show the process was followed.
Look beyond the front desk log
NIST allows paper logs, digital records, or both. Those records may need to cover building entrances and access to rooms where protected systems or equipment are kept.
Your lobby sign-in log may only tell part of the story. Depending on what your assessment covers, you may also need employee access records or door activity from your access control system.
Decide how long to keep access records
The CMMC Level 2 Assessment Guide lets organizations define how long they keep physical access records. It provides an example of keeping paper sign-in sheets for one year, but that isn’t a rule for everyone.
Choose a retention period that meets your contract, legal, and company requirements. Then make sure your deletion settings (and any exported copies) follow that schedule.
Keep useful records without collecting unnecessary sensitive data
Keep the details your team needs to show what happened during a visit. Use this list as a starting point. Not every item is required for every cleared facility:
- Visitor and host. Who attended, their organization, and who was responsible for the visit.
- Purpose and approved scope. Why they came and which areas were authorized, expressed without exposing protected project details.
- Review record. Who completed the required review, when, and an approved reference to supporting authorization where appropriate.
- Escort assignment. Who was responsible and any relevant handoffs.
- Arrival and departure. Recorded sign-in and sign-out times.
- Closeout. Badge return, access removal, and exceptions requiring follow-up.
Keep classified information in systems approved to hold it. Before adding CUI to a cloud service, check with your security team that it’s approved for that use. Marking a field “private” or “sensitive” isn’t enough.
Give reception staff the details they need to manage the visit, while keeping security documents with the people authorized to see them.
How Envoy supports visitor procedures and audit-ready records
Envoy can help teams coordinate the operational steps around a visit:
- Collect visit details. Pre-registration and customizable sign-in flows collect the information needed for each visitor type.
- Route visits for approval. Send invited and walk-up visitors through the required reviews based on your policies.
- Prepare for arrivals. Notify hosts when guests arrive and print badges that help staff identify visitors.
- Connect visitor access. Integrate with access control systems to manage temporary access based on your setup.
- Keep records ready for review. View and export visitor logs, including sign-in and sign-out times, and review approval history within Envoy.
- Control access to sensitive visitor data. Use role-based permissions and retention settings to manage who can see visitor information and how long it’s kept.
For sites with stricter requirements, Visitors Critical brings advanced approvals and audit-ready records to Envoy Visitors, built for teams with the highest security and compliance needs.
Envoy keeps the process organized. Your security team still owns clearance checks, need-to-know decisions, and escort assignments.
—
A well-managed visit gives staff clear steps to follow and security teams records they can rely on. Connecting approvals, arrival procedures, and visit records helps your team put those expectations into practice every day.
Explore how Envoy supports CMMC physical protection workflows. If your visits also involve export-controlled information, see our ITAR visitor management guide for the separate access and disclosure considerations.
Read more
This guide covers what CER means for visitor and contractor access, with practical checks to help teams find gaps and strengthen site resilience.
Explore what a physical security assessment is and learn the steps your team should take to conduct one.
We’ll show you how to put together a visitor process around SQF requirements, with practical steps and records your team can use.
This guide covers CTPAT’s visitor management criteria and the workflows and records that help your team prepare for validation.
This guide covers how visitor management supports FISMA, which NIST controls apply, and what your team needs to document along the way.
In this guide, we’ll break down how cloud digital signage works, how it compares with on-premise signage, cost factors, and what to look for in a solution.

.png)