How do you protect your event against fake staff passes?

Someone arrives at the crew entrance wearing your event's lanyard. They have a radio, a supplier name and a convincing reason to be in a hurry. Your team is already dealing with deliveries. Does the pass get them through?

It should get them checked. Your staff credential process needs to connect the person in front of you with an approved role, the areas that role needs and a current permission record. A printed badge helps staff recognise that arrangement. It cannot establish the arrangement by itself.

The first thing you want to do is agree who can approve staff access and how the entrance team verifies that approval. Then work through the ordinary exceptions: a replacement technician, a lost pass, a late delivery and a supervisor who has gone off shift. Those are the moments when a sensible policy can turn into somebody waving a person through because everyone is busy.

This guide explains how to prepare that process for a paid public event. We'll use a fictional trade show to work through the decisions, including a completed credential record and sample briefing. The examples are planning suggestions, not a security assessment for your venue. Agree the actual controls with your venue and suitably qualified security provider, using the requirements that apply where you operate.

Start with the work people need to do

Before you order passes, list the work that brings people into non-public areas. Your lighting contractor needs to reach production equipment. An exhibitor needs to prepare their stand. A photographer may need a supervised visit to a speaker preparation room. Those are different permissions, even if everyone is working on the same event.

Start from the venue's current layout and your event security plan. Name the areas consistently. If the contract says production office, the pass list says backstage and the entrance team calls it the green room, somebody will eventually approve more access than they intended.

For our fictional Makers Exchange, the organizer sells tickets to a one-day trade show. Its working areas include the exhibition floor, a production office and a service yard. The yard also has vehicle movements, so permission to enter it involves more than being associated with the event. The responsible teams need to consider the activity happening there at that time.

The organizer decides that exhibitor preparation access covers the exhibition floor during the agreed preparation period. It does not include the production office. A courier delivering a parcel reports to the designated receiving point. The courier does not receive a crew pass just because the parcel belongs to the production team.

These distinctions need an owner. Ask each department to identify who can request access and who can approve it. A supplier may submit names, but submission should not automatically become approval. The event's responsible lead checks the request against the work, and the venue confirms any permissions it controls.

ProtectUK's UK access-control guidance recommends limiting staff and visitor access to the areas their roles require, with controlled pass issue and identity confirmation. Use that principle to discuss your own arrangements with the provider. It doesn't establish a universal pass design or staffing level for every event.

Write down the time limits too. Someone needed for the build may have no work during the public programme. Someone arriving for pack-down should not automatically receive access while visitors are still leaving. Your permission record should reflect the actual activity, with a process for approving changes when the schedule moves.

Give credential issue a named owner

An event credential is the pass or other evidence used to show approved staff access. Accreditation is the process of checking and recording that approval. You don't need complicated language on site, but the distinction helps when you are choosing who does what.

Put a named person in charge of the credential register, with a deputy covering their absence. The register is your controlled record of approvals, issued passes and changes. It could be part of a suitable access system or another arrangement your provider can operate reliably. The important question is whether the people checking access can obtain the current answer.

For Makers Exchange, Leila manages credential issue and Sam is her deputy. Department leads request access for their teams. Leila records the approval and issues the credential through the agreed process. The security supervisor controls security decisions and referrals. Leila does not acquire authority to run a security intervention because she prints the passes.

Decide who can approve an exception before you need one. If an exhibitor adds a replacement colleague, the exhibitor coordinator may confirm the staffing change. If a contractor requests access to venue-controlled equipment, the venue may need to approve the request as well. A person who can confirm employment cannot necessarily authorize entry to every working area.

Keep that authority separate from personal influence. An owner, headline speaker or longstanding supplier should use the same confirmation route. Otherwise junior staff get a written policy followed by a practical lesson that senior people can ignore it. Ask the event lead to demonstrate the procedure during the briefing so following it feels normal.

ProtectUK's staff ID and challenge guidance describes clear ownership of staff and visitor passes, visible identification and arrangements for returning passes when work ends. It also distinguishes visitors who have a legitimate purpose and a responsible host. That is useful when deciding how to handle people who need a visit rather than ongoing staff access.

Your credential owner also needs access to the right information. Don't send them ten competing supplier spreadsheets and expect a reliable answer at the entrance. Agree the submission route, the person responsible for checking each list and the way approved changes reach the register. Archive superseded working versions so staff don't accidentally reopen an old attachment.

Collect an approved staff list before arrivals begin

Ask suppliers for the people they intend to deploy, their roles and the period they need access. Give them a deadline based on your preparation work, along with a clear replacement procedure. Explain that an email sent after the deadline still needs confirmation. It isn't permission to travel directly to a restricted entrance and negotiate admission there.

The supplier brief should identify a contact you already know how to reach. Confirm the contact through your existing booking relationship and record a deputy where necessary. When a new person arrives, your team should not have to rely entirely on a phone number supplied by that person to verify their story.

This is especially useful when several companies are involved. A production contractor may book a separate crew provider. Ask who approves that provider's people, who checks their role requirements and who tells the event about substitutions. Avoid a chain where each company assumes the next one has already checked the final names.

You can send a short instruction like this:

"Please submit the names and roles of your proposed crew through our agreed supplier channel. Include the dates and areas needed for the booked work. We will confirm approved access and the collection instructions. Send substitutions to the named event contact before arrival where possible. Crew who arrive without confirmed approval will be referred for verification under the event's access procedure."

That wording describes an administrative process. Your security provider should agree the entrance procedure, including how the team handles an unresolved arrival. The event should also explain any identification requirement in advance and provide a private route to discuss a legitimate difficulty meeting it.

At Makers Exchange, the production contractor submits Amina as an audio technician for the approved preparation and show periods. The production lead confirms the work and required access. Leila adds the approved record. If the contractor later sends Daniel instead, Daniel needs a checked substitution. Amina's approval cannot simply be handed to whoever turns up in the van.

You should also tell suppliers what not to send. A general staff-access request does not automatically require copies of passports, home addresses or unrelated employment records. Where a specialist check requires additional information, agree who needs it and the secure route for supplying it. The entrance team's working list should contain the information needed for that entrance task.

Check the person, the permission and the current status

A useful credential check answers connected questions. Is this the person the credential was issued to? What are they approved to do here? Does that approval cover this area and this time? Is the credential still active?

Your provider should specify how staff answer those questions at each access point. A visual pass might support recognition, while a controlled register or suitable electronic system establishes the current permission. The process must suit the site and its risks. A method used at a small exhibition is not automatically enough for a large festival or a sensitive production area.

The UK's National Protective Security Authority explains that automatic access-control systems can apply rules about who may enter particular areas and when. If you are buying a system, ask the supplier to demonstrate the functions you need in the actual configuration proposed for your event. A list of possible features does not confirm that your hired setup includes them.

A QR code is also a method of presenting information, not a complete answer to identity or authorization. Ask what the check returns, which record it consults and how a withdrawn permission reaches the checking device. Your staff need to understand the result they see, including what to do when that result is unclear.

Keep the physical pass readable for its intended users. Useful information may include the event, holder, relevant validity and a unique reference that connects to the register. Agree the final fields with the provider. Don't make colour the only way staff distinguish permissions, and don't crowd the badge with private information that isn't needed to use it.

We would spend time testing the checking process before paying for decorative pass finishes. A premium print treatment doesn't tell the entrance team whether a supplier replaced the holder that morning. Budget for the staff time, communication and change control the process actually needs.

Your test should include an approved person and an unresolved record. Ask the entrance operator to explain the next action in each case. If a warning produces a shrug, or staff cannot contact the responsible person, you have found an operational problem before it becomes a conversation in front of waiting crew.

Keep ticket admission and staff permission clear

Someone can have a valid ticket and still have no permission to enter a staff-only area. A speaker can have production access without being entitled to invite additional people backstage. Your team needs a consistent answer when several kinds of permission exist at the same event.

At Makers Exchange, an exhibitor's paid admission covers the public show. Their separately approved preparation access lets them work on their stand during setup. Neither automatically includes the production office. The organizer explains this before arrival so the exhibitor doesn't first discover the distinction while trying to bring a delivery through the wrong door.

For public admission, Loopyah's ticketing and check-in tools let organizers give door staff check-in access and scan QR tickets using their phones. That supports the ticket-checking job. Your venue and security team should separately agree how staff permissions are approved and verified for restricted work areas.

Apply the same care to digital accounts. A person operating ticket check-in needs the appropriate event account permissions for that task. A printed crew pass does not grant access to the organizer's login. Issue the access the person needs through the supported team-access process, and assign someone to review it when the person's work changes or ends.

You may also have performers, media, sponsors, exhibitors and escorted visitors. Avoid putting everyone under a vague label such as VIP and expecting the entrance team to interpret the relationship. A sponsor's commercial importance does not describe where their photographer is allowed to work.

Write the actual permissions in the operational record. You can still make the public-facing experience welcoming. Clear instructions let your team say, "Your exhibition access is confirmed. The production coordinator will meet you if your interview needs a visit to the speaker room." That's more helpful than an argument about what a lanyard ought to mean.

Build a lost-pass and replacement procedure

A lost pass creates two jobs. You need to establish whether the person asking for a replacement is entitled to one, and you need to deal with the previous credential. Printing another badge solves only the first visible inconvenience.

Tell staff how to report a loss immediately, including outside the credential desk's normal hours. The credential owner should check the holder and approval through the agreed process, record the loss and apply the provider's withdrawal procedure. The replacement needs its own reference linked to the earlier record so the event can explain what happened.

Don't leave two active credentials because the original badge might turn up. Where your system supports electronic withdrawal, confirm that it has reached the relevant checking points. If your arrangement relies on controlled manual checks, the provider needs a reliable way to communicate the withdrawn credential and verify that staff received the update.

For our fictional event, Amina reports credential MX-041 missing. Leila confirms her identity and current work authorization. The register marks MX-041 withdrawn and links replacement MX-087 to the same approved person. The relevant access teams acknowledge the update before the replacement is used under the agreed procedure. These references illustrate the record; they aren't a numbering standard.

If the old pass is later found, it stays withdrawn unless an authorized process explicitly changes that status. The holder returns it to the designated person. Staff should not reactivate it informally because the photo looks right or because somebody remembers printing it.

The same process needs to cover someone finishing early, a supplier being stood down and a temporary visit ending. Pass collection and access withdrawal are related tasks, but neither proves the other happened. Record the current permission even when the physical pass cannot immediately be recovered.

Discuss what happens if updates cannot reach an entrance. Your provider should decide the appropriate temporary arrangement for the affected access point and the conditions for restoring normal checks. A message typed into a group chat does not establish that the person currently on duty has seen and understood it.

Handle an unclear pass without accusing the holder

An unclear credential is a reason to verify. It isn't proof of fraud. A spelling error, a damaged badge or an approved substitution that hasn't reached the desk can produce a legitimate problem. Staff need a calm referral process that protects access without turning uncertainty into a public accusation.

Agree the words staff can use. For example, "I can't confirm this permission yet. I'll contact the supervisor who handles staff access." The provider should specify where and how the check takes place, with attention to queues, vehicle movements and the person's access needs. Don't improvise a waiting location in a working yard.

The member of staff reporting the issue should describe what they observed. "The pass reference isn't on the current approved list" is more useful than "There's a fake contractor here." The supervisor can then check the credential, the supplier relationship and the requested work without inheriting an unsupported allegation.

This is where the job boundaries matter. An administrative worker checking names should not be expected to search, detain or physically remove someone. Your provider must agree who handles security decisions and interventions, with the training and permissions required locally. If there is immediate danger, staff should use the event's emergency procedure and contact emergency services when needed without waiting for a credential query to be resolved.

In the UK, the SIA's guidance on activities requiring a licence distinguishes simple ticket or invitation checking from activities that can require a security licence. Requirements depend on the work, employment arrangement and premises. Agree the actual duties with your provider; changing a job title to steward doesn't change the work being performed.

Set an accessible route for verification too. Someone may need written communication, a quieter place to explain a problem or an agreed alternative to a particular identification method. The responsible lead should resolve that through the event's approved arrangements. Accent, clothing, disability or confidence should never become an improvised test of whether somebody belongs on site.

A practical referral is specific. The entrance team knows whom to contact. The supervisor receives the relevant facts privately. Someone remains responsible for the original access point. The person seeking access receives a clear answer or an update about the outstanding check. Nobody assumes that walking away from the desk means the question has been resolved.

Respond to confirmed misuse through the security lead

What happens if verification confirms that somebody is presenting a credential they are not entitled to use? The security lead should manage the response under the event's agreed procedures. Your credential owner supplies the approval and issue records, while ordinary event staff continue within their assigned duties. Don't ask the person at the printing desk to investigate the visitor or decide whether a crime has occurred.

Separate the immediate access decision from the follow-up investigation. The provider and venue need to decide what the situation requires now, including whether the concern affects other working areas or people already admitted. Appropriate authorities may need to be involved. A suspected wider problem should reach the responsible lead promptly, with verified facts and clear uncertainties.

Preserve relevant issue and access records through the responsible organization's incident process. Record which credential was presented, what the current register showed, who checked the discrepancy and what action the authorized lead took. Where relevant footage or device logs may exist, tell the person responsible for them so they can manage preservation appropriately. Don't have staff copy footage or personal details into informal chats.

At Makers Exchange, imagine a separate incident in which a presented credential is confirmed not to belong to the person using it. The supervisor handles the person under the agreed security procedure. Leila establishes the genuine holder's current status and records any authorized credential change. The event lead coordinates with the venue about the affected access arrangements. These tasks proceed together; they don't wait for somebody to finish writing a perfect incident summary.

Be precise about what is known. Finding one misused credential does not establish that the whole staff list is compromised. Equally, resolving one arrival does not prove the wider issue is closed. The responsible lead should define what further checks are needed and who completes them. Staff need an instruction they can carry out, rather than a general warning to be extra vigilant.

Communicate changes privately to the people who need to act. If the provider changes a checking procedure, confirm which points and shifts it applies to, how they receive it and when it starts. Avoid public discussion of the event's checking weaknesses or personal allegations. Any public statement should follow the event's agreed communication responsibilities and use confirmed information.

Before normal arrangements resume, the relevant lead should confirm that required changes are operating. That might include a corrected permission record, acknowledged withdrawal or repaired checking device, depending on what happened. Record the decision and any outstanding follow-up. The next shift should be able to tell which issue is resolved and which action still has an owner.

This is also a reason to keep your wider event risk assessment current. If an incident reveals that an assumed control isn't working, review the affected activity with the competent people responsible for it. Reprinting a pass cannot repair an entrance procedure that the team is unable to follow.

Prepare for late suppliers and temporary visits

Last-minute changes are normal enough to plan for. What you want to avoid is a different approval process invented by every department. Ask the venue and provider to agree an exception route that can confirm legitimate work without silently removing the checks applied to everyone else.

A temporary visit should have a purpose, a responsible host and a defined end. Decide who can approve it and which areas it covers. Where an escort is required, name the person accepting that duty and make sure they understand it. Calling somebody a host doesn't help if they're busy presenting on stage and cannot meet the visitor.

For Makers Exchange, a technician from a replacement equipment company arrives after the supplier list was finalized. The production lead checks that the visit is needed, confirms the company through the established supplier relationship and obtains any venue approval required for the work. Leila records the agreed temporary access, and the named host accepts the visit under the provider's procedure.

The temporary permission does not authorize unrelated work. If the technician needs a different area or additional time, the responsible lead approves that change. This matters commercially as well as operationally. Access approval doesn't automatically approve a variation to the supplier's fee or permission to alter venue equipment.

Delivery drivers need their own arrangement. Decide where goods are received, who confirms the delivery and who manages vehicle movements. A delivery booking should not become broad staff access for every person travelling with the vehicle. Coordinate these decisions with the venue's transport and working-area procedures.

Brief departments on what to tell a late arrival. "Ask for me at the crew entrance and say I sent you" leaves the entrance team with a personal claim to assess. "Report to the agreed receiving point; your visit is logged with the access team and your host will meet you" describes a process someone can verify.

The exception record should close when the visit ends. The host confirms departure through the agreed route, the pass is returned where required and the credential owner closes the permission. If the person is expected back later, record the next approved visit rather than leaving an open-ended invitation in yesterday's notes.

Check professional licences separately where required

An event pass answers an event-access question. It does not prove that the holder has the licence, qualification or competence needed for the work. You should settle those requirements when appointing providers, then confirm that the people deployed match the agreed arrangement.

For UK private security work, use the government's service for checking security licences where the role requires an SIA licence. Verify the right licence and current status for the actual individual. An event badge with the word security printed on it is not that check.

Ask the provider who performs those checks, how substitutions are handled and what confirmation you receive. A replacement should not bypass the role checks simply because the original worker was approved. Equally, a current professional licence does not show that the event has engaged that individual or authorized their access to a particular area.

Other roles may have different requirements. Discuss electrical work, medical services and other specialist duties with the competent lead for that function. The credential desk should record the approval it needs for access, without pretending to assess professional competence from a quick conversation.

At Makers Exchange, the production lead confirms that Amina belongs to the appointed audio contractor and has the approved work assignment. The security provider confirms its own personnel and required licence checks through the agreed process. Leila uses those verified approvals when issuing credentials. She does not personally certify every person's professional background.

Keep evidence responsibilities clear in the booking record. Otherwise every company may believe somebody else verified the replacement. The useful question is, "Who checked this person's suitability for the assigned work, and who approved their event access?" Both answers should name an accountable person or organization.

Decide what happens when the system is unavailable

A credential process needs a fallback for a failed device, unavailable network or inaccessible register. Write that fallback with the provider and venue, and test it before arrivals. Staff should know who decides whether affected access can continue and under what conditions.

Ask what information the checking team can rely on during an outage. If you use a controlled offline list, agree who creates it, when it was current and how changes are communicated. A morning export can become inaccurate after a lost pass or supplier substitution. Mark the version clearly and prevent unofficial copies becoming independent approval lists.

Your provider may need to change the arrangement at the affected point while checks are unavailable. Confirm the staffing and communication needed to do that. The fallback should preserve the permission check appropriate to the site, with a clear referral for records that cannot be confirmed.

Don't let a technical problem become a reason to compromise escape arrangements. In Great Britain, HSE's event emergency-planning guidance says escape routes and exits must remain available and unobstructed. Review any proposed access-control change with the venue against its emergency plan before putting it into practice.

At Makers Exchange, a checking device loses access to the register during preparation. The operator reports the failure to the security supervisor. The agreed fallback determines the next step at that point; the operator doesn't declare every printed badge acceptable. Leila continues controlling changes, including withdrawals, through the confirmed fallback communication route.

Once service returns, reconcile actions taken during the outage. Check temporary permissions, withdrawn credentials and any unresolved arrivals. Tell the relevant teams when the normal process resumes and which version is current. Restoring the device isn't enough if half the team is still following a temporary instruction.

Use a credential record people can complete

The following record is a starting point for discussion with your venue and provider. Adapt it to the information your agreed process needs. It should support a decision and later changes, while leaving sensitive supporting documents in their controlled location.

• Event and operating date.

• Holder's name and supplier or department.

• Approved role and purpose of access.

• Approved areas and validity period.

• Person authorizing the permission, with approval reference.

• Credential reference and issue status.

• Identity check completed by, and when, using the agreed method.

• Issue acknowledgement where required by the procedure.

• Temporary host or escort requirement, if applicable.

• Changes, withdrawals and linked replacement reference.

• Return or closure record and responsible person.

Here is a fictional completed example. Makers Exchange takes place on Friday, 6 November 2026. All names, references, times and checks in this example are invented to show how the record works. They aren't a required checking duration or operating schedule.

Amina Patel works for the appointed audio supplier, Northbank Production. Her role is audio technician for the exhibition programme. Maya, the production lead, approves access to the exhibition floor and production office for her assigned work, from 07:30 to 19:00 that Friday. Pat, the venue duty manager, confirms the relevant working-area conditions. Approval AP-12 records those decisions. No escort is required for this approved assignment, and there is no permission to enter the service yard or bring another worker with her.

At 07:40, Leila compares Amina with the photo identification accepted under this fictional event's agreed procedure and checks the approved name. She records the check, issues MX-041 and records Amina's receipt acknowledgement. The working register records completion of the check; it doesn't contain a copied identity document. Any additional work area needs a checked change.

At 10:20, Amina reports MX-041 lost. Leila records the report, verifies the replacement request and withdraws MX-041 under the agreed procedure. The relevant teams acknowledge the update before Leila issues linked replacement MX-087 at 10:30. The underlying work approval remains AP-12. The credential changed while the approved assignment stayed the same.

At 18:45, Maya confirms that Amina's assignment has ended. Sam, who has taken over credential issue, records return of MX-087 and closes its access under the agreed procedure. MX-041 remains missing and withdrawn. The record says so rather than marking both passes returned to make the list look complete.

Notice how the example separates permission, credential and physical return. That lets the next supervisor answer a practical question about MX-041 without reconstructing the day from messages. It also prevents a replacement badge being mistaken for an additional worker on the supplier's deployment list.

Protect the information behind the pass

The credential register may contain names, work assignments, photographs and contact information. Decide what each user needs to see. An entrance operator needs enough information to check access. They probably don't need the supplier's entire personnel submission or the organizer's private incident correspondence.

The UK's ICO guidance on collecting only necessary personal information says data should be adequate, relevant and limited to what the purpose requires. The page is under review following UK legislation changes, so confirm current obligations for your operation. Use the purpose of each field to decide whether it belongs in the working register.

Tell people what information you collect and why through the appropriate privacy information. Agree who can access it, how it is shared with suppliers or the venue and how long it needs to be kept. Account for any records that must be preserved for a genuine incident or other applicable obligation, rather than keeping everything indefinitely.

Avoid circulating a whole register in an open team chat because someone needs to check one name. Use the agreed controlled route. If printed extracts are necessary, assign responsibility for their issue, updates and collection. An abandoned sheet at the credential desk can expose information long after it stops being useful.

Be careful with photographs of passes too. You may want an event-day team photo, but check what is visible before it is posted. The event should decide which pass information can be shown publicly and brief the people handling publicity. Keep the internal permission list and staff contact details out of promotional material.

Incident records need particular care. Write observed facts and distinguish a concern from a confirmed finding. An incorrect name on a list can be an administrative error. Recording somebody as a counterfeiter without evidence creates a different problem and makes the record less reliable for the people who need to review it.

Brief the next shift on changes, not just the original plan

Your opening briefing should explain how access is checked, who approves exceptions and where unresolved questions go. The next shift also needs the changes that happened after that briefing. A lost credential remains relevant even if the outgoing operator dealt with it before lunch.

Use the event team briefing template for the wider roles and escalation arrangements. Add a credential-specific handover covering the current register version, active temporary visits, withdrawn passes, unresolved arrivals and equipment problems. Keep personal details in the controlled record rather than reading them across a public area.

For Makers Exchange, Sam takes over credential issue from Leila. They confirm that MX-041 is withdrawn, MX-087 is the replacement and approval AP-12 is unchanged. They review a temporary supplier visit that is still open and identify its host. Sam confirms access to the current register and the supervisor contact before accepting responsibility.

The entrance handover should connect with that change. An incoming operator needs the current instructions and a working referral route. Ask them to explain what they would do with MX-041, without turning the exercise into a guessing game about pass appearance. The right answer comes from the agreed current record and procedure.

You can use this short briefing wording as a starting point:

"Check staff access using today's approved procedure. A familiar face or printed pass doesn't settle an unclear permission. Refer unresolved checks to the named supervisor using the agreed route. Report lost credentials immediately. Follow your assigned duties and the emergency plan if there is danger. Confirm current changes when taking over from another team member."

Then practise a supplier substitution and a lost-pass report. Let people use the actual contact method and controlled record. If the deputy cannot access the information, fix that before the first lead goes off shift. A briefing has done its job when the team can complete the handoff, not merely repeat the policy.

Review what failed before ordering the next batch

After the event, ask the credential owner, venue and security supervisor where the process became difficult. Did supplier names arrive late? Did department leads request broad permissions because they hadn't described the work? Were withdrawn passes visible to the teams who needed to check them? Use actual records to identify the issue.

Look at legitimate delays as well as suspected misuse. If approved crew repeatedly waited because their permission hadn't reached the entrance, that is a coordination problem worth fixing. Removing the check next time would leave the original problem unresolved. Improve the submission route, approval responsibility or update delivery that caused the delay.

For a significant incident, use the event incident report template alongside the provider's reporting arrangements. Record the observations, decisions, actions and people receiving the handover. Agree any further investigation or external reporting with the responsible specialists and authorities, preserving relevant records through the appropriate process.

Discuss costs against the work delivered. Extra credential staff, replacement printing and additional supervision may need a clear variation record. A low printing bill doesn't tell you whether the access process worked, just as a busy credential desk doesn't prove that every check was necessary. Ask which part of the process each cost supported.

Before your next paid event, choose a real exception from the last one and follow it through the revised arrangement. Start with the supplier's request and finish with the incoming shift checking the current permission. If you can name who approves the work, who issues the credential and who resolves an unclear check at every stage, you have something useful to brief and test with the venue.