productivity

Loan Board

Manage short-term equipment checkout, returns, outstanding items, and history on one device.

Local processing
About your filesFiles and content selected in this tool are processed in your browser and are not uploaded to a Browser Kitty backend.
Operation demo See the basic workflow in a short video.

About this tool

Loan Board is for short-term lending at events, schools, shoots, stages, clubs, and internal activities where one device needs to answer: who has what, and what has not come back yet? Choose a borrower, check out several items together, and use the outstanding board to see the current state.

Returns can cover everything or only the items that came back. Checkout, Return, and Undo remain in history, while the current board is autosaved in the browser. JSON can back up and restore the full board state, and CSV exports are available for outstanding items, operation history, and equipment.

Good for

  • Manage radios, equipment, or supplies checked out and returned at an event or school desk
  • See who currently has each item and focus on equipment that has not yet been returned
  • Keep a checkout history and review or analyze it later in CSV

What it can do

Key capabilities available in this tool.

How to use

  1. Give the board an event or operation name.
  2. Register equipment under Manage. Use numbered batch creation for sets of similar items.
  3. Register borrowers in advance or add a new borrower during checkout.
  4. In Checkout, choose a borrower and one or more available items, then confirm the checkout.
  5. Use the outstanding board to see who currently has each item.
  6. On return, choose Return all or return only the items that came back.
  7. Finish by confirming zero outstanding items and save a JSON backup or CSV when needed.

Supported

  • Checkout: select a borrower and multiple currently available items in one operation.
  • Returns: support full and partial returns and update the current loan state.
  • Equipment: register items individually, create numbered batches, use item codes, and archive retired equipment.
  • Storage: autosave in the browser and back up / restore board, equipment, borrowers, loan state, and history as JSON.
  • Exports: save outstanding items, operation history, and equipment lists as UTF-8 BOM CSV files.
  • Environment: Japanese / English and desktop / mobile; current Chromium-based browsers, Firefox, and Safari are the documented targets.

Limitations and notes

  • It does not synchronize across devices; v1.0.0 primarily targets short-term lending managed on one device.
  • Reservations, due dates, extensions, and notifications are not supported.
  • It is not a commercial rental system for billing or payments.
  • QR-code and barcode scanning are not supported.
  • Autosave depends on browser storage and can become unavailable after clearing site data or under private-browsing restrictions.
  • CSV is for review and analysis and cannot restore the complete Loan Board state.
  • Use JSON backups for important operations.

Frequently asked questions

Can I check out multiple items at once?

Yes. Choose a borrower, select multiple available items, and record them in one checkout operation.

Can I record only some items being returned?

Yes. Partial return lets you select only the items that came back while the rest remain outstanding.

Does the checkout state survive a page reload?

Yes when browser storage is available and the saved data remains valid. Keep JSON backups for important operations.

Can CSV restore the complete board?

No. CSV is for review and analysis. Use the JSON backup to restore the complete board, including equipment, borrowers, loan state, and history.

Is checkout data sent to a server?

No. The hosted page must first deliver the HTML, but equipment, borrowers, loan state, history, and other user data are processed in the app and are not sent by the app to an external server.

Offline version and source code

loan-board.html is a single HTML file containing the UI, JavaScript, CSS, and SVG icon assets. It can be opened directly in a supported browser, and its runtime CSP uses connect-src 'none'. Browser storage behavior for file:// pages can vary, so keep JSON backups for important operations.

View source on GitHub