Atlas / tournament documentation

Compliance

The Compliance Reports screen, the read-only compliance seat, and how policy agreements from competitors and judges are recorded.

Compliance Reports is the screen where a tournament's administrators file and resolve conduct issues, such as a script check that failed, a code of conduct concern, or any other matter that needs follow-up with a team. Each report names the issue type, optionally the affected entry, the compliance room where the matter is handled, and notes. A report stays pending until an administrator marks it resolved.

The screen is the second view under the Records item in the left rail, labelled Compliance. The route is /tournaments/{tournamentId}/admin/compliance. The screen heading is Compliance Reports. The first view under Records is the audit trail, described in Results and closeout.

Who can use it

Role	Reads the reports	Files and resolves reports
Platform admin	Yes.	Yes.
Organization owner or admin	Yes, for the organization's tournaments.	Yes.
Tournament admin seat	Yes.	Yes.
Tab seat	Yes.	Yes. The tab seat is refused only fees, refunds, promo codes and announcements.
Compliance seat	Yes. The heading text changes to: Every report filed for this tournament, read only. The tournament's administrators file reports and mark them resolved.	No. The filing form and the Mark Resolved button are not drawn. A request sent to the screen's actions anyway is refused with: You do not have access to manage compliance reports.
Coach, competitor, judge, observer	No. The screen answers as if it did not exist.	No.

The screen also answers as if it did not exist when the tournament belongs to a different organization than the one the address is scoped to.

The screen at a glance

Part	What it shows	Default or limit
Compliance Reports	The heading.	The page title in the browser tab is Compliance followed by the tournament name.
Intro text	For a role that can file: File an issue, contact the affected team, and record the compliance room. After the issue is addressed, use Mark Resolved. Keep the report open when follow-up is still needed. For a compliance seat: Every report filed for this tournament, read only. The tournament's administrators file reports and mark them resolved.	Fixed text.
Filing form	File a New Report. See the next heading.	Drawn for roles that can file, in the left column.
Report list	Every report filed for the tournament, newest first, as cards.	No filter, no search and no paging. A compliance seat sees the list across the full width.
Empty list	No compliance reports filed yet.	Shown when the tournament has no reports.

File a New Report

Control	What it does	Default or limit
Issue Type	A choice of Script Check, Code of Conduct or Other. A script check is a review of a competitor's prepared material before the round.	Required. The first option, Script Check, is selected when the form opens.
Competitor / Team	A list, whose label carries the word Optional, of every registration in the tournament, sorted by participant name, with the partner's name after an ampersand when the entry has one. The first option, General / Unspecified, files the report against no entry.	Optional. Defaults to General / Unspecified. The list includes entries of every status, including dropped entries.
Compliance Room	A text box for the room where the matter is handled. The placeholder is e.g. Room 101.	Optional. Free text. The screen sets no length limit.
Notes / Details	A text area of four rows for the details. The placeholder is Details of the issue...	Optional. Free text. The screen sets no length limit.
Submit Report	Saves the report with the status pending and the signed-in account as its author.	The form clears and the screen reloads with a confirmation.

A saved report shows this confirmation at the top: Report filed. Review the issue, contact the team if needed, and resolve it once the follow-up is complete. The report appears at the top of the list.

Report cards

Part of the card	What it shows	Notes
Issue type chip	Script Check, Code of Conduct or Other, as filed.	Shown in the accent colour.
Status chip	pending in amber or resolved in green.	See Statuses below.
Mark Resolved	A button at the top right with the line Use after the issue is addressed. beneath it.	Drawn only for a role that can file, and only on a pending report.
Team	The entry the report was filed against, with the partner after an ampersand.	Drawn only when an entry was chosen.
Room	The compliance room as typed.	Drawn only when a room was typed.
Notes	The notes as typed, with line breaks kept.	Drawn only when notes were typed.
Filed	The time the report was filed, for example Oct 19, 2026, 3:55 AM EDT.	In the tournament's time zone, with the zone named.

The card does not show who filed the report. The account is stored with the report and is not displayed.

Statuses

Status	Meaning	How it changes
pending	Filed and not yet resolved. Every new report starts here.	Mark Resolved moves it to resolved.
resolved	The follow-up is complete.	Final. The screen has no control to reopen, edit or delete a report. Mark Resolved is not drawn on a resolved card.

After Mark Resolved the screen shows: Report marked resolved and removed from the pending work queue. The report stays in the list with the resolved chip. Keep a report pending while follow-up is still needed.

What is recorded

Each report stores the tournament, the issue type, the status, the notes, the room, the entry when one was chosen, the account that filed it, and the time it was filed and last changed.
Filing or resolving a report does not write a row to the Records audit trail, and reports are not in the closeout packet.
A pending report does not block Finalize. The Finalize check named judge compliance concerns judges' policy agreements, not these reports.
A finalized tournament still accepts new reports and resolutions. Finalize locks pairings, rounds, ballots and disputes only.
Nothing is sent to the team or to anyone else when a report is filed. The follow-up with the team happens outside the product.

Policy agreements

Competitors and judges each give a policy agreement. These are not shown on the Compliance Reports screen. They live in Setup, in the registration flow, and in Field.

Who	Where it is given	What it says or does	Where an administrator sees it
Competitor	The registration cart, one agreement for each claimed entry. The button reads I have read and agree to the tournament rules/safety policy. After it is pressed the entry shows Policy acknowledged.	The product shows no policy text beside the button. The tournament's rules are whatever its organizers published elsewhere. Checkout is refused for the whole cart until every claimed entry is acknowledged, with: Every registrant must acknowledge the compliance policy before checkout.	Field, Registrations, in the stage strip: Policy signed, with the count of acknowledged cart entries, and the note compliance acknowledged or not required at this tournament.
Judge	The judge's own registration page. The judge reads Mandatory Safety & Compliance Affirmation, which holds three statements, and presses I formally affirm and acknowledge these requirements.	The statements cover the sex offender registry, completed background checks and safety training, and the code of conduct and equity policies. The text is fixed in the product. Pressing the button records the time and sets the judge's status to confirmed. Orientation is a separate step that follows.	Field, Judges. A judge without it appears under the filter Compliance, with a note that names the missing step, such as Compliance statement and orientation incomplete, and says the judge cannot be seated until both are done.

Setting or control	What it does	Default or limit
Require the compliance policy before an entry is complete	A switch in Setup, in the Registration section. When on, competitors must acknowledge the policy at checkout. The Setup text says: Policy signed stage in Field. Judges sign the same statement before they can be confirmed.	On when the tournament never set it. When off, the cart shows no acknowledgment button and checkout does not ask for one.
Compliance statement acknowledged	A checkbox on a judge in Field, Judges, for an administrator who holds the signed paper copy. The hint reads: Tick if they signed the paper copy at the desk.	Unticked until recorded. The judge cannot be set to confirmed until it is ticked. The refusal reads: A judge cannot be confirmed without the compliance statement.

The Setup switch controls the competitor step only. A judge is asked for the affirmation whatever the switch says, and Finalize checks every judge who is not withdrawn.
An acknowledgment is a time stamp. There is no document upload, no signature capture and no policy version recorded.
Unticking the checkbox on a confirmed judge sends the judge back to pending.

The compliance seat

A compliance seat is one of the three seats a tournament can give a person, beside the admin seat and the tab seat. The organization's owner and admins grant it on Users & roles, where it is described as: Read-only: view Records and compliance reports, and change nothing. The invitation mail says: You have been invited to, followed by the tournament name, with the Compliance seat.

What the seat can do	What the seat cannot do
Open Records, read every audit entry and take the Export CSV file.	Open Overview, Setup, Field, Rounds, Ballots, Standings, Announce or any other admin screen. Opening one sends the seat to Records with a notice.
Open Compliance Reports and read every report.	File a report or mark one resolved.
See entry, pairing, ballot and judge names that label Records rows.	Read a judge's email or phone. The seat is given no read of judge contact details.
Use the rail items Records, with the views Audit and Compliance.	See the closeout band, Finalize, the ballot export or the closeout packet.

The limits hold in the database as well as in the screens. The seat is excluded from the set of tournaments a person administers, so an action sent to the server by any other route is refused. The seat's reads are limited to the audit log, compliance reports, registrations, pairings, ballots and judge registrations.

A person who holds the seat sees policy agreements nowhere, because the screens that show them are not open to the seat. An administrator exports or reads them on the tournament's behalf.

Tasks

File a report.

Open Records in the left rail. Select Compliance.
In File a New Report, choose an Issue Type.
Choose the entry in Competitor / Team, or leave General / Unspecified.
Type the room in Compliance Room.
Type the details in Notes / Details.
Select Submit Report.

After the last step the screen shows Report filed and the report is at the top of the list with the status pending.

Resolve a report.

Open Compliance. Find the pending card.
Contact the affected team and complete the follow-up outside the product.
Select Mark Resolved on the card.

After the last step the screen shows Report marked resolved, and the card carries the resolved chip.

Record that a judge signed on paper.

Open Field and select Judges.
Select the judge.
Tick Compliance statement acknowledged.
Select the save button at the foot of the panel, which reads Save changes on the judge's behalf. The judge's status can then be set to confirmed.

Check that every competitor has agreed to the policy.

Open Field and select Registrations.
Read the Policy signed stage and compare its count with Claimed.
Ask each registrant with an open cart to press the acknowledgment button before checkout.

Troubleshooting

Message	What it means	What to do
You do not have access to manage compliance reports.	The account that sent the form is not an admin or tab seat on this tournament, for example a compliance seat.	Ask a tournament admin to file or resolve the report.
Could not check your admin access. Try again.	The access check did not run. It says nothing about the account's rights.	Reload and try again.
This tournament is outside the active organization scope.	The tournament belongs to a different organization than the address in use.	Open the tournament from its own organization's address.
Could not verify the tournament: followed by a database reason	The tournament could not be read when the form was sent.	Try again. If it repeats, report the reason shown.
That compliance report no longer exists.	The report was removed after the page loaded, or it belongs to another tournament.	Reload the screen.
Could not file the compliance report: followed by a database reason	The save failed. The screen raises an error page rather than hide a lost record.	Select Try again on the error page, then check the list before filing the report a second time.
Could not resolve the report: followed by a database reason	The status change failed.	Reload and select Mark Resolved again.
Report filed. Review the issue, contact the team if needed, and resolve it once the follow-up is complete.	Confirmation of a saved report.	None needed.
Report marked resolved and removed from the pending work queue.	Confirmation of a resolved report.	None needed.
No compliance reports filed yet.	The tournament has no reports.	None needed.
Every registrant must acknowledge the compliance policy before checkout.	A cart holds a claimed entry without the policy acknowledgment.	Each registrant presses the acknowledgment button in the cart, or Setup turns off Require the compliance policy before an entry is complete.
A judge cannot be confirmed without the compliance statement.	An administrator set a judge to confirmed with the checkbox unticked.	Tick Compliance statement acknowledged first.