Oral assignments with StudyStride

Choose a task that benefits from visible evidence

StudyStride is a strong fit when a learner should point to something in the browser and explain what they notice, infer, question, or recommend. Good tasks evaluate reasoning that is difficult to demonstrate with a polished written answer alone.

• Reviewing code, a pull request, or test output.
• Evaluating a source, claim, chart, dashboard, or primary document.
• Explaining steps in a mathematical, scientific, or technical solution.
• Critiquing a design, interface, accessibility decision, or engineering tradeoff.
• Defending a research conclusion or portfolio decision with visible evidence.
• Reflecting on revisions by comparing an earlier and later artifact.

Avoid using StudyStride merely to require a longer recording. The browser evidence and spoken reasoning should both matter to the learning objective.

Design the assignment before introducing the tool

1. Name the performance. State what learners must demonstrate: diagnose, compare, justify, interpret, critique, or reflect.

2. Provide the browser artifact. Link the exact code, source, chart, design, problem, or document learners should inspect.

3. Require evidence. Tell learners to keep the relevant material visible and identify the location, claim, line, step, or visual feature they are discussing.

4. Set a realistic duration. A focused five-to-ten-minute response is often more revealing than an unfocused long recording.

5. Specify the submission files. State whether you want the Capture Report PDF, transcript, reviewed optional AI summary, Google Doc link, or a subset.

6. Publish the rubric. Grade disciplinary reasoning, evidence, prioritization, and communication—not the fluency of the AI summary.

7. Provide an alternative. Accommodate learners who cannot record audio or use the required browser/Google workflow.

Learner workflow

1. Open the assigned artifact in a normal Chrome tab and open StudyStride.

2. Name the session, select Any browser page, choose the microphone, and keep key screenshots if the assignment requires visual evidence. Choosing a Google Doc is optional; StudyStride creates one automatically if needed.

3. Start capture and complete the response in the learner’s own words. Keep each cited item visible, pause on important states, and use Capture current view when necessary.

4. Choose Stop & review. Generate the AI summary only after the oral performance is complete.

5. Compare the AI summary with the transcript and original browser evidence. Correct misleading wording and identify any AI omission or misunderstanding.

6. Select the appropriate screenshots and prepare the Capture Report PDF.

7. Submit only the files and links named by the instructor, using the institution’s normal assignment system.

Recommended submission package

For most oral assignments, ask for:

1. Capture Report PDF — the compact connection between visible evidence and the matched verbatim transcript.
2. Verbatim transcript — the closer record of what the learner actually said.
3. Short learner reflection — what any optional AI summary misunderstood, omitted, or represented well.

The reviewed AI summary can be included as a navigation aid, but it should not replace the transcript or become the object being graded. Avoid requiring raw audio unless hearing the original performance is necessary and your policies support collecting it.

Grade the demonstration, not the generated polish

Assignment examples

Narrated code review

“Open the assigned pull request. Identify two correctness risks and one maintainability concern. For each, keep the relevant code visible, explain the impact, assign a severity, and propose a test or change. Distinguish defects from personal style preferences.”

Source credibility review

“Review the assigned article and one linked source. Identify the central claim, evaluate the evidence, point out one limitation, and explain what additional evidence would change your confidence.”

Data interpretation

“Walk through the dashboard. Explain two meaningful patterns, one possible confound, and one conclusion the visualization does not support.”

Problem-solving defense

“Explain the submitted solution step by step. Identify the assumption that matters most, show where it is used, and describe how the result changes if that assumption is removed.”

Accessibility critique

“Navigate the assigned page using the stated review checklist. Document three barriers, explain their user impact, and prioritize a repair sequence.”

Revision reflection

“Compare the first and final versions of your work. Defend two revisions, identify one tradeoff, and explain what you would change with another iteration.”

Keep the AI role transparent and limited

• StudyStride captures and organizes evidence; it does not establish identity or prove who completed the work.
• It is not proctoring, plagiarism detection, cheating detection, emotion recognition, or automated grading.
• AI questions, visual descriptions, and summaries can be wrong and must remain reviewable.
• The instructor should evaluate the original demonstration and evidence, not an AI confidence value.
• Learners should know which artifacts are generated, what will be submitted, who can access them, and how long they must be retained.
• Recording notice, consent, accessibility accommodations, and institutional policy remain human responsibilities.