Who Changed What? Activity History for Tuition Centres

A parent says the fee was Rs 2,500, your records say Rs 3,000. A batch has vanished from the list. A student's status is "Inactive" and the front-desk team swears they did not touch it. In a centre with a few staff members, a couple of branches and a shared spreadsheet, these questions usually end in a shrug.

An activity history (also called an audit log or change history) turns the shrug into an answer: who did it, what they changed, and what the value was before.

What an activity history should answer

When something looks wrong, owners almost always ask the same five questions:

Question	What you need to see
Who made the change?	Name and role of the person
What was changed?	The record (student, batch, fee, enquiry) and the field
What was it before?	The old value next to the new one
When?	Date and time, in your timezone
Where?	Which branch, if you run more than one

If your system cannot show all five, it is a log in name only. A list of "something was updated" lines does not help you settle a fee dispute.

What TuitionDesk records

In TuitionDesk the page is in the sidebar as Change history, and the page itself is titled Activity History. Each row shows:

The person who acted, with their role, for example a teacher or a branch admin.
The action: created, changed, deleted or signed in.
The record, shown by name (for example the student's name) rather than an internal ID. If the record has since been deleted, the row says so.
The branch, for centres with more than one.
The time of the change.

Open any row and you get the details view, with the changed fields laid out as old and new values side by side. Field names are written in plain words such as "Fee status" or "Due date", and your own labels apply: if your centre calls students "learners" or batches "classes", the page uses those words.

Bulk actions stay readable

If someone imports 40 students or edits many records in one go, you do not want 40 near-identical rows. TuitionDesk groups consecutive rows by the same person, the same action and the same record type within the same minute into one line, which you can expand when you need the detail.

Filters that make it usable

The page has filters for:

Record type: student, batch, teacher, organisation, fee, fee transaction, enquiry, branch and sign-in.
Action: create, update or delete.
User: pick one staff member.
Date range: start and end date.

Results come 50 to a page, newest first. A typical dispute takes three clicks: filter to Fee, set the date range around the complaint, open the row.

Pair this with fee corrections. When you reverse a payment, void a fee line or waive a late fee, the correction itself should leave a trail. The activity history is where you check that it did.

Who can see it

Visibility follows permissions, so that the history does not become a surveillance tool for everyone:

Account owners see all activity in their organisation.
Staff with the view all activity permission see all activity in the branch they have access to.
Staff with only the view own activity permission see just their own actions.
A branch admin is limited to the branches they are assigned to.

Entries are always scoped to your own centre: one academy can never see another's history. You can set these permissions per role, which pairs well with separate teacher logins so that every action is tied to a real person instead of a shared password.

Plan availability: we have seen different statements about which plans include the full Activity History, so we are not quoting a tier here. Check the pricing page for the current answer. On any plan, actions taken by TuitionDesk support inside your account are still visible to the account owner.

Five ways owners use it

Fee disputes. Show a parent exactly when a fee line was created or edited, and by whom.
Onboarding new staff. Review the first week of a new front-desk person's changes without hovering over their shoulder.
Finding the "missing" record. Filter by Delete to see what was removed and when.
Branch oversight. In a multi-branch centre, check what a branch admin changed without phoning them.
Sign-in review. Filter by sign-in to see when staff accounts were used.

A short routine that works

You do not need to read the history daily. A light habit is enough:

Weekly, 10 minutes: filter to Fee and Delete actions for the last seven days. Look for anything you do not recognise.
When a complaint arrives: filter by record type and date before you reply to the parent, so your answer is based on the record and not memory.
After staff changes: when someone leaves, review their last month of activity, then remove their access.

What it does not do

Be honest about the limits. An activity history records what happened inside TuitionDesk. It does not tell you why someone did it, and it does not replace a conversation. It also does not recover deleted data on its own. It tells you what was deleted so you can decide what to do next. For money questions, keep a written reason on each correction, which TuitionDesk asks for when you waive or void a fee.

Know who changed what, without asking around

Trust in a team is easier when the records can speak for themselves. A clear activity history protects honest staff as much as it catches mistakes.

Create your free TuitionDesk account and see how change history looks for your own centre.