Use this when... you want to understand how the tuition business is performing across lessons delivered, student engagement, billing activity, and revenue trends.

Before you start... check that sessions are scheduled, attendance is recorded, invoices are issued, and payments are reconciled. Reports are only useful when the underlying operational data is current.

Use Analytics to connect teaching activity with financial and operational outcomes.

Revenue, attendance, and student activity should be reviewed together. Revenue alone can hide delivery problems. Attendance alone can hide payment delays. Student activity alone can hide whether the work is profitable. TuitionFlow reports are most useful when you compare these signals instead of treating each number in isolation.

Select the date range that matches the question you are asking. Daily views are useful for operations. Weekly views are useful for teaching delivery. Monthly or termly views are better for revenue, retention, and growth.

Expected outcome: the report reflects the period you intend to review, rather than mixing current activity with older data.

Look at invoiced revenue, paid revenue, unpaid balances, credits, and any payout-related figures available to your organisation. If invoiced revenue is strong but paid revenue is lagging, move into Billing and aged debt review.

Move from Analytics to Billing when a revenue metric needs invoice-level investigation.

Check scheduled sessions, attended sessions, cancellations, no-shows, and missing attendance. Missing attendance is especially important because it can affect parent communication, billing, tutor pay, and reports.

Use Scheduling to investigate attendance patterns behind the report.

Look for active students, new starts, trial conversions, inactive students, and students without upcoming sessions. These signals help you spot retention issues, onboarding gaps, or capacity problems.

Revenue looks too low: check draft invoices, invoice date filters, payment status, and whether credits or voided invoices are included.

Attendance looks wrong: check session status, date range, branch filters, and whether tutors have recorded outcomes.

Student activity does not match your expectation: review inactive filters, future sessions, and whether new leads have been converted into student records.

Use a short daily check for urgent operational problems, a weekly check for lesson delivery and attendance quality, and a monthly check for revenue, retention, and growth decisions. Save screenshots or exports only when they are needed for management reporting.

When reviewing reports, ask what changed, whether the change is expected, and what action follows. A fall in attendance may be normal during holidays. A rise in unpaid revenue may be normal just after invoices are issued. A drop in active students may need retention follow-up if it continues across several weeks.

Before sharing a report, check for missing attendance, draft invoices, unconverted leads, duplicate student records, and unusual date filters. These issues can make a report look alarming when the problem is incomplete data rather than business performance.

Give each audience the right level of detail. Owners may need revenue and trend summaries. Admins may need action lists. Tutors may need attendance or student engagement information, but usually not parent balances or wider financial details.

Do not compare a partial week with a full week, a school-holiday month with a normal teaching month, or paid revenue with invoiced revenue. Add context when sharing figures so the team understands whether movement is expected or unusual.

End each review with one or two clear actions. For example, chase missing attendance, review overdue invoices, contact inactive families, or follow up high-quality leads. Reports are most useful when they change what the team does next.

When a metric needs action, open the relevant record: Billing for payment issues, Scheduling for delivery issues, People for student status, and Leads for pipeline activity.