The problem with manually maintained status fields
When we looked at the core fields of a work record, we mentioned in passing that a piece’s status shouldn’t be something a potter sets by hand — it should be something the system infers from the firing history. That point deserves a closer look, because the alternative it’s rejecting — a manually maintained status field — is one of the most common points of failure in studio management and record-keeping. It produces what we’d call a “stale record”: a digital entry that quietly stops matching the physical piece sitting on the shelf.
In many general-purpose tracking tools or basic spreadsheets, a work’s status—whether it is “In Progress,” “Completed,” or “Failed”—is a dropdown menu or a checkbox that someone has to remember to update. That sounds manageable in theory, but it adds friction at exactly the wrong moment: when a potter is unloading a kiln full of pieces, their attention is on the physical handling of the work, not on opening an app to update a ledger.
If a potter forgets to update the status for just one or two pieces, the entire record begins to drift out of sync. Within a few weeks, the “In Progress” list — on paper, in a spreadsheet, or in an app — is cluttered with items that were actually finished or discarded long ago. This drift makes the record unreliable; you can no longer trust it to give an accurate bird’s-eye view of the studio. The fix isn’t a better habit of remembering to update a label — it’s removing the label as a thing you maintain in the first place.
A tool-agnostic fix: derive status, don’t maintain it
The underlying technique works in any recording system, including a plain spreadsheet: instead of keeping a separate “status” column that you update by hand, add a column that simply shows the date and result of the most recently logged firing for that piece. When you look at the sheet, you’re reading the actual last event, not a label someone may have forgotten to change. If a row’s last-firing column says “Success, 3/14,” that piece is done and successful — no separate field to fall out of date. The same idea works in a paper log: instead of a status box at the top of a piece’s page, glance at the last dated entry underneath it.
This works because the “status” was never really independent information — it’s just a summary of the most recent firing result. Once you stop treating it as something to set and start treating it as something you read off the log, it can’t drift out of sync, because there’s nothing separate left to forget to update.
How the status is actually calculated
The most reliable way to determine where a piece stands is to look at its most recent interaction with the kiln. In a structured management system, the status is a derived value rather than a static piece of data. It is calculated automatically by looking at the work’s firing history and identifying the latest entry based on the firing date.
Every time a user adds a new firing process log—such as a bisque fire, a glaze application, or a final glaze firing—they record a result for that specific step. The system then performs a background synchronization. It identifies the firing log with the most recent date and pulls the result from that entry to serve as the overall status for the work. If a piece is newly registered and has no process logs attached to it yet, the system defaults the status to “Not Started.”
By ordering the calculation by the firing date rather than the date the entry was created, the system ensures that the status remains accurate even if a potter records their logs out of order or catches up on several days of record-keeping at once. The status becomes a reactive reflection of the piece’s journey through the studio.
Four possible states
By automating the status based on firing results, we can classify every piece in the studio into four distinct, unambiguous categories. This allows for a clean, data-driven organization of the entire inventory.
| Status | What it means |
|---|---|
| Not started | The work has been registered in the system, but no firing process logs have been created for it yet. |
| Success | The result of the most recent firing process log entry was marked as a success. |
| Fail | The result of the most recent firing process log entry was marked as a failure. |
| Needs review | The result of the most recent firing process log entry was marked as needs review (e.g., for a piece that may require a second glaze firing). |
This classification system removes the ambiguity of manual labels. Instead of a subjective “In Progress” tag, a piece is either waiting for its first fire (Not Started) or it has a definitive result from its last kiln cycle. This level of clarity is essential for managing a high volume of work across different stages of production.
Why this design choice makes sense for a multi-step process
Pottery is rarely a single-step endeavor. A piece typically undergoes a bisque firing, a glaze application, and at least one glaze firing. In more complex cases, a piece might be subjected to multiple glaze firings to achieve specific effects or to fix a surface defect identified in a previous cycle.
Because of this multi-step nature, a manual status field is particularly ill-suited for pottery. If a piece is marked as “Success” after a bisque fire, but then fails during the glaze fire, the user would have to remember to manually navigate back to the main work record to change the status. If they don’t, the piece remains incorrectly logged as a success.
A derived status model handles these transitions seamlessly. When the bisque firing is logged as a success, the work’s status reflects that success. As soon as a subsequent glaze firing is logged with a “Fail” or “Needs Review” result, the work’s status updates automatically to reflect the new reality.
This design choice reflects the “where things stand right now” philosophy. The potter does not need to reconcile a manual field against the last firing because the system treats the firing log as the single source of truth. It ensures that the piece’s history and its current status are always perfectly aligned, providing a reliable foundation for studio management.
How KilnNote handles this
We built KilnNote to automate the same derive-don’t-maintain principle described above, rather than asking you to keep a spreadsheet column updated by hand. This automatic status sync is a standard feature available to all users, ensuring that even at the free tier, your records remain accurate and low-maintenance.
In KilnNote, the status is prominently displayed as a color-coded chip on both the main works list and the individual work detail view. This allows you to scan your entire collection and instantly see which pieces are successful and which ones require further attention. When you add or edit a firing process log—selecting from results like Success, Failure, or Needs Review—the app immediately updates the parent work record in the background.
For users who upgrade to the Pro version, this automatic status becomes even more powerful through the Board view. The Board view is a Kanban-style interface that automatically groups all your works into vertical columns based on their current status. Instead of just seeing a list, you see a visual representation of your studio’s output: a column for your successes, a column for pieces needing review, and a column for those that haven’t started their firing journey. Because the status is synchronized automatically, pieces move between these columns on the board as you log your firing results, requiring zero manual dragging or sorting.
KilnNote is a local-first application designed to respect the potter’s workflow by prioritizing speed and data integrity. You can manage up to 5 works for free, which includes full access to the automatic status sync, firing logs, and the glaze master. For those who need to manage an unlimited number of works and access the Board view, we offer a Pro upgrade as a one-time purchase.
You can download KilnNote and see how automatic status can simplify your studio management here: KilnNote on the App Store
Summary
In a professional recording system, the status of a piece should be a reflection of its history, not a manual chore. By deriving the status from the most recent firing log, you ensure that your records are always accurate and reactive to the reality of the kiln. This automation reduces administrative friction and allows you to focus on the craft, knowing that your digital records will always keep pace with your physical work.
For a broader look at the information design required for a reproducible pottery practice, see our hub article: That Glaze Combo You Can’t Reproduce: A Recording System for Potters
To learn more about how to structure the firing logs that drive these status updates, see our guide on the firing process: What Actually Happened in the Kiln? A Firing Log System
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

