The question a work-first view can’t answer
In the standard workflow of a pottery studio, most records are naturally “work-centric.” A potter starts with a lump of clay, gives it a title, and tracks its progress through various stages of production. When looking back at a finished piece, a well-maintained log can easily answer the question, “What glazes did I use on this specific bowl?”. This forward-looking view is essential for documenting individual artistic achievements.
However, a significant problem arises when a potter needs to ask the reverse question: “Which pieces have I ever used this specific glaze on?”. Over years of practice, a single glaze might be applied to dozens or even hundreds of works across various clay bodies and firing conditions. Without a dedicated system, answering this question becomes an administrative nightmare.
In a paper-based notebook or a simple digital list, finding every mention of a specific glaze requires scrolling through every entry one by one. This becomes increasingly difficult as the archive grows, often leading to a situation where the long-term “track record” of a material is lost. The inability to perform a reverse lookup means that the valuable data generated by every firing—such as how a specific glaze behaves on porcelain versus stoneware—remains scattered and unusable for broader studio analysis.
A manual version of the same idea
You don’t need a database to get most of the benefit here — you need to stop relying on search-by-scrolling and start capturing the reverse link as you go. If you keep a glaze notebook, leave a few blank lines or a small table under each glaze’s entry, and jot down the piece it was used on every time you reach for that jar: a date, a short description, and the result. Over a year or two, that running list becomes exactly the “everywhere I’ve used this glaze” record a database would give you automatically, just built up one line at a time instead of computed after the fact. The same works in a spreadsheet: one tab per glaze, one row per use.
How usage history works
The way to solve this is through relational data design. In a properly structured system, a glaze is not just a line of text typed into a work record; it is a unique entity in a shared Glaze Master library, and each time a potter logs a firing process, they select the appropriate glazes from that master list rather than retyping the details.
Because the system uses these consistent references, it can perform what we call a “reverse lookup”. The usage history is not a separate feature that must be manually updated; rather, it is a natural consequence of how the data is linked. When you view a specific glaze record, the system scans all firing-process logs across your entire history and instantly identifies every instance where that glaze was selected.
This architecture ensures that every piece of data serves multiple purposes. A single log entry not only documents the history of a specific work but also contributes to the cumulative knowledge base of the materials used. By organizing information relationally, the system provides a comprehensive view of a glaze’s performance without requiring any additional data entry from the potter beyond the standard firing log.
What the usage history view shows
The usage history view is a specialized list accessible directly from the glaze’s detail screen. Instead of showing you what a glaze is, this view shows you what the glaze has done. It provides a consolidated list of every work and every specific process entry—such as a glaze firing or a second firing—where that glaze was utilized.
For a potter, this view serves as a powerful analytical tool. By reviewing the usage history, you can see at a glance how a glaze interacted with different clay bodies or how its appearance shifted at different firing temperatures. You might notice that a particular green glaze consistently breaks beautifully over a specific dark stoneware but appears flat on a white porcelain body.
Having this information centralized allows for a high-level review of a glaze’s “track record”. Instead of cross-referencing a stack of individual work records or flipping through years of notebooks, you have a single screen that summarizes the material’s entire history in your studio. This makes it much easier to diagnose issues, plan new works, or refine your firing schedules based on historical performance data.
Why this matters most for frequently used glazes
The value of a usage history view compounds significantly for the “go-to” glazes in a studio. Most potters have a few signature materials—perhaps a reliable glossy clear or a specific celadon—that are in heavy rotation and are used across entire bodies of work.
When a glaze is used frequently, its usage history becomes a rich repository of studio knowledge. It captures the nuance of how that material performs across dozens of instances. For a signature glaze, this history helps ensure consistency across different production batches. For a utility glaze like a clear liner, the history can reveal subtle trends in crazing or fit issues that might not be apparent when looking at a single piece.
Usage history essentially turns scattered individual successes and failures into a single, reviewable track record for that specific material. This allows the potter to move from a state of “hoping for a good result” to a state of data-driven confidence. By understanding exactly where a glaze has been, you are much better equipped to decide where to use it next.
How KilnNote handles this
We designed KilnNote to automate the same running-list idea described above, rather than asking you to maintain it by hand. Within the app, the glaze detail screen includes a dedicated Usage History section that automatically populates as you log your work. This feature is included in the free tier of the app, alongside the core Glaze Master and firing log functions.
When you select a glaze from your library during a process log entry, KilnNote creates a link between that work and the glaze record. Later, when you visit the glaze’s detail screen, the app displays every work and firing step that referenced that glaze. You can tap on any item in the usage history to jump directly back to the full work record or firing log for deeper investigation.
KilnNote is a local-first application, ensuring that your entire usage history and all associated photos remain private and stored directly on your device. We also provide free CSV, PDF, and ZIP export tools, so your studio’s cumulative material knowledge is never locked into a single platform and can be backed up at any time. By providing these relational views, KilnNote helps you transform a simple list of jars into a sophisticated, searchable library of studio experience.
You can start building your material usage history by downloading the app here: KilnNote on the App Store
Summary
The ability to look backward from a glaze to every work it has touched is a vital part of a professional studio practice. By utilizing a relational recording system that links process logs to a central glaze master, you gain a cumulative track record of how your materials perform over time. This reverse lookup capability ensures that the data from every firing is preserved and accessible, allowing you to reproduce your best results and refine your craft with confidence.
For a broader look at the benefits of a structured recording system for your entire studio, see our hub article: That Glaze Combo You Can’t Reproduce: A Recording System for Potters
To learn more about how to set up your library of materials to enable this kind of history tracking, see our guide: Beyond a Jar Label: Recording Your Glazes as Data
For kiln operation and firing conditions, please follow your equipment manufacturer’s specifications and safety instructions.
This article organizes information from a recording and organizing perspective. If you notice an error or outdated information, please contact us. Last verified: August 2026
