Clinical · free template

Records Release Form

Authorisation to release records to a named third party, covering the scope, the purpose, an expiry date, exclusions and the patient's signature.

A ready-to-use healthcare & clinical form for small teams who need a reliable intake process: 17 questions, 2 pages, 3 conditional rules.

Questions
17
Pages
2
Layouts
classic · card
Time to complete
5 min
Conditional rules
3
Preview it in the gallery

Searches this template answers

Also filed under

Live preview and test console

This is the real form. Answer it to test the flow — nothing is sent or stored.

Page 1 of 2Scope of release

What is being released, and to whom

Is anything excluded from the release?

This template runs as a straight sequence — no branching rules.

Compliance checklist

Ready to publish
  • Payment items priced — passingEvery payment question charges a real amount, so a submission always records a payment.
  • Conditional logic resolves — passingEvery rule points at a question or page that exists in this template.
  • Medical disclaimer present — passingThis form does not provide medical advice, diagnosis or treatment. Information you share here is not a substitute for care from a qualified clinician. In an emergency, contact your local emergency service immediately.
  • Question labels unique — passingLogic and exports address questions by label, so duplicates are ambiguous.

What happens after submit: nothing is stored in this preview. On your own copy, every response triggers an instant email notification and lands in your response dashboard, ready to export or forward.

Happy with it? Take a copy into your workspace — every question, rule and setting comes with it.

Who this template is for

Records Release Form is built for small teams who need a reliable intake process who need to collect the same complete information from everyone.

  • Small teams who need a reliable intake process working in healthcare & clinical.
  • Teams who need to collect the same complete information from everyone without writing code or paying for a custom build.
  • Anyone replacing chasing missing details over email with one structured record per enquiry.
  • Respondents are the people you send it to — the form asks them 17 questions across 2 screens.
  • Mobile-heavy audiences, thanks to the one-question-per-screen card layout.

Why this form is useful

It removes the cost of chasing missing details over email and turns each submission into a record your team can act on immediately.

  • 15 questions are required, so submissions arrive complete instead of needing a follow-up email.
  • It collects a verified email address so replies and confirmations land.
  • It records a signature you can keep as proof of agreement.
  • It pins the request to a specific date.
  • It allows multiple selections without free text.
  • Conditional logic hides 3 questions until they are relevant — shorter forms convert better than long ones.
  • Splitting the form across 2 pages keeps each screen short and shows respondents how much is left.
  • Every response is stored, searchable and exportable, so nothing depends on one person's inbox.

How to use this template

From copy to live form is a few minutes of work, and every step is reversible.

  1. 1Press “Use this template” — a fresh copy of Records Release Form lands in your workspace, ready to edit.
  2. 2Rename or delete any question, and change what is required. Nothing here is fixed.
  3. 3Open Notifications and add the email addresses that should be alerted on each submission; add an auto-reply to the respondent if the form collects an email address.
  4. 4Publish it, then either share the link directly or paste the embed snippet into your site — the embedded form resizes to fit and loads no marketing or advertising trackers.
  5. 5Watch responses land in Submissions, where you can filter, label and export them to CSV or PDF.

Logic and conditions blueprint

Exactly how this form behaves as it is answered — 3 conditional rules ship with it.

  • Features conditional validation: if “Who is signing this authorisation?” is A representative of the patient, “Authority the representative holds” becomes mandatory before the form can be sent.
  • Features conditional validation: if “Is anything excluded from the release?” is Yes, “What must not be released” becomes mandatory before the form can be sent.
  • Features conditional validation: if “How will the records be sent?” is Secure electronic transfer, “Recipient email address” becomes mandatory before the form can be sent.
  • All 3 rules are editable in the Logic tab, and the built-in checker warns about rules that contradict each other.

About this template

Releasing records to a third party is the disclosure most likely to go wrong, because the request usually arrives with a broad wording and a deadline. This form makes the patient's authorisation specific. It names the person or organisation receiving the records, the reason they need them, and the exact scope: which records, which date range, and whether anything is excluded. The exclusion field matters — patients frequently want a report released without particular episodes attached, and asking directly avoids either over-disclosure or a refusal. An expiry date is required, so an authorisation signed for one insurance claim cannot be reused eighteen months later. The delivery method is recorded, since a secure electronic transfer and a posted envelope carry different risks. The patient confirms that they understand what is being shared, that they can withdraw the authorisation before release, and signs with a date. Where a representative signs, the form asks what authority they hold. The result is a defensible record of exactly what was authorised, by whom, and for how long.

What this form asks

Every question is editable — rename it, make it optional, or delete it entirely.

Page 1 — Scope of release

  • Patient full namerequired
  • Date of birthrequired
  • Recipient name or organisationrequired
  • Purpose of the releaserequired
  • Which records may be released?required
  • From daterequired
  • To daterequired
  • Is anything excluded from the release?required
  • What must not be released

Page 2 — Authorisation

  • How will the records be sent?required
  • Recipient email addressrequired
  • This authorisation expires onrequired
  • Understandingrequired
  • Who is signing this authorisation?required
  • Authority the representative holds
  • Signaturerequired
  • Date signedrequired

17 questions in total.

Example of a completed records release authorisation

A sample authorisation showing how a patient allows specific records to be released to a named recipient.

Patient full name
Aisha Bello
Date of birth
04/07/1987
Recipient name or organisation
Example Insurance Services
Purpose of the release
Supporting a claim for time off work
Which records may be released?
Consultation notes
From date
01/01/2025
To date
01/03/2026
Is anything excluded from the release?
No
How will the records be sent?
Secure electronic transfer
This authorisation expires on
01/06/2026

Sample data — no real people, addresses or records are shown. This example makes no claim about legal effect.

How the form changes as it's filled in

This template ships with 3 conditional rules, grouped into 3 behaviours driven by 3 questions. Everything below is already set up — edit or delete any rule once the template is in your workspace.

Driven by “Who is signing this authorisation?

  • Makes answers required

    If “Who is signing this authorisation?” is A representative of the patient, “Authority the representative holds” becomes required before the form can be submitted.

Driven by “Is anything excluded from the release?

  • Makes answers required

    If “Is anything excluded from the release?” is Yes, “What must not be released” becomes required before the form can be submitted.

Driven by “How will the records be sent?

  • Makes answers required

    If “How will the records be sent?” is Secure electronic transfer, “Recipient email address” becomes required before the form can be submitted.

Set it up step by step

  1. 1

    Require an expiry date

    An open-ended authorisation will be used again for something the patient never had in mind; a date closes that off cleanly.

  2. 2

    Ask about exclusions out loud

    Patients rarely volunteer that one episode should stay out, and asking prevents both over-disclosure and a last-minute refusal.

  3. 3

    Verify the recipient, not just the request

    Check the receiving organisation and address before sending, especially where the request arrived by email.

  4. 4

    Log what was sent and when

    Record the exact scope released against the authorisation so a later query has one answer rather than two versions.

Mistakes to avoid

  • Accepting a broad "all records" authorisation that the patient did not read closely.
  • Releasing records after an authorisation has expired because nobody checked the date.
  • Sending records to an email address supplied in the request without verifying the recipient.

What it pairs with

Most teams don't run this form on its own. These are the forms and systems it sits next to.

What to do with the responses

Check the authorisation is in date and in scope, verify the recipient, release only what was authorised, and log the date, scope and route of the disclosure.

Works in both layouts

These pages cover the same subject ground as the records release form, matched on the words people actually search for.

Privacy & compliance

This form collects health information. Keep access limited to the people who need it, turn on encrypted answers for the clinical questions, and set a retention window so records don't sit in the dashboard forever.

Frequently asked questions

How does this differ from the Quick Records Request?

That form is a patient asking for their own copies. This one authorises disclosure to a third party, which needs scope, purpose, exclusions and an expiry date.

Can an insurer send us their own consent form?

They often will, and you may still prefer this one: the scope and exclusion questions are usually more specific than a standard industry wording.

What if the patient wants to withdraw authorisation?

Honour it up to the point of release and record the withdrawal against the original submission, so the file shows both the authorisation and its cancellation.

Is a witness signature needed?

That depends on the rules where you practise. Add a witness field if your framework or insurer expects one rather than assuming a signature alone suffices.

Is the Records Release Form template free to use?

Yes. You can preview and test Records Release Form on this page without an account, and take a copy into your own HelloForms workspace on the free plan. There is nothing to install and no card required to publish it.

What does the Records Release Form template ask for?

It asks 17 questions across 2 pages, 15 of which are required. Every question is listed in full further down this page, and each one can be renamed, reordered, made optional or deleted after you copy the template.

Can I edit the Records Release Form form after copying it?

Yes — the copy is entirely yours. Change wording, add or remove questions, switch between the classic and card layouts, restyle it to match your brand, and set who gets notified on each submission.

How does the conditional logic in this healthcare & clinical form work?

3 conditional rules ship with the template: Features conditional validation: if “Who is signing this authorisation?” is A representative of the patient, “Authority the representative holds” becomes mandatory before the form can be sent. Features conditional validation: if “Is anything excluded from the release?” is Yes, “What must not be released” becomes mandatory before the form can be sent. Features conditional validation: if “How will the records be sent?” is Secure electronic transfer, “Recipient email address” becomes mandatory before the form can be sent. All rules are editable in the Logic tab.

Where do responses to the Records Release Form form go?

Submissions land in your workspace under Submissions, where you can search, filter, label and export them to CSV or PDF. You can also email a notification to your team on every submission and send the respondent an auto-reply.

Can I embed the Records Release Form form on my own website?

Yes. Publish the form and paste the embed snippet into any page or share the direct link. The embedded form resizes to fit its container and loads no advertising or marketing trackers inside the iframe.

Is the signature on this form legally usable?

The template captures a drawn signature and stores it with the submission, along with the timestamp, so you keep evidence of who agreed and when. Whether that is sufficient depends on your jurisdiction and the agreement itself.

More forms teams pair with the records release form.

Related categories