Bug Bounty Report Form
Structured vulnerability disclosure form for security researchers, covering severity, reproduction steps and impact.
Bug reports, feature requests and technical intake.
32 free templates — preview any of them without an account, then customise every question, colour and layout.
Showing 1–24 of 32 templates · sorted by best match
Structured vulnerability disclosure form for security researchers, covering severity, reproduction steps and impact.
Reason-driven cancellation flow with a save-offer branch and confirmation of the effective cancellation date.
Structured reporting for accessibility barriers, capturing page, assistive technology used, severity and reply preference.
A working example of branching: show, hide, require and page skip rules you can copy into your own form.
First report of a suspected data breach: what happened and when it was discovered, data and people affected, containment so far, and notification clocks.
Qualify and onboard free trial sign-ups with company size, use case and a scheduled onboarding call option.
Structured beta program application covering platform, availability, NDA acknowledgement and feedback channel.
Pre-launch signup for an AI product, capturing use case, current workflow and willingness to pay.
Card-style bug intake with steps, severity and environment details.
Capture feature requests with the problem, workaround and impact — not just the idea.
Structured post-incident review covering severity, timeline, impact, root cause, action items and customer comms.
Capture new project requests with the problem to solve, desired outcome, deadline, priority and budget status your team needs before it starts scoping.
Structured defect logging with steps to reproduce, environment and log attachments.
Recruit moderators who'll actually show up — experience, time zones, judgement calls and scenario answers.
Three-page request to change a live system: what changes and why, who is affected, timing, testing and rollback, communications and approval.
One-screen notice of planned downtime: which service, when it starts and ends, what people cannot do, who is affected and where to go with problems.
Request accounts for a new starter: who they are, start date, team and manager, what they need access to, equipment, and manager approval before setup.
Request a paid tool or seat: what the person needs to do, the tool and cost, who else would use it, data handled, and budget holder approval.
Procurement security review covering data handled, subprocessors, certifications, incident history and evidence upload.
Developer intake for sandbox credentials, scopes and expected call volume.
Learn why customers cancel — and offer a save path — in six honest questions.
Leaver access removal: who is leaving and when, what they had access to, equipment to recover, mailbox and file handover, and confirmation once done.
One-screen equipment request: what the person needs and why, where to deliver it, when it is needed, replacement or extra, and manager approval.
One-screen record of equipment coming back: who returned it, asset tags and items, condition, accessories, whether it was wiped and where it is stored.
Teams browsing this collection often start here too.