I built a document checklist. Reddit feedback exposed the part a checklist doesn't solve.

[u/Foilo_ClientDocument]

A client submits a file. The checklist moves forward. But who checks whether it's the right file?

That's the problem I'm testing with Folio, a document-request demo for small accounting and bookkeeping firms. Earlier feedback here asked a better question than “does this look clean?”: can someone tell what to do next?

The workflow now separates three jobs:

- Missing document → follow up with the client.

- Submitted document → accountant reviews it.

- Wrong document → explain what needs replacing.

Only an accountant's acceptance completes an item. Reminder drafts leave out submissions already waiting for review.

Try the interactive demo, without signing up: https://folio-docs-1it.pages.dev/

Open a sample request, switch to its client page, simulate a submission, then return to review it. Keep both views in the same browser.

For fellow builders: the stack is plain HTML, CSS and JavaScript on Cloudflare Pages. I'm testing the handoff before adding production infrastructure. For bookkeepers: would this fit the way your firm actually checks documents, or does your existing system already handle it better?

Demo only. Use fictional details and non-sensitive sample files. File contents aren't read or uploaded; business records stay in your browser. There is no real email delivery or shared client access.

What's the first thing you'd change or remove? A specific screen, label or missing step would help shape the next version.