Overview
A Check-In Puck is a physical Contactless Check-In point that users tap with a compatible mobile phone.
Pucks can be placed at locations such as:
Main Reception
Staff Entrance
Visitor Entrance
Staff Room
Sixth Form Entrance
Residential Entrance
Departments
Remote buildings
Alternative entrances
When a user taps a Check-In Puck, their phone opens the appropriate Custr check-in or check-out experience.
Depending on the user and the features enabled for the site:
Visitors enter their name and follow the visitor check-in process.
Staff with the Companion App can continue through the app.
Staff without the Companion App can use Secure Check-In with a four-digit PIN, where enabled.
Sixth Form students can use the Companion App or Secure Check-In with a four-digit PIN, where enabled.
Residents can use Secure Check-In with a four-digit PIN, where enabled.
Check-In Pucks may be supplied as:
NFC-only Pucks
NFC and QR Pucks
An NFC-only Puck is used by tapping it with a compatible mobile phone.
An NFC and QR Puck gives users two ways to open Contactless Check-In:
Tap the Puck with their phone
Scan the QR Code printed on the Puck
Each physical Puck must be programmed before it can be used.
Please Note: Check-In Pucks will not work if stuck directly to a metal surface.
Pricing & Activation
Check-In Pucks are purchased individually and require Check-In Puck Activation to be enabled for the site.
Check-In Puck
£19.99 + VAT each
This is a one-off cost for each physical Check-In Puck.
Check-In Puck Activation
£60 + VAT per site, per year
Check-In Puck Activation enables your site to use and manage NFC Check-In Pucks with Custr.
Once activated, you can configure and manage as many Check-In Pucks as required for that site during the 12-month activation period.
The annual activation charge applies per site, not per Puck.
For example, if you require five Check-In Pucks at one site, you would purchase five physical Pucks but only require one annual Check-In Puck Activation for that site.
Choosing Your Check-In Puck Design
Check-In Pucks are available in two visual designs.
Both designs provide the same Custr functionality, so the choice is based purely on which appearance you prefer.
When ordering, please confirm whether you would like Design 1 or Design 2.
NFC only – users tap the Puck using a compatible mobile phone.
NFC + QR – users can either tap the Puck or scan the printed QR Code.
Before You Begin
Check-In Pucks are programmed through the Custr Companion App.
The user programming the Puck must:
Have access to the Companion App
Be signed in to the correct organisation and site
Have the relevant NFC programming permission enabled through Roles & Permissions
Use a compatible mobile phone with NFC available
Have the physical Puck available
Only Companion App users with the appropriate permission will see the NFC programming tools within Settings.
The Enable puck scan on Check In button setting is not required to program a Puck.
It controls whether NFC scanning is available through the Companion App check-in button during normal staff check-in.
Opening the NFC Settings
To access the NFC tools:
Open the Custr Companion App.
Open Settings.
Scroll to the Check-In Puck section.
Depending on the user’s permissions, the available options may include:
Enable puck scan on Check In button
Get puck information
Program a Check-In Puck
Erase a Check-In Puck
View available Pucks
Programming a New Check-In Puck
To program a new Puck:
Open the Companion App.
Open Settings.
Select Program a Check-In Puck.
Select Start Scanning.
Hold the back of the phone near the Check-In Puck.
The Companion App scans the Puck to determine whether it is empty and ready to be programmed.
If the Puck Is Empty
If the Puck does not contain an existing NFC record, the Companion App displays a confirmation that it is ready.
Select Choose tag name to continue.
Choosing a Puck Name
The Companion App allows the user to create a new NFC record as part of the programming process.
Enter a name that identifies the physical location where the Puck will be installed.
Examples include:
Main Reception
Staff Entrance
Staff Room
Visitor Entrance
Sixth Form Entrance
Residential Entrance
North Building
Car Park Entrance
The name is used to help administrators identify the Puck within Custr and understand which check-in location was used.
The Puck name does not change the check-in workflow or user permissions. It acts as a location label.
Each physical Puck should have its own record.
Do not program multiple physical Pucks using the same record.
Where more than one Puck is installed in a similar location, use clear unique names, such as:
Staff Entrance 1
Staff Entrance 2
Main Reception Left
Main Reception Right
After entering or selecting the required name, continue to the next step.
Writing the NFC Record
The Companion App displays the selected Puck name before programming begins.
Check that the correct name has been selected, then:
Select Program a Check-In Puck.
Hold the Puck close to the back of the phone.
Keep the phone and Puck still while the record is written.
Wait for the Companion App to confirm that the NFC record has been written.
Security is applied during programming where supported.
Do not move the Puck away from the phone until the app confirms that the writing process has completed.
Confirming Whether the Puck Has a QR Code
Near the end of the programming process, the Companion App asks whether the physical Puck also includes a QR Code.
The user must select the option that matches the Puck being programmed.
The choices are:
The Puck has a QR Code
The Puck does not have a QR Code
This question cannot be skipped because Custr needs to know whether the Puck supports NFC only or both NFC and QR.
Pucks Without a QR Code
Where the Puck is NFC only:
Select the option confirming that the Puck does not have a QR Code.
The Companion App completes the programming process.
Wait for the programming confirmation screen.
The Puck can then be used by tapping it with a compatible mobile phone.
Pucks With a QR Code
Where the Puck includes both NFC and a QR Code:
Select the option confirming that the Puck has a QR Code.
The Companion App opens the phone camera.
Scan the QR Code printed on the physical Puck.
Wait for the app to confirm that it has been read.
Complete the programming process.
The QR Code is read so that Custr can configure it to open the same Contactless Check-In location as the NFC function.
The QR Code must be scanned during programming so that it can be associated with the new Contactless Check-In point.
If the QR Code is not scanned, Custr cannot configure the QR part of the Puck correctly.
Programming Complete
Once the process has completed successfully, the Companion App displays a confirmation screen.
This includes:
The Puck name
The security status
Whether write access is allowed
Confirmation that programming has completed
The screen may show:
Security: Protected
Write access: Allowed
Select Done to finish.
It is good practice to test the Puck immediately after programming.
Tap it using a compatible phone and confirm that the correct Contactless Check-In experience opens.
Where the Puck includes a QR Code, scan the QR Code separately and confirm that it also opens Contactless Check-In.
Understanding Puck Security
Security is applied to the Check-In Puck during programming where supported.
A protected Puck is designed to prevent unauthorised NFC-writing applications from changing or overwriting the record.
Depending on the physical NFC hardware, some Pucks may have different write or protection capabilities.
A protected Custr Puck may still be managed through the Custr Companion App, but it must normally be erased before it can be programmed again.
The confirmation screen shows the security and write-access status after programming.
Programming a Puck That Already Contains Data
If the Companion App detects that the Puck already contains an NFC record, it will not immediately overwrite the existing information.
The existing record must be erased before the Puck can be programmed again.
This applies to:
Previously programmed Custr Pucks
Pucks containing another NFC record
Pucks being moved to another location
Pucks being renamed or reused
Use Erase a Check-In Puck before starting the programming process again.
Erasing a Check-In Puck
To erase a Puck:
Open the Companion App.
Open Settings.
Select Erase a Check-In Puck.
Hold the phone near the Puck.
Follow the instructions displayed in the app.
Wait for confirmation that the NFC data has been erased.
The user must be viewing the site associated with the Puck in order to erase it.
For example, a Puck programmed for Site A must be erased while the Companion App is viewing Site A.
After erasing the Puck, it can be programmed again using a new or existing location name.
Where the physical Puck includes a QR Code, the QR Code should also be scanned again during the new programming process.
Getting Puck Information
The Get puck information option allows an authorised Companion App user to scan a Check-In Puck and view information about it.
This can be used to identify:
Which Custr site the Puck belongs to
Whether the Puck has been programmed
Information held against the NFC record
To view the information:
Open the Companion App.
Open Settings.
Select Get puck information.
Hold the phone near the Puck.
Review the information displayed.
This can be useful when:
A Puck has been removed from its original location
The location name is unclear
An administrator needs to confirm which site it belongs to
A Puck needs to be erased or reprogrammed
Several Pucks are being installed at the same time
Viewing Available Pucks
The View available Pucks option displays the NFC records available for the current site.
This allows authorised users to review the Check-In Pucks that have been created.
The list may include names such as:
Reception
Staff Entrance
Staff Room
Sixth Form Entrance
Residential Entrance
Each physical Puck should have its own unique record.
The available-Pucks list is useful for checking:
Which locations have already been created
Which names are already in use
Whether a Puck record exists for a particular entrance
Which name should be selected or avoided when programming a new Puck
Enabling NFC Through the Companion App Check-In Button
The Companion App includes an Enable puck scan on Check In button setting.
Where enabled, staff selecting the check-in button in the Companion App can be prompted to scan or tap a Check-In Puck as part of the attendance process.
This setting relates to normal staff check-in and check-out.
It is separate from the permissions required to program, inspect or erase Pucks.
Whether staff can check in directly without scanning a Puck depends on the organisation’s Roles & Permissions settings.
How Users Check In Using a Puck
Once programmed and installed, the user taps the Puck with a compatible mobile phone.
The journey depends on the user type.
Visitors
Visitors are taken to Contactless Check-In.
They:
Enter their name.
Allow Custr to search for an Invite or Pre-Approved Visitor record.
Select the relevant record where found.
Continue as a Standard Visitor where no match is found and the site permits it.
Complete the relevant visitor questions, documents and other requirements.
Visitors do not need to install an app.
Staff With the Companion App
Staff with access to the Companion App can tap the Puck and continue through the app.
The Companion App identifies the member of staff through their signed-in account.
Any configured staff check-in or check-out questions are still displayed.
Staff photo capture does not take place through the Companion App.
Staff Without the Companion App
Staff without the Companion App can use Secure Check-In with a four-digit PIN, where enabled.
They:
Tap the Puck.
Open Secure Check-In in their phone browser.
Enter their four-digit PIN.
Confirm the identity displayed.
Answer any configured staff questions.
Complete their check-in or check-out.
Staff photo capture does not take place through Secure Check-In.
Sixth Form Students
Sixth Form students can use a Check-In Puck through the Custr Companion App or through Secure Check-In, depending on how the site is configured.
Where the student has Companion access, they can:
Tap the Check-In Puck using NFC
Scan the QR Code printed on the Puck, where included
The Companion App identifies the signed-in student and records the appropriate check-in or check-out against their Sixth Form record.
Sixth Form students can also use Secure Check-In with a four-digit PIN, where enabled.
Their attendance is recorded against the same Sixth Form student record regardless of which method they use.
Residents
Residents do not use the Companion App.
Where Secure Check-In is enabled, they:
Tap the Puck.
Enter their four-digit PIN.
Confirm their identity.
Answer any configured questions.
Complete the check-in or check-out determined by their current status.
No resident photograph is captured during check-in or check-out.
Pucks With NFC and QR
Where a Check-In Puck includes both NFC and QR, users can either:
Tap the Puck with a compatible phone
Scan the printed QR Code
Both options open Contactless Check-In for that location.
The QR Code is particularly useful where:
The phone does not detect the NFC tap
The user is unsure where the phone’s NFC antenna is located
NFC is disabled on the phone
The user prefers to scan a QR Code
The QR Code does not turn the Puck into a QR reader. The user scans the printed code using their own phone.
Check-In Pucks Are Not RFID Readers
Check-In Pucks and RFID Readers perform different functions.
A user cannot check in by tapping an RFID card or fob against a Check-In Puck.
Check-In Puck
Used with a mobile phone
Opens Contactless Check-In or the Companion App
Does not need to be connected to a Reception Kiosk
Can be installed away from reception
Cannot read RFID cards or fobs
Programmed through the Companion App
RFID Reader
Used with compatible RFID cards or fobs
Reads an RFID credential directly
Must be connected to a Reception Kiosk tablet
Normally operates alongside the Reception Kiosk
Designed to read supported RFID cards or fobs
Configured as Reception Kiosk hardware
Check-In Pucks are not replacements for RFID Readers.
Installation and Naming Best Practice
Before installing Pucks, plan where users will need to check in and out.
Good locations may include:
Main entrances
Staff-only entrances
Reception areas
Sixth Form areas
Residential entrances
Staff rooms
Departments
Remote buildings
Event spaces
Use names that clearly identify the location.
Avoid vague names such as:
Puck 1
NFC 2
New tag
Entrance
Prefer names such as:
Main Reception
Staff Entrance 1
Sixth Form Entrance
Residential Main Door
North Building Staff Room
Each physical Puck should have its own record, even where several Pucks are installed close together.
After programming:
Test the NFC tap
Test the QR Code, where included
Confirm that the correct location opens
Install the Puck where it is easy to see and reach
Avoid placing it where users may mistake it for an RFID Reader
Make sure instructions clearly tell users to tap or scan using their mobile phone
Troubleshooting
The Companion App Does Not Show the NFC Settings
Confirm that:
The user is signed in to the Companion App
The user has the relevant Roles & Permissions
The user is viewing the correct organisation and site
The app is up to date
The phone supports the required NFC functionality
Only authorised Companion App users can see and use the programming tools.
The Phone Cannot Detect the Puck
Try the following:
Move the Puck slowly around the back of the phone
Remove a thick phone case
Confirm that NFC is available and enabled
Keep the Puck still while scanning or writing
Try the top or centre area of the back of the phone
Confirm that the Puck is not damaged
Close and reopen the programming process
The location of the NFC antenna differs between phone models.
The App Says the Puck Already Contains Data
The Puck must be erased before it can be programmed again.
Use Erase a Check-In Puck, then restart the programming process.
The Puck Cannot Be Erased
Confirm that:
The Companion App is viewing the site associated with the Puck
The user has the required permissions
The phone can detect the Puck
The Puck is held in the correct position
The Puck has not been permanently locked by unsupported NFC-writing software
Some NFC hardware may not allow records to be changed once permanently locked.
The QR Code Was Not Scanned During Programming
Where the physical Puck includes a QR Code, it must be scanned during programming.
Erase the Puck and repeat the programming process, selecting the option confirming that the Puck has a QR Code.
Scan the printed QR Code when prompted.
The Puck Opens the Wrong Location
Use Get puck information to confirm the site and NFC record stored on the Puck.
Where necessary:
Erase the Puck.
Program it again.
Select or create the correct location name.
Scan the QR Code again, where included.
Test the Puck before reinstalling it.
An RFID Card Does Not Work With the Puck
This is expected.
Check-In Pucks only work with mobile phones. They cannot read RFID cards or fobs.
An RFID Reader connected to the Reception Kiosk is required for RFID credentials.
Important Notes
Check-In Pucks are programmed through the Custr Companion App.
A valid Check-In Puck Activation is required for the site to use and manage Check-In Pucks.
Check-In Puck Activation costs £60 + VAT per site, per year.
Physical Check-In Pucks cost £19.99 + VAT each.
One site activation allows you to configure and manage as many Pucks as required at that site.
The Companion App user must have the relevant Roles & Permissions.
The Companion App creates a new NFC record during the programming process.
Each physical Puck must have its own record.
Puck names are location labels and do not change the check-in workflow.
NFC-only Pucks are completed without scanning a QR Code.
NFC and QR Pucks require the printed QR Code to be scanned during programming.
The QR scan creates the QR Contactless Check-In connection for that Puck.
An existing programmed Puck must be erased before it can be reprogrammed.
A Puck can only be erased while viewing the site it belongs to.
Get puck information identifies the site associated with the Puck.
View available Pucks shows the Puck records available for the current site.
Security protection helps prevent unauthorised apps from overwriting the NFC record.
Users tap Pucks using a compatible mobile phone.
Pucks cannot read RFID cards or fobs.
Pucks are not replacements for RFID Readers.
RFID Readers must be connected to a Reception Kiosk tablet.
Staff questions still apply through the Companion App and Secure Check-In.
Staff photo capture does not occur through the Companion App or Secure Check-In.
Residents do not have photographs captured during any check-in or check-out method.
Sixth Form students can use the Companion App where access has been provided.
Sixth Form students using Companion can tap or scan a Check-In Puck to check in or out.
Residents do not use the Companion App and can use Secure Check-In with a PIN where enabled.