A Publisher's Deposit Tracker: Does “Sent to the Library” Mean the Obligation Is Closed?

For a small publisher, printing a book and recording a sale are not the same as completing a legal-deposit workflow. If you need software to follow that work, distinguish the exact publication, the destination responsibility, the physical dispatch and whatever acknowledgement is actually available. A missing catalogue entry must not automatically trigger another parcel, and a printed postage label must not automatically close the task.

This guide uses the British Library's service information checked on 26 October 2026. It is a brief for a publisher's internal workflow, not a full interpretation of deposit law. Confirm your publication's scope, applicable deadlines and any electronic-deposit arrangements directly with the relevant institutions or advisers. The example does not establish rules for publishers in other countries.

Start with the publication, not the sales order

Decide how staff identify the work and the particular edition or issue being handled. Retain its actual publication information and the basis for including it in the deposit worklist. A sale to a bookshop is a customer transaction; a deposit copy needs its own purpose and destination record even if the same warehouse prepares both parcels.

Use a hypothetical publisher with a new title and a subsequent changed edition. The responsible person should review which deposit action belongs to each. The app should not infer the legal answer merely from a changed stock code or a fresh printing job. Equally, one title-level checkbox must not hide several separately reviewed publication records.

Ask for an explicit owner who confirms inclusion, the required action and the source of the instruction. Keep uncertain scope visible for review rather than silently excluding it from the list.

Keep the British Library and agency work distinct

The British Library's legal-deposit service page asks publishers to continue submitting print publications despite service disruption. It specifically says not to wait for a claims letter and distinguishes its claims from those of the Agency for the Legal Deposit Libraries. The page explains that the agency acts for the other five deposit libraries.

That distinction matters to your data model. A communication from the agency should not casually close a separate British Library task. Record the institution or represented institutions, instruction or request, relevant publication and agreed next action. Have the responsible person confirm the actual destination and quantity rather than embedding an assumed universal parcel rule.

For a journal or other continuing publication, agree how an instruction relates to later issues. Do not create unrelated duplicate requests merely because correspondence repeats the title. Conversely, do not let a previous issue's dispatch stand in for a newly reviewed issue.

Plan for an acknowledgement that is not currently available

At the check date, the British Library page said received print publications were being recorded and stored securely, but it was not yet able to offer receipts or show catalogue updates during recovery. This is a dated service observation, not a prediction about when those facilities will return.

A tracker that requires a receipt before staff can explain the state of a parcel will misrepresent that situation. Preserve preparation, actual dispatch evidence, any carrier delivery evidence, correspondence and the institution's published acknowledgement limitation as different records. None should be renamed “library receipt” when no such receipt exists.

Also separate “awaiting acknowledgement” from “known failed delivery.” An absent catalogue record under the described disruption does not establish that a copy was lost. If delivery is uncertain, give a person a reconciliation task before preparing a replacement. Avoid an automatic resend loop that produces duplicates without resolving what happened to the first copy.

Do not silently switch the deposit medium

The same service page describes disruption to electronic submission routes and gives route-specific instructions. A downloadable PDF on the publisher's website is therefore not evidence that an institution accepted an electronic deposit. Nor does a software upload button establish that a receiving service currently works.

For a print-deposit tracker, keep electronic arrangements outside automatic completion unless the relevant institution has confirmed the route and your process has evidence of its use. Store reviewed instructions with an access date. Recheck operational destinations and methods before acting; do not build a permanent integration around a temporary recovery notice.

Demonstrate the unresolved case before buying software

Test a fictional title with a British Library task, separate agency correspondence, an actual dispatch and no library receipt. Add a changed edition and a parcel with uncertain delivery. Staff should see what was sent, which responsibility remains open and who must investigate, without fabricating acknowledgement or sending duplicate copies automatically.

Bring this example to a publishing workflow discussion. The acceptance criteria should test the publication-specific destination record and uncertainty handling, not just whether an email reminder arrives. The useful result is an explainable deposit worklist. It is not a certificate that every legal obligation has been satisfied or that a deposited publication is already discoverable in a public catalogue.