Training providers
Keep course enquiries
moving to the right person.
A business asks about a course or group session; course interest and preferred dates must reach the right administrator.
An illustrative handoff
- 01
An organisation requests a course or group session.
- 02
The supplied course, date and group details are captured.
- 03
The agreed administrator receives the next action.
- 04
Suitability and places remain for staff to confirm.
Hypothetical process, not a deployed customer system.
Organise the work.
Leave judgement visible.
Public dates, private groups and onsite requests can require different administrative details. A small workflow can organise what was supplied and what still needs a conversation. It should not decide which qualification a person needs or imply that a requested date is available.
Create an owner-assigned course-enquiry record and an internal draft acknowledging the request.
What goes in.
What stays with you.
Information required
Organisation contact, requested course, indicative group size and requested date where supplied.
Only agreed and authorised fields belong in the connection. We establish identifiers, field types, owners and the expected volume during feasibility. Do not send private sample records in an initial email.
The human decision
Staff confirm suitability, availability, fees and booking terms.
A preferred date is not a reserved place. Missing learner numbers or an unclear delivery location should become a clarification item. Retries should not create extra bookings, and no learner assessment or certification is performed.
Start with
the actual process.
- Which details are needed for a group enquiry?
- How are requested dates distinguished from confirmed bookings?
- Where do incomplete requests wait for review?
An existing system or a better checklist may already handle the need. We do not assume that a visible enquiry form or a manual step establishes a commercial problem.
Try the related fictional exampleOne workflow.
Only if it fits.
A narrow version may fit the £450 starter pilot after intended-tool feasibility: one input, one existing tracker and at most two approved app connections. The fee is not a sector-wide implementation package. Several channels, bespoke planning, data migrations and wider reporting require separate scope.
Read the pilot scopeA clear next step
Tell us about
one workflow.
What comes in, where should it go,
and who needs to act?
A short outline is enough. Please leave passwords and private records out of an initial email.