0 views
Auto-Archiving Drafts: Keeping Your Project Clean Without Manual Cleanup
How Telematic automatically archives forgotten content drafts without turning the project into an eternal dump of cards, and when data is permanently deleted.
How Telematic automatically archives forgotten content drafts without turning the project into an eternal dump of cards, and when data is permanently deleted.
Open almost any project where content is automatically gathered from multiple sources for months, and you will almost certainly see dozens, if not hundreds, of cards that have been neglected. Some of them are materials that became irrelevant at the time of collection. Others are drafts that someone started to revise, got distracted, and forgot about. Over time, these cards accumulate to outnumber the ones that are actually needed, and finding among them what is truly waiting for publication becomes a separate task.
The problem seems organizational at first glance — "just tidy up manually." But with automatic content collection, the volume of drafts grows faster than a person physically has time to sort through them, especially if there are multiple sources providing material daily. We built into Telematic a logic that addresses this problem at the system level, rather than relying on user discipline.
Let’s break down how the content lifecycle works and why auto-archiving is not about "deleting the unnecessary," but about keeping the project a working tool rather than a dump.
Each material in the system goes through clear stages, and at each stage, it has a different status:
The key idea is that this downward movement through the chain happens automatically over time if a person has not made a decision earlier. A draft that no one has touched for long enough automatically shifts to rejected, and then to archived. The system does not wait indefinitely for someone to eventually return and sort through the accumulated content.
The most tempting and most incorrect solution is to delete old drafts entirely as soon as they become outdated. The problem is that the decision "this material is not needed" is often made too hastily by automation and requires the right to be reconsidered by a person. Perhaps the draft just arrived at an unfortunate moment — for example, during the vacation of the person responsible for the content, or during a period when the team was focused on another topic — while the material itself was quite usable.
Therefore, in Telematic, files are deleted only at the very last stage of the lifecycle, not immediately upon archiving. While the material is in the status of draft, rejected, or even archived, it can be revisited, the script can be regenerated, reprocessed, and still brought to publication. Archiving is not a death sentence, but a way to remove material from immediate view in the main working list while preserving the option to reconsider it.
From an interface perspective, the effect is simple: the content list in the project remains a manageable size, rather than growing linearly with each source collection run. Materials that have been neglected for long enough automatically leave the main field of view, and you primarily see what is truly fresh and requires a decision now.
This is especially noticeable in projects with multiple active sources: an RSS feed, a couple of specific websites, and periodic transcriptions of others' YouTube videos together easily bring in several materials a day. Without automatic archiving, after a month or two, the list of drafts would have accumulated so many cards that new, truly important material would simply get lost among the old.
When we tested the project with multiple sources ourselves, literally within three weeks without a single manual review, so many drafts accumulated that opening the content list became unpleasant — we had to scroll and scroll to find what we actually wanted to process today. Some of these cards were frankly irrelevant: news from a week ago, duplicate topics, materials that had lost their meaning over time.
After enabling automatic archiving, the situation corrected itself without a single manual action on our part: old untouched drafts gradually left the main list, and new materials became visible immediately. At the same time, no file physically disappeared — if we needed to return to an archived card from a month ago, it would be possible because deletion occurs only at the very last stage of the cycle, not at the time of archiving.
Auto-archiving does not require daily attention, but it is worth considering how it aligns with your team's rhythm. If content is usually reviewed once a week, rather than every day, it is important to keep this in mind when assessing how many drafts actually accumulate between reviews — the mechanism is designed specifically for "forgotten" cards, not for a normal working rhythm with weekly checks.
A useful habit is to periodically check the archive section, not just the main draft list. There may be material that was unjustly set aside at the time — for example, a topic that has become relevant again after months. Since files at this stage are not yet deleted, regeneration and reprocessing remain available just like for a fresh draft.
Ultimately, the goal of auto-archiving is not to get rid of content but to separate two tasks: "what needs to be resolved right now" and "what can be safely stored in case it is needed later." The system takes on the routine sorting over time, while the final decision about data deletion remains at the last stage of the cycle, allowing always enough time to reconsider.
Source Site Blocks Collection: What Telematic Does
Platform Unavailable During Publication: What the System Does