Plans and roadmap / Business

Idea

Duesbook

Members, dues and volunteer hours for a small club, kept on the treasurer's phone.

This is a plan, not a promise. It can change, and no release date is promised. The screens below are drawings made from the plan, not screenshots of a finished app.

Why this app

Small clubs often keep dues in a spreadsheet that only the treasurer understands, or use a team app that shows ads or charges per season. Duesbook is planned as a plain notebook for one treasurer: who paid, what came in and went out, and who gave how many volunteer hours. It does not take payments and does not need the members to install anything.

How it might look

Grid layout. Navigation: a side drawer lists Members, Dues, Cash book, Hours and Reports. Type: serif for headings, standard font for text, serif for numbers. Corners 10 points, compact spacing, label cards.

Accent #797839Accent, dark mode #ADAB48Background #F6F3EABackground, dark mode #1C1B16

Icon idea: a membership pin with one ledger line through its middle

Dues gridPaid months are filled, open months are outlined, the total sits at the row end.
Cash bookEvery line has a date and a text, and the balance runs underneath.
Volunteer hoursHours by person, with a signed sheet each can take along.
Dark member cardOne member at night: fee level, dues state and hours.

Features

Solid marks are planned for version 1. Hollow marks come later, if at all.

Members

  • Member list with join date, fee level and contact note
  • Dues grid: members down, months across, paid or open
  • Different fee levels such as adult, junior, family
  • Import the member list from a CSV file

Cash book

  • Money in and out with date, text and category
  • Running balance
  • Receipt per payment as PDF
  • Year summary by category
  • Photo of a paper receipt

Volunteer hours

  • Hours per member and task
  • Signed sheet as PDF for the member
  • Yearly total per member

Safety

  • Backup and restore as one file
  • Export all books as CSV
  • Several officers editing at once would need a server, so it is not planned for v1

What we leave out

Plan and honest status

Specin progressThis page is the first draft. Nothing is built yet.
Enginenot startedPlanned as plain logic with an independent check script.
Screensnot startedOnly the mockups on this page exist.
Testsnot startedNothing to test yet.
Storenot startedNot submitted. The order of releases is decided by the owner.

The same plan is the basis for the code. If the code and this page disagree, the page is wrong and gets fixed.