VC use case
New Zealand LCQ credential
Verify NZ Licence Controller Qualification (LCQ) credentials for duty managers and hospitality staff.
- Hospitality
- Government
Overview
Hospitality staff receive an LCQ credential from an approved training provider. Venues verify the credential before appointing duty managers or assigning alcohol service responsibilities.
The venue needs a current, auditable proof that the worker holds accepted LCQ training for the role, not a broad copy of the worker’s training history.
Why it matters
LCQ checks are often manual and inconsistent. Certificates may be copied, emailed, or rechecked through separate processes, making it harder for venues to maintain reliable compliance evidence.
Verifiable Credentials create a cleaner model:
- approved training providers issue trusted LCQ credentials
- workers present the credential from a wallet when applying for duties
- venues verify issuer trust and credential status before appointing the role
- compliance teams can audit the verification outcome without storing unnecessary source documents
Ecosystem roles
- Issuer: Approved training provider issuing LCQ credentials.
- Holder: Hospitality worker storing the credential in a wallet.
- Verifier: Venue, employer, or regulator checking eligibility for duty manager or alcohol service responsibilities.
- Trust governance: The rules that define approved issuers, credential format, status checks, expiry, and renewal.
Trust decision
The verifier decision is narrow: can this worker be appointed to this LCQ-dependent role right now?
That decision depends on accepted issuer, credential status, expiry, role requirements, and any local regulatory policy.
Privacy and assurance
The verifier should request only the LCQ proof needed for the role. Assurance depends on checking issuer trust, credential status, expiry, and the worker’s binding to the presented credential.
The verification record should support compliance audit while avoiding unnecessary storage of full credential payloads.
Implementation notes
- Define which LCQ issuers and credential schemas are accepted.
- Keep status checks available for onboarding, roster assignment, and periodic compliance reviews.
- Align verifier policy with venue licensing and local regulatory obligations.
- Provide fallback handling for workers with older certificates or wallet access issues.
- Objective
- Confirm staff hold valid LCQ training.
- Description
- Verify an LCQ credential before appointing duty managers or assigning alcohol service roles.
- Actors
- Training provider; hospitality worker; venue, employer, or regulator.
- Dependencies
- Approved issuer registry, LCQ credential schema, verifier policy, and status endpoint.
- Preconditions
- The worker has completed approved LCQ training and holds a current credential.
- Postconditions
- The worker is cleared, denied, or sent to exception handling for the role.
flowchart LR
TRAIN@{icon: "tabler:certificate", label: "Training provider", pos: "b"} -->|Issues LCQ VC| WAL@{icon: "tabler:wallet", label: "Wallet", pos: "b"}
WAL -->|Present LCQ proof| VER@{icon: "tabler:glass-cocktail", label: "Venue / employer", pos: "b"}
VER -->|Check status| REG@{icon: "tabler:book", label: "Registry/status", pos: "b"}
sequenceDiagram
participant Trainer as Training provider
participant Wallet
participant Worker
participant Verifier as Venue / employer
participant Registry as Registry/status
Trainer-->>Wallet: Issue LCQ VC
Worker->>Verifier: Apply for role or shift
Verifier->>Wallet: Request LCQ proof
Wallet-->>Verifier: Present LCQ proof
Verifier->>Registry: Validate issuer and status
Registry-->>Verifier: Valid
Verifier-->>Worker: Cleared or denied
Talk to UNIFY