A course page in Üsküdar can give a clear date and price yet leave prospective learners guessing whether they qualify. Before registration opens, give applicants observable examples of the skills they need and a route to ask about experience gained another way.
Describe what a learner must already be able to do
Separate required skills from preparation the provider recommends. For a sample spreadsheet course, replace a broad label such as intermediate level with tasks a learner can recognise. They might need to sort a list and use a simple formula before class. If a skill will be taught in the course, list it under the programme so the same task does not appear as a barrier to entry.
Put entry requirements above the registration button and repeat them in the applicant instructions.
Show which evidence the team can assess
Explain what the team accepts for each requirement. If work experience can count in place of a prior course, give an example of the evidence the applicant can describe. Provide one contact route for uncertain cases. Ask only for the information the team needs to decide at this stage.
Rehearse three applicant journeys
Use three fictional applicants in a test copy. One meets the requirements, one has equivalent experience and one needs a preparatory course. Ask each to explain the next step after reading the page. Compare their choices with the steps the registration team expects. Check that a visitor can find the preparation route before committing to the wrong course.
Make decisions consistent across both languages
Record the course code, required task, acceptable evidence and next step for each example. Give the same record to both editors. Read the English and French pages beside the application instructions and confirm that they describe the same requirements.
Checklist before publishing
- Required and recommended skills easy to distinguish
- Equivalent experience has a clear review route
- Preparation option visible before registration
- Entry requirements agree in both languages