Client intake form template (free)
A free client intake form for freelancers and agencies. Ask about scope, budget, timeline and past experience before the first call.
11 questions on one page
Bug report form template (free)
Good bug reports save hours. This bug report form template asks people for a short summary, a severity level, the steps to reproduce it and what they expected to see. They can paste a link to the page where it broke and attach screenshots, recordings or logs. Two hidden fields, app_version and browser, arrive from the link your app opens, so reporters never type them and you never have to ask. The form fits on one page and takes about two minutes. Sign up for free, open the template and change the severity levels to match your own triage words.
Free plan, free forever. Sign up and the template opens in your workspace.
What's in this form
6 questions on one page. Every question, in order:
Page 1: Report a bug
| No. | Question | Answer type | Required? |
|---|---|---|---|
| 1 | SummaryShort answer, Required | Short answer | Required |
| 2 | SeverityDropdown, RequiredChoices: Low, Medium, High, Critical | Dropdown | Required |
| 3 | Steps to reproduceLong answer, Required | Long answer | Required |
| 4 | Expected vs actual resultLong answer, Optional | Long answer | Optional |
| 5 | Where did it happen?Link, Optional | Link | Optional |
| 6 | AttachmentsFile upload, OptionalScreenshots, recordings or logs. | File upload | Optional |
What people see after sending
Thanks for the report!
We'll investigate and follow up if we need more details.
Built in
- File upload
- Hidden fields
Hidden fields it reads from the link: app_version, browser
Who it's for
- Small software teams that get bug reports by email and chat
- Support staff who pass problems on to developers
- Indie makers who want reports with steps and a screenshot
- Beta testers and community members who help test a release
When to use it
- Adding a "Report a bug" link inside your app or help center
- Replacing a vague "it's broken" email with a form that asks the right things
- Collecting screenshots and logs without a long back and forth
- Sorting reports by severity before the next release
Make it yours
- Build the link from your app. Open the form with ?app_version=2.4.1 and &browser=Safari filled in by your code, and every report carries that context. Your code can read both values before it opens the link.
- Rename the four severity levels to your own words. Teams that triage as P1 to P4 can use those labels, and the dropdown keeps everyone consistent.
- Keep the file question on. A file upload takes up to 10 files, and the Free plan allows 10 MB per file, which fits screenshots and short recordings.
- Send each new report to Slack, free on every plan, so developers see it while the memory is fresh. Hidden fields show up beside the answers.
- Connect Google Sheets, free on every plan, and filter by the severity column to build a bug list for the next sprint.
Where the answers go
Every response lands in your HornetForms inbox. From there, send it wherever your team already works.
- Turn on an email to yourself for each new response, on every plan
- A confirmation email to the person who filled it in, when the form asks for their email
- A new row in Google Sheets, a message in Slack or Discord, or a page in Notion, free on every plan
- Connect with Zapier, or send signed webhooks to n8n, Make or your own app
- CSV export on every plan, and Excel export on Pro and Business
Questions people ask
What are the app_version and browser fields?
They are hidden fields. The link carries their values, so the reporter sees nothing extra and you still get both in every response. They help you match a bug to a release and a browser without writing back to ask.
Can reporters attach screenshots and recordings?
Yes. The attachments question accepts up to 10 files, and you can limit the allowed file types. Its description tells people they can add screenshots, recordings or logs, so most reports arrive with proof.
Which questions does a reporter have to answer?
Three: a summary, a severity and the steps to reproduce. The expected and actual result, the page link and the attachments stay optional, so a quick report still gets through without blocking busy people.
Can I use this for feature ideas too?
This form is built for faults. A feature request has different questions, such as the problem and the benefit, so keep a separate form for ideas and link to both from your help page.
Related templates
Waitlist form template (free)
A free waitlist form that records which link sent each sign-up and asks what people need, so your list is useful on launch day.
8 questions on one page
Further reading
A feature request form that shows who asked (free template)
A free feature request form template that asks for the problem, stamps each request with who asked, and sorts the pile in a free triage sheet.
Published9 min read- guides
- templates
Start from a template, finish with your form
Sign up for free, pick a template and change anything you like: questions, logic and design. The Free plan stays free forever, with unlimited responses.