← Feocey Blog

Visitor management procurement

Visitor Management System With an ID Scanner: What Data Do You Actually Need?

Evaluate a visitor management system with an ID scanner by separating an identity check, the reception record, and the credential used at the entrance.

Illustrative reception counter with a blank mock ID card and a visitor sign-in tray

Before you choose

Key takeaways.

  • Give each proposed ID field an owner and a specific purpose before deciding whether to capture it.
  • Check what stays in the scanner, visitor platform, exports, and logs when raw images are disabled.
  • Test the door credential separately from the reception team's identity check.

Decide what the reception team needs to establish

A visitor management system with an ID scanner should collect the information your reception process actually uses. Define the result the receptionist needs before choosing which fields to scan, store, or share. For one office, the result may be a visual check that the guest matches the appointment. Another site may require a specific recorded field for a documented reason. Start with the visit policy and ask the supplier to show a workflow that fits it.

Describe a real type of visit without using a real guest's information. For example, a maintenance contractor arrives at a shared office for a scheduled appointment. The receptionist needs to confirm the appointment, identify the appropriate host, and follow the site's approval process. The doors need a decision about a specific credential and time window. Each step should be able to stand on the information it needs from the prior step.

Separate viewing, capture, and retention

Viewing a document at the desk is one interaction. Capturing selected fields creates a record the system may share with other services. Keeping an image or raw scan adds a different type of data to manage. Ask whether the scanner brings fields into memory before filtering them, and whether the device, its companion app, or the vendor service keeps images, logs, or diagnostic data. A short list of visible fields does not by itself show what the underlying system processed.

The Federal Trade Commission's business guide on protecting personal information recommends taking stock of personal information and keeping what the business needs. Apply that starting point to your specific visit types. Ask the site policy owner to determine the required data and handling before setting an expiration period or enabling a scanner option.

Design the fallback while the workflow is still being evaluated. A visitor may have a document the scanner cannot interpret, the reader may be unavailable, or the guest's appointment may use a different name format. Give reception a clear way to reach an authorized person and record the decision in the visit history. An exception process should make it clear which steps still need to be completed before access is granted.

Ask for a field-by-field example of what the host receives. If the host only needs an arrival notification, verify that the notification can identify the appointment without attaching the document scan or copying its fields to email. Repeat the check for an export sent to facilities and an incident report sent to a designated reviewer. Different recipients may need different records.

Example field review for a scheduled office visit
InformationQuestion for the buyerDemonstration evidence
Appointment and hostCan the desk find the right visit using the invitation?Reception retrieves the appointment and confirms the responsible host.
Identity check resultWould a reviewer need the result, who checked it, and when?The visit record shows the outcome and the authorized reviewer.
Additional document fieldWhich approved process needs this field after the visit?The buyer locates the field, its access settings, and its configured retention.
Raw document imageWhat documented purpose would justify keeping an image?The vendor shows the configured behavior in the device, service, and exports.

Keep identity decisions with the right system

The reception platform determines whether the visitor can proceed under the site's policies. A separate pass can identify the authorized visit and carry the minimum information needed for entry validation. Ask the integrator to show what the credential contains, which service looks it up, and which component authorizes the entrance. Avoid designs that put raw ID details into a pass, a device message, or a general access event as a shortcut to link records.

The Feocey FC7735 is a QR reading point for interactions at the entrance. If you evaluate it downstream of visitor reception, test with the planned QR credential, the selected reader interface, and the host that makes the access decision. An ID scanner used by the reception desk is a separate component to qualify. In the pilot, confirm that an approved reception check, issued pass, reader interaction, and actual entry are distinguishable in the systems that own those records.

Ask for a demonstration with synthetic documents

Give each supplier the same fictional visitor, appointment, and two sample documents approved for testing. Establish which fields the visitor policy authorizes and which the system should avoid retaining. Ask to see the actual scanner configuration and inspect each system that receives the sample. Use an export to verify the visible fields, an ordinary receptionist account to verify role boundaries, and a permitted administrator account to inspect the relevant settings.

Start with a successful check. Then repeat the test with a document type the scanner cannot read and with the integration temporarily unavailable in the demo environment. Verify that the exception reaches the assigned reviewer and that the system gives the visitor a clear next step. Ask the vendor to demonstrate how an eligible sample expires or is deleted under the configured rule, including how backups and diagnostic records are handled under the service agreement.

Bring the field list, scanner option, and sample pass flow to the final supplier review. If you are evaluating the entrance reading point, contact Feocey about the FC7735 and your receiving system. For the end-to-end reception workflow, see the office visitor management handover guide. Use the pilot result to decide whether the scanner adds enough value to justify the data it needs to process.

  • Who owns the field list and can change an optional capture setting?
  • Which device, application, service, logs, and exported records can hold the test scan or its fields?
  • What can a receptionist, site administrator, or integrator see without broader access?
  • How will a reviewer verify that the pass refers to the correct visit while the door system receives only expected information?

Source references

FC7735 user manual ↗

Put the guide to work

Find the reference for your model.

Compare each device with your requirements. Confirm configuration and compatibility for the complete installation.

Discuss your project ↗

Interested in this guide?

Tell us the model and quantity.