Independent Business Analysis Case Study

Digitising Firearms Licensing in South Australia

How moving firearms licence applications from paper to an online portal could cut the time to licence from about 5 months to about 3 months, removing double data entry and the postal rework loops that cause most delays.

Marshal Anthony · Business Analyst · Master of Computer Science · SA Public Sector
~65 days
faster to licence (best case, 44%)
7 of 8
key process steps automated
~95%
shorter rework loop for missing documents
0
manual re-typing & in-person visits

At a Glance

ProjectPaper-to-digital transformation of new firearms licence applications, modelled on SAPOL's publicly announced South Australian Firearms Register (SAFR) program
TypeIndependent business analysis case study (self-initiated)
My perspectiveFirearms Adjudication Clerk (ASO2), SAPOL Firearms Branch — daily user of the current paper process
Duration6 weeks, completed alongside full-time work
Toolsdraw.io (BPMN 2.0), Microsoft Excel, Power BI, Microsoft Word
BA techniquesProcess modelling, root cause analysis, stakeholder analysis, requirements elicitation, MoSCoW prioritisation, user stories, change impact assessment, KPI design

Projected Outcomes (illustrative)

MeasureCurrent stateFuture stateImprovement
Time to licence (best case)~147 days~82 days~65 days faster (44%)
Time to licence (missing document)~217 days~89 days~128 days faster (59%)
Rework loop for a missing document3–6 weeks1–3 days~95% shorter
Key process steps automated0 of 87 of 8Only the suitability decision stays human
Manual data entryEvery application re-typedCaptured once by applicantDouble handling removed
In-person visits required10Fully online
Scope and confidentiality
  • This is an independent case study created to demonstrate business analysis capability. I was not a member of the SAFR project team, and this work does not represent SAPOL's official analysis, design or results.
  • The future state is based on publicly available information about SAFR. Steps not confirmed publicly are marked (A) for assumption.
  • All figures, dates and dashboard data are illustrative estimates or fictional sample data. No confidential SAPOL data, documents, system detail or operational procedures are used.
  • Outcomes are projected, not measured results.

01The Problem

Applying for a firearms licence in South Australia has traditionally been paper-based: a PD303 form, an in-person lodgement, physical transfer to Firearms Branch, and manual re-entry into the register.

2×

Double data entry

Every application is written by the applicant and re-typed by staff — double effort and transcription errors.

!

Incomplete applications

A paper form can't stop someone submitting without a key document. Each gap triggers a slow rework loop.

?

No visibility

Applicants can't see where their application is, so they call and email — taking officer time away from processing.

✉

Slow paper communication

Postal transit, outcome letters and posted licence cards add weeks.

Problem statement: "Paper-based firearms licence applications create double handling, rework and long waiting times for applicants and Firearms Branch, because the current process has no validation at lodgement, no digital data flow, and no self-service status tracking."

02Objectives

#ObjectiveSuccess measure
O1Reduce time from application to licenceBest-case time to licence reduced by 40%+
O2Eliminate double data entry100% of online applications enter the register without re-typing
O3Reduce incomplete applicationsRework requests reduced by 70%+
O4Improve applicant visibilityStatus available online 24/7; fewer status enquiries
O5Maintain public safety and legal compliance100% of suitability decisions remain with trained officers; legislated rules enforced

03My Approach

A standard business analysis lifecycle, adapted to a self-initiated case study.

Week 1

1. Discover

Reviewed public SAFR info, the PD303 form and Firearms Act requirements; documented the current process.

Week 2

2. Model

As-is and to-be BPMN 2.0 maps; pain point register.

Week 3

3. Analyse

Time-to-licence model from 1 January; delay scenarios.

Week 4

4. Define

Stakeholder analysis, MoSCoW requirements, user stories.

Week 5

5. Assess

Change impact matrix for each stakeholder group.

Week 6

6. Measure

KPI design and a Power BI dashboard on sample data.

04Process Mapping (BPMN 2.0)

Both processes modelled with swimlanes, so you can see who does what, where work changes hands, and where it loops back.

Paper / manualAutomatedHuman decisionRework / delay

4.1 Current State (As-Is): Paper-Based

Applicant
1Completes paper PD303 form
→
2Attends service point in person
9Completes safety training
Service Point
3Checks ID, takes photo, takes payment
→
4Posts paper application to Firearms Branch
Registry
5Checks form is complete
→
◆ 6. Complete?
No → letter/email for missing info (rework loop)
Yes → manually re-types into register
10Issues licence; card posted
Adjudication
7Fit & proper person assessment
→
◆ 8. Suitable?
No → refusal letter posted
Yes → approval to train sent
Hand-offs: 4Manual data entry points: 2Paper transfers: 2Rework loops: 1 (unlimited repeats)

4.2 Future State (To-Be): Online Portal

Applicant
1Logs in to online portal (A)
→
2Guided form — submission blocked until complete (A)
→
3Uploads ID & photo, pays online, submits
10Completes training → digital licence in mySA GOV app
Portal / System
4Auto email with reference number
→
5Data written straight into register — no re-typing (A)
Outcome sent instantly by email & portal
Registry
6Reviews from digital queue, oldest first (A)
→
◆ 7. Anything missing?
Yes → portal request; applicant uploads within days (A)
Adjudication
8Suitability assessment — stays human
→
◆ 9. Suitable?
Hand-offs: 3Manual data entry points: 0Paper transfers: 0Rework loops: 1 (short, digital)

4.3 What Changed

AreaAs-IsTo-BeBenefit
FormPaper PD303Guided online form with validation (A)Incomplete applications largely prevented
LodgementIn personOnline, 24/7Access for regional and working applicants
Data captureTyped twiceCaptured onceTranscription errors removed
TransferPhysical transit (3–7 days)InstantDays saved on every application
Missing documentsLetter / email, 3–6 weeksPortal request, 1–3 days (A)Rework loop ~95% shorter
StatusPhone and email enquiriesLive portal status (A)Officer time freed
OutcomePosted letterEmail + portalSame-day notification
LicencePosted cardDigital licence (mySA GOV app)No postal delay or loss

05Root Cause Analysis

5 Whys on the main problem: "Why does it take ~5 months to receive a licence?"

Why?Applications wait weeks in a queue before assessment starts.
Why?Each application needs manual handling: transit, completeness checking and re-typing.
Why?Applications arrive on paper, often incomplete.
Why?A paper form cannot validate information at the point of lodgement.
Root causeThe process relies on unvalidated paper capture with no digital data flow between the applicant and the register.

Pain points traced to requirements

Pain pointRoot causeAddressed by
Double data entryNo digital data flowBR-06
Incomplete applicationsNo validation at lodgementBR-02
Slow reworkPostal / email requestsBR-08
Status enquiriesNo applicant visibilityBR-09
Postal delaysPaper outcomes and cardsBR-10, BR-11

06Time-to-Licence Analysis

One applicant applies on 1 January 2027 through both processes.

Current — best case
~147 days · ~28 May
147 days
Current — missing document
~217 days · ~6 Aug
217 days
Future — best case
~82 days · ~24 Mar
82 days
Future — missing document
~89 days · ~31 Mar
89 days

6.1 Milestone Dates

MilestoneCurrent stateFuture stateDays saved
Application lodged5 Jan (public holiday 1 Jan; must attend in person)1 Jan (online)4
Received by Firearms Branch12 Jan1 Jan11
Assessment starts~16 Mar~5 Feb (A)~39
Suitability assessment complete~16 Apr~26 Feb (A)~49
Approval to train sent~23 Apr~26 Feb~56
Licence in hand — best case~28 May 2027 (147 days)~24 Mar 2027 (82 days)~65 days
Licence in hand — missing document~6 Aug 2027 (217 days)~31 Mar 2027 (89 days)~128 days

Queue times are illustrative. Check them against the processing times SAPOL publishes on its "Status of my application" page.

6.2 Delay Scenarios in the Current Process

ScenarioAdded delay todayWith online portal
Missing birth certificate or passport3–6 weeksPrevented at submission, or fixed in 1–3 days (A)
Request email goes to spam+2–4 weeksRequest also visible in the portal (A)
Illegible or incorrect handwriting+1–2 weeksTyped, validated fields
Referral to another agency+2–8 weeksStill possible (complex cases), but tracked digitally
Key insight: most of the delay is waiting and rework, not the assessment itself. Removing paper handling shortens the queue for everyone, not just the applicant who made the mistake.

07Stakeholder Analysis

Nine stakeholder groups placed on a power / interest grid to decide how to engage each one.

INFLUENCE →
Keep satisfied
Government / Minister
Manage closely
RegistryAdjudicationBranch managementICT / project team
Monitor
—
Keep informed
ApplicantsDealersService pointsClubs & industry
INTEREST →
StakeholderInterestInfluenceKey concernEngagement
Firearms Branch – RegistryHighHighWorkload, data quality, new systemManage closely — workshops, training, feedback loops
Firearms Branch – AdjudicationHighHighComplete information, legal complianceManage closely — requirements workshops, UAT
Firearms Branch managementHighHighBacklog, performance, riskManage closely — progress reports, KPI dashboard
ICT / project teamMediumHighScope, security, integrationManage closely — sign-off, change control
Government / MinisterLowHighPublic safety, public confidenceKeep satisfied — high-level reporting
Applicants / licence holdersHighLowSpeed, simplicity, knowing their statusKeep informed — guides, FAQs, status updates
Firearms dealersHighMediumFast permits, easy portalKeep informed / consult — user testing
Service pointsMediumMediumChanging role as lodgement moves onlineKeep informed — transition plan
Shooting clubs & industryMediumMediumFair process, delays, communicationKeep informed — briefings
Insight: the groups with the most influence are also the ones whose daily work changes most. Early involvement in requirements and testing is the biggest factor in adoption.

08Business Requirements

Prioritised with MoSCoW and traced back to the objectives.

8.1 Functional Requirements

IDRequirementPriorityObjective
BR-01Applicants can apply for a new licence online, 24/7MustO1, O4
BR-02The form blocks submission when mandatory fields or documents are missingMustO3
BR-03Applicants can upload identity documents and a photoMustO1
BR-04Applicants can pay fees onlineMustO1
BR-05Automatic confirmation with a reference numberMustO4
BR-06Application data flows into the register without re-typingMustO2
BR-07Officers work from a digital queue ordered by date receivedMustO1
BR-08Officers can request missing information through the portalShouldO3
BR-09Applicants can view their application statusShouldO4
BR-10Outcomes are sent electronicallyMustO1
BR-11Licences are available digitally (mySA GOV app)ShouldO1
BR-12System enforces legislated rules (e.g. 28-day minimum for permits to acquire)MustO5
BR-13Full audit trail of actions and decisionsMustO5
BR-14Management can report queue size and processing timesShouldO1
BR-15Applicants could receive SMS reminders for outstanding actionsCouldO3
BR-16Automated suitability decisionsWon'tO5 — decisions stay human

8.2 Non-Functional Requirements

🔒 Security

Secure, verified login; role-based access for staff.

🛡 Privacy

Personal information protected under SA privacy principles.

♿ Accessibility

Portal meets WCAG 2.1 AA.

🕑 Availability

Available outside business hours.

📝 Auditability

Every change logged with user and time.

👍 Usability

First-time applicant completes the form without help.

Traceability: every pain point maps to at least one Must or Should requirement, and every requirement maps to an objective — keeping scope focused on what causes delay.

09Change Impact Assessment

StakeholderWhat changesImpactRisk if unmanagedSupport needed
Registry officersPaper intake & re-typing replaced by digital queue reviewHighSlow adoption, workarounds, errorsHands-on training, quick guides, super-users, go-live floor support
Adjudication officersAssess on screen; record decisions digitallyMediumConcern about completenessUAT involvement; clear audit trail
ManagementNew performance data and reportingMediumData not used for decisionsKPI dashboard, reporting routine
ApplicantsApply online instead of on paperHighDigital exclusionGuides, help line, assisted digital option
DealersOnline transactions and supportMediumErrors helping customersDealer guides, training
Service pointsFewer in-person lodgementsMediumRole uncertaintyEarly communication, transition plan
Clubs & industryMembers ask about the new processLowMisinformationBriefings, FAQs

9.1 Risks and Mitigations

RiskLikelihoodImpactMitigation
Applicants with low digital skills left behindMediumHighAssisted option; clear guides; help line
Temporary backlog increase at go-liveHighMediumPhased rollout; extra staff; brief parallel running
Data migration errorsMediumHighData cleansing; reconciliation checks
Staff resistance to changeMediumMediumEarly involvement, super-users, show time savings
Security or privacy breachLowHighSecurity testing, role-based access, audit logging

9.2 Risk Reduction for People

Fewer licence errors

Details entered once by the applicant and checked by the system.

Public safety protected

Suitability decisions stay with trained officers; legislated waiting periods enforced by the system.

Less personal info on paper

Lower risk of documents lost in transit or misfiled.

Complete audit trail

Every decision can be reviewed.

10Power BI Dashboard: Licensing Performance

Designed to show how the change would be measured. All data is fictional sample data (~2,400 applications over 24 months: 12 paper, 12 online). Click the tabs to switch pages.

Firearms Licensing Performance — Before vs After
App type: All ▾Channel: Paper | OnlineRegion: Metro | RegionalMonth: Jan 26 – Dec 27
85Avg days to licence (online)
147Avg days to licence (paper)
95%Complete at first submission
91%Applications lodged online
Average days to licence by month
Go-live Jan 26Dec 26Dec 27 15085
Applications received vs decided per month
■ Received   ■ Decided
Average days in each stage — Paper vs Online
Paper Online ■ Transit■ Queue■ Data entry■ Assessment■ Training/issue
Funnel — online channel (sample)
Lodged 1,200 Complete 1,140 Assessed 1,100 Approved 1,040 Licence issued 1,010
Oldest applications on hand (top 5, sample)
App IDTypeChannelDays waiting
A-10482New licencePaper96
A-10511New licencePaper91
A-10533RenewalPaper88
A-11204New licenceOnline41
A-11219PTAOnline38
30% → 5%Rework rate (paper → online)
30 → 3Avg rework days
0Data entry corrections (online)
Rework reasons (paper channel)
Missing ID document Illegible details Missing signature Payment issue
Rework rate by month
~30% paper~5% online
Illustrative mock-up of the Power BI report · fictional sample data · Paper = grey, Online = blue

10.1 KPIs and Targets

KPIDefinitionPaper baseline (sample)Online target
Average days to licenceLodged date to licence issued date~147 days≤ 90 days
Complete at first submission% with no information request~70%≥ 95%
Rework rate% needing ≥1 information request~30%≤ 5%
Average rework durationRequest sent to information received~30 days≤ 3 days
Applications on handLodged but not yet decidedGrowingStable or falling
Manual data entryApplications re-typed by staff100%0%
Online uptake% lodged online0%≥ 90% within 12 months

10.2 Data Model (Star Schema)

FactApplications

ApplicationID, LodgedDate, ReceivedDate, AssessmentStartDate, DecisionDate, LicenceIssuedDate, Channel, Outcome, ReworkCount, ReworkDays, AppTypeKey, RegionKey

DimDate

Date, Month, Quarter, Year, IsAfterGoLive

DimAppType

New licence, Renewal, Permit to acquire

DimRegion

Metro, Regional

DimReworkReason

ReasonKey, Reason

10.3 Key DAX Measures

Avg Days to Licence =
AVERAGEX (
    FILTER ( FactApplications, NOT ISBLANK ( FactApplications[LicenceIssuedDate] ) ),
    DATEDIFF ( FactApplications[LodgedDate], FactApplications[LicenceIssuedDate], DAY )
)

Rework Rate % =
DIVIDE (
    CALCULATE ( COUNTROWS ( FactApplications ), FactApplications[ReworkCount] > 0 ),
    COUNTROWS ( FactApplications )
)

Applications On Hand =
CALCULATE ( COUNTROWS ( FactApplications ), ISBLANK ( FactApplications[DecisionDate] ) )

Online Uptake % =
DIVIDE (
    CALCULATE ( COUNTROWS ( FactApplications ), FactApplications[Channel] = "Online" ),
    COUNTROWS ( FactApplications )
)

10.4 Sample Findings

⏱ ~147 → ~85 days

Time to licence falls after go-live, driven mostly by shorter queue and transit stages.

🔁 ~30% → ~5% rework

Validation stops incomplete submissions.

📈 Short spike at go-live

Applications on hand rise briefly — why a phased rollout and extra staffing matter.

🌾 Regional applicants gain most

They no longer travel to lodge.

10.5 How I Built It

  1. Created sample data in Excel with realistic date ranges for each stage.
  2. Cleaned and typed the data in Power Query.
  3. Built the star schema and relationships in the model view.
  4. Wrote DAX measures for each KPI.
  5. Designed three report pages with consistent colour: Paper (grey) vs Online (blue).
  6. Added slicers and drill-through from the trend chart to application details.

11Projected Results and Benefits

Benefit areaProjected resultHow it is measured
Time saved for applicants~65 days faster (best case); ~128 days faster when a document is missingAvg Days to Licence
Automation7 of 8 key steps automated: validation, data capture, confirmation, status, information requests, outcome notice, digital licenceProcess map comparison
Error reductionDouble data entry removed; incomplete applications largely preventedRework Rate %, data corrections
Staff capacityTime on re-typing, chasing documents and status calls redirected to assessmentApplications decided per officer
Access and equityApply 24/7 from anywhere; no travel for regional applicantsOnline uptake by region
Public safety and complianceSuitability decisions stay human; legislated rules enforced; full audit trailAudit log, compliance checks

12User Stories

Format: As a [user], I want [goal], so that [benefit], with acceptance criteria in Given / When / Then.

WORKED EXAMPLE · US-01 · APPLY ONLINE
As an applicant, I want to apply for a firearms licence online, so that I don't have to complete a paper form and visit a service point.
Linked: BR-01, BR-02, BR-03, BR-04Priority: MustEstimate: 8 points
  1. Given I am logged in, when I complete all mandatory fields, upload documents, pay and submit, then my application is lodged and I see a confirmation screen.
  2. Given a mandatory field or document is missing, when I click Submit, then the missing items are highlighted and the application is not submitted.
  3. Given my payment fails, when I submit, then I see an error and my form data is kept so I can try again.
  4. Given I save and leave part-way, when I log back in, then my draft is restored.

Definition of done: acceptance criteria pass in UAT · accessibility check passed · Registry and applicant representatives have signed off.

Full Story Set

IDUser storyAcceptance criteria (summary)Priority
US-01As an applicant, I want to apply online, so that I don't need to visit a service pointLodged when complete; blocked when incompleteMust
US-02As an applicant, I want instant confirmation, so that I know my application arrivedEmail with reference within 10 minutes; shown in portalMust
US-03As an applicant, I want to see my status, so that I don't need to call the branchReceived / Under review / Info requested / DecidedShould
US-04As a Registry officer, I want to request missing documents in the portal, so that the applicant responds quicklyApplicant notified by portal and email; status updatesShould
US-05As a Registry officer, I want applications in a digital queue already filled in, so that I don't re-type formsData complete, ordered by date receivedMust
US-06As an Adjudication officer, I want to record my decision in the system, so that the applicant is notified and there is an audit trailOutcome sent electronically; decision, officer and time loggedMust
US-07As a manager, I want a report of queue size and processing times, so that I can manage the backlogOn hand and average days shown by typeShould
US-08As a dealer, I want to check a customer's licence status online, so that I complete a sale correctlyValid / not valid shown for a licence numberShould

13One-Page Case Study (STAR)

Situation

New firearms licence applications in SA relied on paper forms, in-person lodgement and manual re-typing, leading to waits of around five months.

Task

As a frontline Firearms Branch officer, analyse the process from a BA perspective and model the impact of moving to the publicly announced online SAFR portal.

Action

BPMN as-is/to-be maps · 5 Whys · 1 January time-to-licence model · 9-group stakeholder grid · 16 requirements, 6 NFRs, 8 user stories · change impact & risks · Power BI KPI dashboard.

Result (projected)

~147 → ~82 days (44% faster); up to ~128 days faster with missing documents · 7 of 8 steps automated · rework ~30% → ≤5% · decisions stay human.

Process modellingRoot cause analysisStakeholder analysisRequirements elicitationMoSCoWUser storiesChange managementKPI designPower BI & DAXRegulatory awareness

14What I Learned

Most delay is waiting, not working

Queue time and rework loops — not the assessment — drive time to licence.

Validation at the start saves weeks later

One rule — "you can't submit without your ID document" — removes the most common rework loop.

Automation should stop where judgement starts

In a regulated public-safety service, automate the paperwork and keep decisions with trained people.

Change impact matters as much as the system

Digital exclusion and go-live backlogs are the biggest risks — both need a plan before launch.

15About Me

MA

I'm Marshal Anthony, an Adelaide-based public sector officer with a Master of Computer Science (University of Adelaide) and frontline experience in regulatory licensing at SAPOL. I'm moving into Business Analyst roles where I can combine an understanding of legislation and operations with technology and data.

LinkedIn · marshal007anthony@gmail.com