What Marko can and can't do (yet)
Marko is powerful, but not magic. Here’s an honest read on what works well today and what’s still in development. We update this as new capabilities ship.
What Marko does well today
Answering questions about your work
- Class and student performance across one assessment or many
- Question-level analysis (difficulty, outliers, distributions)
- Misconceptions and common mistakes
- Status checks (“what’s still being marked?”)
- Specific marks (“why did Sam get 3/5 on Q4?”)
- Cross-assessment comparison (“how did this term compare?”)
Doing things on your behalf
- Marking submissions — single, batch, or all pending in an assessment
- Retrying failed submissions
- Re-marking a whole submission, or re-running one question across the class
- Overriding a specific mark to a specific value — Marko applies your value and re-totals the submission
- Editing a question — changing its total marks, or its answer key / marking criteria (optionally re-marking existing answers with the new key)
- Flagging a submission for review
- Creating and revoking share links
- Generating PDF and CSV exports
- Renaming an assessment, updating its subject / topic / year group, or changing a submission’s class
- Managing the student roster — archiving and unarchiving students, assigning them to classes, setting a year group, and merging duplicate students
- Getting your personal referral link
- Opening billing settings and specific pages, and navigating you to an assessment, submission, or student
- Saving, editing, and clearing memory preferences
Working with context
- Picking up your current page as default scope
- Reading the scope chip and adapting questions accordingly
- Carrying conversation context through a session
What Marko isn’t great at yet
- Writing fresh feedback for you to copy. Marko can summarise patterns but isn’t a drop-in feedback writer today — the per-question feedback comes from the marking engine, which you can edit.
- Acting on data outside Marking.ai. Marko doesn’t talk to your LMS, gradebook, or email. Exports and CSVs are the bridge.
- Changing branding or output customisation. Marko can open your billing settings, but there’s no tool to open or change customisation / branding settings — you’ll do that yourself in Settings.
- Long, multi-step plans. Marko handles single-action requests well; multi-step plans (“mark these, then share, then export, then send to gradebook”) work better broken into separate requests.
What’s coming
We’re actively working on:
- Better proactive nudges (“you’ve got 18 failed submissions worth retrying”)
- Deeper cross-assessment longitudinal analysis
- Tighter integration with branding and shared output customisation
- More user-facing Marko tools where they save real time
A note on trust
Marko is here to help you mark faster — not to replace your judgement. Confidence indicators, confirmation previews on the actions that matter, and the auditable scope chip all exist so you can verify what Marko is doing. Marko can change marks and edit questions, but every write is yours to review — and destructive or bulk actions always confirm with you first. If anything ever looks wrong, drop us a line.
Need help?
Open the Account menu and choose Chat to a human, ask Marko, or email connect@marking.ai.
FAQs
How often does this article get updated?
Whenever a meaningful Marko capability changes. Check back when you spot a new behaviour and want a sanity check.
Can Marko really change a mark?
Yes. If you ask Marko to set a specific mark to a specific value, it applies your override and re-totals the submission — the same result as changing it yourself in the mark details. It only does this when you explicitly ask.
Can I request a feature for Marko?
Yes. Open the Account menu, choose Chat to a human, and tell us what you’d want Marko to do for you. We read every suggestion.