Skip to content

SecurePoint Visitor

Visitor management for regulated sites.

Hosts invite visitors ahead of time, visitors check in at a lobby kiosk or the front desk, and every visitor is screened before a badge prints. A possible match waits for a person to decide, and each step stays on the visit record.

Pictured: the Front Desk Dashboard in a demo organization with fictional visitors.

The SecurePoint front desk roster for a demo organization, with three visitors marked On hold: security review. Each row tells the desk the visitor is not checked in, not to issue a badge, and that compliance will decide.
Pre-registered or walk-in
Hosts invite visitors ahead of time. Walk-ins check in at the kiosk or the desk.
Screened before the badge
Screening runs when a visitor registers, or at the kiosk for walk-ins.
Held for a person
A possible match waits for a reviewer, who records the decision and a reason.
No badge until the checks clear
Pending reviews, missing NDAs and incomplete screening stop the print.
Hosts told on arrival
An email when a cleared visitor checks in, and a text where texting is set up.
10-year decision records
Screening and review records can't be deleted for 10 years.

A visit, start to finish.

Five steps, and each one leaves a record. The film follows one visit in a demo organization with fictional visitors.

  1. 1

    The host invites the visitor

    When the visitor fills in their details, they are screened against sanctions and restricted-party lists. Once cleared, a QR code arrives by email.

  2. 2

    The visitor checks in

    Pre-registered visitors scan that QR code at the lobby kiosk. Walk-ins are screened when they check in, at the kiosk or the desk.

  3. 3

    A person reviews any possible match

    The visit is held until a reviewer decides. Who decided, when, and the reason go on the record.

  4. 4

    The host is told and the badge prints

    When the checks clear, the host gets an email, or a text where texting is set up, and the badge prints at the kiosk or the desk.

  5. 5

    The visitor checks out

    At the kiosk with the QR code on their badge, or at the desk. The time and who checked them out are recorded.

Read the transcript

At a defense plant or any regulated site, the front desk should know who is walking in, screen them, and keep a record of every decision.

A host invites their visitor ahead of time. When the visitor fills in their details, SecurePoint screens them against U.S. and international sanctions and restricted-party lists.

Once they're cleared, a QR code arrives by email.

At the lobby kiosk, they scan the code and their ID, sign the visitor agreement, and take a badge photo.

If a name looks like a possible match, the visit is held until a reviewer decides, and their reason goes on the record.

When everything checks out at check-in, the host gets an email that their visitor has arrived, and the front desk prints the badge.

Every check-in, screening result and decision is logged, so when an auditor asks, you can export the evidence.

SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

At the front desk and the kiosk.

The desk and the lobby kiosk work from the same visit records, for the site the operator is working.

The desk sees the whole day on one screen.

The Front Desk Dashboard, pictured at the top of this page, lists who is expected today, who is on site, who is waiting on a review and who has left. Today's pre-registered visitors are listed ahead of time, and anyone past their expected time is flagged.

When a visit is missing something the site requires, such as the NDA, the safety briefing or a photo of the ID, the visit lists it and the desk can finish it before the badge prints.

Read the transcript

Step 1. Open the visitor's record. Missing for this visit lists what's left.

Step 2. Select NDA. Have the visitor sign it here, or send it to their phone and keep this window open.

Step 3. Select Safety Briefing. Have them watch it here, or send it to their device the same way.

Step 4. Select Headshot, capture the visitor's face, and save it for the badge.

Step 5. If you have ID Vault, select ID Front, then capture and save their ID.

Once nothing is missing for a cleared visitor, select Badge to open the preview.

Screen visitors at check-in. Keep the decisions on record.

Visitors can check themselves in.

Pre-registered visitors scan the QR code they were emailed, and walk-ins start with their ID. Depending on the site's rules, check-in covers ID capture, a badge photo, U.S.-person status and the visitor agreement.

Get the SecurePoint Kiosk app from the App Store on an iPad, or from Google Play on an Android tablet. Both are available in the United States. The kiosk also runs in a browser on the tablet or PC already in the lobby.

SecurePoint visitor kiosk welcome screen on a portrait tablet for a demo facility: a Scan ID or QR button, an ID required for entry note, and a Check out button.

Check out, or revoke with a reason.

At the end of a visit, the visitor scans the QR code on their badge at the kiosk, or the desk checks them out. The time and who did it are recorded. Revoking is not an early check-out: it takes a reason, ends the visit, and records the visitor as denied.

Read the transcript

On the Front Desk Dashboard, Check out and Revoke look alike, but do different jobs.

Step 1. When a visit ends normally, select Check out.

Pick a reason, then select Confirm Checkout. The time and who did it are recorded.

Step 2. To remove someone, select Revoke. It's not an early check-out.

Revoke requires a reason. Keep it short, with no names, then select Revoke Access.

The visit ends, and the visitor is recorded as denied, with your reason.

Recent activity tells them apart: Out for a check-out, Revoked for a revoke.

Screen visitors at check-in. Keep the decisions on record.

When screening finds a possible match.

Screening runs when a visitor registers, or at the kiosk for walk-ins. Each list refreshes on its own schedule.

The visit waits for a person.

Visitors are checked against named lists: OFAC SDN and SSI, BIS Entity and Denied Persons, UN, UK, EU and more. When a name comes back as a possible match, the visit is held and no badge prints until an authorized reviewer records a decision and the reason.

Name matching is fuzzy matching, not AI: it looks for close spellings as well as exact names. By default an AI provider named on the subprocessors page also writes a summary of each screened name for the reviewer.

Read the transcript

Sometimes the details match. Here the date of birth and the country are the same as the list entry, and the name is nearly the same.

Do not clear a case like this on a hunch. For a match this strong, Not a Match needs a different date of birth or ID document, or a second reviewer.

Step 1. The visitor stays on hold. Nothing on this screen releases them until a decision is recorded.

Step 2. If you are not sure, choose Send for Senior Review. Choose the reason and write what you found. Your organization's compliance admins get an email.

Your note stays on the case. The next reviewer sees it with your name.

Step 3. If you are sure this is the listed person, choose Deny Access. Choose the reason and write the note. The program shows what will happen and asks you to confirm.

Access is refused and no badge prints.

Step 4. Follow your organization's own sanctions procedure from here. SecurePoint records the decision. It does not file reports for you.

Reviewers work from one queue.

Held visitors wait in the compliance queue with their best match, candidates, age and assignee, and the queue shows how long each review has been waiting. A reviewer records one of four decisions: not a match, approve the visit, deny access, or send it for senior review.

Clearing a strong match takes a written reason, and the strongest also need a date-of-birth or ID mismatch, or a second reviewer.

The SecurePoint adjudication queue for a demo organization: tabs for visitor check-ins, screening reviews and all cases, counts of the cases that need a decision and of the decisions made in the last 30 days, chips for an escalated case and for screenings that did not finish, and held visitors with their best match, candidates, age and assignee.

The badge, and the host.

The badge reads from the visit record, so it prints only what the visit has and waits for what it is missing.

The badge waits for the checks.

Each site's security profile sets what a visit needs: host approval, ID capture, an NDA or safety briefing, an escort. The visit lists what is still missing, with optional items kept apart from required ones, and the badge does not print until screening has cleared and the required items are done.

Only a staff role allowed to override can print past a missing step, and it takes a written reason. A required escort can't be skipped that way.

SecurePoint Visitor detail screen showing the host, the escort requirement, and the documents outstanding before a badge can be issued

It prints at the kiosk or the desk.

Badges print on the Brother QL-820NWB with DK-2251 labels, which SecurePoint supports. A person releases each one: the host or the desk taps Print Badge once the visitor is cleared.

The SecurePoint Kiosk app on an iPad or Android tablet, and a Windows PC running the SecurePoint Print Connector, print with no print window. At the desk, the browser's print window may open, as it does in the film.

Read the transcript

Admins set up a badge template for each visitor type: the shape, a black or red stripe, and what the badge shows.

A print check confirms the layout fits the label before anything prints.

At the front desk, a badge is available once the visitor is checked in and cleared.

It carries their photo, company and host, the hours it's valid, and a QR code. At an export-controlled site, it also shows their screening and escort status.

It prints on a Brother QL-820NWB label printer. Finish in your browser's print window if one opens.

The visit record now shows the badge was sent to print.

At the end of the visit, they scan the badge's QR code at the kiosk to check out.

SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

Hosts invite, and hear when their visitor arrives.

Host Hub is the host's own portal. Hosts invite visitors before they arrive, see the screening status of each invite, and complete after-visit reports. When a cleared visitor checks in, the host gets an email, and a text where texting is set up.

SecurePoint Host Hub: a host's own portal showing pending after-visit reports, pending invites, and the invite action.

Set up a site, then show the record.

Short films for the admins who set a site up, and for whoever answers the auditor afterwards.

  • Set up the NDA and safety briefing

    Visitors sign the NDA and acknowledge the safety briefing at the kiosk, and both are saved with the visit.

    Read the transcript

    Step 1. In Admin, under Compliance, open NDA and safety, and select Set up the default NDA. The default is used at every site, unless you add an exception.

    Step 2. It starts with a sample NDA for your counsel to review. Give it a title that says NDA, and paste in your agreement text. What the kiosk shows previews it.

    Step 3. Tick Show visitors the safety video. Paste a YouTube link, or upload an MP4 or WebM file.

    Step 4. Select Save. The overview shows both steps on, and Recent changes lists who saved it.

    Step 5. Under Check what a visitor gets, pick a site to see what a visitor signs and is shown.

    At the kiosk, visitors sign the NDA, then acknowledge the safety briefing. A QR code check-in skips whichever they finished while registering, unless the site requires them at every visit.

    Both are saved with the visit and shown on its Compliance tab.

    Screen visitors at check-in. Keep the decisions on record.

  • Set up and assign a badge template

    One template per visitor type, with a preflight check before it is saved and a preview of what each site prints.

    Read the transcript

    Step 1. In Admin, open Badges, and Duplicate the template closest to what you need.

    Step 2. In Quick Edit, name it, choose what the badge shows, and set text sizes.

    For exact positions and sizes, switch to Advanced Design.

    Step 3. Try a long sample name, and check that Preflight says Ready. Then select Save.

    Step 4, for org admins. In Badge assignments, choose it for a visitor type.

    Nothing is live until you select Review Changes, then Apply Assignments.

    Step 5. What Will Actually Print shows which template each site prints.

    At the front desk, the contractor's badge preview shows the same template.

    Screen visitors at check-in. Keep the decisions on record.

  • Export the record for an auditor

    Screening results, review decisions and audit records for a date range, in one ZIP file with an SHA-256 checksum for each file.

    Read the transcript

    When an auditor asks how visitors were screened, an admin opens the Evidence Center and picks a template and a date range.

    SecurePoint builds a ZIP file with screening results, review decisions and audit records from that period, and its manifest lists an SHA-256 checksum for each file.

    Evidence Pack History keeps each sealed pack, so a later download is the same file, with the same checksum.

    The audit ledger shows who did what, and when: check-ins, screening results, reviewer decisions, and exports.

    Users can't edit or delete ledger records, and exports from this page come with an SHA-256 checksum.

    SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.

See it with a visit you run every week.

Bring a sample visit. We'll check in a visitor, hold a possible match, print the badge and check the visitor out.

Frequently asked questions

What is SecurePoint Visitor?
Visitor management software for regulated facilities, delivered as a hosted service. It covers pre-registration, check-in at a lobby kiosk or the front desk, ID capture, sanctions screening, host notifications and badge printing. It keeps an append-only, hash-chained audit log that application users cannot edit or delete, with a verifier that checks the chain.
Which lists does SecurePoint screen visitors against?
Named government sanctions and watch lists, including OFAC SDN and SSI, BIS Entity and Denied Persons, Section 1260H, UFLPA, the UN Security Council list, the UK Sanctions List, EU financial sanctions, the French asset-freeze register, World Bank and IADB debarments, and INTERPOL Red Notices and FBI Most Wanted. Screening runs when a visitor registers, or at the kiosk for walk-ins, and each list refreshes on its own schedule.
What happens when a visitor is a possible match?
The visit is held, and no badge prints. An authorized reviewer compares the visitor with the list entry and records a decision and a reason: not a match, approve the visit, deny access, or send it for senior review. The decision, who made it and when go into the audit log. Name matching is fuzzy matching, not AI. By default an AI provider named on the subprocessors page also writes a summary of each screened name for the reviewer.
How does badge printing work?
A badge prints once the visitor is checked in and cleared and the site's required steps are done. It shows the visitor's photo, company and host, the hours it is valid and a QR code for checking out, and at an export-controlled site their screening and escort status. It prints on a Brother QL-820NWB with DK-2251 labels, from the SecurePoint Kiosk app on an iPad or Android tablet, from a Windows PC with an Intel or AMD processor running the SecurePoint Print Connector, or through the browser's print window at the desk.
Can hosts pre-register visitors?
Yes. In Host Hub, hosts invite visitors before they arrive, and screening runs when the visitor registers. When a cleared visitor checks in, the host gets an email, and a text where texting is set up. Host Hub is the host's own portal, so hosts don't need front-desk access.
Does SecurePoint Visitor support ITAR and CMMC programs?
It supports both. It doesn't certify either one, and it doesn't file with any agency. At a site marked ITAR-controlled, visitors attest U.S.-person status at check-in, a foreign national needs an escort and host verification, and the desk can't admit them until an escort is assigned. For CMMC Level 2, visitor records are direct evidence for PE.L2-3.10.3 and PE.L2-3.10.4, support PE.L2-3.10.1 and PE.L2-3.10.5, are partial for PE.L2-3.10.2, and do not address PE.L2-3.10.6.
How is the audit trail kept?
Check-ins, host approvals, screening decisions, badge prints and check-outs are written to an append-only, hash-chained audit log that application users cannot edit or delete, with a verifier that checks the chain. Screening and review records can't be deleted for 10 years. Evidence packs export the visits, screening results, decisions and audit trail for the date range and sites you pick.
Are the screenshots and films on this page the real product?
Yes. They come from the running SecurePoint Visitor application, in a demo organization with fictional visitors. No customer data appears in them.
Is there a per-screening fee?
No. Visitor plans are priced per site, with unlimited visitor screenings.