EduMark Journeys

Less chasing.
More flowing.

All the steps. All the people.
One flow that makes sense.

Connect submissions, AI checks, marking, messages and results in a visual journey. Build it around how your team works. Let EduMark handle the handovers.

Build your first journey See how it flows
No code needed Your team stays in control
Everyday assessmentExample journey
  1. Learner submitsThe work comes in
    01
  2. Similarity & AI checkUse the limits your team sets
    02
    Over your limit
    A person takes a lookFlagged work goes to your chosen reviewer before it moves on.
  3. MarkingYour team reviews the work
    03
  4. Results & feedbackRelease when the checks are complete
    04
The next step is already clear.
Your steps. Your rules. One connected process.
From the first submission to the next step.
  • Connect
  • Check
  • Route
  • Review
  • Release
The work between the work

The assessment is only
half the story.

There’s the wrong file. The second pair of eyes. The reminder nobody sent. The results waiting for someone to press a button. Journeys gives all of it a place to go.

Sound familiar?

“Has this been checked? Who’s marking it? Can we send the feedback yet?”

With Journeys

Everyone knows the process.
Every piece of work has a next step.

See the whole picture

A simple route.
As much possibility as you need.

Start small. Add a check, a branch, a message or a review. The process stays visible, even when the rules get more involved.

A few ways it can flow

From submitted to sorted.

Check the work, get it marked, and send approved feedback to the learner. Give anyone who needs another go a clear way back.

Illustrative examples. Build and save your own journey inside EduMark.

Everyday assessmentExample journey
  1. Learner submitsThe work comes in
    01
  2. Similarity & AI checkUse the limits your team sets
    02
    Over your limit
    A person takes a lookFlagged work goes to your chosen reviewer before it moves on.
  3. MarkingYour team reviews the work
    03
  4. Results & feedbackRelease when the checks are complete
    04
The next step is already clear.
Your steps. Your rules. One connected process.
Your process, piece by piece

Pick the steps.
Join the dots.

You don’t need to squeeze your team into somebody else’s process.

Start with the work

Set the assignment, check the brief, collect submissions. Give every piece of work a clear starting point.

Ask a useful question

Check uploaded work against the brief, count words, or ask AI a question your team needs answered.

Bring in the right person

Route to a marker, an integrity reviewer, a second marker or your quality team. Choose who steps in and when.

Keep everyone in the loop

Send messages as work moves on. Remind learners before the deadline or follow up with those still to submit.

Choose what happens next

Send everyone down one path, pick a sample, or give flagged and borderline work the attention it needs.

Close the loop

Release approved feedback, hold results together, or open another attempt for learners who need one.

A little help from Aurora

If you can explain it,
you can start building it.

Tell Aurora how you want the journey to work, in your own words. Type it or dictate it. Review the proposed flow, make your changes, and apply it when it looks right.

Already have a journey? Ask Aurora to change the part that’s causing the headache.

Meet Aurora
Aurora for your journeyExample
“Check the work when it comes in. Send anything flagged to our quality team, and release approved results as soon as they’re ready.”
A flow you can review

Submission → checks → review → marking → results

You review the journey before applying it.

Put AI inside the flow, too.

“Does this upload answer the right brief?” “Has the learner included a reflection?” Write the question, choose what counts as a pass, and decide what happens next. The answer stays with the work as evidence for your team.

Your journeyWork reaches a step
Your systemsSend an update. Get an answer.
External connections · Available now
Keep your tools connected

The flow doesn’t have
to stop at EduMark.

Send selected details to an external system when work reaches a step. Or ask a connected service a question about an upload and use its answer in a submission check.

Choose the connection and the information it receives. Bring the systems your team already relies on into the process.

Coming soon

More apps. More possibilities.

Ready-made apps will give you more ways to connect the tools around your assessments.

Build once. Make it yours.

A shared way of working.
Room for the exceptions.

Save the journeys that work. Use them again. Give each course or assessment the route it actually needs.

  1. 01

    Your organisation

    Set a shared starting point.

  2. 02

    Your centre

    Fit the way your team works.

  3. 03

    Your course

    Match the qualification.

  4. 04

    Your assignment

    Choose the right journey.

Automation with a human in the picture

Move the work along.
Keep the decisions in your hands.

A journey follows your permissions, review rules and release checks. See where work is waiting and why. Ordinary edits apply to future submissions, so work already under way keeps its route.

Review before applying Existing release checks respected Clear progress for your team
A few good questions

Before you
join the dots.

What is EduMark Journeys?

It is a visual flow for how assessment work moves through EduMark, from setting an assignment and receiving submissions to checks, marking, quality assurance, results and another attempt. Connect the steps, choose the rules, and see who does what next.

Do I need to write code?

You can build and edit a journey visually, start with a template, or describe what you want to Aurora and review its proposed journey. Connecting your own external service uses an HTTPS connection and may need help from the team that manages that service.

How can I use AI in a journey?

Aurora can help create or change the flow. Submission checks can ask AI whether an uploaded document matches the brief, or answer questions you write about the work. You can also include similarity and AI-writing checks. AI check results are evidence for staff; your assessment and review rules still apply.

Can I connect external systems?

Yes. A configured external connection can receive selected information when work passes a step. An “Ask an app” submission check can also use an answer from your service. Ready-made apps are coming soon.

Can different courses use different journeys?

Yes. Set a shared journey for your organisation, centre or course, choose a saved journey for an assignment, or customise its route. You can reuse a process without rebuilding it for every assessment.

What happens to work already in progress?

Ordinary journey edits apply to future submissions. Work already submitted keeps the journey that applied at submission time. Applying changes to existing work is a separate, explicit operation, with the normal checks and release permissions still in place.

Make the next step easy

Your process.
With the headaches taken out.

Start with one assessment. Build a flow that works for your team.

Get started Explore the demo