ITKIT
Airport and road gates · 18 / 20
iBoard
Boarding-pass reader and live headcount at the door
From the problem to how we solve it
October 2026
Interactive prototype · synthetic data only
The problem
Counting by hand.
1
Gate agents count passengers by hand before the door can close.
2
Passengers reach the wrong aircraft and are found late.
3
Bags of passengers who never board are traced late and delay departure.
Passengers at the door · Counted by hand · The door waits · Every pass read
ITKIT · iBoard · Prototype screens, synthetic data
The problem
Our answer
Door closed · 163 on board
A reader at the jet-bridge door checks each pass against flight, gate, group and the passport-control exit record, and shows green, amber or red. The agent tablet keeps the headcount and flags bags of passengers who never board for offload.
How it works · 1 of 5
At the door
GO AHEAD
iBoard reads the pass at the door. Green means go, with a word and an icon, not colour alone.
ITKIT · iBoard · Prototype screens, synthetic data
How it works
How it works · 2 of 5
Wrong gate
STOP · WRONG GATE
A pass for another flight turns amber and tells the passenger where to go.
ITKIT · iBoard · Prototype screens, synthetic data
How it works
How it works · 3 of 5
Not cleared
PLEASE WAIT
No passport-control exit record? Red. The reason goes to the agent only.
ITKIT · iBoard · Prototype screens, synthetic data
How it works
How it works · 4 of 5
Every scan
Decoded to IATA Resolution 792
Every scan is decoded field by field, signatures are checked, and duplicates are caught.
ITKIT · iBoard · Prototype screens, synthetic data
How it works
How it works · 5 of 5
Reconcile
3 no-shows · 2 bags to offload
The agent reconciles no-shows. Their bags are flagged for offload from the iCheck tags.
ITKIT · iBoard · Prototype screens, synthetic data
How it works
What it includes
5 screens and workflows in the prototype
Door reader: green
Boarding passengers at the jet-bridge door
Door reader: amber, wrong gate
Passengers at the wrong door
Door reader: red, not cleared
Passengers who cannot board yet
Agent tablet: boarding and door close
Gate agents
Pass check details
Gate agents and station supervisors
ITKIT · iBoard · Prototype screens, synthetic data
What it includes
Built to standards
International standards it is built to
| Standard | What it covers in iBoard |
|---|---|
| IATA Resolution 792 (BCBP, guide 7th ed.) | Barcode symbologies |
| IATA Resolution 792, item 30 | Airline security data (digital signature) |
| Leading practice (BCBP check-in sequence) | Duplicate boarding detection |
| IATA Resolution 753 | Loading tracking point and inventory at departure |
| IATA RP 1745 | Baggage messages for offload |
| WCAG 2.2 SC 1.4.1 Use of Color | Door outcomes |
| ISO/IEC 27001:2022 and data minimisation | Reasons shown to the agent only |
| Leading practice (door close) | Headcount reconciliation |
We align with these standards; certification is issued by accredited bodies, not by ITKIT.
ITKIT · iBoard · Prototype screens, synthetic data
Built to standards
Connects to
What iBoard works with
Airline departure control systems (DCS)
Airport baggage system and ramp team
iGates and border desks (exit record)
iCheck (bag tags)
Airport operations
ITKIT · iBoard · Prototype screens, synthetic data
Connects to
Safeguards
What iBoard will never do
Hardware is an open decision: flap door or lights only, face match or not.
The reader advises and the gate agent decides who boards.
Not an airline DCS or a baggage system.
ITKIT · iBoard · Prototype screens, synthetic data
Safeguards
How delivery works
Start small, prove it, then scale and hand over
6–10 weeks
Assess
Map what already exists and decide, system by system: reuse, integrate, modernise or build.
4–6 months
Pilot
iBoard at one authority, with real users and a measured outcome, on national infrastructure.
12–24 months
Scale
Roll out by region and service, sharing identity, integration and audit.
Agreed per contract
Operate and transfer
We run it with your team, train them, then hand over operations, code escrow and keys.
ITKIT · iBoard · Prototype screens, synthetic data
Durations are typical ranges, fixed per contract
Next step
See iBoard with a synthetic flight at gate B7.
When the numbers agree, the door closes and the bag inventory goes out. iBoard is a working name. Ask for a demo.
1 · Demo
A guided session on the iBoard prototype
2 · Assess
6–10 weeks to map what exists and fix the pilot scope
3 · Pilot
4–6 months with real users and a measured result
ITKIT · [contact name, email and phone]
Thank you