Industry
Software for education and training
Education organizations run many systems for one learner: enrolment, timetable, course platform, finance, and messages. We connect them, build the portals and workflows around them, and make the records easy for staff, learners, and families to use.
- 1,200+ clients helped
- Building since 2010
- 15 services, one team
- 50+ technologies
At a glance
What we build
We build the systems schools, colleges, training providers, and education companies use to enrol learners, deliver courses, communicate, track progress, and report.
Problems we solve
Learner records, course platforms, finance, and communication tools are separate, staff re-enter the same details, and families and learners cannot see what they need in one place.
Who we serve
Schools, colleges, universities, training providers, and education technology companies.
How to choose
Start where staff re-type the most, usually enrolment and records, then give learners and families one clear place to see their own information.
What is different
Many users, many roles, one learner
An education system serves more kinds of user than most. Learners, parents or guardians, teachers, administrators, and funders each need a different view of the same learner, and each has different rights over the data.
Rhythm matters too. Demand arrives in surges at enrolment, at the start of term, and at results. A system that is fine on an ordinary Tuesday can fail on the day that counts.
And much of the data concerns children or young people, which raises the standard of care. Access has to be tightly limited, and every system that touches the data must be able to explain why it does.
Funding and inspection add a final layer. Many education bodies must report attendance, results, and spending to outside parties, in set formats and on set dates, so the numbers have to be right the first time and traceable afterwards.
What DECHY can do
How we help education teams
Build
- Portals, enrolment paths, and internal tools.
- Accessible designs that work for all learners.
Connect
- Records, learning, finance, and communication systems.
- Data checks that catch mismatches.
Report
- Dashboards for leaders and teachers.
- Scheduled returns built from the same data.
Protect
- Role-based access and activity logs.
- Careful handling of data about minors.
What it looks like
An assistant for routine questions from learners
Routine inquiries can be answered quickly from approved content, with a person for anything more.
What we build
Typical systems for education teams
Learner and family portals
A private place for timetable, results, documents, and messages. See customer portals.
Enrolment and admissions workflows
Applications routed to the right staff, with reminders and checks. See process automation.
Connected records and platforms
Learner data shared between the records system, learning platform, and finance. See integrations.
Reporting and dashboards
Attendance, progress, and funding figures from agreed definitions. See business dashboards.
Websites and course catalogs
Clear course pages that lead to enrolment. See business web platforms.
Answering routine questions
An assistant for common inquiries, handing over the rest. See AI customer support.
Where to start
What causes the most re-typing?
Start with the place where staff copy the most details between systems.
Where is effort being lost?
Choose this when
Applications arrive by form, email, and phone, and are re-entered into the records system.
- What you get
- A single enrolment path that creates the learner record once and starts the follow-up.
- Keep in mind
- Peak days: test with realistic numbers before the enrolment period.
Choose this when
Messages go out by several tools, and replies are lost.
- What you get
- A shared place for notices, messages, and forms, tied to the learner record.
- Keep in mind
- Respect consent and contact preferences, especially for minors.
Choose this when
Attendance, results, and funding returns are assembled by hand.
- What you get
- Data joined and checked, with reports produced from it.
- Keep in mind
- Agree each definition, such as attendance, before building the report.
Choose this when
Learning platforms, timetables, and records do not share information.
- What you get
- Connections so enrolments and results flow between them.
- Keep in mind
- Pick one system as the source of truth for each learner fact.
Technical depth
Learner data and accessibility notes
Our engineering choices on learner data, peak load, and accessibility, written for the people who will own the system after launch.
- Access is limited by role and by relationship: a family sees only its own learner.
- Retention rules are written down, and old records are removed or archived on schedule.
- Rules for children's data differ by country, so we ask which apply and build to them.
- Enrolment, results, and start-of-term days are load-tested ahead of time.
- Static pages are served from a content delivery network, so heavy traffic does not reach the application.
Public services in education carry high expectations for accessibility. We build to the web accessibility guidelines, test with keyboard and screen reader, and check contrast and text size on every screen.
Selected work
Education projects we have delivered
What clients say
Teams like yours, in their own words
Our old site looked fine on a laptop, but parents struggled to find dates and fees on their phones. The new pages put those details where people actually look.
Priya NairSchool AdministratorBrightPath Learning AcademyEducation Five students got stuck on the same screen during our first usability session. By the next round, they were getting through it without needing us to explain every step.
Aiden RiveraProduct Design LeadLearnSpring EducationEducation I expected a new visual design. What we got first was a clearer way to choose a membership. People could compare the plans without opening several pages, and the team had fewer questions to answer at the front desk.
Leah ScottMembership Services ManagerCommunityFit ClubFitness
Common questions
Questions about education software
Can you work with our existing records system?
Usually, yes. We connect through the interfaces it offers and avoid changing what already works.
How do you protect learners' data?
With role-based access, encryption, minimal data collection, and logs. Development uses test data, not real learner records.
Can you build accessible systems?
Yes. Accessibility is part of how we build and test every screen, not a later add-on.
Will it cope with enrolment day?
We test with realistic peak numbers before the period and keep monitoring during it.
Can you support online and in-person learning together?
Yes. We connect the learning platform, the timetable, and the records, so a learner's enrolment, attendance, and results look the same whichever way they study.
What about tools staff already like?
We keep what works. If staff like a tool, we connect it to the rest instead of replacing it, and we only replace what causes re-typing or errors.
Have a different question?
Tell us what you are weighing up and we will answer it plainly.
Ask a questionAlready a client? Email support@dechytech.com
Tell us where staff re-enter the same details
Describe the systems that hold learner, course, and finance data. We will outline the connections and a first stage.