Development Agency
Contact Sign in Get a project quote

Service

Training centre software development

For centre managers and owners of vocational and professional training providers who need enrolment, timetabling, attendance, instructor assignment, instalments and certification designed around how their courses actually run.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A training centre of any size tends to run on a course spreadsheet, a wall planner, a booking page bolted onto the website and an accounts package that does not know what a cohort is.

  • A learner enrols online onto a Level 3 course without the Level 2 the course requires, and nobody notices until the first day.
  • The timetable for March is drawn up on the planner, then an instructor goes off sick and the administrator spends the morning phoning fourteen learners.
  • Attendance is taken on a paper register that is scanned at the end of the week, so when a funding body or an employer asks for a learner's hours, someone counts ticks.

Where it gets harder

Money is the hardest part.

  • Some learners pay in three instalments, some are funded by their employer who wants one invoice per quarter listing every employee, some are on a funded programme with its own evidence requirements.
  • The administrator reconciles all three from memory.
  • Certificates are typed by hand from the assessment results and posted, and a learner who rings to ask for a replacement two years later starts a search through filing boxes.
  • The centre manager cannot say how many places are left on next month's cohorts without opening four files.

Scope of the service

What the build covers

A custom training-centre build normally covers:

  • A course catalogue where each course has prerequisites Duration, assessment method and the certificate it leads to
  • Scheduled cohorts with places A venue or room and an instructor
  • Enrolment that checks prerequisites and records the funding type Whether self-funded, employer-funded or programme-funded
  • A timetable per cohort with sessions Rooms and instructors and capacity checks across rooms
  • An attendance register per session With reasons for absence and a running hours total per learner
  • Instructor assignment with availability and qualifications per course
  • Instalment plans and employer invoicing With the learners listed per invoice
  • Assessment results and certificate issue With a verifiable certificate number
  • Corporate bookings where an employer books a whole cohort

We follow three real learners through the centre first: a self-funded evening learner, an employee sent by a company, and a learner on a funded programme. Every point where their paths differ becomes a named stage in the scope document: enquire, enrol and check prerequisites, allocate to cohort, timetable, attend, assess, certify, invoice or collect instalment.

Deliberately out of scope

  • The accounts ledger itself, payroll for instructors, and the content of the courses, which lives in your own materials or a separate learning platform. Funding-body returns are treated as an export to be shaped once we have seen the format, never as a ready submission

When the scope grows

Scoping scenario

A centre running forty cohorts a year across two sites with twelve freelance instructors needs instructors to set their own availability, employer invoices grouped by cost centre, attendance thresholds that trigger a warning to the learner and the employer, and certificates with a public verification page. The instructor availability and the threshold rules are what make it a custom project.

Deliverables

What you receive

  • Discovery notes from following three learners with different funding types through the centre
  • A scope document naming each stage from enquiry to certificate and what is out of scope
  • Design of the cohort view, the timetable, the attendance register and the enrolment flow on desktop and tablet
  • The build, deployed to your hosting or ours, with role permissions and an audit of enrolment and result changes
  • Migration of courses, learners, open cohorts, instalment balances and issued certificates, where relevant
  • Training for administrators, instructors and the centre manager, with a written guide per role
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access to the course spreadsheet, the planner, the booking page and the accounts package, with a named administrator as the day-to-day contact.

    Project stage: Onboarding

  2. Planning

    Learner walk-throughs with the administrator, an instructor and the centre manager; the scope document and milestone plan are agreed.

    Project stage: Planning

  3. Design

    Clickable designs of the cohort board, the timetable, the register and the employer invoice, reviewed with the people who will use them daily.

    Project stage: Design

  4. Development

    Built in stages: catalogue and cohorts first, then enrolment and prerequisites, then timetable and attendance, then instalments, invoicing and certificates.

    Project stage: Development

  5. Client review

    The centre runs a test cohort from enrolment to certificate on sample learners, including an instructor absence and an employer invoice run.

    Project stage: Client review

  6. Revisions

    Changes from the review, particularly to attendance rules, invoice layout and certificate wording, are made and re-checked against the scope document.

    Project stage: Revisions

  7. Ready for launch

    Data migrated and balances reconciled, timetables for the next intake loaded, cut-over planned between cohorts.

    Project stage: Ready for launch

  8. Delivered

    The centre runs on the new system; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Accounting packages for invoices, instalments and payment allocation
  • Card and direct-debit payment providers for self-funded instalments
  • Email and SMS providers for session reminders and attendance warnings
  • Calendar feeds so instructors see their sessions on their own devices
  • Learning platforms where course content and online assessments live
  • Funding-body and awarding-body reporting, assessed per body as an export
  • E-signature tools for enrolment agreements and employer contracts

How we would approach it

Worked example

Concept demo

A two-site centre with freelance instructors and employer cost centres

In this scoping scenario, a centre delivering forty cohorts a year across two sites wanted its twelve freelance instructors to publish their own availability so cohorts could only be scheduled when an instructor qualified for that course was free and the room was empty. Employers sending staff needed quarterly invoices grouped by cost centre, and learners whose attendance fell below a threshold needed an automatic warning copied to their employer.

The scope we would propose: an instructor availability calendar checked at scheduling time against qualifications and room capacity, employer records with cost centres and a quarterly invoice run listing learners and sessions, attendance thresholds configured per course with notifications to learner and employer, and certificates with a verification page. The reason this needs a custom build is the scheduling check: most training booking tools let an administrator put anyone in any slot and rely on them to know, which is exactly what this centre wanted the system to prevent.

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of courses, cohorts per year and sites or rooms
  • Number of instructors and whether they manage their own availability
  • Funding types in use and how employer invoicing must be grouped
  • Attendance rules, thresholds and who is notified
  • Certificate design, numbering and public verification
  • Volume and condition of learner, cohort, balance and certificate data to migrate
  • Funding-body or awarding-body exports to be shaped
  • Hosting choice: your own hosting or ours

Start from a package

Training centre management package

Course catalogue, cohorts, enrolment, timetable, attendance register, instructor assignment, instalments, employer invoicing and certificates for vocational and professional training providers.

Custom build
View the package

FAQ

Frequently asked questions

When is a custom build the right choice rather than the package?

When your scheduling rules, funding mix or invoicing structure break the assumptions of the training centre management package. During discovery we lay your three learner walk-throughs against the package and say plainly whether configuration covers them or whether, for example, your instructor availability checks need custom work.

Can the system produce our funding-body returns?

We treat each return as an export to be shaped once we have seen the exact format and the data it needs. The scope document states which exports are in scope and which have not been assessed; nothing is promised as a ready submission.

Can learners under eighteen be enrolled?

Yes. Enrolment records a guardian contact where the learner is a minor, and access to learner records is limited by role and logged. The centre remains responsible for its own safeguarding arrangements; the build provides the controls and the records.

Can you migrate our open cohorts and instalment balances?

Usually yes. We import courses, learners, cohorts, attendance history and balances from your spreadsheets and accounts exports, reconcile balances before cut-over and plan the switch between intakes. The scope document states what can be carried over once we have seen the data.

Who owns the system afterwards?

The centre does. Source code and data are handed over at delivery; hosting and maintenance are optional, separately agreed and movable to another provider.

Get a project quote for training centre software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences