Built to replace the spreadsheet, not add another one

Why "Marka"

Marka is the Filipino word for "mark" or "rate," the same act at the center of every peer evaluation: one student marking how another did. It's also a name that doesn't need translating for the teachers and students who'll actually use it.

The problem

Peer evaluation is a routine part of running group work: students rate their groupmates at the end of a term, and the teacher folds that feedback into a grade or a conversation. In most classrooms, that routine still runs on a Google Form. Responses land in a spreadsheet one row per submission, and the teacher has to combine them by hand, build a pivot table to get one row per student, and mail-merge a results summary to send out, assuming they send results back at all.

None of that is hard, exactly. It's just slow, repetitive, and easy to get subtly wrong: a formula reference that doesn't update, a student whose name is spelled two different ways across responses, a low-response student whose "score" is really just one classmate's opinion presented as data.

The approach

Marka is built by teachers, for teachers, by the same developer behind MarkIT, an attendance app for the same kind of classroom. Marka keeps the workflow a teacher already runs (build a rubric, open an evaluation window, collect peer feedback, hand back results) and replaces every manual step around it with a real data layer: bulk CSV roster import instead of a class list typed by hand, per-student access codes instead of a shared Google Form link anyone can share, and a one-button Consolidated Final Report instead of a pivot table rebuilt every term.

It also goes beyond simple averaging: Marka's Peer Integrity Engine automatically flags free-riders, inflated self-ratings, scoring cliques, and rater bias, for the teacher's eyes only, before grades go out rather than after.

The one rule that shaped the most design decisions: nothing reaches a student until it's ready. A result built from one or two evaluators isn't shown with a "limited data" caveat. It's withheld entirely, because at that sample size a supposedly anonymous score is close to identifiable. Public notes go through moderation before release. Every teacher's classes, students, and results are kept in their own separate space, built into the foundation of the system, so isolation between classes and between different teachers' accounts never depends on someone remembering to double-check it.

What's built in

• Teacher-authored rubrics, analytic or holistic, reusable across every class
• Anonymous peer scoring with optional self-evaluation comparison
• n ≥ 3 evaluator threshold before any result reaches a student
• CSV roster import with a validation preview and bulk access-code printing
• Live in-progress rollups, coverage view, and a completion matrix while a period is open
• Peer Integrity pattern detection: free-riders, self-rating overconfidence, collusion cliques, and rater bias, teacher-only
• Consolidated Final Report with an executive summary, cross-period trend view, and CSV export in one generation
• Note moderation with bulk-approve and auto-flagging
• No student email, ever: access codes only, with every teacher's data kept completely separate and private

Get in touch

For questions, feedback, or upgrade requests, email us at support@markaph.app.

Marka is a small, focused product. We read every email.