Running a shared class flashcard deck: structure, corrections and weekly routines

Build one teacher-owned deck per unit and order it the way you teach: the objective first, then core facts, one rule or equation, applications, a common misconception and a closing comparison. Share it after the lesson. Collect corrections during the week, fix the source in one go, and leave each student's review schedule alone.

This guide covers how to run that routine: how to structure the deck, how often to correct it, and what a week looks like in a few common teaching situations. For the product overview, including sharing modes, browser and Apple app access, privacy and pricing, see Memor More for teachers. The examples use a short demo we prepared around a 12-card Year 9 biology unit.

Structure the deck around one unit

A class deck works best when it has one defined purpose. Each prompt should be small enough to retrieve in one step: a term and its definition, a short translation, a formula and when to use it, or a compact question and answer. Before sharing, check every card for correctness, reading level, accepted variants, accessibility and curriculum fit.

The demo unit covers cellular respiration in 12 connected cards, in teaching order:

We prepared this 12-card unit to make the workflow concrete. It uses structured teaching material and contains no real teacher, student, school or classroom data.

Ten to twenty prompts per lesson sequence is a manageable size.

Keep the deck to things that can be recalled. Flashcards suit vocabulary, core facts, formulas, distinctions and recurring misconceptions. They are a poor container for a complete proof, extended writing feedback, laboratory technique, speaking assessment, or anything that depends on performance and explanation. Those stay in the lesson.

Decide how students will get the deck

Make this decision before the first lesson, because it changes how corrections reach students later.

In the full app, the teacher chooses one of the current sharing modes:

• Link only keeps the deck out of public discovery, although anyone with the link can access it while the share remains active.
• Public makes the deck discoverable in the public library as well as available for copying.
• Editable is marked Coming soon. Students do not collaboratively edit the teacher's source through this workflow.

Link only is unlisted; Public adds discovery. Collaborative editing is not currently available.

Link only is an access model, not an identity check. A forwarded URL gives the same access as the original message. Send links through an approved channel, and never put student names, grades, health information, private feedback, unreleased assessments or other sensitive data on shared cards.

Then pick the student route:

• Browser route. The Memor More browser app runs on any platform with a modern browser, including Android, Windows, ChromeOS, Linux and shared computers. Students can create, import, edit and study decks, with data stored locally in that browser. It does not yet provide accounts, cross-device sync, AI generation or guaranteed offline launch, so a student should stay in the same browser profile and keep a source copy when continuity matters.
• Full Apple app route. The iPhone, iPad and Mac app is the flagship experience. An imported shared deck keeps a link to the teacher's source and picks up your revisions the next time the student opens the app or the deck with a connection. The app also adds iCloud sync, AI generation and offline use. It currently needs iOS or iPadOS 18 or later, or an Apple-silicon Mac on macOS 15 or later.

A mixed-device class can use the same material on both routes. Tell students up front which route they are on, because that decides how they will receive corrections.

Set a correction cadence

Corrections are the part of a shared deck that needs a routine. When a prompt is ambiguous, outdated or wrong, correct the teacher-owned source rather than sending students a list of manual edits. In the full Apple app, the imported deck checks for your edits when the student opens the app or the deck while online, or pulls down to refresh. Nothing is pushed instantly, and students cannot edit the source with you. Browser learners get the change when you supply an updated import.

The correction leaves the learner's progress in place. In the demo, the revised card keeps its existing due date, level and last-reviewed value, so nobody has to rebuild it.

The correction demo shows revised content together with Due tomorrow, level 3 and Last: Today. It demonstrates the maintenance principle without presenting a classroom outcome as evidence.

A rhythm that fits most units:

1. During the week, collect. Note confusing cards as students mention them, along with anything you spot while teaching.
2. Once a week, fix the source. Make all the edits in one sitting. A card that is factually wrong is the exception: fix that one straight away.
3. At the start of the next lesson, announce. Tell students what changed and ask full-app users to open the deck so it picks up the edit. Give browser learners the updated import.
4. Spot-check one device. Open the revised card on at least one student's device before treating the change as distributed. An offline device will not have it yet.

Deleting a source card also reaches full-app imports the next time students open the deck. Stopping the share makes the old link unavailable, but students who already imported the deck keep their local copies. Revocation is not remote deletion.

Agree the ownership details before the course starts: who maintains the deck, how students report errors, how quickly corrections should be made, and what happens to the deck when the course ends. Only the owner manages the native share. Keep the approved source material somewhere the institution controls too, so a personal app deck never becomes the only curriculum record.

Each student keeps a personal schedule

You distribute the content; each learner owns their practice history. If one student marks a card Good and another marks it Again, their future intervals diverge, because each review record reflects that learner's answer.

The prepared student view shows the same 12-card unit at different scheduling stages, without using a real learner's history.

There is no teacher dashboard for those answers. You cannot use this workflow to see who opened a deck, who completed a review, what anyone scored, or which card a particular student finds hard. That suits independent study. It rules the tool out when you need completion tracking or grading.

Example routines

A science unit, week by week

Share the unit deck after the first lesson of the sequence, built in the order shown above. Students import once and work from their own due queue for a few minutes at a time. In week two, the misconception cards are a good warm-up discussion: ask students which ones caught them out. Check understanding somewhere other than the flashcard queue, with a short written explanation or an exit question, because a finished review session is not evidence that a student can explain respiration.

A language unit: asking for directions

Imagine a teacher preparing an A2 unit on asking for directions:

• The source deck holds target-language phrases, short meanings, an audio or pronunciation cue where it helps, and accepted variants.
• The teacher checks register, spelling, regional usage, and whether each card asks for one retrievable response.
• Students import the deck and review on their own schedules. One learner keeps missing prepositions while another needs more practice with polite forms.
• After class, the teacher notices that one translation is too literal and corrects the source.
• Students on the full shared-update route receive that revision the next time they open the deck. Browser learners get an updated import.
• In the next lesson, students use the phrases in a dialogue. That separate speaking task checks whether recall carries over into communication.

To see what a finished vocabulary set looks like before building your own, open the public Spanish A2: Everyday Topics deck: 80 single words with English prompts. Treat it as an example to inspect, not certified curriculum.

A clean review queue does not prove communicative competence. Flashcards provide a retrieval layer around teaching; they do not replace conversation, feedback, contextual practice or teacher judgment.

A formula or vocabulary core that lasts a term

Use atomic pairs such as term and definition, phrase and meaning, or formula and conditions for use. Keep one source deck running through the whole unit and add only reviewed material. Students rate their own cards, so their schedules drift apart naturally. Worked proofs, extended reasoning, pronunciation feedback and practical performance belong in the lesson or another activity.

A catch-up pack for one learner

Give one learner, or a small study group that has agreed to it, an unlisted deck with the prerequisite facts for a defined topic. Use the next session to talk through errors and whether the facts transfer, then improve the source deck where needed. Ask the learner to show the skill outside the cards. The app supports the retrieval layer, not the whole teaching interaction.

Try it with one group before a whole course

1. Choose the access route. Decide whether students will import into the browser app or use the Apple app for shared updates. Confirm school policy, minimum operating systems, whether external links are allowed, and consent requirements.
2. Build ten non-sensitive cards. Use material you are permitted to distribute. Record sources for curriculum-specific wording, and ask a qualified colleague to check correctness and learner level.
3. Review the student experience. Check card order, accepted answers, pronunciation or notation, accessibility, and the instructions students will receive. Label optional material so it is not mixed in with required cards.
4. Share with a small group. Have learners import the deck and complete one review. Make sure they understand their schedule is personal and not visible to you.
5. Test one harmless correction. Change a phrase and confirm the revision path: reopen the deck or pull down to refresh in the full app, or an updated import for browser learners. Check that existing progress still makes sense.
6. Write down what needs fixing. Note preparation time, access problems, learner questions, maintenance work, and whether the routine suits the course. Judge learning with a task outside the card queue.

The pilot is small and reversible on purpose. It tells you what to change in the instructions and the material before a wider rollout.

Limits to plan around

Free and Premium sharing

Free lets you share one deck at a time; stop sharing it to share a different one. Premium has no limit on the number of shared decks. The limit counts decks, not the students who import them (checked for version 1.6.0 on 12 October 2026). Premium should not be described as a classroom or site license: purchases are tied to the individual Apple subscription. The current pricing page explains the available billing evidence and Family Sharing status. Storefront prices and entitlements can change, so check the live in-app offer before budgeting.

Where shared data goes

A private native deck can remain on-device or use a person's private iCloud setup. Publishing a shared deck is different: the deck content and associated media are uploaded to Memor More's service so recipients can retrieve them and, in the full-app workflow, check for updates. Student review history is not part of the teacher's shared-deck changes, and there is no teacher view of that history.

Read the current privacy policy, then apply your institution's data-protection, copyright, safeguarding, accessibility and parental-consent rules. If you do not have permission to upload material, do not share it through the service.

When it is the wrong tool

It is not a replacement for an LMS. There are no assignments, grades, attendance records, rosters, or teacher monitoring of student activity. It is also a poor fit for collaborative source editing, confidential student data, unreleased assessment material, and learning goals that need extended reasoning and rich feedback rather than short recall.

A school that requires native Android software, browser account sync or guaranteed offline browser launch should evaluate those needs separately. Browser access solves the question of which devices students can study on; it does not bring every native feature to the browser.

What the demo shows, and what it does not

The prepared demo shows the core behaviour: a teacher builds a coherent source, students receive and study it, schedules stay personal, and the teacher can correct the material without turning the deck into a collaborative document. It shows how the product behaves; it does not measure how much students learn.

That verification is not a universal learning claim. Results still depend on card quality, lesson design, student participation, feedback, access, and how well retrieval connects to real practice. Memor More supports those decisions; it does not make them for you.

If those boundaries fit your setting, see Memor More for teachers for the product details, try the browser app on any platform, or use the iPhone, iPad and Mac app for the complete shared-deck workflow.