From book cart to board packet, without the paper chase
shelfpost.hub.elitecoders.ai
A planned workflow for Texas school librarians managing SB 13 purchase lists. Bring proposed titles, posting dates, public comments and board decisions into one place. In development, with early access shaped by librarians.
Free. You get one email when the first version is ready.
You are on the list. Thank you!
That email address did not look right. Please check it and try again.
Winter book lists Sample data
Planned list dashboard · Fictional sample
| List | Titles | Posted | Comments | Status |
|---|---|---|---|---|
| Winter A | 24 | Nov 16 | 4 | Posted |
| Winter B | 32 | Nov 20 | 3 | Posted |
| Donations | 18 | Oct 15 | 0 | For board |
| Spring A | 22 | Not yet | 0 | Draft |
A book order now has a paperwork trail.
Librarians in the Texas Library Association's SB 13 Q&A asked how small teams could handle the added steps. ShelfPost is being planned around that administrative work.
Keep the book cart. Connect the paperwork.
A stack of proposed books can turn into a cart export, a public list and a meeting packet. ShelfPost would carry the same title records through those steps, while your district keeps control of its policy and decisions.
One list, from proposal to recorded decision
An illustrative winter purchase cycle. Dates are sample planning targets; your district confirms its own process and board schedule.
- Nov 13
Import the cart
Upload the vendor CSV and compare ISBNs with your catalog export. Review suggested matches before deciding what needs posting.
- Nov 16
Publish the list
Share a public page with the proposed titles, posting date and comment form. Keep feedback attached to the list.
- Dec 17
Prepare the packet
Bring the list, posting history, comment summary and review notes into a PDF for the board. Record its decision after the meeting.
- Dec 18
Track the next step
Mark approved titles as ordered, then cataloged when they arrive. Keep tabled titles separate and preserve the decision history.
What the first version will do
- Catalog and vendor-cart CSV imports with ISBN normalization and reviewable match reasons
- District-branded public purchase lists with posting dates and a comment form
- A comment inbox and library advisory council notes tied to titles and lists
- Board packet PDFs with list details, posting history and comment summaries
- Recorded board outcomes, followed by ordered and cataloged status tracking
- An exportable history, role-based access and a dashboard of upcoming list dates
What it will not do
- Judge or rate book content, or use AI to decide which titles belong in a library.
- Guarantee legal compliance or replace your district's policy, legal review or board decisions.
- Replace Destiny or another catalog, write back to it, or place purchase orders.
- Collect student records. Removal and challenge workflows are planned for the larger tier.
Become a founding member
Pay $79 now. It becomes your first month of ShelfPost District, and $79 a month stays your founder price for life. Fully refundable on request at any time before launch.
One payment, becomes your first month
- Founder price of $79 a month, locked for life
- District plan: up to 5 campuses, unlimited lists and titles, public posting, comments and board packet PDFs
- Fully refundable on request any time before launch
Thank you for preordering! Check your inbox for the receipt.
Who is building this
I'm Emad, a software developer who builds small tools for niche businesses. Reading librarians' questions about small teams, ISBN checks and public feedback made me want to test a focused workflow tool. I am validating ShelfPost before building it, and I have not worked as a school librarian. If you handle library purchases for a Texas district, join the early-access list and help shape the workflow. Your district's policy and purchasing process come first.