Accreditation software for eventsWe set it up around your event.

Teams apply for their own people on your portal, you approve with the rules enforced, the badge prints from your design and the gate goes green on any phone. Accreditation, or credentialing, for championships, tournaments, festivals and conferences.

From £950 or $1,200 per event, setup included · No hardware to buy · Hosted on AWS in the UK

A request from Westvale Harriers:
Accreditation request · Westvale Harriers
Marcus Feldt
Coach · Team official · Safeguarding current to 14 Aug 2027
Kenji Tanaka
Coach · Team official · Safeguarding lapsed 3 June
CategoryTeam official
Zones asked for
FOPCR
Delegation quota11 of 127 of 12
Press it. This is what one approval does. Every line is written on the record.
Needs a current safeguarding check.
What one approval does Saving… Approved
  1. Pass issued NC26-TO-017 · FOP CR · valid 9 to 12 July
  2. Email queued to marcus@westvale.org: Your pass is approved, with the confirmation letter attached
  3. Text sent to the team manager: Marcus Feldt is approved for the Championships
  4. Badge drawn from your design and queued at the desk printer
  5. Let throughMain gate · Field of play · on a steward's phone

What one press writes on the record, in the order it happens.

Nothing to press. The field of play pass needs the Safeguarding trained group, and Kenji's check lapsed on 3 June. The team manager read that on the portal when she applied, so it never reached your inbox. The rule says no, so you don't have to.

A drawn demo. Every step is the product's own: the pass, the email, the text, the badge and the scan are one approval.

Nobody re-keys a list that arrived by email. Each team applies for its own people on your portal, against a quota it can see.

The thirteenth request is refused by the quota, not by you. Whoever is applying reads why at ten at night instead of emailing you.

When the question arrives in August, the answer is already on the record: who approved it, when, and every scan since.

How it works

From the first application to the gate.

One system holds who is coming, who approved them, what they may enter, and the badge in their hand. A junior tournament, a national championship, a festival or a race weekend: the steps are the same, and every screen carries your categories, your statuses and your words.

1

Teams apply for their own people

Each club, broadcaster or supplier signs in to your portal, applies against its quota and uploads the photos and documents.

2

You approve, and the rules are enforced

A request moves through your statuses. Nobody without a current check is approved, and nobody holds two passes at once.

3

The badge prints from your design

With the photo, the zones and a code, on your card printer or as a PDF for the print shop. A lost badge is replaced in a minute.

4

The gate checks on any phone

A steward's phone reads the code and says green or red, by zone and by day, with the face on the screen. Every scan is kept.

One pass on screen: approved, held by Marcus Feldt, printed and collected, with the zones it opens.

One pass, as the office sees it: its status, who it's for, whether it has been printed and collected, and the zones it opens.

Automation

The workflow runs itself.

Every step you do by hand today, between an application arriving and a badge being collected, becomes a rule: when this happens, do that. Written as plain sentences, built with you at setup, and changed by you afterwards with nobody technical in the loop.

  • One approval issues the pass, emails the letter and texts the team manager
  • A request that breaks a rule is refused before it reaches you, with the reason
  • Try a rule on a real record and see exactly what it would do before you switch it on
  • Rules can run on a clock too: a reminder two weeks before, a report every Monday
What is enforced

The system says no, so you don't have to.

The rules you set are checked on every request, every pass and every scan, whoever is pressing the button. Nobody argues with a greyed-out option, and nobody has to be the one who said no.

The check

A pass can require a current check: a safeguarding certificate, a licence, an induction, a briefing. A pass that needs it cannot be given to anybody without it. Somebody whose check lapsed on Tuesday is not inside on Saturday.

The quota

Every team, outlet and supplier has a quota it can see on its own page. The thirteenth request is refused by the quota, not by you, and whoever is applying reads why at ten at night instead of emailing you.

One per person

One person cannot hold two live passes, and a duplicate request is refused before it reaches you. A lost badge is replaced in a minute, and the old code is refused at every gate from that moment.

Written down

Every approval, every change and every scan, with who did it and when. When the question arrives in August, the answer is already on the record.

In your brand

Your event looks like the big ones.

A public site for your event on your own domain, a portal where the teams apply, emails from your own address and a badge from your design. To the teams, the broadcaster and the board, everything carries your name and your colours, never ours.

An event's own public site: Northgate Athletics' header, a full-screen photograph of runners on a track at dusk, The Northgate Championships, and buttons to register and apply for accreditation.
The same site on a phone, signed in as an athlete: her championship pass with its code, ready to show at the gate, and her screening booking.

The event's site

A countdown, the programme, the venue, the partners and the forms, built with you from your brand and published on your own domain.

Their pass, on their phone

Each person signs in to see their own pass, its status, and what to bring. A team manager sees everyone they look after.

Emails and the badge

Received, approved, changes needed, your pass is ready: from templates in your brand, with the letter attached. The badge prints from your own design.

At the gate

Green or red, on any phone.

Any phone's camera reads the code and says green or red, by zone and by day, with the face on the screen and a reason the steward can read out when it's red. Every scan is kept.

  • Works on the phones your stewards and volunteers already carry
  • Once-a-day passes and expiring passes, enforced at the door
  • A lost badge is cancelled everywhere at once
No hardware to buy. The phones you own, the printer you have, and a PDF for anybody else. Card printers and scanning phones are available for hire or purchase if you want them; order at least three weeks before your event.
AI, where it helps

It does the reading. You do the deciding.

Three places a model reads so that a person doesn't have to. None of them approves anybody, refuses anybody or moves a status: each one reports, and you decide. Included in every plan, and off until an administrator switches it on.

Uploads checked before they reach you

A team manager uploading a photo with a kitchen behind it is told so before Send. A passport is read and its number checked against the record. What doesn't look right is listed for you; nothing is refused.

Forward an email, get the changes done

Forward a request to your workspace's own address. What it asks for comes back drafted and checked, and one press applies it. Only your own staff's email is read; anybody else's is dropped unread.

Ask a question, get the chart

Which clubs are waiting, how many are approved, where the applications are. The assistant answers from your records, as you, and draws the chart; a report keeps the question and asks it again whenever it is opened.

  • Runs on Amazon Web Services in London
  • Never approves, refuses or moves a status
  • Nothing marked sensitive is ever sent
Set up for you

Start from what you already have.

Last year's spreadsheet, the form you copied, the badge you printed: send them over. We build your categories, your approval steps and your rules from them, import your data once, and walk your team through it. Day one is not a blank screen, and a spreadsheet comes back out whenever you want one.

How we set you upIncluded in every plan
  1. Week 1
    We learn your event
    A call, last year's spreadsheet and the badge you printed.
  2. Week 2
    We build it for you
    Your categories, approval steps, emails, badge and portal, with your data imported once.
  3. Week 3
    You try it with us
    We walk your team through it and change whatever doesn't fit.
  4. Open
    Applications open
    Teams, outlets and suppliers apply for their own people on your portal.
  5. Event
    Support on the day
    Badge day and gate day, with support that already knows your event. Not a ticket queue.
Pricing

The price is on the page.

Flat, per event, by how many people you accredit. No quote, no per-badge pennies, no seat licences. Every feature, AI included, and setup from what you already have.

Event
Up to 500 people
£950
one event · $1,200 in the US

A regional championship, a junior tournament, a conference or a one-day event.

Start with this one
Event
Up to 3,000 people
£3,300
one event · $4,200 in the US

A games, a festival or a large championship, under most purchase-order limits.

Start with this one
Season
Any number of events
£4,800a year
up to 1,500 people at each · $6,000 in the US

For an organiser who runs more than one event a year.

Talk to us

Every plan includes

  • Every feature, and setup from what you already have: your data imported once, your team shown round on a call
  • A site and a portal in your brand, where teams apply for their own people
  • Checking on any phone, and badges as a PDF or on your own printer
  • The AI checks, the assistant and the email address, within the plan's monthly allowance
  • No charge per user, up to 25, 50 or 75 by size, so every steward has their own sign-in
  • Twelve months, so next year starts from this year

The small print, in full

People means everybody issued a badge for the event, however many times it is reprinted. Go over your size by up to a tenth and nothing changes; go over by more and the next size applies, and you hear from us before it happens, never on an invoice after. Paid when your account opens, with nothing to true up and nothing that recurs by surprise. Text messages are the one extra, charged per message where we can send them. Larger than 3,000? A conversation, not a form.

Introductory The first three customers pay half for their first event, in return for a named case study and a reference call. List prices are held for twelve months from publication.

Card printers, ribbons, blank cards and scanning phones are available for hire or purchase, priced on their own. Nothing in bluebric depends on them.

Security and the data

Serious about the data, in writing.

Passport numbers, dates of birth and background checks are what an accreditation system holds. Here is what is done with them, and every line of it is in the agreement you sign.

Hosted in the UK

On Amazon Web Services in London, with a copy of the database's backups kept in Ireland. Where your data is held is written in the agreement, not in a support article.

Kept apart

Your records are kept apart from every other organisation's at the database itself, not only on the screen.

Sensitive means sensitive

A passport number or a date of birth is marked as such, and is never sent anywhere but to the person it belongs to.

Only what you publish

The public sees only the pages and the fields you put in front of them. A team's contact reaches their own people and nobody else's.

An agreement with every customer

A data processing agreement, signed before your data arrives, with the sub-processors listed and 30 days' notice of any change to either.

Yours to take away

Export your records as a spreadsheet whenever you want. Your account stays open for twelve months, and nothing renews by itself.

Support from the people who set you up

By email while applications are open, answered within one working day, and on the phone on badge day and your event days. Nobody starts from a ticket.

The company

bluebric is made by JTW Software Ltd, a software company registered in England. The terms, privacy notice, data processing agreement and sub-processor list are linked below and sent with every order.

Get started

Tell us about your event.

We reply within one working day with a date for the first call, and your setup is built with you from there. If you would rather talk first, say so and we will ring you. Or email hello@bluebric.com.

  • Setup included, from last year's spreadsheet
  • A data processing agreement before anything arrives
  • We never add you to a list

We use what you type here to reply to you, and for nothing else.