You've downloaded a project's plan sets from the documents shelf and you want an AI to help you read them. You have three tiers of choice — and for journalism the difference matters, because it decides who else sees your documents and your questions.
Upload the PDFs to NotebookLM, ask questions, get answers with citations back to the page. Ten minutes, no setup. The trade: Google processes your documents and sees what you're asking about. Fine for public plan sets; wrong for anything involving a source.
Nothing leaves your machine — no Google, no OpenAI, no Anthropic, no server logs, works on a plane. The open-model world is led by strong Chinese and open-source labs (Qwen, DeepSeek, Kimi/Moonshot, GLM/Z-ai, plus Llama, Gemma, and Mistral), and the tooling has become genuinely easy. Much of this guide follows the working notes of Simon Willison — who also happens to have built Datasette, the tool behind our query pages — and his llm command-line tool.
Setup (Mac, ~15 minutes):
brew install ollama # the local model runner ollama pull qwen3:8b # a strong small model (~5 GB download) brew install poppler # gives you pdftotext pip install llm files-to-prompt llm install llm-ollama # connect Simon Willison's llm tool to Ollama
Pick the model your hardware can carry:
qwen3:8b or gemma3:12b —
capable readers of extracted text.qwen3:32b or a DeepSeek-R1 distill —
noticeably better reasoning over long documents.The workflow:
# 1. extract the text from a downloaded plan set pdftotext proj3_plans.pdf plans.txt # 2. ask questions of it, entirely locally files-to-prompt plans.txt | llm -m qwen3:8b \ "List every mention of affordable or below-market units, with sheet numbers."
Plan drawings vs text: plan sets are mostly drawings — pdftotext
gets the labels and tables but not the pictures. For the drawings themselves, use a local
vision model (ollama pull qwen3-vl and point it at page images), or accept
Tier 1 for the graphical sheets.
The largest open models (Kimi K2, DeepSeek's full releases, GLM's flagships) outgrow laptops but are served cheaply by many independent providers — you keep model choice and price leverage, though you're trusting a server again. A reasonable middle when a document set is huge and non-sensitive.
← Back to the reporters page · Sources and further reading: Simon Willison's weblog and llm documentation — the living reference for local-model practice.