Appearance
An application will not submit
A family has filled the form in and it will not go. Almost all of it is the applicant's details page, and almost all of that is the date of birth being measured against things the family cannot see - two separate ranges, an age worked out at the start of the course rather than today, and one message that blames the course for a service-wide setting.
Step 1 of 10
Two ranges guard a course, and both say the same two things
A course can be limited by **age** and, separately, by **school year**. Either one refuses, and both use the same pair of messages — *"Applicant is too young for this course/event"* and *"Applicant is too old for this course/event"*. So the message does not tell you which range it failed.
Check both before changing anything. A pupil can be the right age and the wrong school year, which is the case that wastes the most time because the date of birth looks obviously fine.
Use the arrow keys to move between steps.
Why this one is worth knowing
Nearly every one of these is the date of birth, and the date of birth is measured against three things the family cannot see: the course's age range, the course's school year range, and the date the course starts. A parent looking at a correct-looking date, told their child is too old, has no way to work out which of the three is talking.
The other half of the value is knowing which messages are not the family's problem. Four of them are settings or data at your end, and a family told to check their details again will check them and ring back.
The messages, and what each one means
| What they see | What it actually means |
|---|---|
| "Applicant is too young / too old for this course/event" | The age at the start of the course, or the school year — two separate ranges, one pair of messages |
| "Adults cannot apply for this course" | Your service is in Child Mode. Nothing to do with this course |
| "DOB too early for someone who is NOT an adult" | The opposite of how it reads: the date given is too recent for an adult applicant |
| "Please select a reasonable school year according to the DOB entered" | The year chosen is more than three off the date of birth |
| "Date lies too far in the past" | Before 1925 — almost always a mistyped year |
| "Please provide at least one file for remission evidence" | A file. A link is allowed for application evidence, not for this |
| "Relationship types need to be set up on the database" | A settings list of yours is empty |
| "Sorry, this activity is not open for applications at this time" | Its application window, at your end |
Ask for the course's start date, not the child's age
The quickest way through a "too young" or "too old" call is to work out the child's age on the day the course starts and compare it with the range on the course. Nine times in ten that settles it without opening the pupil record at all.
The age message does not say which range refused it
Age and school year are checked independently and share their wording, so a pupil can be squarely inside the age range and still be refused on the school year. Check both, in that order, before telling a family their date of birth is wrong.
See also
- Making an application — the journey the family is on when they meet these
- A pupil is in the wrong school year — how a school year is worked out from a date of birth, and the offset
- Add says I must create something else first — the same idea in Fusion, where a record cannot be made until its pieces exist
- Answering the service — evidence, remissions and subsidies on the way through
