EBTL: from three disconnected channels to a single platform.

A public body running vocational training and communication with two teams, dozens of courses a year and a set of tools that didn't talk to each other. The most comprehensive project we've delivered so far.

The problem

Two departments, three enrollment channels, no overall view

The Training department handled enrollments from companies, private workers and special cases across three disconnected channels: Excel files, online forms and the internal management system. Every catalog change had to be copied by hand into all three. At peak times, distributing course materials alone generated up to 180 manual emails a day. The Communication department relied on a single person to connect the website, newsletter, social media and external consultants: without her, everything stopped.

The approach

Before proposing any automation, we mapped the entire current state: four working sessions with both department heads and the vendors of the existing systems, turned into a detailed process document. Only once every step was explicit, exceptions included, did we design the future setup.

The outcome

A four-phase roadmap over about nine months, with Younity as the central platform, N8N orchestrating the automations and Microsoft Planner as the shared task system, open to external consultants too.

Project sheet

Client
EBTL, public body in the tourism sector
Duration
About 9 months, in 4 phases
Departments
Training and Communication
Technology
Younity, N8N, Microsoft Planner and Teams
Status
Roadmap approved, first changes already in use
Methodology

Why we map before we automate

A common mistake is jumping straight to the technology. An automated system built on an unclear process, or on messy data, only creates faster problems.

How we mapped the current state

  • Working sessions with each department head
  • Interviews with the vendors of existing systems
  • A shared process document summarizing it all
  • Exceptions and edge cases made explicit, not just the ideal flow

What a serious mapping reveals

  • The real bottlenecks, often different from the perceived ones
  • Critical dependencies on single people
  • The data that needs fixing before it can be automated
  • Real priorities: what to solve now and what can wait
A mapped process

A concrete example: company enrollments

One of the processes we analyzed, before and after the portal and automations.

Beforemanual

Every step weighs on the organization's team

  1. 1Course catalog emailed as an Excel file
  2. 2The company fills it in and sends it back
  3. 3Names checked by hand in the management system
  4. 4Phone follow-ups for missing data
Afterautomated

The team only steps in on exceptions

  1. 1The company logs into the portal with its own credentials
  2. 2It selects employees from an already-synced list
  3. 3The system checks automatically and flags only anomalies
  4. 4Automatic email reminders until confirmation

The workload shifts from the organization's team to the company, which enters the names, and to the system, which checks them.

The architecture

How Younity, N8N and Planner work together

Three tools, three distinct roles: no overlap, no system doing another's job.

Younity, the central platform

The single source of truth for catalog, enrollments, contacts and website. Add a course and its public page is generated automatically: no manual uploads, no mismatches.

N8N, connecting the systems

Connects Younity, the existing management system and Microsoft 365. It handles reminders, course materials, end-of-course certificates, and creates communication tasks for every new course.

Microsoft Planner, collaboration

Replaces personal spreadsheets and scattered tools with one task system, for course preparation and the editorial plan alike. External consultants join as guests in Teams.

The roadmap

Four phases, not one big-bang change

No automation is built before the underlying data is reliable. That's why phase one works on the foundations.

Phase 1, months 1-2

Foundations

Platform setup, first contact sync, and shared task management live within one or two weeks.

Phase 2, months 3-5

Enrollment portals

A portal for companies, one for private workers, and handling of special cases outside the management system.

Phase 3, months 5-8

Automations

Reminders, course materials, certificates and satisfaction surveys with a results summary.

Phase 4, months 8-9

Optimization

Fine-tuning based on real use and consolidated analysis of training quality.

Have similar processes to sort out?

Let's start with a call to see where time is being lost today.

Book a call