About FormHoney
FormHoney exists because the form people fill in and the form an organisation actually uses are usually two different documents — and the gap between them is where the work goes.
The problem it was built for
Most organisations already have a form. It is a Word document, or a PDF, or a paper sheet that has been photocopied since 2011. It is laid out the way it is for good reasons: it matches a process, it fits an envelope, it puts the signature in the place people expect.
Putting that online normally means giving it up. Online form builders hand you a single column of fields and a result that looks nothing like the thing you started with — so the printed version and the digital version drift apart, and somebody ends up maintaining both. FormHoney starts from the page instead, so the document survives the move.
What it stands for
Answers belong to whoever asked the question
Every response is written to the database and stays there. Emailing a copy is something you can add, never something that replaces the record. Exports are open formats you can take elsewhere, because a platform that makes leaving difficult is relying on the wrong thing to keep you.
Nothing important should depend on being remembered
A form that closes on a date closes on that date. A question that should not have been answered is discarded on the server as well as hidden in the browser. A response is never deleted because a subscription lapsed. The platform is meant to hold up on the days nobody is watching it.
Accessible by default, not by request
Labels are bound to the fields they describe, errors are announced with the field they belong to, and every check a person has to pass works with a keyboard. Where a visual check is unavoidable there is a written alternative beside it. None of that is a setting to find — it is how the pages are built.
Plain language, everywhere
Error messages say what to do next. Dialogues say what will happen. Nobody filling in a form should have to interpret the software, and nobody running one should have to guess what a setting does.
Who it is for
Teams whose forms have to look right and behave properly: community and outreach services, clinics and practices, schools and colleges, membership organisations, HR and onboarding, event registration, and the internal processes that have quietly outgrown a spreadsheet.
It suits people who care what the finished document looks like — because it will be printed, filed, or handed to someone — as much as they care about the data underneath.
How it is built
FormHoney is a small, self-contained PHP and MySQL application with no third-party runtime dependencies: the emails, the spreadsheets and the documents it produces are all generated directly. That is a deliberate choice about longevity. Fewer moving parts means fewer things that stop working when something upstream changes, and an installation that can be understood in full by the person responsible for it.
Looking for something more specific?
How it works walks through designing, sharing and collecting, step by step. Pricing covers the plans and what is included in each.