Branditify

Branditify for schools

A school website should not end at “contact us”.

A family reads the site, still cannot work out how admission actually works, and phones to ask. Branditify builds the website, the admission information and the enquiry so a family can understand the school — and so the admissions team receives something they can act on rather than a name and a number.

Branditify is a digital studio. We are not a school and not a board — we make no affiliation, recognition or compliance claim, we assess no child, and no admission decision is automated here.

Northstar SchoolSchoolENQ-2048
In progress

It belongs to a person. This is where most school enquiries are kept or lost.

Parent
Neha Kapoor
Child
Kabir Kapoor
Grade
Grade 5
Source
Website · the admissions page
Owner
Admissions · Rhea
Next action
Answer the question and offer a visit.
ApplicationNot startedWhat they askedAsked about school transport from their area.

An illustrative enquiry. Northstar School, its family and its reference are invented.

What Branditify can build

The systems a school can operate, and the work that gets them there.

Two different things, and knowing which is which decides what a project actually costs. A system is something the school uses every day. A service is a piece of work with a start and an end. Everything below links to its own page, where it is described as the general thing it is rather than the school version of it.

Systems a school can operate

Four, and only one of them is about the school year.

Branditify builds more systems than these. These are the ones that change something for an institution whose intake is annual, whose audience is families, and whose reputation is local.

Lead system · once a child is enrolled

School Management System

Students, guardians, classes, attendance, fees and results live in separate sheets, and every school-year change means retyping the same child.

One student record carrying the guardians attached to it, the class and section it sits in, what is recorded against it and what the parent is allowed to see — so a child stays one record instead of being re-entered each time the school changes task.

The school year stops being a re-entry exercise.

The office, the class teacher, and whoever answers the phone when a parent calls.

It is the school’s operating record and it begins at enrolment. It does not manage the prospective family — that is the next card — and it does not deliver lessons.

School Management System
System · before anybody is admitted

CRM

Admission enquiries arrive on the site, on the phone and on WhatsApp, and nobody can say which ones still need answering.

The prospective family — which grade they asked about, where they came from, what they actually wanted to know, who owns it and what happens next.

An enquiry stops depending on who happened to see it.

It holds the family before admission. It is not a student record, and chapter nine is about exactly where that line falls.

CRM
System · what a family can see

Parent Portal

Every circular, document and small question becomes a phone call to the office.

A controlled parent-facing view of what the school has chosen to publish — announcements, documents, their own requests, and the information about their own child.

The routine questions stop arriving as phone calls.

The school decides what a parent can see. Staff notes, other families’ children and internal records are not parent-facing, and no existing system’s portal is assumed to connect.

Parent Portal
System · only if learning is delivered online

LMS

Lessons, materials and assessment are being run through a system built for administration, or through nothing at all.

Learning delivery as its own thing — material, coursework and progress — for schools that genuinely deliver or supplement teaching online.

Teaching stops being squeezed into an admin tool.

Most schools do not need one. An LMS delivers learning; it does not run the school, and treating the two as one system is the most common mistake in this category.

LMS

Most schools that start here start with the website and the enquiry, because that is where families are actually being lost. The operating record usually already exists in some form, and the honest first question is whether it should be replaced or connected to.

What Branditify builds

The work, described for a school.

Each is a full service in its own right, and its own page explains it in general terms. What is below is what it means when the audience is families choosing where their child will spend the next several years.

Service · design and build

School websites

The site has a gallery, a principal’s message and a notice board, and a parent still cannot tell how admission works.

Structuring what the school offers, for which grades, what the day actually looks like, how admission works, what the school is required to publish, and where a family goes next.

A family can understand the school without phoning first.

It presents what the school itself publishes. It states no fee, date or eligibility rule that the school has not supplied.

School websites
Service · structure and discovery

Search and answer-engine work

Parents search for a grade, a curriculum and a neighbourhood, and the site answers with a homepage.

Structuring what the school offers, where it is and how admission works so the questions families actually type have a page that answers them directly.

The school is findable by what it is, not only by its name.

No ranking, position or enquiry volume is promised, and no admissions outcome is claimed.

Search & answer engines
Service · build and connect

Connecting what already runs

A system already holds the students, and the website knows nothing about it.

Establishing which system is authoritative for what, what it will actually expose, and building only the part that genuinely does not exist.

The website and the office stop keeping two versions of the truth.

No integration is promised before it is verified. Many school systems publish no interface at all, and that is established in scoping rather than assumed.

Custom systems
Service · only when justified

A parent app, only where it earns itself

Somebody has decided the school needs an app, and nobody has said what a parent would open it for.

A mobile build where there is genuine daily use — communication, attendance, requests or coursework a parent or student would open repeatedly through the term.

The decision gets made on evidence rather than on fashion.

A prospective family will never install one, so an app does nothing for admissions. It is a tool for people already inside the school.

App development

Why families fall through

None of these is a missing feature. Each one is a missing answer.

Schools rarely describe a technology problem. They describe parents phoning to ask what the site should already have said, and enquiries that nobody remembered to answer.

01

How does admission actually work here?

Every family deciding in the same three weeks as everybody else.
What a family findsA PDF from two years ago, a notice, and a form that asks for a phone number.
What would answer themThe process written out as a process — what happens, in what order, and what the family needs to do.School websites

They ask a school that answered the question on its website instead.

02

Who is answering this enquiry?

The parent, who follows up because nobody else did.
What a family findsIt arrived on the website, went to a shared inbox, and is now in somebody’s phone.
What would answer themAn enquiry that carries its grade, its source and an owner from the moment it exists.CRM

A family who had chosen you goes to whoever replied.

03

Why is the office answering this again?

The front desk, and the parent who waited on hold.
What a family findsThe same questions arrive by phone all day, and the answers exist but are not findable.
What would answer themWhat parents already need, published where they can find it — and a portal once the volume justifies one.Parent Portal

Time that should be going to families who are actually deciding.

One family, one decision

A parent is not browsing. They are choosing where their child spends the next several years.

It is one of the higher-stakes local decisions a family makes, it is usually made by two people who disagree, and it is largely made on a phone in the evening. These are the questions that decide it, in the order they get asked.

Is this school for us?What the school is actually like, and who it is for — in the school’s own words rather than a mission statement.
Do you take my child’s grade?Which grades are offered, and which are actually taking admissions this cycle.
What is the curriculum?What is taught and how, stated factually, so a parent can compare it with the school down the road.
Where is it, and how would they get there?Location, and whether transport exists for their area — one of the most-asked questions and one of the least-published.
How does admission work?The process as a sequence, so a family knows what is coming rather than discovering it one call at a time.
What do we do next?One clear step. Not a phone number and a hope.

What should a modern school website include?

Enough for a family to finish the decision: what the school is and who it is for, which grades are offered and open, what is taught and how, where it is and how a child would get there, how admission works as a sequence rather than a notice, and one clear next step. Whatever the school is required to publish belongs there too, kept current. Everything else — the gallery, the messages, the awards — is optional and usually over-built.

None of this replaces visiting the school. It is what has to be true before a family decides the visit is worth their Saturday.

The page that matters most

The admissions page is the most-read page on a school website and usually the least designed.

It is where a family decides whether to engage or move on, and it is typically a notice, a PDF and a form. Written as a process, it does most of the school’s admissions work before anybody picks up a phone.

Which grades, and which are openThe single most-asked question, answered before a family has to ask it.
The process, in orderWhat happens first, what happens next, and what the family has to do at each point.
What will be neededWhat the school will ask for, so a family can prepare instead of being surprised.
What happens after they askWho responds and roughly when — the thing that stops a parent chasing.
One clear next stepAsk a question, book a visit, or begin an application. One, made obvious.
What the school must publishKept in one maintainable place rather than scattered across old pages and files.
On mandatory disclosure, preciselySchools affiliated to a board are typically required to publish a set of public disclosures, and agencies usually treat this as a checklist to bolt on. It is really a content problem: the information has to stay accurate, be findable, and survive the next redesign. Branditify structures it so the school can publish and maintain what its own board requires. What we do not do is determine what any school is obliged to publish, verify that anything satisfies it, or claim affiliation with, recognition by or compliance with any board.
What an admissions page will not do
  • It states no fee, date, age cut-off or eligibility rule that the school has not supplied and does not maintain itself.
  • It makes no admission decision and performs no assessment, screening or evaluation of any child. The school decides; the page carries what was said.
  • It gives no educational, legal or admissions advice, and makes no claim about a family’s chances.

What should a school admissions page include?

Which grades are offered and which are actually open, the process written as a sequence rather than a notice, what the school will ask for, what happens after a family enquires and roughly when, and one obvious next step. Whatever the school is required to publish belongs in one maintainable place rather than scattered across old pages. What it must not do is state a fee, date or eligibility rule the school does not itself maintain.

The handover

An enquiry form’s job is not to collect a name. It is to hand over something somebody can act on.

Most school enquiry forms ask for a name, a phone number and a message. What comes out the other end is a note that tells the admissions team nothing, so the first call is spent asking what the family already said.

Who is askingEnough to reply properly, and nothing the school does not need.
For which child and gradeThe one field that changes who should answer and what they should say.
What they actually want to knowIn their own words, not a category from a dropdown.
Where they came fromRecorded once, at the only moment it is knowable.
Who owns it nowA named person from the moment it exists, not after the morning meeting.
What the form does not do
  • It collects only what the reply and the process actually require. A prospective enquiry is not the place for a child’s records.
  • It performs no screening, scoring, ranking or eligibility check, and no enquiry is accepted or rejected automatically.
  • What is collected, who can see it and how long it is kept are scoped around the school’s own requirements and obligations. Branditify makes no data-protection compliance or certification claim, and gives no legal advice.

How should school admission enquiries be organised?

So that each one arrives carrying who is asking, for which child and grade, what they actually wanted to know, where they came from, and who owns it — before anybody picks up the phone. That single change removes the discovery call, which is where most school enquiries lose their momentum. The owner matters most: an enquiry belonging to everybody belongs to nobody.

The expensive failure

The family thinks they are in a conversation. The school does not know one started.

This is the failure that costs a school real admissions, and it is nearly invisible — because an enquiry nobody owned leaves no record of having existed. Both columns below describe the same enquiry on the same day.

What the family believes
  • We asked the school a question about Grade 5.
  • We told them which child and where we live.
  • Somebody from the school will get back to us.
  • We will give it a few days before we look elsewhere.
What the school actually has
  • A form submission in a shared inbox.
  • No grade recorded, because the form did not ask.
  • No owner, because nobody was assigned one.
  • No next action, so nothing is scheduled to happen.

A school does not need more enquiry channels if nobody owns the next step. The family is not lost because the school was unwelcoming — they are lost because nothing was scheduled to happen.

Off the screen and back again

The decision is made on a campus visit. The record should survive it.

Almost every school admission is decided in person, which is exactly why the digital part gets neglected. But the visit is a stage in a journey, not the end of one, and what a family said before and after it belongs in the same place.

The visit is arrangedFrom the enquiry that already exists, so the family is not asked everything again.
What they asked is notedThe questions a family asks on a tour are the most useful thing the school learns all week.
The follow-up is ownedA named person and a date, rather than a general intention to call.
An application is startedCarrying what is already known, so the form is short instead of exhausting.
What is outstanding is visibleTo both sides — which is what stops the second and third chasing call.
The school decidesThe decision is the school’s, made by people. The file only carries what was said.

Nothing here decides an admission, ranks a family or assesses a child. Those are the school’s judgements, made by its own staff under its own process. Nothing claims that digital systems improve educational outcomes, results, attendance or learning either — what they can do is stop a family being lost between the website and the office, which is a smaller and truer claim.

The decision that gets made wrong

A school CRM and a school management system are not rivals. One hands over to the other.

This is the most confused comparison in this category, and the usual framing — which one should we buy — is the wrong question. They hold the same family at different points, and the handover between them is where the value is.

A CRM holds the family before admission

  • Which grade they asked about, and where the enquiry came from.
  • What the family actually wanted to know.
  • Who owns it, and what stage the conversation is at.
  • Everything that matters while this is still a maybe.

What it does not hold is a student, a class, attendance, fees or results. Asked to, it becomes a worse version of the next column.

CRM

A school management system holds them afterwards

  • The student, and the guardians attached to them.
  • The class and section, and what is recorded against the year.
  • What the school publishes to the parent.
  • The record that carries across school years rather than restarting.

What it does not do is run an admissions pipeline. It begins where the enquiry ends, and it does not deliver lessons either.

School Management System
The handover is the whole thingA school may run both, and most growing ones eventually do. What decides whether that works is one question settled early: when a family is admitted, does the file travel — or does somebody retype it? Every symptom on this page traces back to that answer.

Does a school need a CRM for admissions, and how is it different from a school management system?

They are consecutive rather than competing. A CRM holds the family while they are still deciding: which grade, where the enquiry came from, what they asked, who owns it and what happens next. A school management system begins at enrolment and holds the student, the guardians, the class, and what is recorded across the year. A small school with one person answering every enquiry may genuinely not need a CRM yet; what it does need is for that person not to be the only record.

The other decision

Running a school and delivering learning are two different systems.

Vendors increasingly sell both in one package, which is convenient and also the reason schools end up paying for a module nobody opens. The distinction is simple once stated.

A school management system runs the school

  • Students, guardians, classes and sections.
  • Attendance, fees and the school-year cycle.
  • Results as records, and what the parent is shown.
  • The administrative spine, used by the office every day.

What it does not do is teach. Coursework and content pushed into an admin system is the usual reason teachers stop using it.

School Management System

An LMS delivers the learning

  • Material, lessons and coursework.
  • Submission, review and feedback.
  • Progress through content rather than through a year.
  • Used by teachers and students rather than by the office.

What it does not do is run the school. Most schools that teach in person do not need one, and buying one because it was bundled is the common mistake.

LMS

What is the difference between a school ERP and an LMS?

A school ERP or management system runs the institution — students, guardians, classes, attendance, fees, results and the school-year cycle — and is used mostly by the office. An LMS delivers learning: material, coursework, submission and progress, used by teachers and students. A school may need one, both or neither built custom. Most schools teaching in person need the first and can manage without the second, and buying an LMS because it came bundled is how modules end up unused.

What a family can see

A parent portal is a permission question before it is a product question.

The build is not the hard part. Deciding what a parent may see, and being certain the rest cannot appear in their view, is the hard part — and with children’s information it is the part that has to be right.

WhatWhyParentSchool
School announcementsWhat the school has chosen to publish, in one place rather than five channels.
Their own child’s informationWhat the school records and has decided to show, for their child only.
Documents the school issuesThe copies a family is entitled to, without asking the office to find them.
Their own requestsWhat they have asked for, and where it has got to.
Staff and internal notesWorking notes are written for colleagues, not for parents.
Another family’s childThe single thing a school portal must never get wrong.
Records outside the parent’s relationshipA parent sees their own child, not the class, the year group or the school.
What a portal is not
  • It shows what the school’s own systems hold and what the school has chosen to publish. It is not a window into any other system, and no existing platform’s connection is assumed.
  • Access, collection and retention are scoped around the school’s own requirements, users and obligations, established during scoping. Branditify claims no COPPA, FERPA, DPDP, GDPR or other compliance or certification, and gives no legal advice.
  • Nothing here decides who is a parent or guardian. That is the school’s own record and its own process, and the portal follows it rather than defining it.

Does a school need a parent portal, and what should it show?

It earns itself when the same routine requests — a circular, a document, a small question — occupy somebody in the office most days. It should show a family the school’s announcements, their own child’s information as the school has chosen to publish it, the documents they are entitled to and their own requests. It must never show staff notes or another family’s child, which is why the permission model is settled before anything is built.

A real decision

A school app cannot help admissions, because a prospective parent will never install it.

This is worth stating plainly because apps get sold to schools as growth tools. An app is for people already inside the school. The families you are trying to win are, by definition, not.

A mobile website is enough for

  • Every prospective family, all of whom arrive from a search or a link.
  • Admissions, programmes, the process and the enquiry.
  • Announcements and information a parent reads occasionally.
  • Anything that has to be findable by somebody who has never heard of you.

What it cannot do is hold a logged-in daily relationship comfortably. That is the honest limit.

An app starts to earn itself for

  • Parents already enrolled, opening something weekly through the term.
  • Daily communication, attendance or requests that repeat.
  • Coursework and materials, where learning genuinely runs on a device.
  • Staff and teacher workflows away from a desk.

Its limit is installation. Every parent has to be persuaded to install and keep it, and a school with one term of enthusiasm and no daily use ends up maintaining an empty app.

App development

Does a school need a mobile app?

Not for admissions, and that is the part usually sold wrongly — a prospective family will never install an app to enquire, so the app can do nothing for the families you are trying to win. It earns itself for people already inside the school: daily communication, attendance, requests or coursework that a parent or student would open weekly through the term. Without that repeated use, a school ends up maintaining an app nobody opens.

One possible setup

How these connect around a single family.

One architecture, not a package. Most schools build the first three and stop there for a year or two, which is usually the right call.

01Search or referralWhere a family actually starts.
02The school websiteWhat the school is, and for which grades.
03Admission informationThe process, written as a process.
04An enquiryCarrying parent, child, grade and source.
05CRMWhere it gets an owner and a stage.
06Admissions ownerA named person, from the first moment.
07Visit and applicationOff the screen and back again, without retyping.
08School Management SystemThe operating record, once a child is enrolled.
09Parent PortalOnly where routine requests justify it.
10LMSOnly where learning genuinely runs online.
Where the family is foundWhere the school operatesOnly where it earns itself

No school needs every one of these, and building them in the wrong order is the most common expensive mistake in this category. The website and the enquiry come first because that is where families are lost.

A real decision

Off-the-shelf school software is often the right answer.

There is a mature market of school ERP products, and for a great many schools one of them is the correct decision. Saying otherwise would be selling. The question is which situation a school is actually in.

Off-the-shelf usually wins

  • When the school year works the way the product assumes.
  • When the modules cover enough that the gaps are inconveniences.
  • When the school does not have people to own a system long-term.
  • When standard process is an acceptable price for starting this term.

Its limit is that the school adapts to the product. For most single-campus schools that is a fair trade, and it should be made deliberately rather than by default.

Custom starts to make sense

  • When a group runs several campuses that must share and separate data.
  • When systems that have to exchange information cannot, and retyping is the join.
  • When the parent or teacher experience is genuinely a differentiator.
  • When manual work is limiting what the school can actually take on.

Its limit is that it is a build, with the cost, timeline and ownership that implies. A custom version of something that already exists is the most expensive way to arrive where you started.

Custom systems

Custom or off-the-shelf school management software?

Off-the-shelf is the right answer more often than agencies admit — the market is mature, and adapting to a good product is usually a fair trade for starting this term. Custom earns itself where a group runs several campuses that must share and separate data, where systems that must exchange information cannot, where the parent or teacher experience is a real differentiator, or where manual work is limiting what the school can take on.

Moving what exists

There is already a school running, and it cannot pause.

Nobody starts empty, and the risk in a school project is everything that already works. A school year does not stop for a migration, which is why the order matters more here than almost anywhere.

InventoryStudents, guardians, classes, current enquiries, whatever the office maintains, the existing site and the URLs that already bring families in.
SampleOne grade taken end to end before anything moves in bulk, because that is where the surprises are.
Field mapWhat each column actually means, agreed with the people who maintain it rather than guessed from its heading.
CleanDuplicate siblings, students who left, guardians recorded twice, classes from a previous year.
Load and connectIn stages, timed around the school calendar rather than around the project plan.
VerifyCounts, guardians, classes and the pages that already bring families in — checked against the source, not the import log.

What can move depends entirely on what the current systems export. Students, guardians and classes usually move; attendance and result history often do not, and some products make export deliberately hard. That is worth discovering before the decision rather than after it, and no perfect migration is promised.

Can existing student and admission data be migrated?

Usually students, guardians, classes and current enquiries. Attendance and result history are the ones that frequently cannot, because many school products either do not export them or export them without their links. Establish what the current system will actually give up before committing to a move, and time the work around the school calendar — a migration during admissions season is a different project from one in the holidays.

Selected work

Website, enquiry and product work.

Each of these is shown for a specific thing it documents about the journey on this page, and each says exactly what it was and in which category.

B2B logistics · 2024

Swift Logix

A website carrying a service booking interface and a CTA-led enquiry journey — the closest documented case for a site whose job is to hand over a request somebody can act on.

Website DevelopmentUX/UI DesignLogistics Website DesignResponsive Web Design

Shown for the enquiry handover. Another category, and not a school.

View Swift Logix
Insurance · 2024

FWD Insurance

A digital experience engagement for an institution in a regulated sector — UX and interface design, website experience design, interaction design and brand storytelling.

UX/UI DesignWebsite Experience DesignInteraction DesignBrand Storytelling

Shown for institutional website experience. Another category, and not a school.

View FWD Insurance
Ayurveda & wellness · 2024

VedaMedi

A brand identity and a premium website built together, so the site expressed the positioning rather than decorating it.

BrandingPremium WebsitesLogo DesignBrand Identity

Shown for the website build itself. Another category, and not a school.

View VedaMedi
Health & fitness · 2024

LeanTrack

A mobile application designed and built around genuine repeated daily use — the evidence behind the website-versus-app chapter above.

EditorialMobile App DevelopmentUX/UI DesignHealth App Design

Shown for the app decision. Another category, and not a school.

View LeanTrack

Scope shown per project is taken from that project’s own record. No admissions, enrolment, enquiry, traffic, ranking or parent-engagement figure is attached to any of them.

What determines the size of this

Two schools of the same size can be very different projects.

These move it more than anything else, in roughly this order.

One campus or severalA single school is one set of grades, one process and one site. A group is a decision about what campuses share and what they must keep apart, and that decision shapes everything else.
What already runs the officeWhether an existing system stays, gets connected to, or gets replaced is the single biggest fork — and it is answered by what that system will export, not by its feature list.
How much has to be publishedProgramme, faculty, facilities and whatever the school is required to disclose all have to be written, structured and kept current. That is the longest task in most school website builds.
Whether admissions is in scopeAn enquiry form is one project. An owned admissions pipeline with stages and follow-up is another.
Whether a portal is in scopeA parent portal is a permission model before it is a screen, and with children’s information those decisions take real time.
The school calendarAdmissions season and the start of a school year are immovable, and they decide what can be delivered when far more than the estimate does.

What digital system should a school build first?

Almost always the website and the admission journey, because that is where families are lost and it is the only part that works on people who have never contacted the school. An admissions CRM comes next, once more than one person is answering enquiries. The operating system, the portal and any LMS follow, and usually only after establishing whether what already runs the office should be replaced or connected to.

Questions

School questions, answered directly.

What should a modern school website include?

Enough for a family to finish the decision: what the school is and who it is for, which grades are offered and open, what is taught and how, where it is and how a child would get there, how admission works as a sequence, and one clear next step. Whatever the school is required to publish belongs there too, kept current. The gallery, the messages and the awards are optional and usually over-built.

What should a school admissions page include?

Which grades are offered and which are actually open, the process written as a sequence rather than a notice, what the school will ask for, what happens after a family enquires and roughly when, and one obvious next step. What it must not do is state a fee, date or eligibility rule the school does not itself maintain.

How should school admission enquiries be organised?

So each one arrives carrying who is asking, for which child and grade, what they wanted to know, where they came from, and who owns it — before anybody picks up the phone. That removes the discovery call, which is where most school enquiries lose momentum. The owner matters most: an enquiry belonging to everybody belongs to nobody.

Does a school need a CRM for admissions, and how is it different from a school management system?

They are consecutive rather than competing. A CRM holds the family while they are still deciding: which grade, where the enquiry came from, what they asked, who owns it and what happens next. A school management system begins at enrolment and holds the student, guardians, class and what is recorded across the year. A small school with one person answering every enquiry may not need a CRM yet — but it does need that person not to be the only record.

What is the difference between a school ERP and an LMS?

A school ERP or management system runs the institution — students, guardians, classes, attendance, fees, results, the school-year cycle — used mostly by the office. An LMS delivers learning: material, coursework, submission and progress, used by teachers and students. Most schools teaching in person need the first and can manage without the second, and buying an LMS because it was bundled is how modules end up unused.

Does a school need a parent portal, and what should it show?

It earns itself when routine requests — a circular, a document, a small question — occupy somebody in the office most days. It should show announcements, their own child’s information as the school has chosen to publish it, documents they are entitled to, and their own requests. It must never show staff notes or another family’s child, which is why the permission model is settled before anything is built.

Does a school need a mobile app?

Not for admissions — a prospective family will never install an app to enquire, so it can do nothing for the families you are trying to win. It earns itself for people already inside the school: daily communication, attendance, requests or coursework a parent or student would open weekly through the term. Without that repeated use, a school maintains an app nobody opens.

Can a school website connect to an existing school ERP?

Sometimes, and it depends entirely on what that system exposes. Some publish an interface worth building against; many school products publish none at all. For those the honest answer is one authoritative source and a defined direction of travel rather than a pretence of live sync. That is settled before the build, because a project designed around a connection that does not exist is the most expensive mistake in this category.

Can existing student and admission data be migrated?

Usually students, guardians, classes and current enquiries. Attendance and result history frequently cannot, because many school products either do not export them or export them without their links. Establish what the current system will give up before committing, and time the work around the school calendar.

Custom or off-the-shelf school management software?

Off-the-shelf is the right answer more often than agencies admit — the market is mature, and adapting to a good product is usually a fair trade for starting this term. Custom earns itself where a group runs several campuses that must share and separate data, where systems that must exchange information cannot, where the parent or teacher experience is a differentiator, or where manual work limits what the school can take on.

What digital system should a school build first?

Almost always the website and the admission journey, because that is where families are lost and it is the only part that works on people who have never contacted the school. An admissions CRM comes next, once more than one person is answering enquiries. The operating system, the portal and any LMS follow.

What should stay in the school’s existing system?

Whatever it already does reliably and exports poorly. If the office runs attendance, fees and results in a system everybody knows, replacing it is rarely the first project — connecting to it, or leaving it alone and building the part that genuinely does not exist, is usually cheaper and less disruptive. The test is what the system will give up, not what its brochure lists.

Does Branditify handle CBSE or board compliance for schools?

No. We make no affiliation, recognition, approval or compliance claim in relation to CBSE, ICSE, IB, Cambridge or any other board, and we do not determine what a school is obliged to publish. What we do is structure the school’s own required disclosures so they are findable, maintainable and survive the next redesign — which is a content and architecture job, not a compliance one. What must be published is a matter between the school and its board.

What determines the scope of a school digital project?

Whether it is one campus or several, what already runs the office and what that system will export, how much content has to be written and kept current, whether admissions and a parent portal are in scope, and the school calendar — which is immovable and decides what can be delivered when far more than the estimate does.

Next

Open your admissions page on a phone and time yourself.

See how long it takes to find out which grades are open and what a parent is meant to do next. If it takes more than a minute, that is the whole conversation — and it costs nothing to have.