The scenario library

Last updated September 4, 2026

The scenario library is a shared collection of drills that departments have chosen to publish. Anyone who builds drills can browse it and take a copy, and a department administrator can offer their own scenarios to it.

It is only visible to departments using Scene SizeUp. It is not on the public internet and it is not indexed by search engines.

Using a scenario from the library#

Open Library, find one, and press Copy to my scenarios.

The copy is yours. It lands in your Scenario Builder like anything else you built, and you can rename it, move the fire, change the responding units and run it tonight. Editing your copy has no effect on the library, and the department that published it never sees what you did with it.

Filter by the type of call and the building, or search by name or by the department that published it.

Check it before you train on it#

Library scenarios are authored by other departments and we do not verify them. Building construction, water supply, apparatus capability and local practice all vary, and a scenario built for one district can teach the wrong lesson in another.

Two things are worth a look every time:

The responding units. They arrive with the callsigns the original author used, and their capabilities are that department's rigs. Rename them to your own and check the numbers.
The address. It is removed when a scenario is published, so a copy arrives with none. Set your own on the Setup tab, or the dispatcher will not read one.

Nothing in the library is a pre-incident plan, and none of it should be relied on at a real incident.

A department administrator submits a scenario, from the share button on its row in the Scenario Builder. Publishing commits the department's name and grants other departments the right to use the scenario, which is why it is an administrator's decision rather than an instructor's.

We review every submission before it is published.

What is published, and what is not#

A copy of the scenario is taken at the moment you submit it. That copy is what we review and what gets published, so you can carry on editing your own without changing what is in the library.

Removed automatically, before anyone sees it:

The street address. It is never published.
The links to your apparatus inventory, so a copy never adds phantom rigs to another department's fleet. Your callsigns stay.
Named mutual-aid partners.

Everything else goes: the photographs, the scene, the responding units and their timing, situation levels and injects.

Credit#

A published scenario is credited to the department, by name. Nobody on your roster is ever named.

Before you submit#

Review is a second pair of eyes, not the only pair. Ask:

Do we have the right to publish these photographs? This matters most for images your department uploaded.
Is it a private residence?
Is it a building whose pre-incident plan your agency restricts? Schools, hospitals, courthouses, correctional and industrial sites deserve a deliberate decision.
Does the scenario's name, or an inject, give the address away?

Tracking a submission#

The scenario's row shows in review, in the library or not published, and a card under your scenario list shows the same with any feedback we sent. Whoever submitted it also gets an email when we have looked at it.

If we do not publish something, we say why, and you can change it and submit it again.

Withdrawing#

You can withdraw a published scenario at any time. It leaves the library and nobody else can take a copy.

Departments that already took a copy keep theirs. A copy is an independent scenario in their account by then. Treat what you publish as published.

If a scenario is removed#

We can also take a published scenario out of the library ourselves, and we will if something turns out not to have been ours to publish: imagery a department did not hold the rights to, or a building that should not have been made public.

When that happens:

It leaves the library, so nobody new can copy it.
Every department that already took a copy is emailed the reason, and sees a note beside their copy on the scenario list.
Nobody's copy is deleted. We do not reach into a department's account and remove their training material. The note is there so you can decide whether to keep using it.

If you see that note on one of your scenarios, the copy still works. Read the reason and decide. If the reason is that the imagery should not have been shared, delete it.

To report something that should not be in the library, email [email protected] with "library" in the subject. You do not need an account with us if you are the owner of a building or of an image.

See the scenario library terms for the full position.