Features
Everything the old workflow needed you to do by hand
Built around one evaluation period at a time: build a rubric, run it, get results, without a spreadsheet in between.
Rubric builder
Your rubric, your scale, built once
Rubrics are teacher-scoped, not tied to one class. Build one and assign it to every section you teach. Each criterion gets its own indicator text at every score level, so a "3" means something specific rather than a bare number.
- Analytic mode: one shared min–max scale across every criterion
- Holistic mode: each criterion carries its own point range, no forced averaging
- Score interpretation table maps a numeric mean to a verbal label you define
- Rubric and roster lock automatically on period activation, fully immutable once students start
- Multiple evaluation periods per class (midterm, final, etc.), kept fully separate
- Optional minimum/maximum evaluation requirements, checked against group size at creation
- Scheduled auto-open/close per period, with manual override always available
Who it's for: Teachers with several sections of the same subject who don't want to rebuild the same rubric five times.
Rubric: Group Project
Fair, anonymous scoring
Honest feedback, without the social cost
Students score each criterion with a slider bounded by the rubric's scale, add an optional private note the teacher alone sees, and an optional public note the evaluated student sees with no attribution. A confirmation screen recaps everything before final submit, a guard against a slider mis-tap on a phone.
- Self-select or teacher-assigned groups, set per evaluation period
- Optional self-evaluation, recorded separately and never mixed into the peer average
- A student's results view can overlay their self-evaluation against the peer average, per criterion, as a comparison chart
- Evaluations autosave locally first, so a dropped connection never loses a draft
- Aggregate-only results: no student ever sees another student's individual score
Who it's for: Teachers who've seen a Google Form get quietly gamed by whoever wrote the harshest or kindest comment; anonymity here is enforced server-side, not just hidden in the UI.
Trust safeguards
Nothing reaches a student until it's ready
Two independent gates protect what a student eventually sees: a minimum-evaluator threshold on results, and moderation on public notes. Neither can be worked around: both are enforced automatically behind the scenes, not just hidden in the interface.
- n ≥ 3 evaluators required before any numeric result or public note is shown
- Public notes reviewed before release, with bulk-approve and auto-flagging
- Teacher can exclude a specific evaluator's rating, with a required reason; the original submission is never edited or deleted, only flagged
- Teacher can override the n≥3 threshold per student when they judge it appropriate
- Reopening a period after release marks those results stale until re-released; any note touched after a reopen reverts to pending review
Who it's for: Any teacher handing evaluative feedback about minors to other minors. This is the part of the spec built to be airtight, not just functional.
Results: awaiting release
Roster & access codes
Bulk import, no email required
Upload a CSV of Student ID, name, and an optional group/team column. Marka validates it before anything commits: new students, matched existing records, duplicates, and missing fields are all called out up front. Every student gets a 7-character access code, printable in bulk for handing out in class.
- A full preview shows what will change before you confirm the import
- One student record per teacher, linked across every class they're enrolled in
- Codes exclude ambiguous characters, no 0/O or 1/I/L mix-ups when read aloud
- Bulk export, print sheet, and single-student reveal for a lost code
Who it's for: Teachers who already keep a class list in a spreadsheet and don't want to type 40 names into a web form.
Roster: 10-A Section
Live rollup & coverage
Watch a period without waiting for it to close
Expand any student's row while a period is still open to see a provisional, clearly-labeled aggregate: bar chart by default, radar chart optional. A separate coverage view sorts students by evaluations received, not just given, so a self-select period can't quietly leave someone with unusable results.
- In-progress rollup, expandable per student, marked provisional
- Completion tracker (given) and coverage view (received), tracked separately
- Evaluator × evaluated completion matrix
- Unusual scoring pattern flags surfaced for a look, not treated as proof — see the full pattern-detection breakdown below
Who it's for: Teachers who want to nudge stragglers before a deadline instead of discovering gaps after the period closes.
In progress: 4 of 7 evaluations so far
Peer Integrity Engine
Looks for the patterns behind the numbers, not just an average
Most peer-eval tools stop at averaging scores. Marka's Peer Integrity Engine goes further: every time an evaluation period runs, it quietly looks across all the scores and notes for patterns worth a second look, then surfaces them to the teacher only. Nothing is ever labeled a violation and no score ever changes on its own — every flag is worded as "worth a look," and the teacher decides what, if anything, to do about it.
- Free-riders and standouts: students consistently rated well below or above their own classmates, flagged relative to their own class rather than a fixed cutoff
- Self-rating mismatches: students who consistently rate themselves much higher or much lower than their peers rate them, including a repeat trend across periods
- Careless or rushed evaluations: the same score given to every criterion regardless of the question, or a set of ratings submitted too quickly to reflect real thought
- Friend-group inflation: small groups of students who consistently rate each other unusually high, a pattern easy to miss by eye but easy to catch across a full class
- Rater bias: a student whose scores consistently run far higher or lower than everyone else's opinion of the same classmates, plus pairs who suspiciously always rate each other at the extremes
- Every flag lives on its own review screen, grouped by class and period, so a teacher can work through them in minutes before results go out
Who it's for: Teachers who want free-riders, grudge scoring, and friend-group inflation caught before grades go out, not after a parent or student appeals one.
Flags: Final Project, Section 10-A
Reporting
The pivot table, generated for you
The Consolidated Final Report is a named, one-click action available once a period has results: the direct replacement for the old export → pivot table → mail-merge step. Confidence context (n, limited-data flags) travels with the export, so a spreadsheet copy is never more misleading than the in-app view.
- Dashboard table and CSV download, generated together
- Multi-period side-by-side view for comparing midterm and final
- Cross-period trend view — track a student's growth from midterm to final
- Printable full report with an executive summary page, then one page per student
- Evaluator-level drill-down: exclude a specific rating with a reason, and the average recalculates immediately, reversibly
- Simplified name + General Average export for pasting into a gradebook
Who it's for: Teachers who currently combine multiple Google Forms exports by hand before they can hand results back to a class.
Class rollup: General Average
Security & privacy
Your students' data never leaves your class
Every class, student, and result is tied directly to the teacher who owns it, at the foundation of how Marka stores data, not just remembered by a setting in the app. One teacher's students and results can never mix with another's, and that boundary can't be turned off by accident.
- No student ever receives email, only teacher accounts do
- A period's rubric and roster snapshot on activation, then become fully immutable
- Rate limiting on both teacher password login and student access-code entry
- Archive vs. permanent delete kept distinct: deletion requires typing "DELETE" to confirm
Who it's for: Any school administrator who asks where student data lives before signing off on a new tool.
Kept separate, per teacher