Two systems can watch the same crowd and see completely different things. A sensing platform sees a shape: 4,200 devices in the north pavilion, average dwell eleven minutes, flow building toward the eastern egress. An admission platform sees a list: 3,880 general admission, 240 exhibitor staff, 61 contractors, three of whom have a site induction that expired at midnight.
Neither view is complete. The first cannot tell you who to call. The second cannot tell you where they are. Run them separately and you get two dashboards that agree on nothing; run them together and you get an operating picture that is actually actionable.
That is the reason AdmitMe and CrowdSense are built as counterparts rather than competitors, and why AdmitMe is CrowdSense's preferred admission and credentialing partner across the ecosystem.
Two halves of the same question
Every venue operator, event organiser and site manager is trying to answer one question in two parts: who is here, and should they be?
The two halves have genuinely different engineering constraints, and that is the whole reason they are separate products.
Counting has to work at ambient scale. It has to cover a whole site, including the people who never queued at a gate — the delivery driver, the venue's own staff, the member of the public who wandered in from the adjoining park. It has to work without anyone consenting to anything, which means it has to work without identity. CrowdSense does this by reading the anonymous Bluetooth signals already present in every crowd, plus camera-based counting where occupancy limits require it, and resolving them into presence, dwell and movement in a control room.
Credentialing is the opposite. It is narrow, deliberate and necessarily named. A ticket belongs to a buyer. An induction belongs to a worker who acknowledged specific site conditions on a specific date. An insurance certificate belongs to a company and expires on a date that either does or does not cover your bump-out. None of that works anonymously — the whole point is attribution.
The design rule: the sensing layer must never need to know who someone is, and the admission layer must always know. Collapsing them into one product would force a compromise on both — a sensing system that suddenly needs consent, or a credentialing system that stops being able to name anyone.
Why the separation is a feature, not an accident
There is commercial pressure to merge these. A single vendor with a single dashboard is an easier sale. It is also, for this particular problem, the wrong architecture.
The moment a sensing platform starts holding identities, three things happen. Its privacy story becomes complicated enough that legal review slows every deployment. Its deployable footprint shrinks to places where you can get consent, which excludes most public space. And its data becomes something that has to be governed, retained and eventually breached.
Keeping CrowdSense anonymous by construction is what lets it go up in shopping centres, council precincts, construction sites and festival grounds without a six-month privacy impact assessment. Keeping AdmitMe identity-bound is what lets it actually block a badge.
That argument gets sharper, not weaker, as the admission side gets stronger. AdmitMe now offers palm vein credentials for restricted zones — an encrypted biometric template bound to a named person. Holding that data is exactly why it must live on one side of the line and never cross to the other. The sensing layer does not receive it, does not need it, and is architecturally incapable of using it.
A control room showing 4,200 people in the north pavilion is useful. A control room showing 4,200 people, of whom 61 are contractors, of whom three have a lapsed induction, is a decision.
The integration point is not a shared database. It is a shared site plan and a shared event timeline — the two things both systems have to agree on for their outputs to be comparable.
What "preferred integration partner" actually commits to
The phrase is doing real work here, so it is worth being specific about what it means and what it does not.
It means four things:
- A shared spatial model. Zones, halls, gates and thresholds are defined once and used by both platforms, so "the north pavilion" means the same polygon in the CrowdSense control room and the same access rule in AdmitMe accreditation.
- A shared event timeline. Bump-in, public days, bump-out and pack-down are the same dates in both systems. Credential expiry is checked against the full operational window, not just the days the public is on site.
- Aligned access categories. AdmitMe's badge types — contractor, staff, exhibitor, sponsor, speaker, VIP — map to the zones CrowdSense reports on, so occupancy in a restricted area can be reconciled against who was accredited for it. Where palm vein readers are installed on those thresholds, the same zones stop being reporting boundaries and become enforced ones.
- A single delivery team. Joint deployments are scoped, installed and supported by Artefact Group, who engineer both platforms. There is no integration partner to coordinate between two vendors, because there is one team.
It does not mean the two products are bundled, that you need both, or that either is locked to the other. AdmitMe runs standalone for the large majority of its clients. CrowdSense runs standalone in plenty of deployments that have no ticketing at all. Preferred partner means that when you want both, the integration is already engineered rather than quoted as custom work.
What a joint deployment looks like
Concretely, on a two-hall expo with a three-day build:
Six weeks out. The exhibitor list lands in AdmitMe. Forms are assigned per exhibitor — insurance and WHS for everyone building a stand, food safety only for the caterers, drone approval only for the two exhibitors flying anything. Portal links go out as tracked short links.
Two weeks out. Contractor and stand-staff accreditation closes. Every person who will be on site during bump-in has a named record with an emergency contact, a site induction acknowledgement and — where the work requires it — a current licence or certificate with its expiry recorded as a date, not as a line in a PDF. Anything expiring inside the operational window is already flagged.
Bump-in, day one. Sense Nodes are live. The control room shows occupancy per hall. AdmitMe has issued badges only against approved records, so the contractor headcount on the wall and the accredited headcount in the system are the same number — and when they diverge, that divergence is the signal.
Public days. Ticket scanning at the gates feeds admission counts; CrowdSense feeds dwell and flow. Together they answer questions neither answers alone: are the people in Hall 2 the ones who bought Hall 2 tickets, is the queue at gate three a throughput problem or a scanning problem, is the eastern egress loading faster than the plan assumed.
Bump-out. Accreditation expiry is enforced through pack-down, which is when most incidents actually happen and when most spreadsheet-based systems have long since stopped being maintained.
And if the alarm goes. CrowdSense reports the count still inside the eastern yard. AdmitMe's zone entries and exits turn that count into a list of names with mobile numbers and emergency contacts. That is the single clearest demonstration of why the two layers are worth running together — and why neither one alone is sufficient.
Beyond events
The same pairing generalises past the event floor, which is what the CrowdSense industry variants are built around.
| Context | The count (CrowdSense) | The credential (AdmitMe) |
|---|---|---|
| Trade shows & expos | Hall occupancy, dwell by zone, egress flow | Tickets, exhibitor approvals, stand staff accreditation |
| Construction sites | Live headcount by area, muster verification | Contractor inductions, competency cards, expiry enforcement |
| Council & civic venues | Precinct footfall, facility utilisation | Hirer insurance, stallholder permits, volunteer records |
| Resources & industrial | Zone presence, restricted-area occupancy | Visitor and contractor inductions, site-specific clearances |
In every row, the left column tells you the situation and the right column tells you what to do about it. A muster count that says forty-one people are still in the eastern yard is an emergency. A muster count plus an accreditation list that names them is a response.
Where Artefact Group fits
Artefact Group engineers, deploys and orchestrates both platforms. That is not a branding line — it is the reason the integration works.
Sensing hardware has to be surveyed, mounted, powered and networked against a real floor plan. Admission has to be configured against the same floor plan, the same timeline and the same access categories. When those are two vendors, the site plan gets transcribed twice and diverges immediately. When it is one delivery team, the site plan is authored once.
Artefact also carries the parts neither product ships out of the box: venue integrations, network and signage, control-room fit-out, and the bespoke work that every large site turns out to need.
How to start
Most clients arrive at the pairing from one side or the other, and that is fine.
- Start with admission. Put one event on AdmitMe — fourteen days free, no card. Ticketing, inductions and exhibitor management are on every plan, so you can test the whole model on a single show.
- Start with sensing. Talk to CrowdSense about node coverage for your site. Admission can be added later against the same spatial model without redoing the survey.
- Start with both. Joint deployments are scoped by Artefact Group. This is the right path for venues, multi-site operators and anyone with a control room already in the budget.
Whichever way in you take, the commitment on our side is the same: the count and the credential will describe the same site, on the same timeline, using the same words for the same places.