How the period is going
Enrolments by session, by destination and by programme, set against the matching period of the previous season.
The eighth module of DBJOY turns operational data into decisions: a management dashboard, the real margin by session, destination and programme, production by partner school, and the comparison between what you quoted and what you actually banked.
The dashboard reads the live booking files and the closed ones: sales for the period, enrolments open, sessions about to depart, instalments expected, margin earned. It is not a report you have to ask somebody for; it is the first thing you see when you log in.
Enrolments by session, by destination and by programme, set against the matching period of the previous season.
Allotments about to expire, release dates approaching, family instalments not yet received, sessions still below the guaranteed departure threshold.
The dashboard has no database of its own. It reads the same booking files that sales, operations and finance work on, so there is nothing to consolidate.
Every booking file carries its own revenue and its own costs: partner school and accommodation net rates in the contract currency, the exchange rates applied, cancellation charges, no-shows, free places granted to accompanying teachers. The margin of that file is the difference between what you took and what you really spent on that session, not a departmental average.
From there the numbers aggregate along the dimensions that matter when you decide where to put next season’s money.
A session is sold on an expected margin and closed on a real one. The distance between the two is never an accident: it always has a cause, and the cause is only recoverable if you can see it.
If the gap repeats on a destination, the problem is in the rate card. If it repeats on a partner school, the problem is in the contract. If it repeats on a salesperson, the problem is in the discount policy.
Three different diagnoses, three different actions. Without the comparison, all three read as “this year went worse”.
A report is useful if it answers the question somebody is asking today. In DBJOY the views change with the role, but they all rest on the same booking files: nobody works from a different extract than a colleague.
Where the season’s margin sits and where it is being eroded. Which destinations and which partner schools deserve more allotment and which should be cut back before next year’s contracts are signed.
Which rate cards stand up against the net rates actually confirmed, and which need revising. Which sessions really fill and which stay below the guaranteed departure threshold every year.
Which enrolments are still open, which allotments expire shortly, and which schools and agents come back every season rather than buying once.
Reports are exported so they can be shared with people who do not log into the system, from the board to the firm that keeps the books. Your data stays yours and stays exportable even if one day you decide to change software.
The production report by partner school shows how many students, how many weeks of tuition and how much purchasing went through each school, over which sessions and at what margin for you. It is the document that changes the tone of a renewal: you are not asking for better terms in the abstract, you are asking for them against the value you brought.
The same report tells the other half of the story: places contracted and never sold, and sessions that closed below the guaranteed departure threshold. An allotment left unsold weighs as much in a negotiation as one sold badly, and the two are worth seeing together before you sign the next season.
Turnover tells a study travel operator how much work went through the company. Margin tells the operator which of that work actually paid. DBJOY reports margin per booking file, because a high-turnover destination with heavy partner school costs and a smaller destination with strong mark-up look almost identical on a turnover report and completely different on a margin report.
DBJOY is designed to report margin along the dimensions a study travel operator actually manages: booking file, session, destination, partner school, programme, salesperson, family and travel agency. The point is comparability, with the same margin definition applied across every dimension, so a decision about next season rests on consistent figures rather than on separately built spreadsheets.
DBJOY holds partner school and accommodation costs attributed to booking files, so purchase volume per school, per destination and per season can be read from the same data that produces the margin. That figure is the basis of a negotiation: a conversation about next season’s rates goes better with the actual volume in hand than with an impression of it.
A study travel operator regularly needs figures outside the system: for the accountant, for a board pack, for a bank. DBJOY is designed so report data can be extracted rather than only viewed on screen. Which export options are available, and which reports they cover, is confirmed on the operator’s actual configuration during set-up rather than promised in advance.
Didn't find your question? Go to the full FAQ hub
We set the system up together on your own rates, partner schools and destinations. At the end of the three months the decision is yours, with no strings attached.
No credit card. No automatic renewal. Your data stays yours and stays exportable.