Tutor LMS Gradebook stores final grade computations in wp_tutor_gradebooks and per-result rows in wp_tutor_gradebooks_results, with quiz attempts in wp_tutor_quiz_attempts (and per-question answers in wp_tutor_quiz_attempt_answers) and assignment submissions in wp_comments with assignment meta. The default Gradebook screen shows per-course summary; cross-course grade history, pending-grading queues, and gradebook pivots for cohorts are not part of the built-in admin.

SleekView reads all four tables directly. An instructor grading queue filters tutor_quiz_attempts to attempt_status = review_required sorted by submission date so instructors process pending work in one pass. A per-student grade history joins gradebook results, quiz attempts, and assignment submissions to give a complete academic record on one screen. A gradebook pivot turns student rows and course columns into a class-wide grade matrix for end-of-term review.

Inline grade entry routes through Tutor LMS's grading API so completion hooks fire, certificates issue, and parent-portal notifications send (if installed). Direct table writes are available for grade corrections where you don't want re-notifications. Instructor scoping ensures each teacher sees only their own courses; capability gating layers admin and support roles on top.

Grading is one of the most time-consuming parts of running an online course at scale, and the default Tutor LMS Gradebook admin treats each gradable artefact as a separate workflow. Quiz attempts pending review live in one screen, assignment submissions live in another, and the cumulative gradebook view is per-course rather than per-instructor or per-cohort, which means an instructor teaching three courses opens three tabs and then never builds a picture of what's actually pending across their teaching load. Course designers want to know which quiz questions are ambiguous (most students get the same wrong answer), and that information is available in tutor_quiz_attempt_answers but isn't a built-in report.

Student support wants a complete academic history across courses, and instead has to click through quizzes, assignments, and gradebook screens for a single student. SleekView's job is to expose all four tables (tutor_gradebooks, tutor_gradebooks_results, tutor_quiz_attempts, and the assignment-comment records) as a shared workspace, then let each role build the saved view they actually need. Inline edits through Tutor's grading API mean hooks fire, certificates issue, and parent-portal integrations stay consistent; direct writes are available for back-fills.