CCFuse · RespectLog

Record the incident.
Preserve the evidence.
Manage the follow-up.

Incident reporting for community sport. One record per incident, with every photo, statement and decision attached to it and timestamped, so a league can see what was reported and what was actually done about it.

Talk to us about a pilot See what gets recorded

Built for leagues, associations and clubs. Reports can be filed by officials, club staff, volunteers and spectators.

Example case timeline

OPEN

  1. 3:42 PM

    Incident recorded at the ground

  2. 3:47 PM

    Spectator asked to leave

  3. 4:03 PM

    Report submitted by the match official

  4. 4:09 PM

    Three photos attached

  5. 4:12 PM

    Match footage timestamp linked

  6. 7:18 PM

    Witness statement received

  7. NEXT DAY

    League administrator assigned the case

  8. +7 DAYS

    Outcome recorded, case closed

Today

One incident, eight places

Most clubs already deal with incidents. The information just arrives in pieces, and the pieces live in different places.

  • An email to the club secretary
  • Texts between volunteers
  • A paper form in a folder
  • Screenshots on someone's phone
  • A phone call nobody wrote down
  • Match footage in another system
  • A witness who was never asked
  • A decision with no record of why

With RespectLog

One incident, one record

The reporter answers questions relevant to what happened, rather than filling in one generic form. Everything they add stays attached to the same case.

Guided by incident type
A hazard report and a safeguarding concern need different questions. The form changes to suit.
Routed automatically
The reporter does not need to know who at the club or league should receive it.
Witnesses can add their own account
They get a private link and a form. No app to install, no account to create.
Follow-up is part of the record
Assignment, requests for more information, actions taken and the outcome all sit on the same timeline.

What people report

Behaviour is where it starts, not where it ends

Abuse and misconduct

Abuse of officials, spectator behaviour, threats, and player, coach or team-official misconduct.

Injury and concussion

Injuries and suspected concussions, including what was observed at the time and who was told.

Ground and equipment hazards

Lighting, surfaces, access and equipment problems, so the same ground does not keep causing them.

Child-safety concerns

Handled as restricted records, visible only to the people with a safeguarding role.

Online abuse

Abuse that starts at the ground and continues in messages, team chats or social media afterwards.

Exclusions

Ejections, venue removals and longer-term exclusions, with the reasoning kept alongside them.

The record

Evidence is only useful if you can say where it came from

A photo in a group chat is not evidence of much. RespectLog keeps the file with the facts about the file, so months later it is still clear who provided it, when, and whether anyone changed it.

Every time someone opens a piece of evidence, that is recorded too.

Captured with every attachment

uploaded_by
The person who provided it, and their role at the time
uploaded_at
When it reached the system, not when someone typed a date
captured_at
When the photo or video was actually taken
checksum
A fingerprint of the file, so a later copy can be checked against it
original
Whether this is the original or an edited or redacted copy
accessed_by
Everyone who has opened it since

What it is not

A report is an allegation, not a finding

It does not replace anyone you are required to contact

Filing here is not a report to emergency services, police or a child-protection authority, and it does not discharge a mandatory reporting duty. The forms say so at the point it matters.

It does not decide who was right

The system records what was reported and what was done. It does not judge whether an allegation is true, assign blame, or recommend an outcome.

It does not show everything to every admin

Child-safety and medical detail are restricted to the people who hold those roles. A general association administrator does not get access by default.

Already using RespectPlay?

Your clubs, teams, venues and fixtures are already there

RespectPlay and RespectLog are separate products that share one CCFuse account. An association already using RespectPlay does not set up its competition again, re-enter clubs and venues, or invite its administrators a second time. Reports attach to games that already exist.

Product access is granted separately, so RespectPlay administrators do not automatically get access to incident records.

Tell us how incidents reach you now

We are working with a small number of leagues and associations to shape the first version around processes that already exist. If you handle incident reports, we would like to hear how that currently works.

Get in touch