What Should a Good Forest School Child Record Include?

A child record can begin very simply.

A name. A date of birth. A parent's telephone number.

Then come medical details, allergies, emergency contacts, dietary requirements, consent, additional needs, attendance, accidents, observations and other information gathered over months or years.

Before long, a Forest School can hold a considerable amount of information about one child.

But more information does not automatically mean a better child record.

A useful record should help the setting answer practical questions:

• Who is this child?
• Who is responsible for them?
• Who should we contact if something happens?
• Is there anything practitioners need to know to support them safely?
• Are there individual needs or strategies that could help?
• What permissions and consents apply?
• What has happened during their time with the setting?
• Is the information still current?

The purpose is not to build the largest possible file.

It is to maintain the right information, for the right reasons, for the right people.

Start with identification

The record needs enough basic information to identify the child correctly.

Depending on the provision, this may include:

• full name
• preferred name
• date of birth
• home address where required
• parent or carer details
• relationship to the child
• relevant contact information

This sounds straightforward, but accuracy matters.

Two children may have similar names. A child may use a different name from the one originally supplied. Family circumstances can change.

The information should allow practitioners and administrators to be confident that they are looking at the correct child's record.

But basic identification is only the beginning.

Emergency contacts

If something happens during a session, knowing who to contact can become immediately important.

Current Department for Education guidance for parents and carers using out-of-school settings in England says that providers should collect, for each child:

• at least one emergency contact number for a parent or carer, ideally more than one
• the parent's full name
• the child's home address

The same guidance tells parents and carers to share medical concerns and allergies with the provider.

That provides a useful baseline for thinking about emergency information.

But simply collecting an emergency number once is not enough.

Telephone numbers change.

Relationships change.

Children may remain with a Forest School for several terms or years.

The DfE guidance specifically says that where a child attends an activity for more than a year, the provider should ask for updated information.

Good record keeping therefore includes a way of reviewing and updating information, not simply collecting it.

Medical information and allergies

Medical information can be among the most important information held about a child.

Depending on the child and provision, relevant information might include:

• allergies
• medical conditions
• medication information
• relevant health needs
• important instructions from parents or carers
• dietary requirements where they affect safe provision

The question should not be:

How much medical information can we collect?

It should be:

What information do we genuinely need in order to provide the service and support this child appropriately?

There is another reason to be careful here.

Information concerning a person's health is special category data under UK GDPR.

That means it receives additional protection.

Processing special category data requires an appropriate lawful basis under Article 6 of UK GDPR and a separate condition under Article 9.

The objective is enough information to support the child safely — not an unnecessary medical history.

Dietary requirements are not always just preferences

Dietary information can sometimes look like a relatively minor administrative field.

In practice, it may represent very different things.

A dietary requirement could relate to:

• an allergy
• an intolerance
• a medical condition
• a religious requirement
• an ethical or family choice
• a simple preference

Those distinctions can matter.

If food or drinks are provided during a session, practitioners need enough information to understand what applies to the child and, importantly, whether getting it wrong could create a health risk.

A field containing simply:

Dietary requirements: Yes

is not particularly useful.

Good records should make relevant information understandable.

SEND and additional needs

A child record may also contain information about SEND or other additional needs.

This is an area where usefulness matters more than labels.

Knowing a diagnosis can sometimes provide useful context.

But practitioners may gain much more from information such as:

• communication needs
• sensory needs
• known triggers
• signs that a child is becoming overwhelmed
• regulation strategies
• calming strategies
• agreed adjustments
• mobility or accessibility requirements
• support arrangements
• approaches that have worked well previously

This does not mean a record should attempt to reduce a child to a list of behaviours or strategies.

Children change.

Context matters.

What worked six months ago may not work today.

The record should support practitioners in knowing the learner, not replace the relationship with the learner.

Information should describe support, not define the child

The language used in child records matters.

There is a difference between recording useful information and creating a permanent collection of subjective judgements.

Statements such as:

"difficult child"

or

"always badly behaved"

are not useful descriptions of need.

They are labels.

A more useful record might describe:

• what happened
• the context
• what the child appeared to need
• what support was offered
• what helped
• what practitioners may want to consider next time

The Forest School Association describes behaviour as communication and emphasises learner-centred practice responsive to learners' needs and interests.

That is a useful principle for records too.

Consent needs enough detail to be meaningful

Forest School providers may need various permissions or consents depending on what they do.

Photography is a good example.

A single field saying:

Photo consent: Yes

may be insufficient if photographs are used for different purposes.

A family might be comfortable with a photograph being used:

• internally
• in their child's private Learning Journey

but not:

• on social media
• on a public website
• in printed marketing

If a setting distinguishes between those purposes, the child's record needs to preserve those distinctions.

The same principle applies more broadly.

A record should not create the appearance of consent while losing what the person actually agreed to.

If not, the information may be too vague to guide a real decision.

Attendance becomes part of the child's history

A child record is not necessarily limited to information entered by a parent when the child first registers.

Over time, operational information can build a history.

Attendance is one example.

A provider may need to know:

• which sessions the child was booked to attend
• which sessions they actually attended
• dates of attendance
• absences or cancellations where relevant

The immediate purpose of a register is knowing who is present and who the setting is responsible for.

Over time, however, attendance records can also provide useful historical context and evidence.

This is one reason it is helpful to distinguish between a current session register and the child's longer-term record.

They are connected, but they serve different purposes.

Accidents and incidents

If a child has an accident or relevant incident, that record may also become connected to their history with the setting.

A useful record may need to establish:

• what happened
• when and where it happened
• relevant circumstances
• action taken
• first aid or other response where applicable
• who was informed
• any appropriate follow-up

Exactly what must be recorded and how long records should be retained can depend on the nature of the provision and the legal or regulatory framework that applies.

Providers should therefore avoid assuming that one retention rule applies universally to every Forest School.

There is also a practical distinction between responding to an accident and documenting it.

The child's immediate care comes first.

The record exists to document and support accountable practice afterwards.

Observations and Learning Journeys

Forest School is a long-term process.

The Forest School Association describes planning, adaptation, observation and review as integral elements of Forest School and states that practitioner observation is an important part of Forest School pedagogy.

That means some child records may contain something very different from administrative or safety information:

a record of the child's journey.

Over time, observations might capture:

• interests
• confidence
• independence
• social interaction
• problem solving
• emotional regulation
• engagement with the natural environment
• supported risk-taking
• emerging skills
• moments of particular significance

This information serves a different purpose from medical or emergency information.

It helps practitioners understand progression, interests and development over time.

Not every moment needs recording.

The purpose of observation is not to produce the largest possible archive.

It is to preserve meaningful information that contributes to understanding the child's experience.

Different information has different audiences

One of the easiest mistakes in digital record keeping is to assume:

If the organisation holds the information, every member of staff should be able to see it.

That does not necessarily follow.

An administrator processing payments may need information that a session assistant does not.

A practitioner responsible for a child may need medical, allergy or SEND information that somebody handling marketing does not.

A safeguarding record may require significantly more restricted access.

Financial information may have no relevance to a practitioner delivering a session.

Good information architecture should therefore consider role and purpose, not simply whether someone is a member of staff.

Data minimisation matters

UK GDPR includes the principle of data minimisation.

Personal data should be adequate, relevant and limited to what is necessary for the purposes for which it is processed.

That principle is particularly important when records concern children and when sensitive information is involved.

A useful question is:

Why are we collecting this field?

If there is no clear answer, it is worth asking whether the information needs to be collected at all.

If not, the problem may not be that your child record needs more fields.

It may need better information governance.

Keeping information accurate matters as much as collecting it

A beautifully designed registration form only tells you what was true when somebody completed it.

Children and families change.

Over time:

• telephone numbers change
• addresses change
• medical circumstances change
• allergies may be newly identified
• medication may change
• SEND support may evolve
• emergency contacts change
• consent decisions may change
• support strategies may become outdated

A child record therefore needs a process for keeping information current.

This might involve:

• allowing parents or carers to update information
• asking families to review information periodically
• highlighting important changes
• recording when information was last reviewed
• ensuring practitioners receive relevant updates

The exact process will depend on the provision.

What matters is recognising that data quality is an ongoing responsibility.

What about old information?

Not everything should necessarily remain in the active record forever.

Some information has an obvious historical purpose.

Other information may become irrelevant.

UK data protection principles include storage limitation: personal data should not be kept for longer than necessary for the purposes for which it is processed.

But "delete everything old" is not a sufficient retention policy either.

Some records may need to be retained because of:

• legal obligations
• safeguarding requirements
• insurance requirements
• accounting requirements
• regulatory requirements
• legitimate operational or evidential needs

Different categories of information may therefore need different retention periods.

A good system should make those distinctions possible.

A child record is more than a registration form

This may be the most useful distinction.

A registration form collects information at a point in time.

A child record can become something much broader.

It may connect:

• current family information
• emergency contacts
• medical information
• allergies and dietary requirements
• SEND and support information
• consent
• bookings
• attendance
• accidents or incidents where appropriate
• observations
• Learning Journey history
• relevant updates over time

That does not mean all of those things need to appear on one screen.

In fact, they probably should not.

The value comes from maintaining a coherent history while presenting the relevant parts in the right context.

What should the practitioner see during a session?

This brings us to an important distinction.

The complete child record and the information a practitioner needs during today's session are not the same thing.

During a session, relevant information might include:

• child identity
• attendance
• relevant medical information
• allergies
• dietary requirements
• emergency contacts
• SEND information
• triggers and regulation strategies
• relevant consent

The practitioner probably does not need the entire administrative history.

This is where thoughtful record design becomes particularly important.

A practical child-record review

Take one child record from your setting and ask:

Identification

• Can we confidently identify the child?
• Are parent or carer details current?

Emergency

• Do we have current emergency contacts?
• Could the relevant practitioner access them if needed?

Health

• Do we hold the medical and allergy information we genuinely need?
• Is it clear and current?
• Is access appropriately restricted?

Individual support

• Does the record contain useful information about SEND or additional needs where relevant?
• Does it describe strategies that actually help the child?

Consent

• Can we tell what has actually been agreed?
• Are different purposes distinguished where necessary?

History

• Can relevant attendance, incidents and observations be understood over time?

Accuracy

• When was the information last reviewed?
• Can parents or carers tell us when something changes?

Privacy

• Why do we hold each category of information?
• Who can access it?
• How long should it remain?

If those questions are difficult to answer, adding more fields is unlikely to solve the underlying problem.

The record should help people care for the child

A child record sits at an interesting intersection.

It is administrative.

It can be operational.

It can contain sensitive information.

It can provide evidence.

And, in a long-term Forest School programme, it can also help tell the story of a learner's experience over time.

That creates a responsibility to treat it as more than a form that parents complete before the first booking.

A useful record should be accurate enough for administrators, accessible enough for practitioners, protected enough for the child and flexible enough to remain useful as circumstances change.

Most importantly, it should serve a purpose.

The goal is not to know everything about a child.

It is to make sure the people responsible for them have the information they genuinely need to support them well.