Make-or-buy analysis for academics, curriculum, and lesson planning

1. Define the decision

State the academic problem, decision, users, subjects, campuses, records, outcome, timeline, constraints, current process, and non-negotiable controls. Include lesson planning, curriculum, resources, classes, reports, integrations, and family or student views where relevant.

Do not compare products before defining the work and evidence required.

2. Describe the options fairly

Compare buy, configure, build, retain, or redesign by academic fit, information quality, permissions, accessibility, safeguarding, integration, support, continuity, supplier dependence, upgrade path, and exit.

Include the option of removing unnecessary workflow or reducing local variation rather than automating it.

3. Calculate total cost and capacity

Include discovery, curriculum modelling, content cleanup, resource migration, development or setup, testing, integrations, training, support, security, privacy, accessibility, storage, monitoring, upgrades, internal staff time, incident response, and exit.

The U.S. Department of Education data governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring. GOV.UK guidance emphasises accountable and secure handling.

4. Test real academic scenarios

Run unit planning, current-resource selection, absence, substitution, changed class, mixed group, revised outcome, duplicate resource, missing lesson, transferred student, report, integration failure, and outage scenarios.

Record expected result, observed result, manual work, limitation, owner, evidence, support route, and residual risk.

5. Assess maintainability

Ask who maintains curriculum definitions, resource versions, permissions, reports, integrations, validation, accessibility, support, documentation, backups, retention, and corrections after the initial project ends.

A technically possible option is not sustainable if the school lacks the capacity or expertise to keep it safe and current.

6. Make and review the decision

Use hard gates for safety, privacy, accessibility, continuity, and academic minimums, then score weighted preferences and total cost. Record assumptions, evidence gaps, owner, decision date, and exit condition.

Review lesson readiness, resource currency, corrections, teacher effort, access exceptions, support demand, reporting confidence, and the original outcome at 30, 60, and 90 days.

Turn the guidance into an academic decision

Apply this guidance to one bounded part of make-or-buy analysis for school academic management software. Define the academic decision, record, purpose, authoritative source, accountable owner, permitted users, correction route, and evidence needed to approve the next step.

Test an ordinary lesson or curriculum record and meaningful exceptions such as a changed class, missing lesson, substitute teacher, timetable change, transferred student, revised outcome, duplicate resource, or reporting-period change. Record who resolved it and how the correction reached dependent views.

Keep product capability, school responsibility, professional judgment, legal advice, and measured outcome separate. If evidence is incomplete, narrow the claim and pilot the smallest safe change.

Review the result at 30, 60, and 90 days. Check completeness, timeliness, consistency, corrections, access exceptions, teacher effort, support demand, reporting confidence, and the original outcome. Decide whether to expand, repair, consolidate, or hold.

Before approval, ask a reviewer who was not involved in the design to challenge the strongest assumption. Replace broad language with the exact evidence, population, date, and limitation the school can verify.

Document what was tested and what was not. A successful demonstration with an ideal lesson plan does not establish readiness for substitutions, absences, mixed classes, resource changes, late work, or a new academic period.

Keep the evidence beside the decision record so a later reviewer can distinguish observed behavior from an assumption, estimate, or supplier statement. Name the next test where the current evidence is incomplete.

Revisit the boundary when the school adds a subject, campus, role, integration, reporting period, or policy. A small change can alter permissions, definitions, timing, or retention even when the workflow appears familiar.

Set the next review date and owner. A dependable academic system is maintained through clear definitions, controlled change, professional judgment, and visible accountability rather than a one-time setup.

Make the handoff readable to a teacher, academic leader, and reviewer. State what passed, what remains manual, which records are authoritative, who owns unresolved conflicts, and how a correction is communicated without creating an uncontrolled copy.

Keep approved definitions beside validation rules, training notes, support routes, and change history. New year groups, subjects, campuses, roles, integrations, or calendars can change the risk even when field names stay the same.