Skip to content

How Askel keeps coursework trusted.

Five steps that follow a project from the first week to the moderator’s desk. Every feature sits under one step, so you can see what happens when, and who does it.

Step 1 of 5

Prepare

Have we told students the rules, and can we show we did?

Everyone knows the AI rules before the work starts.

Student reading the AI rules before the project starts, with a tick and the date
01Students read the AI rules and tick to say they have, with the date.
AI rules practice quiz for students
02A short practice quiz on what’s allowed.
Staff AI training log with dates
03A record of which staff have had training, and when the school’s policy was last checked.
Step 2 of 5

Show

Can a student show how their work grew?

The work shows how it was made, as it’s made.

Student log stage asking where a pasted paragraph came from
01Each step of the project has a date. Drafts are saved as they go. If a student pastes in a big chunk of text, Askel asks where it came from.
Supervisor signing a student’s AI-use statement
02Students say which AI tools they used, and the teacher signs it too.
Meeting record with the help given, tagged and dated
03Meetings and any help given are written down.
Step 3 of 5

Notice

How do I spot a problem without accusing anyone?

Teachers see facts worth talking about. We don’t guess whether AI wrote it.

Teachers only

Facts for teachers to look at, not a verdict.

Staff comparing saved versions of a student’s writing over time
01A picture of how the writing grew over time.
Staff list of facts worth a conversation, each with its reason
02A short list of students it may be worth checking on, with the reason.
Step 4 of 5

Resolve

What do I do when I’m worried, and how do I keep it fair?

A worry becomes a fair, written-down conversation.

A teacher writing down a worry about a piece of work
01Any teacher on the course can raise a worry.
The student’s invitation to talk, and space to add their own account
02The student is invited to talk, not accused, and can give their side in their own words.
The senior teacher’s page for deciding, with the school’s policy beside it
03A named senior teacher or the exams officer decides, using the school’s own policy. All of this happens before the student signs off the work.
Step 5 of 5

Prove

Can I sign the statement, and back it up if asked?

Signed records that anyone can check.

Cohort view showing what is done and what is still to do before signing
01Before the teacher signs, Askel shows what’s done and what’s still to do. It fills in this year’s exam board forms.
Checking a signed record by its code, with no account
02Every PDF it makes is signed, with a short code and QR code anyone can check.
Inspection pack export for the exams officer
03The records a JCQ inspector may ask for are in one place, and there’s a short report for governors with no names in it.
What Askel records

What Askel records, and what it doesn’t.

Askel records what people do in Askel, with dates. It doesn’t watch students.

Records

  • Plans, milestones and stages, with dates
  • Drafts saved in Askel, like the EPQ diary
  • A fingerprint for each file linked from elsewhere
  • Meetings and any help given
  • Which AI tools students say they used
  • Teachers’ sign-offs and signed statements
  • Worries raised, the conversation and what was decided

Doesn’t record

  • Keystrokes
  • What’s on the student’s screen, or their camera
  • Work done in other apps or websites
  • The coursework itself, for most subjects. It stays where your school keeps it.
  • Anything sent to AI companies. There’s no AI in Askel.
Already using Project Q?

Start your next cohort in Askel. Keep this year’s students where they are.

Project Q is AQA’s online system for the EPQ.

Switching from Project Q

From first idea to hand-in, on the record.