Use this when... you want TuitionFlow pages, portals, emails, forms, or public-facing experiences to reflect your tuition business brand.

Before you start... prepare approved brand assets, including logo files, colours, business name, contact details, and any white-label domain or visibility settings your plan supports. Avoid uploading temporary graphics that parents or tutors may see.

Use Branding settings to control how your organisation appears to families, tutors, and staff.

Branding can affect more than the admin app. Depending on your configuration, it may appear on parent-facing pages, enquiry forms, booking flows, notifications, invoices, portals, and your tuition website. Treat branding changes as public-facing changes.

Go to Settings, then Branding. Check the current logo, colours, organisation name, and any preview areas. If your business has multiple branches, confirm whether branding is organisation-wide or branch-specific.

Branding sits inside Settings with other organisation-wide configuration.

Upload the approved logo file in the recommended format. Use a clean version that works on light backgrounds and, if supported, provide alternatives for dark headers, square icons, or email use.

Expected outcome: the logo displays clearly without cropping, stretching, or a low-resolution edge.

Choose brand colours that are readable and accessible. Check text contrast, buttons, links, and headers. Add or review the public business name, support email, website URL, and any footer or invoice details your setup supports.

If your plan includes white-label features, review which TuitionFlow branding is hidden, which custom domains are active, and whether public links use your business domain. Domain changes may require DNS setup outside TuitionFlow.

Check forms, invoices, portals, messages, and website pages after saving. Public-facing branding should look consistent and should not hide important action buttons or payment instructions.

The logo looks cropped: upload a version with better padding or aspect ratio.

Colours look wrong: check whether the saved colour is being used on a different background than expected.

A public page still shows old branding: refresh, check cache, and confirm you changed the correct organisation or branch setting.

Limit branding changes to owners or trusted admins. A small visual change can affect parent trust, invoice recognition, and website consistency. Keep a copy of approved assets outside TuitionFlow so the team can restore them if needed.

Keep a master folder of approved logos and colours outside TuitionFlow. Include the main logo, square icon, light-background version, dark-background version, and any brand colour references. This makes it easier to restore consistent branding if someone uploads the wrong file later.

Check that buttons, links, headers, and invoice text remain readable after colour changes. A colour that looks good in a logo may not work as a button or header background. If a parent cannot read the payment button or form label, choose a clearer combination.

For established organisations, treat branding updates as a small release. Make the change during a quiet period, preview key surfaces, and tell the team what changed. This avoids confusion when parents mention a new invoice or portal appearance.

Check both desktop and mobile views, then check the surfaces parents and tutors actually use: enquiry form, booking link, invoice, payment page, parent portal, tutor portal, emails, and website pages. A logo can look correct in settings but appear too small, stretched, or low contrast in another surface.

Before making a major branding change, keep the previous logo, icon, header image, domain notes, and colour values available. If a public page becomes hard to read or looks wrong, you can restore the previous version quickly while you prepare better assets.

Ask one teammate to preview the changed surfaces before families see them.

After saving branding, review enquiry forms, invoices, parent portal pages, tutor-facing pages, and messages to confirm the brand is consistent across the full customer journey.