How EduGenius's Content History Helps Teachers Find Past Generations Again
Content History is EduGenius's running archive of everything a teacher has generated — searchable, filterable, and organized well past a plain reverse-chronological list. Every quiz, worksheet, flashcard set, and lesson plan you've ever created lives there, browsable by format, favorite status, and creation date, with a stats scorecard summarizing the whole archive at a glance.
Quick Answer: Content History is a real, working archive — text search, a format-type filter, a favorites toggle and filter, newest/oldest sort, a grid/list view switch, pagination, and a stats scorecard (total materials, total questions, most-used formats, favorite count). It's genuinely different from Recipes (saved generation presets for next time) and Assign (turning one generation into a gradable assignment) — History is purely for finding and organizing what already exists. You can view, export, share, delete, or assign a past item, but there's no regenerate, clone, or remix action anywhere; that job belongs to Recipes. Search is real but bounded — a substring match over your most recent roughly 200 to 500 entries, not a full-text index of your entire teaching history. Nothing is auto-deleted and nothing about how much history you can see is gated by plan.
A teacher who generates a handful of materials a month can find last week's worksheet by scrolling. A teacher who generates dozens a month, across a full school year, is looking at hundreds of entries by spring — and "scroll until you recognize it" stops being a plan.
This piece covers what Content History actually does end to end: the real controls, the honest limits on search, the stats scorecard, what actions are and aren't available on a past generation, and how long anything actually sticks around.
What Content History Actually Is (and Isn't)
Content History is the record of everything you've generated with EduGenius, stored per-teacher and populated automatically the moment a generation completes — you don't have to save anything to it on purpose.
A Real Archive, Not a Decorative List
Every entry carries its title, subject, topic, format type, question count, and creation date, and the surface built around that data supports actual retrieval work: searching, filtering, favoriting, sorting, and paging through results. It's built to answer "where is the thing I made" rather than just display a feed.
Think of the difference between a folder of files named by date and a folder you can actually query. A plain feed forces you to scroll and recognize; a real archive lets you ask a specific question — "the flashcard set I made about cell division" — and get a narrowed answer back. That's the gap Content History is built to close.
How It's Different From Recipes and From Assign
Two other EduGenius features sit close to Content History, and it's worth being precise about the boundary between them.
- Recipes are saved generation presets — the formats, settings, subject, topic, and class profile you picked, stored under a name so you can run that same setup again for a new week or a new topic. See how to save and reuse content recipes in EduGenius for the full picture.
- Assign takes one already-generated item and turns it into a distributable, trackable classroom assignment with a no-login student link. It's covered in how EduGenius's Assign feature turns a generated quiz into a gradable assignment.
- Content History does neither of those jobs. It doesn't pre-fill a new generation and it doesn't publish anything to students on its own — it's the layer underneath both, the place you go to find the item you'd want to turn into a recipe or an assignment in the first place.
Why Finding Your Own Work Gets Harder as the Archive Grows
A list that's easy to scan at twenty items stops being easy to scan at two hundred, and that shift isn't specific to EduGenius — it's a well-studied pattern in how people manage their own accumulated material.
The Filing Problem Isn't New — It's Just Digital Now
In a classic study of how office workers organized their own desks, Thomas Malone found that people split roughly into "filers," who sort material into named categories as it arrives, and "pilers," who let it accumulate in loose, recency-ordered stacks — because classifying something the moment you create it is real cognitive work that's easy to defer (Malone, 1983). A generation tool that produces dozens of documents a month recreates that exact desk, just on a screen.
People Find Their Own Files Mostly by Recognition, Not Search
Barreau and Nardi's research on how professionals actually locate their own computer files found that people lean heavily on browsing and location memory — "I know it's roughly from a few weeks ago" — for anything used recently, and fall back to search mainly for older material they can no longer place in time (Barreau & Nardi, 1995). That's the practical case for pairing a recency-sorted browse view with search as a backup, rather than treating search as the only way in.
Personal Archives Don't Organize Themselves
William Jones's research program on personal information management frames this as a continuous, unglamorous problem rather than a one-time setup task: the more a person accumulates, the more that organizing, re-finding, and periodically pruning becomes its own ongoing labor, not something solved once and forgotten (Jones, 2007). A school year's worth of generated materials is exactly that kind of accumulating archive.
| Research finding | Source |
|---|---|
| People split into "filers" and "pilers"; upfront classification is effortful enough that many defer it | Malone, 1983 |
| Recent files get found by browsing/recognition; search becomes the fallback mainly for older material | Barreau & Nardi, 1995 |
| Personal archives require ongoing re-finding and organizing effort as they grow, not a single setup step | Jones, 2007 |
Content History's actual design — a recency-sorted default view, plus real search, filters, and favorites layered on top — maps onto exactly this research rather than assuming a teacher will file everything perfectly the moment it's created.
The Real Controls: Search, Filters, Favorites, Sort, and View
None of the controls on Content History are decorative. Each one does real filtering or sorting work against your actual generated materials.
Text Search, With an Honest Boundary
The search box matches against a generation's title, description, prompt, subject, topic, and class profile name — a genuine substring match over real Firestore-backed data, not a keyword tag you have to add yourself.
The honest caveat: it isn't a full-text index across your entire lifetime of generations. It scans your most recent documents — roughly up to 500 when an active search term is present, roughly up to 200 when you're just browsing without one — ordered by creation date, and searches within that window. For the overwhelming majority of a single school year's output that window covers everything; for a multi-year archive, a very old item might sit outside it.
Format Filter and the Favorites Toggle
You can narrow the list to a single format — quizzes only, flashcards only, worksheets only — and separately mark any item as a favorite with a bookmark toggle, then filter down to favorites alone. Both run as real filters against your stored generations, not a client-side trick limited to whatever happens to already be on screen.
Newest/Oldest Sort and Grid/List View
A sort control flips the list between newest-first and oldest-first, and a separate toggle switches the whole layout between a card grid and a denser list view. Results page rather than dumping everything at once, so opening History doesn't mean waiting on your entire archive to load before you can do anything.
| Control | What it actually does |
|---|---|
| Search | Substring match on title, description, prompt, subject, topic, class profile — bounded to a recent-document window |
| Format filter | Narrows to one content type (quiz, worksheet, flashcards, etc.) |
| Favorites toggle + filter | Bookmarks any item; filters the view to favorites only |
| Sort | Newest-first or oldest-first by creation date |
| Grid/list view | Switches layout density; both stay searchable and filterable |
| Pagination | Loads results in batches rather than the full archive at once |
The Stats Scorecard: What It Actually Tells You
Above the list itself, Content History surfaces a small scorecard summarizing your archive as a whole, computed from your real stored data rather than a sample.
Four Numbers, Not a Sales Dashboard
The scorecard shows total materials generated, total questions across everything you've made, which formats you use most, and how many items you've marked as favorites. It's a plain summary, not a growth chart or an engagement metric — there's no invented "time saved" figure or usage streak attached to it.
A Different Angle Than Insights
If what you actually want is trends over time — Bloom's-level coverage, a daily mastery trend, assignment performance aggregated across a term — that's a separate feature covered in how EduGenius's Insights dashboard tracks Bloom's-level mastery over time. Both surfaces read from the same underlying generation history, just answering different questions: History answers "what did I make and where is it," Insights answers "what does my teaching look like in aggregate."
What You Can Do With a Past Generation — and the One Thing You Can't
Once you've found the item you were looking for, Content History offers a small set of real actions on it, and it's worth naming the boundary plainly rather than letting a teacher discover it by trial and error.
View, Export, Share, Delete, Assign
Opening an entry shows the full generated content. From there, a genuine set of actions is available: export it (including a path to send a quiz straight to Google Forms), share it, delete it permanently, or launch the Assign wizard to turn it into a classroom assignment. Every one of those actions operates on the real, original generation — not a copy or a placeholder.
The Honest Limitation: No Regenerate, No Clone, No Remix
Here's the boundary worth stating directly: there is no "regenerate this," "use as a starting point," or "remix this" action anywhere in Content History. You cannot open a past quiz and one-click produce a new variant of it from that screen. If what you actually want is a reusable starting point — the same setup, ready to run again on a new topic — that's a different feature by design, not a missing button.
| Action | Available in Content History? |
|---|---|
| View the full generated content | Yes |
| Export (PDF, Google Forms, etc.) | Yes |
| Share | Yes |
| Delete permanently | Yes |
| Turn into a tracked assignment (Assign) | Yes |
| Regenerate, clone, or remix as a new draft | No — use Recipes instead |
Where Recipes Picks Up
That gap is deliberate, and it's exactly the territory Recipes is built to cover — a saved preset you can run again with one click, rather than a one-off variant of a specific past item. Content History finds what exists; Recipes produces something new from a saved setup. Keeping those two jobs separate is a real, intentional design choice, not an oversight worth working around.
Retention and Deletion: What Persists, What Disappears
Unlike some product areas that quietly cap history or lock it behind a plan tier, Content History does neither.
No Time Limit, No Plan Gating
Entries stay in your archive indefinitely. There's no auto-deletion after a set number of days or months, and how much history you can see isn't restricted by whether you're on a free or paid plan — a free-plan teacher's archive from September is exactly as visible in June as a paid-plan teacher's.
Delete Is Permanent, and It Cascades
The one way an entry disappears is if you delete it yourself, and that action is real and permanent — there's no trash or undo window. Deleting a generation also removes any assessment-attempt data linked to it (student responses tied to that specific quiz or worksheet), so the deletion genuinely clears the record rather than leaving orphaned data behind under the hood.
Pro Tips
- Use the recency window to your advantage. Because search covers your most recent several hundred entries, a recent generation you're hunting for is almost always inside it — the bounded window rarely matters for anything from the current term.
- Favorite anything you expect to reference again. The favorites filter turns a long archive into a short, curated shortlist instantly, which is faster than re-searching the same term every time.
- Check the stats scorecard before assuming you need to generate something new. A quick glance at "most-used formats" sometimes reveals you already made something close to what you're about to generate again.
- Sort oldest-first when you're archaeology-hunting for something from early in the year. Newest-first is the useful default day to day, but it works against you when the item you want is genuinely old.
- Turn a favorite into a Recipe once, instead of re-searching for it every term. If you keep finding yourself re-locating the same kind of generation in History, that's the signal to save its setup as a Recipe instead.
- Delete deliberately, not defensively. Since there's no retention cap forcing cleanup, there's no need to delete old material just to keep the list tidy — do it only when you actually want the item, and its linked student data, gone for good.
What to Avoid
- Don't expect a "regenerate" or "remix" button on a past item. It doesn't exist anywhere in Content History by design — reach for Recipes if you want a reusable starting point instead.
- Don't assume search reaches your very first generation ever, on a multi-year account. It's a bounded recent-document scan, not a full-text index of your entire lifetime archive.
- Don't treat delete as reversible. There's no undo, and it also removes any linked assessment-attempt data — confirm you actually want the item gone before you click it.
- Don't confuse History with Insights when you want trend data. History tells you what you made and where it is; for Bloom's-level trends and performance aggregated over time, that's Insights.
- Don't assume older history is hidden behind a paid plan. It isn't — retention and visibility aren't plan-gated, so there's no upgrade needed just to see further back.
- Don't rely on memory alone once your archive gets large. The research on personal file organization is consistent on this point: recognition-based browsing works well for recent material and breaks down for older material, which is exactly when the search and filter controls earn their keep.
Key Takeaways
- Content History is a real archive, not a decorative feed: text search, a format filter, a favorites toggle and filter, newest/oldest sort, grid/list view, pagination, and a stats scorecard are all genuine, working controls.
- It's distinct from Recipes and Assign by design: Recipes saves reusable generation presets, Assign turns one generation into a tracked assignment, and History exists purely to help you find and organize what you've already made.
- Search is real but bounded: a substring match over your most recent roughly 200 to 500 entries, not an unlimited full-text index of your entire history.
- The honest limitation is real and deliberate: there's no regenerate, clone, or remix action on a past item anywhere — that job belongs to Recipes.
- You can view, export, share, delete, or assign a past generation directly from its History entry.
- Nothing is auto-deleted and nothing is plan-gated: entries persist indefinitely until you delete them yourself, and deletion cascades to remove linked assessment-attempt data.
- The stats scorecard gives you four real numbers — total materials, total questions, most-used formats, favorite count — computed from your actual archive, not a sample or an estimate.
Frequently Asked Questions
Can I search my entire generation history, no matter how old?
Not with unlimited reach. Search is a real substring match against real stored data, but it scans a bounded window of your most recent entries — roughly up to 500 when actively searching — rather than indexing your entire lifetime archive. For a single school year's worth of material, that window covers effectively everything.
Is Content History the same thing as Recipes?
No. Recipes are saved generation presets you can run again for a new topic; Content History is the archive of everything you've already generated. They intentionally solve different problems — reuse versus retrieval — and neither replaces the other.
Can I turn an old generation into a new variant directly from History?
No. There's no regenerate, clone, or remix action in Content History — that's a deliberate boundary. If you want a reusable starting point, save the original setup as a Recipe instead.
Does deleting a past generation also delete student results tied to it?
Yes. Deleting an entry is permanent and also removes any linked assessment-attempt data, such as student responses tied to that specific quiz or worksheet, so nothing orphaned is left behind.
Is there a limit on how much history I can see based on my plan?
No. History retention and visibility aren't gated by subscription tier — a free-plan account and a paid-plan account both keep full, unrestricted access to everything they've generated.
Does anything in Content History get automatically deleted over time?
No. There's no time-based auto-deletion. Entries persist indefinitely unless you explicitly delete them.
What's the difference between Content History and the Insights dashboard?
Content History shows you what you've made and lets you find and manage it. Insights aggregates that same underlying activity into Bloom's-level mastery trends and assignment performance over time — one is about locating individual items, the other is about the pattern across all of them.
Can I favorite an item and still find it through the normal search and filters?
Yes. Favoriting doesn't remove an item from the regular list — it just adds a shortcut. You can filter to favorites only, or ignore the favorites filter entirely and keep searching and sorting the full archive as usual.
Do I need to organize or tag my generations manually for search to work?
No. Every generation is indexed automatically the moment it's created — its title, subject, topic, prompt, and class profile name are all searchable without you doing any manual tagging or filing. The controls exist specifically so upfront organization isn't a prerequisite for finding something later.