Browse documentation
Docs/Functionality

Verified Learning For Instructors And Students

Verified Learning turns a protected Grid model into a structured assignment. Each student receives a separate attempt model, answer-cell changes are recorded in order, and submission,…

Verified Learning For Instructors And Students

Verified Learning turns a protected Grid model into a structured assignment. Each student receives a separate attempt model, answer-cell changes are recorded in order, and submission, review, accommodations, appeals, and answer-key release stay attached to that attempt.

The model still does the calculation. Verified Learning adds the assignment rules and work record around the cells an instructor chooses as answers.

Instructor Workflow

1. Prepare the exercise

Create a protected model and declare every cell that students may answer as an input. Keep prompts, formulas, reference data, and scoring helpers outside those answer inputs.

Open the model and choose Create Assignment from the top bar. The action is available for a protected model that is not already an attempt. The setup dialog reports when the model has no declared input to select.

2. Define the assignment

Enter a template ID and title, add optional instructions, and choose a positive duration. Select each answer cell and choose its check:

  • Exact value compares the submitted value with the expected value.
  • Formula response compares the submitted formula text with the expected formula text.
  • Instructor rubric reserves the points for instructor review.

An instructor can also configure deterministic variants, partial-credit bands, secure-session observations, and additional accommodation approvers through the full assignment contract. A formula-response check compares normalized authored text; it does not claim that two differently written formulas are mathematically equivalent.

3. Distribute isolated attempts

After publishing the template, add one roster row per student:

student principal ID, attempt ID, model ID

When a roster connection supplies external identifiers, add the student user identifier as the fourth value and fill in the optional roster context. Choose Distribute assignment. The receipt lists the separate attempt model created for every recipient.

Use Refresh roster to see each student's status, recorded edit count, score, and appeal count. This view is reconstructed from the assignment and attempt records; it is not a manually maintained grade table.

Student Workflow

1. Open the assigned model

Open only the attempt model assigned to you. The Verified Learning chip in the top bar opens the attempt panel and shows the deadline, attempt state, work record, and a selected variant prompt when that variant defines one.

2. Work in the grid

Edit the declared answer cells as you would edit normal Grid inputs. Each accepted edit receives a stable place in the attempt history. Cells outside the admitted answer set cannot be submitted as answers.

The browser grid currently relies on the deployment authorizing ordinary writes to the student's attempt model. Cloud-organization deployments deny those generic model-write routes today; use the principal-bound learning answer API through a configured adapter there until browser write admission is aligned.

If Grid reports an interrupted answer write, open the Verified Learning panel and choose the reconciliation action before continuing. Reconciliation checks whether the model contains the value before or after the interrupted edit. It does not guess when the model contains a third value.

3. Request support when needed

Before submission, use the accommodation section to request additional time and include a reason. The instructor can decide the request in the panel; a named accommodation approver can decide it through the configured API or adapter. An accepted request updates the displayed deadline without replacing the earlier attempt record.

Instructor notes and deadline adjustments appear in the same panel. Older work events can be loaded when the current view does not contain the full history.

4. Submit and review

Choose Submit attempt when finished. Submission closes answer editing and scores the recorded final answers. Rubric items remain pending until the instructor records their scores and verification decision.

The answer key and per-check outcomes remain sealed until the instructor explicitly releases them. After submission, a student can open an appeal from the attempt panel; its later instructor resolution remains visible beside it.

Instructor Review

Open a student's attempt model and use the Verified Learning panel to:

  • inspect the ordered work record and the recorded secure-session event count;
  • add a note or deadline adjustment;
  • decide accommodation requests;
  • score every required rubric item;
  • accept or return the final verification;
  • release the answer key when disclosure is appropriate;
  • resolve student appeals; and
  • record retention or legal-hold instructions before an eligible deletion.

Preparing a grade exchange records the score that a configured learning-system connection should deliver. Delivery and acceptance are separate states; do not treat a prepared score as confirmation that another system received it.

Secure-Session Controls

While the student keeps an enabled attempt panel open, Grid can ask the student to enter full screen, record document-hidden and fullscreen-exit events, emit bounded heartbeats, and prevent clipboard or context-menu events in the Grid document. These observations help document the panel session, but they are not proof of identity or misconduct.

They cannot prevent another device, operating-system capture, browser extension, or action outside Grid. Institutions that require managed-device lockdown, identity verification, or proctoring need a separately reviewed service and policy.

Privacy And Access

Attempt models are separated by student identity. Students see their own work; the assigned instructor sees the review controls; named approvers receive only the direct accommodation-decision authority granted to them. Public model visibility does not make another student's attempt discoverable.

Deletion is deliberate. Purge remains blocked until the latest retention disposition permits deletion and no legal hold remains. There is no automatic background deletion.