How a publishing schedule becomes sustainable
Freelance Traveller and Accessible Games show how publishing cadence depends on time, tools, contributors and the commitments already made to readers.
Jeff Zeitlin changed Freelance Traveller from monthly to bimonthly publication in 2016. In his retrospective on its hundredth issue, he describes needing more time between releases. He increased the issue size from twenty-eight pages to sixty. A slower rhythm allowed the publication to continue on terms he could manage. Zeitlin’s retrospective
The choice is more interesting than a general instruction to publish less. It rearranged the relationship between the editor’s time, the amount of material and the reader’s expectation. The magazine retained its ambition while changing the interval in which that ambition had to be realised.
This essay compares two publishers’ accounts of their own work. They explain particular decisions and constraints. They do not establish a sustainable schedule for every RPG zine, or a general income level for independent publishing.
An issue has work around its contents
The current magazine archive records the introductory issue in November 2009, monthly publication from January 2010 through December 2015, and bimonthly publication from January 2016. In October 2026 it presents the September/October issue, with PDF editions in US Letter and A4 and article access through the website.
Those publication routes involve more than gathering a sufficient number of words. A release must be assembled and identified. Contributors need communication. Files and links need checking. An issue page needs contents that correspond to the issue it describes. Each additional route can help readers while adding work to the release.
A publisher can therefore be constrained by the frequency of handoffs even when enough material is available. An editor who has contributors’ drafts still needs time to read them and return questions. Reducing the number of deadlines may change that pattern more than simply reducing a page count would.
Zeitlin’s account gives evidence for his own decision. I would resist turning it into a formula. Another publication might depend on short, frequent releases, or on a contributor cycle that makes larger issues harder to complete. Sustainability has to be described against the actual work and the people doing it.
The publishing tools also consume time
In his September 2026 account of rebuilding the Accessible Games website, Jacob Wood describes moving to static HTML after difficulties with WordPress maintenance and his changing use of assistive technology. He also reports publishing Accessible Gaming Quarterly issue 14, hopes for issue 15 by the end of the year, and identifies two issues still owed to Year 4 campaign backers.
Those statements have different evidential weights. A published issue, an intended release and an outstanding commitment describe three states of work. Wood’s account is valuable because it identifies them separately. A library should preserve those distinctions when recording the serial or discussing a future partnership.
Susan Leigh Star and Karen Ruhleder’s analysis of infrastructure attends to the relationship between technical arrangements and organised practice. In this setting, the publishing system includes the editor’s means of accessing and maintaining it. A website that readers can browse may still impose difficult work on the person responsible for updating it.
That observation changes what I would count as publishing capacity. It includes the ability to use the tools, communicate with contributors and maintain the routes by which readers receive the work. Counting available manuscripts alone misses much of the task.
A serial record can acknowledge change
The word quarterly in a title can outlive a regular quarterly schedule. A dated issue proves its own existence. It does not prove that three others appeared in the same year. A library’s holdings description needs the issues actually received and a current account of frequency where that information is available.
For a reader trying to complete a run, an unexplained gap can mean several things. An issue may be missing from the library, delayed, combined with another number or never published. Those possibilities need investigation before a request is sent to a small publisher as though a shipment has certainly been lost.
I would make a serials enquiry specific. Identify the issue number and date, say what the library holds, and ask about the uncertain item. A precise question reduces the research the publisher must do merely to understand the request. If the answer changes the expected sequence, preserve the explanation where receiving staff will find it next time.
An academic collection studying the publication can retain evidence of changed schedules as part of its history. A public collection serving players may emphasise which usable issues are available now. Both benefit from avoiding an invented regularity that the publication’s own record does not support.
Partnerships should name the extra work
A library can buy a zine, invite an editor to speak, commission a workshop or offer practical production support. Those are distinct relationships. A purchase does not quietly include an event, and an event invitation should not assume that the creator can supply free teaching materials in addition to preparing and delivering the session.
For a proposed partnership, I would agree on a bounded contribution and the resources attached to it. A workshop might need an accessible room, printing, a second facilitator and time to adapt an exercise for the audience. Naming that work makes it possible to decide whether the invitation fits the creator’s current capacity.
The same discipline applies to institutional enthusiasm. A successful first event can generate requests for a recurring series. Before announcing the next six dates, the library and creator need to decide whether repetition changes preparation, compensation or responsibility for administration. The fact that one session worked does not settle those questions.
A sustainable schedule is an agreement between ambition and available work, revised when circumstances change. The useful evidence is concrete: what has appeared, what remains promised, how production operates and what the people involved can undertake next. A library can support that continuity by making its own commitments equally clear.
