Building a Study Guide From Lecture Notes With Grok
It's Thursday night, you've got 40 minutes of raw lecture notes on Newton's laws of motion, and a study guide due in students' hands by Monday. Retyping your own notes into a clean handout is the kind of task that eats an evening without teaching you anything new, which makes it a good fit for Grok, as long as you give it your actual notes instead of a vague topic name.
If you haven't used Grok much yet, the Complete Beginner's Guide to Grok covers the basics this workflow builds on. This is the specific version for turning what you already wrote on a whiteboard, or typed into a messy outline, into something a student can actually study from.
Why "write me a study guide on Newton's laws" doesn't work
Asked that way, Grok will write a perfectly reasonable, entirely generic study guide, the one you'd get from any textbook's chapter summary. It won't match what you actually covered, in the order you covered it, with the emphasis you gave certain sub-topics and the shortcuts you skipped. If you spent 20 minutes on the difference between mass and weight and thirty seconds on terminal velocity, your study guide should reflect that. A generic prompt can't know that; your actual notes do.
The fix is simple and easy to skip when you're tired on a Thursday: paste the real notes in.
The workflow, start to finish
- 1
Paste your actual notes, messy is fine
Copy your lecture notes as they exist, bullet fragments, abbreviations, half-finished sentences. Grok doesn't need clean prose to work from; it needs the real content and the real order you presented it in.
- 2
Tell it the format your students actually use
Specify what a study guide means for your class: a section per topic with a two-sentence summary and three review questions, or a table of terms and definitions, or a set of practice problems with answers hidden below. Match whatever format your students are used to seeing from you.
- 3
Set the difficulty and depth explicitly
Tell Grok the grade level and whether this is a first exposure to the material or exam review. The same lecture notes produce a very different study guide for "introduce the concept" versus "this is the night before the test."
- 4
Review for anything it filled in that you didn't teach
Grok will sometimes round out a thin section with textbook detail you didn't actually cover in class. That's not wrong information, usually, but it can put something on the study guide that wasn't on the lecture and shouldn't be on the test either. Read it once before it goes out.
The input: what the notes actually look like
Here is a realistic set of raw notes for a 9th grade physical science class, the kind you'd actually have at 9pm. The class, teacher, and numbers are invented for illustration.
Teacher's lecture notes
Raw notes as typed during class, illustrated
Newton 1: object at rest stays at rest, moving stays moving unless net force. Inertia = resistance to change in motion. Seatbelt demo, cart + block. Newton 2: F = ma, net force. Did 3 practice problems, 10 kg cart pushed w/ 20 N gives 2 m/s^2. Mass vs weight: mass is amount of matter (kg), weight is force of gravity (N), W = mg, g about 9.8 m/s^2. Spent a long time on this, kids kept mixing them up. Newton 3: equal and opposite action-reaction, different objects. Balloon rocket, skateboard push-off. Friction mentioned briefly. Did NOT cover terminal velocity or momentum, save for next unit.
The prompt
Turn these lecture notes into a study guide for my 9th grade physical science class. Format: one section per major topic, each with a 2-3 sentence summary in plain language, then 3 review questions (no answers, they'll discuss those in groups). This is review before Friday's quiz, so weight sections by how much class time I spent, and keep it focused on what's likely to be tested. Do not add anything I marked as not covered. Notes: Newton 1 covers objects at rest and in motion, inertia, seatbelt demo. Newton 2 is F = ma, three practice problems, a 10 kg cart pushed with 20 N gives 2 m/s^2. Mass versus weight took the longest and students kept mixing them up, W = mg with g about 9.8. Newton 3 is equal and opposite action-reaction pairs acting on different objects, balloon rocket and skateboard demos. Friction was mentioned only briefly. I did not cover terminal velocity or momentum.
”That prompt does three things worth noticing. It gives the actual content instead of a topic name, it states the format precisely enough that Grok doesn't have to guess, and it flags what wasn't covered so Grok doesn't quietly add it as if it were part of Friday's material. It also tells Grok to weight sections by class time, which is the one instruction a generic prompt can never replicate.
The output: a representative study guide excerpt
A good response gives more space to mass versus weight than to friction, and keeps the questions tied to what happened in class. Here is a representative excerpt, shown as a table so you can see how the sections map to the notes:
| Section | Summary (excerpt) | Review question (excerpt) | Where it came from |
|---|---|---|---|
| Newton's first law | Objects keep doing what they are already doing unless a net force acts. Inertia is the resistance to that change. | Why does a passenger lurch forward when a car brakes suddenly? | Seatbelt demo |
| Newton's second law | Net force equals mass times acceleration. A bigger force on the same mass gives a bigger acceleration. | If the 10 kg cart is pushed with 40 N instead of 20 N, what happens to its acceleration? | Three practice problems |
| Mass versus weight | Mass is how much matter an object has. Weight is the pull of gravity on that mass, so it changes with location. | Why would the same rock have a different weight on a planet with weaker gravity? | Longest section, the confusion point |
| Newton's third law | Forces come in pairs that act on two different objects. They are equal in size and opposite in direction. | In the balloon rocket, which two objects form the action-reaction pair? | Balloon and skateboard demos |
| Friction (brief) | Friction is a force that opposes motion between surfaces. | Name one place friction helped or hurt in today's demos. | Mentioned briefly, kept short |
Two things to check here before it goes out. First, confirm the second-law question is not doing the arithmetic for students in a way that changes the answer you taught, and check any number Grok generates against your source, since figures are where a plausible-sounding mistake is easiest to miss. Second, confirm terminal velocity and momentum are absent, because those were the two items you explicitly left out.
Tip
If you want practice questions with answers instead of discussion questions, say so explicitly, and specify whether you want multiple choice, short answer, or a mix. Grok will default to whichever seems most common for the subject if you don't specify, which isn't always what you actually want.
Why this worked
Three inputs did the heavy lifting. The real notes fixed the content, so the guide couldn't drift toward a generic textbook chapter. The stated format fixed the shape, so the output needed no reformatting. And the explicit "not covered" line set a boundary, which matters because a model asked to be helpful will tend to fill a gap with plausible material. Take away any one of the three and you are back to editing a guide that only loosely matches your class.
The next move
Once the guide exists, the strongest follow-up is one that only you can prompt for: paste in a note about what students got wrong on the last exit ticket and ask Grok to add two extra review questions on that specific confusion. That puts your read of the room back into the document. If you are comparing approaches, the Gemini version of this workflow works from slides and lab handouts, and the Copilot version for students starts from the other side of the desk.
Where a Skill saves real time across a semester
If you're teaching the same course for a full semester, you're going to run this exact workflow fifteen or twenty times, always with the same format, the same reading level, the same instruction to flag anything you didn't actually teach. Retyping that instruction every week is exactly the kind of repetition Grok's Skills feature exists to remove. A Skill is a named, persistent instruction set Grok remembers across every conversation, not just within one chat, so you can build one once, something like "9th Grade Science Study Guide Formatter," with your format, tone, and depth rules baked in, and from then on you just paste the week's notes and reference the skill instead of rewriting the brief. The step-by-step is in building a custom Grok Skill.
That's a different shape from asking a fresh question every time, and it's worth setting up in week two of a semester rather than week fourteen, once you've noticed the pattern in what you're asking for.
What this workflow isn't for
This works well for consolidating and reformatting material you've already taught. It's a weaker fit for generating brand-new content you haven't verified, an entirely new unit's worth of material with no notes behind it, or anything involving specific numeric data like exact experiment results, where you should double-check figures against your source material rather than trust a plausible-sounding number. And a study guide is not a substitute for your own read of what students actually struggled with in class; Grok has no way to know which question got blank stares and which one everyone answered instantly, so keep that judgment in your hands even after the formatting is done.