Reporting in AceDraft for Teams: What the Report Shows

There is no date picker on this page. Not a hidden one, not a quiet default of the last thirty days: every figure Reporting shows covers the whole life of your organisation, so pulling one term out on its own means exporting twice and subtracting by hand. I haven't watched this page run. I read its code on 19 September 2026, and everything below is what the code says.

Key takeaways

Admin only. The route and the endpoint behind it both check the role.
Five tiles across the top for money and export counts, one table under them for per-batch usage.
Export CSV writes those same figures to a file, built in your browser from what already loaded.
Limitation: no date range, no filter, no paging, no per-student rows.
Limitation: the Resumes column counts every resume a batch member has ever made, including work from before they joined that batch.

Prerequisites. An admin account and an organisation. With no organisation linked to you, the server answers with nothing and the page stops at its heading.

Who can open Reporting?

Enterprise admins. The route carries an admin-only role list, and the guard bounces anyone else: a student to their own resumes, a moderator to the dashboard. The endpoint repeats the check itself, so a hand-made request from a moderator's session is refused too.

Scope comes from your session. The organisation id is read off your token and every query filters to it, so there is no organisation switcher.

The five tiles across the top

They read Spent, Topped up, Paid exports, Free exports, Credits left. The first two carry your wallet's currency in front of the number; the last three are plain counts.

Four of the five come from your organisation's wallet history. Spent totals the export charges, Topped up totals both manual top-ups and automatic recharges, and the two export tiles count charged exports and free-credit exports separately. All lifetime, because the query has no date bound at all.

Credits left is the odd one. It skips the wallet and adds up each batch's unused free credits, floored at zero per batch, so a batch that somehow overspent cannot drag the total down. Above the tiles sits one line with your organisation's name and the current wallet balance.

What each column of the per-batch table counts

Six columns: Batch, Tier, Seats, Credits used, Resumes, Exports. Seats and Credits used are each written as a pair, consumed over allowed. Batch shows the name you gave it, falling back to the tier name with the word "batch" after it on every batch you left unnamed.

Rows are your organisation's batches, newest created at the top, with Seats counting the members attached to each.

Resumes is the column to be careful with. It counts every resume row belonging to anyone in that batch, with no window and no link back to the batch, so a student who used AceDraft last year brings that history in with them, and a student sitting in two batches is counted in both. Exports counts the subset of those resumes the student marked published, which is a different question from the Paid exports tile and will not usually match it.

One thing the server sends and the page never draws: each batch's per-export rate. I'd rather say so than have you hunt for a column that was never built.

Export CSV, and what lands in the file

Export CSV is the outlined button beside the heading. It only appears once a report has loaded, so while the request is out you see the Building report line and no button.

Pressing it makes no second request. The file is assembled from the report already in memory and downloaded straight away, named for the moment you pressed it. Inside: your organisation name, the wallet balance, a blank line, then one row per batch, then the billing summary as label-and-value pairs.

The file is slightly more generous than the screen. Seats used and seat cap arrive as separate columns rather than one pair, same for credits used and credits total, which saves you splitting them later.

Heads up. CSV is the only format. There is no PDF button, no print layout, and no scheduled copy arriving anywhere.

What this report does not cover

Placements. The page says so itself in grey text under the table: it reflects resumes, exports, credits and wallet spend, and the app does not capture who got hired. Nothing in the response holds an outcome, an offer or an employer.

Nor does it break down by student, by month, or by moderator. An organisation with no batches yet gets the line "No batches yet." in place of the table, and while the request is out you get "Building report…". If the request fails, that message clears and the page goes quiet, leaving the heading alone with no error text to tell you why.

Who this page is for

Use it when someone above you wants a number for the money and the volume, and you want it in a spreadsheet inside a minute. Skip it when the question is about one student or one month, because both of those live elsewhere and this page will only hand you a lifetime total with their name nowhere in it.

Reporting in AceDraft for Teams: What the Organisation Report Shows