Beta: what Offload is, what we need from you, and how it fits real study weeks

What the web app does

Offload is a study companion in the browser: it helps you turn messy inputs (syllabus, notes, PDFs) into something you can actually run — plans, review sessions, and practice — instead of holding the whole term in your head.

• Exam planning & structure: Build exam-centred plans from your dates and materials, with topics, sessions, and generated study artefacts (e.g. notes, question-style practice, flashcard decks) where the pipeline supports it.
• Flashcards & spaced review: Right now, study sessions are built around five study methods. After launch we will add more methods based on what users like and use most. Underneath that, adaptive flashcards and spaced scheduling still push retrieval — so you rehearse what you are weak on, not only what feels comfortable.
• Calendar & nudges: Sync review blocks and sessions where you use Google Calendar — useful as reminders, not as a replacement for your official timetable.
• Study loop & dashboard: A place to start sessions, see progress, and move between planning, focus, and review without re-deciding everything from scratch each time.
• Free guides (no login): Longer reads on sleep, past papers, catching up, and how to revise under pressure — same evidence-led mindset as the product, usable even if you never sign up.

How using Offload can help your studies

• Less decision fatigue: "What should I do in the next 45 minutes?" is answered from your plan and due reviews, so you spend capacity on the work, not on re-planning from zero.
• Stronger memory habits: Short, repeated retrieval (flashcards, checks) spaced over days beats cramming the night before for most people — the app is built to nudge that pattern.
• Exam-shaped practice: When materials generate well, you get closer to question-level and topic-level work, not only passive notes.
• One place to return to: Dashboard, calendar hooks, and the study loop are meant to reduce tab-hopping between five different tools during a heavy week.

What we need tested — and why

We can simulate flows in the office; we cannot simulate your real college week, phone habits, or subject edge cases. Beta testers help us see where the product breaks or feels unfair.

• Exam planning & PDFs: Does upload, topic breakdown, and generated materials match your course? Where is the output wrong, thin, or unusable? That feedback directly improves prompts and pipelines.
• Flashcards & difficulty: Are intervals too aggressive or too easy? Do cards match how your exam actually asks questions? We tune algorithms and UX from real failure modes.
• Calendar & notifications: Do review events land at sensible times? Do duplicates or misses happen? We need real calendars, not demos.
• Onboarding & first week: Whether someone who finds us from a guide actually completes a first useful session tells us if we are asking too much too soon — or not enough.
• Honest friction: If something feels embarrassing, slow, or confusing, that is signal. We fix forward; we do not treat rough edges as secrets.

Known gaps (still true in beta)

• Coverage and quality vary by subject and exam board — not every syllabus path is equally strong yet.
• Calendar and notifications are assistants only; your institution's timetable and deadlines stay authoritative.
• We will ship mistakes. When we do, we correct what we can.