Centre dashboard guide — premium plan
This guide covers premium features. For the basics, see the free dashboard guide.
What you get with premium
- Your own CTA button — families stay on your site
- Attendance comparison panel showing 3, 4 and 5 day costs side by side
- Organisation branding (colour, font)
- Bulk import of rooms and fees via spreadsheet
- Scheduled fee updates (by date, per location)
- Full widget insights with breakdowns by location, session and income band
- API endpoints to pull your config into custom pages
- Combined widget showing all your locations in one embed
Branding
In the left panel, under Organisation Branding:
- Widget colour — the accent colour used in buttons and highlights throughout the widget
- Widget font — applied across all your centre widgets
- CTA label — the text on the button families tap at the bottom of the widget (e.g. "Book a tour", "Enquire now")
- CTA URL — where the button points, usually your enrolment or contact page
Click Save Branding. The change applies to all your centres.
If a centre has its own CTA settings configured in its card, those take priority over the organisation-wide settings.
Attendance comparison
On the premium plan, the widget shows an attendance comparison panel after a family runs an estimate. It displays the out-of-pocket cost for 3 days, 4 days and 5 days per week using the same household details, so families can see the difference at a glance.
This replaces the CCSChecker button. There is no link away from your site.
Bulk import via spreadsheet
If you have multiple rooms or locations, importing from a spreadsheet is faster than entering each one manually.
Download the template from the Template button in the Centres panel toolbar.
Fill in one row per session. The key columns are:
| Column | What to enter |
|---|---|
| Location Name | Centre name as parents will see it |
| Location ID | A short unique slug, e.g. ashmore |
| State | QLD, NSW, VIC, etc. |
| Service Type | Long Day Care, OSHC, etc. |
| Room / Program Name | The room name |
| Age Group | 0_2, 3_5_not_school, or 5_12_school |
| Session Label | e.g. Full day |
| Session Hours | Hours charged per day |
| Fee Amount | Daily fee in dollars |
| Live At | Optional. See below. |
Leave the kindy columns blank for rooms without kindergarten funding.
To import: Click Upload in the toolbar, select your file, check the column mapping screen, then confirm. You will see a preview of every change before anything is applied.
Scheduling via the Live At column
The Live At column in the import template lets you schedule fees to go live on a future date, per location.
- Leave it blank to publish that location immediately on import
- Enter a future date (e.g. 06/07/2026) to hold the fees as a draft until that date
On the scheduled date, the widget updates automatically. Families see your current fees until then.
This is useful for loading next year's fees in advance, or aligning a fee change with the new CCS year on 6 July.
Scheduling a single centre update
Inside any centre card, make your changes and click Save Draft. Then click Schedule instead of Publish now, and pick an effective date.
The card shows a blue badge with the date. Click Cancel on the badge to remove the schedule and go back to draft.
Reordering centres
The order of your centre cards controls the order locations appear in the combined widget dropdown.
Use the up and down arrows on the left side of each card to change the order. The new order saves automatically.
Insights
The Insights tab shows how families are using your widgets across all locations.
What you can see:
- Widget views, estimates run, and completion rate
- CTA clicks (how many families tapped your button)
- Attendance comparison views (how many saw the 3/4/5 day panel)
- Estimates by location
- Which rooms and sessions families are selecting
- Days per week distribution (3, 4 or 5 day selections)
- Weekly out-of-pocket cost bands
- Activity hours entered
Use the date range selector to switch between 7 days, 30 days, 90 days and all time.
Click Export to download a CSV of all the data for the selected period.
No personal information is stored. All data is aggregate.
Embed codes
Combined widget (all locations):
In the left panel, scroll to Embed code. This single snippet shows all your published centres in a dropdown. Families pick a location and the calculator loads for that centre's fees.
Use this on your main website, a pricing page, or a page that covers all your sites.
Single centre widget:
Expand a centre card and scroll to Embed code — this centre only. This loads directly into one centre's calculator with no location selector.
Use this on a page dedicated to a single location.
Both codes are permanent and update automatically when you publish changes.
API access
In the left panel, scroll to API access. You will see two endpoints pre-filled with your organisation ID:
- All locations — returns all published centres with their config
- Single location — returns one centre by ID
Both are public, CORS-enabled and require no authentication. Copy either URL and use it from any external system — a custom website, a web agency's build, or any integration that needs to display your fees.
The API returns published data only. Drafts and scheduled configs are not included.
Common questions
How do I change the CTA URL if my enrolment page moves? Update it in Organisation Branding and save. The change applies immediately across all widgets without republishing.
Can different centres have different CTA buttons? Yes. Expand a centre card and set the CTA label and URL there. That overrides the organisation setting for that centre.
Does the combined widget update when I add a new centre? Yes. Once a centre is published it appears in the combined widget automatically. The embed code does not need to be updated.
What if a fee change is ready but I want to wait until the new CCS year? Use the Live At column in your spreadsheet import, or click Schedule on the centre card and set 6 July 2026 as the date.
The attendance comparison is not appearing. It appears after a family completes an estimate. It is not visible before they run the calculation.