Raising a concern about another member

Most of what goes wrong in an academy gets sorted on the mat. Some of it does not, and the person who notices is usually a member rather than a coach: someone training through an illness they have not mentioned, someone who ignores a tap, someone whose behaviour in the changing room is making a beginner not come back.

Reports give that a private route to the people who can act on it.

They are off until you turn them on. Settings, then your academy, then Member reports, behind a short disclaimer worth reading.

What a member does

On a training partner's card there is a quiet Report a concern. It opens a list of reasons in two groups, six about ordinary conduct and five about safeguarding, an optional note for staff, and a choice of sending it signed or anonymously.

Three a day, and only one about the same person per day. A member also needs a date of birth on file before they can send one, because the system has to know whether the person raising the concern is a child.

Where it goes

Ordinary conduct reaches the owners, and the managers too when the academy has chosen to let them see conduct reports.

Anything else goes to owners only, always: any report about a young member, any report naming a member of staff, and any report sent by a minor. That is not a setting and cannot be changed.

A report about an academy's only owner is refused outright, with a pointer to the police and to MatPilot support. It is the one case where filing it inside the academy would put the report in front of the person it is about, and a system that quietly did that would be worse than one that says it cannot help.

Signed or anonymous

Signed is usually better. Staff can come back to you for the detail that decides what happens, and most concerns turn on a detail.

Anonymous is genuinely anonymous. Nothing stored against the report points back at the sender, which is what makes it safe to raise something about somebody you have to train beside next week. It also means nobody can ask you anything afterwards, and you cannot take it back, so put enough in the note to act on: it is all your academy will ever have.

Either way, you can tick Also block them as you send. Neither of you can then find the other by name, give kudos, or start a conversation. They are not told, and it changes nothing about the report itself. You can undo it in your account settings.

What nobody sees

The person reported is never told a report exists. Not in a notification, not in their profile, not in the academy's activity log, and not in the copy of their data they can ask for.

Nor does the person who sent it keep a list. Reports are not shown to members at all, including the member who raised one. A list of concerns you have filed about people you train beside, sitting in the app next to those people, is not a thing anyone should carry around.

Owners are told a report has arrived by an email and a notification carrying nothing but the academy's name. The reason, the names and the note live in the tray, behind the same permissions the report was routed by.

What an owner does

Reports gather under Members, in a tray showing who and when, the reason, the note, and whether it was signed. You set each one to Reviewed, Actioned or Unfounded, and add a staff note.

Reports are kept for five years and then deleted automatically. They are excluded from the reported member's own data export, because a report about you is a record about somebody else's concern, not a record of you.

Nothing about a report is written to the academy's activity log, on purpose: that log is readable by every owner, and a line in it would tell a reported co-owner that a report exists.