Governance & Reporting

This page consolidates authority levels, sign-off evidence, reporting, reconciliation and team operating model standards.

Authority Levels

Authority defines what a person may do within a specific operating scope. It is not a job title and is not automatically granted by completing a chapter.

Level	Name	May Do	Must Not Do Without Higher Approval
Level 1	Observe & Record	Monitor dashboards, collect evidence, prepare updates	Change production settings, client-impact decisions, risk-control changes
Level 2	Supervised Action	Execute clearly defined checklist tasks under review	Independently change configuration, restrict clients or take unapproved risk actions
Level 3	Independent Routine Operation	Own routine shift monitoring, approved SOP execution, escalation and handover	High-impact parameter changes or emergency controls outside SOP
Level 4	Control Approval	Approve or lead higher-impact controls and exception reviews	Policy-exception action without evidence, record or governance review

Shift Leader Confirmation

The on-duty Dealer should notify or seek confirmation from the Shift Leader when:

• A client-impact action may be required.
• A risk action, temporary control or configuration change is considered.
• Quote, Bridge or execution conditions materially deteriorate.
• Abnormal order flow or client-impact scope is unclear.
• An item has no responsible person, approval record or next update time.

Authority Sign-Off Evidence

Dealer:
Scope:
Training / SOP review:
Observed shift samples:
Evidence quality:
Escalation quality:
Handover quality:
SOP discipline:
Approved authority level:
Limitations:
Reviewer:
Review date:
Next reassessment:

Reporting and Reconciliation

Reporting and reconciliation are control processes. They confirm that platform records, broker reports and regulatory-facing records remain consistent.

Minimum standard:

• Use the correct reporting date, timezone and platform scope.
• Compare account, symbol, order ID, volume, open / close time and trading result.
• Separate timing differences from real breaks.
• Escalate differences affecting client balance, platform records or regulatory reports.
• Record correction reason, responsible person and timestamp when a report must be amended.

Team Operating Model

Work Area	Standard
Platform and Bridge awareness	Chapter 2 teaches concepts; Operations Manual defines records and escalation
Client behavior review	Chapter 3 teaches evidence; Incident & Risk Workflow defines escalation language
Exposure and event controls	Chapter 4 teaches risk logic; Incident & Risk Workflow defines action boundaries
Handover and audit trail	Chapter 6 teaches discipline; Shift Operations defines required records
Reporting and reconciliation	Governance & Reporting defines quality and escalation standards

Quality Rule

Good governance makes work repeatable. Every controlled action should have evidence, authority, responsible person, validation and closure.