Study PUA50519 by translating each management concept into an incident scenario: define the concept, decide who does what at which level, write the decision you would make, then check it against the principles the concept is meant to protect. Work through control versus command, span of control, the incident action plan, risk decisions, delegation and briefings, and finish with a rubric you can score yourself on.
Control, command and coordination: three words that change your answer
In Australian incident management practice, control is overall direction of the incident, command is authority over your own personnel and resources, and coordination is bringing responding agencies into a coherent arrangement. Deciding which word applies to a situation determines what decision you are actually being asked to make.
When you read a scenario question, the first diagnostic step is to ask whether the problem is about the incident as a whole, about people within one agency, or about agencies that do not take orders from each other. An overall incident objective like protecting a township sits under control. Directing your own crew to deploy a hose line sits under command. Agreeing evacuation priorities with police and health services is coordination, because police members answer to police command, not to the fire commander. Naming the correct level is itself the decision many scenario questions are built around.
A practical way to lock this in is to rewrite each concept as a testable sentence. Control answers 'what is the incident objective and who owns it overall'. Command answers 'who can direct this person and this resource'. Coordination answers 'who needs to agree with whom'. Trace one news report of a multi-agency incident through these three sentences and label every reported decision. If you cannot label a decision, you have found the concept you need to reread, which is far more efficient than rereading whole chapters.
Be careful not to treat the three terms as interchangeable synonyms, because they impose different limits. A controller in control of the incident does not thereby gain command of another agency's crew, and a commander with command authority over their crew cannot unilaterally set incident objectives without the control function. Write your scenario answers using the specific word, then justify why that word and not its neighbours.
- Control: overall management of the incident and its objectives
- Command: direction of personnel and resources within your own agency
- Coordination: arranging the actions of agencies that retain their own command authority
| Function | Question it answers | Typical decision it covers | Who must comply |
|---|---|---|---|
| Control | What is the overall incident objective? | Setting the incident strategy and priorities | The incident as a whole, through agreed structure |
| Command | Who directs these personnel and resources? | Tasking crews, approving their tactics within intent | Members of that commander's own agency |
| Coordination | Who needs to agree and share information? | Establishing liaison, common communications and priorities | No one is ordered; agencies align their own actions |
Span of control: when to split the incident into sectors
Span of control is the number of subordinates one supervisor can effectively direct. Common doctrine uses a guideline of roughly one supervisor to about five subordinates, treating it as a trigger to review workload rather than a fixed law, and splitting into sectors or divisions when it is exceeded.
The management insight behind the guideline is that supervision has a cost: every subordinate adds information the supervisor must receive, brief and monitor. A crew leader handling three appliances at one car park fire can maintain an accurate picture. Add four more appliances, two water carriers and a utility across a large industrial site, and the same leader is now filtering communications from many sources at once, and details such as crew welfare and water supplies start to slip. The guideline exists because attention, not courage or competence, is the limiting resource.
Apply it as a review trigger, not arithmetic. In a worked example, an incident controller is supervising seven task groups spread along a bushfire edge. A rigid reading of the ratio says create two sectors immediately. The better decision is to assess whether the geography and task variety genuinely exceed one person's picture: if all seven groups are doing identical containing work within sight and radio range of the controller, splitting may add a reporting layer without benefit. If the groups face different problems, such as a structure threat at one end and a hazard reduction line at the other, sectoring by geography gives each sector commander a coherent picture. Why it matters: the ratio protects awareness, and awareness, not the number itself, is the thing you defend.
A common mistake in scenario answers is splitting sectors to make the organisation chart look tidy. Sectoring multiplies communication paths, so justify each split by the workload it removes, and be ready to merge sectors again when the incident contracts.
The incident action plan: objective, strategies, tactics, tasks
An incident action plan states the incident objective, the strategies that achieve it, the tactics that implement each strategy, and the tasks assigned to specific resources. Its purpose is to make the next operational period coherent for everyone who was not part of the last briefing.
Learn the hierarchy in order, because each level constrains the next. The objective states the desired outcome, for example 'prevent the fire crossing Ridge Road before forecast wind change'. Strategies are the broad ways to achieve it, such as controlling the eastern flank or protecting assets. Tactics are the methods chosen for each strategy, such as establishing a control line with dozers on the northern edge. Tasks are what a named crew does next shift. When you write scenario answers, check that every task you propose traces upward to an objective; a tactic with no parent strategy is a strong sign you are solving a local problem the plan has not acknowledged.
The planning discipline also reveals mistakes. In a scenario where a crew has begun backburning without an approved plan line, the question is not whether the burn is tactically sound in isolation, but whether it serves the stated objective and sits inside an approved strategy. If it does not, the better decision is to pause, refer up, and have the objective confirmed, even if the burn looks effective. Why it matters: uncoordinated tactics consume resources the plan may have committed elsewhere, and can create new hazards, such as a fire edge outside the control line at wind change.
For study, practise writing a one-page plan for a familiar local scenario: one objective, two strategies, two tactics per strategy, and taskings with named roles. Then have someone else brief from your plan and note every question they ask; each question is a gap your plan should have closed.
Risk decisions on paper: hierarchy of controls applied to incidents
Incident risk management applies the same structure as workplace risk: identify hazards, assess likelihood and consequence, then prefer elimination and substitution over administrative controls, with personal protective equipment last. On paper, your job is to show the reasoning, not just the protective clothing.
The habit to build is ordering your controls instead of listing them. Suppose a scenario asks how to manage firefighters working near a hazardous tree after a fire front pass. An answer that begins with 'wear helmets and eye protection' fails the hierarchy, because personal protective equipment is the weakest control. Stronger answers move up the ladder first: can the hazard be eliminated by excluding crews from the drop zone and treating the tree as unsafe until assessed? Can substitution or engineering help, such as directing work paths away from the lean? Only after higher-order controls are exhausted should protective equipment appear, and then as a residual layer, not the plan.
Worked scenario: your crew must protect a shed with LPG cylinders nearby while the fire front approaches. A common mistake is to accept the assignment because crews are trained and equipped. The better decision sequence is: identify the cylinders as a specific hazard with severe consequence; assess whether they can be cooled or the exposure time reduced; consider eliminating exposure by repositioning to an alternate asset the plan identifies; and if crews stay, define the trigger conditions under which they withdraw. Why it matters: a decision that depends only on equipment fails the moment conditions exceed the equipment's limits, and paper scenarios reward showing that trigger-based reasoning.
Distinguish dynamic risk assessment from the planned assessment. The plan handles foreseeable risks in the planning phase; dynamic assessment is the continuous check that conditions still match the plan. Write both into scenario answers: the control you chose, and the observation that would cause you to change it.
Scenario one: escalation and the sector split decision
This scenario practises reading workload and geography together: an incident grows past one controller's span of control, and you must decide whether and how to sector, then brief the new structure.
The situation: a grass fire starts at a road reserve and, over two hours, runs to a boundary with a hospital on the northern side, an aged care facility to the west, and farmland to the east. The controller is personally directing six appliances, two tankers, a dozer and liaison with police. Requests now queue on the radio, and the hospital's evacuation question has not been answered for twenty minutes. A plausible mistake is to keep commanding everything personally and simply work harder, treating the backlog as a stamina problem. The better decision is to recognise the structure, not the effort, has failed: workload and distinct problems exceed one picture.
The stronger answer sectors by problem type and geography: a northern sector handling the hospital interface with police liaison embedded, a western sector for the facility with its evacuation needs, and an eastern sector for containment. Each sector commander receives the incident objective, their priorities, communications plan and reporting expectations, and the controller retains control of the incident objective and resources held in reserve. Why it matters: the escalation decision is not 'get help', it is 'redraw the management structure so each decision-maker has a picture they can hold'. Mark yourself by checking that your answer named the new roles, their boundaries, and what the controller stopped doing.
Scenario two: delegation and the resource order that went wrong
This scenario practises delegation within unity of command: a crew receives a conflicting task from a second officer, and you must resolve it through the chain of command rather than improvising on the fireground.
The situation: a sector commander tasks an appliance crew to back up a containment line. Minutes later, an operations officer from a neighbouring sector, running short on crews, directs the same appliance to water supply duty. The crew leader now holds two tasks from two people. A common mistake is for the crew to split the difference, doing both tasks partially, or to obey the most recent order. Both responses break unity of command, which holds that a resource takes direction from one supervisor at a time, and both leave the sector commander unaware their task is unfilled.
The better decision is for the crew leader to state the existing tasking, refer the conflict up to their own sector commander, and stand by on the original task until the commanders resolve resource ownership between themselves. The conflict is a coordination and resourcing problem between sectors, not a choice the crew should arbitrate. Why it matters: when crews self-arbitrate, neither commander has an accurate resource picture, plans built on phantom resources fail, and accountability for the decision becomes unclear. In study terms, practise writing the referral message: who you are, what task you hold, who tasked you, and the new direction received, then ask which supervisor you report to.
A practice exercise, a marking rubric, and your preparation sequence
Consolidate by writing and marking your own scenarios. Use a repeatable exercise, score it against explicit observations, then sequence your preparation so each session produces a written artefact you can compare against the rubric.
The exercise: take a fire near a familiar local feature, such as a school, fuel depot or residential edge, and write a one-paragraph scenario with at least three agencies and six resources. Produce four artefacts: the incident objective with strategies, a sector structure with spans of control, one briefing message to a new sector commander, and one risk assessment naming a control at each level of the hierarchy. Expected observations when you self-mark: the objective is measurable and time-bound; every sector has a stated boundary; spans sit near the guideline you chose, with justification where they do not; the briefing names objective, situation, tasks, communications and reporting; and the risk answer shows elimination or engineering controls before protective equipment. Score each artefact out of five and note why any score fell below four.
Rubric check questions for every scenario you write: Can a reader tell who controls the incident versus who commands each crew? Does every task trace to a strategy? Is there one supervisor per resource at every point in the timeline? Did you state a trigger that would change each risk control? Did you specify what reports flow up and how often? If you answer no to any question, revise the artefact rather than moving on. This rubric is a learning milestone, not a prediction of any assessment outcome.
An adaptable sequence: week one, master the control-command-coordination distinctions by labelling reported incidents; week two, practise sectoring on growing scenarios like the hospital example; week three, write and brief full action plans and have someone question the briefing; week four, drill the risk hierarchy on asset-protection scenarios; week five, run the delegation and unity-of-command conflicts; final week, mark your full artefact set against the rubric and rewrite the two weakest. Keep every artefact so you can see your earlier decisions improve.
For administrative matters about the qualification itself, such as its current status and training package context, refer to the training.gov.au entry for PUA50519; this guide addresses learning content, not enrolment or assessment logistics.
- Objective check: measurable, time-bound, traceable to strategies
- Structure check: one supervisor per resource, justified spans of control
- Briefing check: objective, situation, tasks, communications, reporting all present
- Risk check: controls ordered by hierarchy, with change triggers stated
- Communication check: referral messages name task, tasker and conflict
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.