Gravity Forms Quiz writes every submission into wp_gf_entry with quiz field values stored alongside the rest of the entry data and the calculated score in wp_gf_entry_meta under the gquiz_score meta key. The percentage score sits in gquiz_percent and a per-question correctness flag is recorded for every quiz field on the form for later review.

The default Gravity Forms entries screen at Forms > Entries shows quiz results as another row in a flat list, with the score buried in a sortable column. That works for a single quiz with twenty submissions a month. It collapses the moment an instructor runs a real assessment at scale, because there is no quick way to see how many students passed, how many need a manual review, and how many failed without scrolling and sorting repeatedly.

SleekView Kanban groups entries by the gquiz_percent meta into Passed, Needs Review, Failed, and Retake lanes with the student email, the percentage score, and any short-answer question excerpt on each card. Dragging a card from Needs Review to Passed writes a review status meta back through the Gravity Forms data layer and fires the standard entry update hooks so any LMS sync or grade-export automation stays in step with the board.

Gravity Forms Quiz handles the scoring math well, calculating a percentage from the correctness flags on every quiz field and persisting it to the entry meta. The grading review side is where the default admin runs out of road. Short-answer and essay fields cannot be auto-graded, so an instructor has to open every entry, read the response, and make a manual decision.

The default entries list shows passed, failed, and pending review entries as the same kind of row, with only a sortable column for the percentage. That works for a quiz with twenty submissions a month. It does not work for a compliance test with hundreds of submissions a quarter.

A kanban view fixes that by mapping every score band to a lane and exposing the short-answer excerpt on the card. The instructor sees the Needs Review queue depth, reads each card, and drags the result to Passed or Failed in one motion. The review status writes back to the entry record so the LMS sync, the grade export, and any student notification stay correct.

The team finally sees grading as work in progress instead of a hidden backlog.