APS4 selection criteria examples and application guide.
APS4 is where ownership of routine work becomes yours. The work level standards expect clearer judgement, discretion over how work is delivered, and often supervision of a small work group. The six worked examples below show what calibrated-at-APS4 actually reads like — and how to avoid the most common pitch errors.
What APS4 actually is.
An APS4 role sits at the upper end of the operational levels. The APSC work level standards describe APS4 work as involving "procedural, clerical, administrative, operational, technical or supervisory work under general direction." Functionally, this is where routine work becomes yours to own: you exercise discretion over how it gets delivered within established procedures, you contribute to improving those procedures, and you often supervise a small work group or a couple of more junior staff.
APS4 also tends to be where applicants move from "task-doer" framing to "outcome-owner" framing in their writing. You are no longer just executing the work — you are responsible for whether it gets done well, and you have authority over how. That distinction is the single most important calibration shift between APS3 and APS4 responses.
Application formats at APS4 are similar to APS3 — short pitch, statement of claims, or application questions — but expected length and depth are higher. Where an APS3 response might run 180–250 words, an APS4 response often runs 200–300 words because the scope being described is larger.
At APS4 you're demonstrating: I own routine work in my area. I make judgement calls about how to deliver it within established procedures. I contribute to improving those procedures when I see better ways. I supervise junior staff or trainees and can run a small piece of work end-to-end. I escalate genuinely complex matters but handle the rest myself.
You're not demonstrating: organisational-wide influence, leading change initiatives, managing significant budgets, or setting policy. Those are APS6+ claims.
What APS4 panels are actually testing.
APS4 selection criteria typically test five capabilities. The set overlaps with APS3 but the depth expected is greater, and you'll often see supervision and procedural improvement appear at APS4 that didn't appear at APS3.
Communication. Written and verbal at increased complexity — longer documents, more demanding audiences, more difficult conversations.
Teamwork and collaboration. Working with colleagues, but often with the added dimension of supervising junior team members or coordinating with adjacent teams.
Stakeholder management. APS4 typically introduces stakeholder management more formally — managing relationships with internal and external stakeholders rather than just communicating with them.
Problem solving and judgement. Resolving issues that fall within your authority, exercising discretion on what to escalate, contributing to procedural improvement.
Delivery and accountability. Owning outcomes for your area of work, meeting deadlines, accuracy and quality under volume.
A sixth capability you may see is supervision — particularly if the role formally has direct reports.
Six worked APS4 selection criteria examples.
Target length is 200–300 words per response. Italicised gold tags mark the STAR sections.
Written and verbal communication with diverse stakeholders
Demonstrated ability to communicate effectively in writing and verbally with internal and external stakeholders, including the ability to adapt communication style to audience.
I communicate effectively in writing and verbally across diverse audiences, including stakeholders unfamiliar with technical or administrative content (restate the criterion). In my current role as a Senior Administrative Officer with a regulatory agency, I am responsible for client communications about compliance obligations (situation). Many recipients are small business owners with limited familiarity with the regulatory framework (task).
When I draft compliance correspondence, I write two versions in my head and pick the clearer one — one that uses the regulatory terminology, and one that explains the same thing in plain language. The second one almost always lands better with our SME audience. I structure every compliance letter the same way: what the recipient needs to do, by when, what happens if they don't, and where to get help. I avoid the passive voice that creeps into regulatory writing. When I take calls from recipients confused by a letter, I never start by re-reading the letter back to them — I ask what specifically they did not understand and work from there. For internal communications, I write differently again, using the regulatory shorthand colleagues expect. I review my own correspondence after a week, looking for places where a recipient might still have misunderstood, and feed those learnings into future drafts (actions).
Compliance response rates for my correspondence have run at 87% within 14 days, against a team average of 73%, over the past three quarters. My team leader has shared two of my standard letters as templates for newer team members (result).
Supporting a team and supervising junior staff
Demonstrated ability to work effectively as part of a team and to provide guidance and support to junior staff.
I contribute to team objectives and provide structured support to junior team members, including informal supervision and on-the-job training (restate the criterion). In my current role I sit within a team of eight, with two APS2 administrative trainees who joined in the past six months (situation). The team leader asked me to act as the day-to-day point of contact for the trainees during their settling-in period (task).
I built a simple onboarding process for them rather than answering questions ad-hoc as they came up. The first three days I walked them through our case management system, our document templates, and the escalation pathway for issues outside their authority. From week two, I set up a 15-minute check-in each morning to clear questions before the day started rather than interrupting workflow. I gave them work that gradually increased in complexity, and I never gave them the same task back to redo without explaining specifically what I would change and why — correction without explanation builds resentment without building capability. When one trainee was struggling more than the other, I raised it with the team leader rather than letting it slide. Throughout the period, I kept my own workload visible so the trainees could see the rhythm of work at the next level (actions).
Both trainees were on independent caseloads by the end of their first three months, ahead of the usual four. Our team leader noted in my mid-year review that the structured approach had reduced disruption to her own work during the onboarding period (result).
Managing internal and external stakeholder relationships
Demonstrated ability to manage relationships with internal and external stakeholders, including in situations involving competing interests.
I manage stakeholder relationships across internal and external counterparts, including in situations where their interests do not fully align (restate the criterion). In my current role I act as the primary day-to-day contact between our agency's case management team and three external service providers contracted to deliver client support (situation). Tensions had emerged over inconsistent referral information being passed between us (task).
I started by listening carefully to each provider separately about what they actually needed from referrals to do their work properly, which revealed a pattern I had not seen in the formal complaints — the providers needed two specific data points we were not consistently including. I worked with our internal case officers to understand why those data points were inconsistent, which turned out to be a system field that was optional rather than required. I drafted a short proposal to make the two fields mandatory, including the providers' rationale and the case officers' workflow implications, and put it to my team leader. Once approved, I ran a 30-minute briefing with the case officers explaining why the change mattered, rather than just telling them the form had changed. I followed up with each provider individually after the change to confirm the referrals were now arriving in usable form (actions).
Referral quality complaints from the three providers dropped to zero in the following quarter, and our case officers reported the new mandatory fields had not slowed their referral process meaningfully. The team leader has referenced the approach with our other contracted service interfaces (result).
Resolving issues and contributing to procedural improvement
Demonstrated ability to identify and resolve issues, including contributing to improvements in established procedures.
I resolve issues within my area of responsibility and identify opportunities to improve the procedures that govern routine work (restate the criterion). In my current role I observed over a six-week period that our quarterly compliance report was taking three full days to produce, against a budgeted day-and-a-half (situation). The overrun was happening for two consecutive cycles, and the team leader had flagged it as something to look into (task).
I mapped the report production process from end to end, talking to each person who contributed data, and identified that we were collecting the same client status data twice — once in a manual spreadsheet update at the start of the cycle, and again through the case management system extract at the end. The duplication was a hangover from a system change two years earlier that nobody had circled back to. I drafted a revised process that eliminated the manual update and added a single validation check at the end-of-cycle extract. I tested it against the most recent quarter's data to confirm the validation check caught the issues the manual update had been catching. I documented the new process clearly enough that anyone in the team could run the report, not just the person who had been doing it (actions).
The following quarter's report was produced in 1.2 days — under budget for the first time in five cycles. The team leader has since asked me to look at two other routine processes for similar review (result).
Owning outcomes and meeting deadlines under pressure
Demonstrated ability to deliver outcomes against agreed deadlines, including in situations of competing priorities and time pressure.
I deliver outcomes against agreed deadlines, including in situations where competing priorities and external time pressure converge (restate the criterion). In my previous role with a state government department, I was responsible for compiling the agency's monthly performance dashboard for the executive team (situation). During one cycle, two contributing data sources were delayed simultaneously — one by a system outage and one by a staffing issue in another team — with the dashboard due to the executive in three working days (task).
I called the contacts in both contributing teams within an hour of identifying the delays rather than waiting for an update, which gave me realistic timeframes for when each dataset would arrive. With that information, I sequenced my own work to do everything I could without the missing data first, so I would only need to slot the late inputs in at the end rather than restart sections. I notified my manager early about the risk to the deadline, with a clear plan and a contingency — producing a dashboard with footnoted gaps if one of the datasets did not arrive in time. I kept communication tight with the two contributing teams across the three days, not chasing them but staying close to their progress. When the second dataset arrived 90 minutes before deadline, I had everything else ready to integrate it (actions).
The dashboard was delivered on time with full data. My manager noted the contingency planning specifically in the team's quarterly review (result).
Maintaining accuracy across complex casework
Demonstrated attention to detail and ability to maintain accuracy across complex or high-volume work.
I maintain accuracy across complex work, including caseloads where small errors have downstream consequences for clients or compliance (restate the criterion). In my current role I manage an active caseload of around 80 client files at any given time, each with multiple status fields, time-bound obligations, and document attachments (situation). The team accuracy benchmark is 97% on quarterly file audits, with errors in critical fields counted at double weight (task).
To maintain accuracy at this caseload size, I rebuilt my own file management workflow when I first joined the team. I review each case file at three checkpoints — intake, mid-cycle, and pre-closure — against a personal checklist rather than relying on memory or the system reminders alone, because system reminders only catch some categories of error. I keep a running note of the error categories the quarterly audits flag most often across the team, and I check my own files specifically for those categories before submitting. When I notice a case where I am uncertain about a status decision, I escalate to my team leader rather than guessing — getting it wrong creates rework that costs more time than the escalation. I also flag systemic patterns I notice in errors back to the team leader so the team can address them at source (actions).
Over the past four quarterly audits my accuracy rate has averaged 99.1%, well above the team benchmark. The team leader incorporated two elements of my approach into a revised quality assurance procedure for the team last year (result).
Common APS4 pitfalls and how to avoid them.
Still writing at APS3 level
The most common APS4 mistake: describing what you do rather than what you own. APS3 examples often read as "I handled X" or "I responded to Y." APS4 examples need to read as "I am responsible for X" or "I own the outcome of Y." The difference is small in words and large in calibration.
Overreaching into APS5 or APS6 claims
APS4 is not the level for leading change initiatives, managing significant budgets, or influencing organisational strategy. Candidates with senior private-sector backgrounds often overshoot. The panel reads this as either misreading the role or as a flight risk — someone who will leave for an APS5 the moment one comes up.
Skipping the supervision dimension
Many APS4 roles include supervision of junior staff. Candidates often skip this in their responses because the supervision feels informal. Include it. APS4 supervision examples don't need to be formal line-management — mentoring trainees, running induction, providing day-to-day guidance all count.
Procedural improvement absent from the application
APS4 work level standards explicitly include contributing to procedural improvement. If your application doesn't show at least one example of you improving how routine work gets done, you are missing a marker the panel is looking for. Find an example — even a small one — for at least one criterion.
Inflated scope
Caseload of 80 sounds modest, but is real APS4 scope. If you write that you "managed a portfolio of 400 stakeholders" without context, the panel will probe in interview. Genuine numbers grounded in real scope read more credibly than inflated claims.
Application formats at APS4.
APS4 applications use similar formats to APS3 but with slightly higher expectations on depth.
Short pitch (500–750 words). Standard for most APS4 roles. Address all criteria in integrated form, drawing on three to four different examples across the pitch.
Statement of claims. Each criterion under its own heading, 200–300 words per response. More common at APS4 than APS3.
Application questions in PageUp. Two to four targeted questions, each capped at 300–400 words. Increasingly common in larger agencies.
If you are applying for APS5 or APS6 from an APS4 base, the calibration shift is significant. APS5 is where work increases in complexity and you begin to act with limited supervision on routine matters. APS6 is where you exercise considerable independence on complex work and may have substantial supervisory responsibility. See our APS6 selection criteria and pitch writing guide for the full calibration framework above APS4.
Want us to write your APS4 application?
Our writers calibrate every response to the level you are applying for — APS3 reads as APS3, APS4 reads as APS4, APS5 reads as APS5. One-hour information-gathering session, drafts within three business days of payment, 14-day editing window with unlimited revisions.