Onboarding - Debrief Field Mapping

Modified on Wed, 6 May at 9:50 PM

Preparing Your Data for AMS Onboarding

When planning your journey from your current systems to AMS, it is important to consider the data that you will be transferring across.

This guide will help you plan your data with your onboarding team and provide a simple mapping reference that can be used to align your current data exports to AMS.

Debriefs

Debriefs are entities in AMS which are linked to incidents and contain learning outcomes.

During onboarding, your team should identify where debrief information is currently stored and how it relates to your incident records.

Incidents

Incidents are used to provide the operational context for debriefs and learning outcomes.

The primary incident fields to consider are:

AMS Field	Description	Mapping Guidance
Incident number	The unique reference number for the incident.	For best practice, we highly recommend using the IRS number where available.
Incident type	The classification of the incident.	AMS fits best with the three primary headers: Fire, Special Service, and False Alarm, along with their respective child types.

Learning Outcomes

Learning outcomes are the key learning records captured from a debrief. These help your service identify, track, and act on learning from incidents.

Each learning outcome has several important fields:

AMS Field	Description	Mapping Guidance
Author	The person who created or submitted the learning outcome.	Map this to the person, role, or user identified in your current export.
Theme	The subject area or category of the learning.	Map this to your current learning category, theme, or equivalent field.
Source	Where the learning came from.	This may relate to the originating debrief, incident, review, or other learning source.
Details of the learning identified	The main description of the learning that has been identified.	Map this to the narrative or free-text learning field in your current system.
Scope / outcome type	The level at which the learning applies.	Identify whether the learning is a local issue, service-wide issue, or national learning item.

Suggested Mapping Template

To support onboarding, we recommend preparing a simple mapping document using the structure below.

AMS Entity	AMS Field	Notes
Incident	Incident number	Use IRS number where possible.
Incident	Incident type	Map to Fire, Special Service, False Alarm, and relevant child types.
Learning Outcome	Author	Identify who submitted or created the learning.
Learning Outcome	Theme	Map to your current theme or category.
Learning Outcome	Source	Map to the origin of the learning.
Learning Outcome	Details of the learning identified	Map to the main learning narrative.
Learning Outcome	Scope / outcome type	Local, service-wide, or national learning.

Example Data Mapping Guidance for AMS Onboarding

The example below demonstrates how an existing debrief export from a service may be reviewed and aligned to AMS during onboarding.

The purpose of this exercise is not to enforce a fixed structure, but to help identify:

Which information already exists within your current systems
How that information may align to AMS entities
Which fields may require standardisation or review before import

Example AMS Mapping Guidance

The table below shows an example approach your onboarding team may take when reviewing existing data exports.

Existing Export Header	Suggested AMS Entity	Suggested Use in AMS	Guidance Notes
Id	Debrief	Legacy Reference	Useful for migration tracking and cross-referencing historical records during onboarding.
Start time	Debrief	Debrief Submitted Time	Helps identify when the debrief process was initiated.
Completion time	Debrief	Debrief Completion Time	Can assist with reporting and audit timelines.
Email	Learning Outcome	Author	May help identify the user or individual who submitted the learning.
Name	Learning Outcome	Author	Can be used alongside email to identify the contributor.
What did this debrief result from?	Debrief	Source	Helps determine whether the learning originated from an incident, exercise, training event, or other activity.
Incident Number (if applicable)	Incident	Incident number	We strongly recommend using the IRS incident number wherever possible.
Date of Incident or Exercise	Incident	Incident Date	Used to provide operational context for the debrief.
Which appliance / resource did you attend the incident or exercise on?	Incident	Operational Context	Useful for filtering, reporting, and operational trend analysis.
Type of Incident / Exercise	Incident	Incident type	AMS aligns best with the three primary categories: Fire, Special Service, and False Alarm, alongside child types.
Were any specific issues encountered at the incident and if so, did they involve any of the following?	Learning Outcome	Theme / Details of the learning identified	This field may contain multiple themes or learning categories that require review during onboarding.
What went well at the incident or exercise?	Learning Outcome	Details of the learning identified	Positive learning and best practice examples can also be imported into AMS.
What could have been improved at the incident or exercise?	Learning Outcome	Details of the learning identified	Often forms the primary operational learning narrative.
Incident/Exercise involved cross border working?	Learning Outcome	Scope / outcome type	May help identify learning that affects wider operational areas or partner organisations.
Were any operational tactics used outside of standard CFRS operating procedures?	Learning Outcome	Scope / outcome type	Useful for identifying higher-level operational assurance or governance learning.
If yes, please explain what tactics were employed or decisions that were made and how we captured the rationale for the decision?	Learning Outcome	Details of the learning identified	May contain important contextual learning or operational decision rationale.
Upload any images as required.	Debrief	Attachments / Supporting Evidence	Images and supporting documentation may be reviewed separately during onboarding depending on migration scope.

Important Notes

This example is intended as onboarding guidance only and does not represent a fixed import specification.
During onboarding, your AMS team will work with you to validate field mappings and identify any service-specific requirements.
Some fields may contain multiple pieces of information and may require cleansing or transformation before import.
Historical exports often evolve over time, so field consistency and formatting reviews are recommended before migration activity begins.

Recommended Next Step

Before onboarding workshops begin, we recommend preparing:

A sample export from your current system
Descriptions of what each field represents
Any known reporting requirements
Examples of learning outcomes or debriefs you consider important

This allows the onboarding team to better understand your current processes and support a smoother migration into AMS.