Start free
Home › Guides › PDF to practice questions
Study tools

PDF to practice questions: turn a chapter into a test you can sit

Reading a chapter twice makes it familiar, not recallable. Here is the workflow that uses questions to find the edge of what you know — and what generation cannot do for you.

29 October 20267 min readLookfornotes
The short version

Re-reading a chapter feels like progress because the material becomes familiar. Familiar is not the same as recallable. A question set answers the question you actually care about — what can you produce with the book closed — and it tells you where to spend the next hour.

Why questions beat another read-through

When you read a page twice, the second read is easier. The ease gets read as learning, and then the exam asks you to produce the same content with no page in front of you. That gap is not a memory problem, it is a retrieval problem, and retrieval only improves by being practised under the conditions that make it hard.

There is a second reason questions are worth the effort: they mark out the edges. A chapter you have read feels uniformly understood. Sit ten questions on it and the shape of your ignorance becomes specific — usually two or three sub-topics, not the whole chapter. That is a much cheaper place to start revising.

What makes a generated question worth answering

Tool output varies enormously, and most of the difference comes down to four things. Test any generator with a chapter you already know well; you will spot the failure mode in five questions.

  • 1. It asks about something the chapter actually says. Vague questions answerable from general knowledge are worse than useless, because you can get them right and learn nothing.
  • 2. It asks for one thing. A question with three parts hides which part you missed, and you cannot score it honestly.
  • 3. The answer is checkable against the source. If you cannot point at the sentence that settles it, you cannot trust a wrong answer, and a generated question with a wrong answer teaches the wrong thing.
  • 4. The difficulty matches the exam. "Define X" is not the same demand as "explain why X happens here" — a set of pure definitions trains recall of labels, not the application the paper asks for.

A workflow that takes about twenty minutes

  1. Pick one chapter, not the whole book. Fifty questions over a 300-page PDF produces a set too broad to score and too shallow to trust. One chapter, one pass.
  2. Generate the questions before you revise. Sit them cold. The score is a baseline, and a baseline is the only thing that tells you whether the next hour worked.
  3. Mark honestly. Anything you half-knew counts as wrong. The point is to find the boundary, not to protect your feelings about the chapter.
  4. Group the misses. Usually they collapse into two or three ideas. Those ideas, not the chapter, are your revision list.
  5. Turn the misses into cards. One card per missed fact, phrased as a question you can answer in five seconds. This is where generation earns its keep — you are making cards for the ten things you got wrong, not all forty things in the chapter.
  6. Re-sit a fresh set a few days later. Not the same questions, or you are testing memory of the answers. A new set over the same chapter is the real check.

Where generation stops being enough

Three limits are worth knowing before you rely on this for a graded exam.

  • Generated questions are not past-paper questions. They test the content; they do not imitate a marking scheme. For a DSE or A-Level paper, the command words and the mark allocation are part of the skill, and only real papers teach that.
  • They can be easier than the exam. A model reading a chapter tends to ask what the chapter emphasised. Exams ask what the syllabus emphasised, which is not always the same.
  • Answers need checking. On a chapter with numbers or definitions you know well, read the answers before you trust the score. One wrong "correct answer" can cost you a topic you had actually learned.

So use the set for the job it does well — finding the edge of what you know, fast — and use real papers for the job only they do.

How this works in Lookfornotes

Paste text, give a URL, or upload a PDF, and the workspace offers four outputs on the same document: summary, mind map, flashcards, and practice questions. A question set costs 4 points and a flashcard set costs 5, against 30 free points on a new account with no card required. Extra points are one-off packs, not a subscription, so a six-week revision push does not turn into a recurring charge.

There is no public library of ready-made question banks and no way to import one — the source is always your own document. If what you want is a bank of exam-style questions written by an examiner, that is a different product, and worth paying for separately.

Try it on the chapter you have been avoiding

Upload one chapter and sit the set cold. A question set costs 4 points, and a new account starts with 30.

FAQ

Can I turn a PDF into practice questions?

Yes. Upload a PDF (or paste text, or give a URL), choose practice questions, and the workspace drafts a set from that document. A set costs 4 points and a new account starts with 30 free points.

Are the generated questions the same as exam questions?

No. They test the content of your document rather than imitating a marking scheme. Use them to find gaps early, then sit real past papers for exam technique and command words.

How many questions do I get from one chapter?

It varies with how much testable content the chapter contains and how the document is structured. Dense definition-heavy chapters produce more usable questions than discursive ones, and you can generate another set if the first one is thin.

Should I make flashcards or questions first?

Questions first, if you have not revised the chapter yet. The misses tell you which cards are worth making, so you build ten cards for your gaps instead of forty for the whole chapter.

Can it read scanned PDFs?

It works with the text layer of the file as uploaded. A pure image scan with no text layer is the weak case — check the file before relying on it.