Public · free template

Library Card Application

Apply for a public library card with proof-of-address details, card type and a borrowing agreement.

A ready-to-use government & public sector form for councils, agencies and public bodies: 13 questions, 3 pages, 3 conditional rules.

Questions
13
Pages
3
Layouts
classic · card
Conditional rules
3
Typical time
4 min
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 2 conditional rules — nothing is sent or stored.

Page 1 of 3Applicant details

Library card application

Include your country code.

1 question is hidden by conditional logic right now — change an answer above to reveal it.

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

Library Card Application is built for councils, agencies and public bodies who need to run a public request or application to a consistent standard.

  • Councils, agencies and public bodies working in government & public sector.
  • Teams who need to run a public request or application to a consistent standard without writing code or paying for a custom build.
  • Anyone replacing paper forms that are slow to process and hard to audit with one structured record per enquiry.
  • Respondents are residents and applicants — the form asks them 13 questions across 3 screens.
  • Mobile-heavy audiences, thanks to the one-question-per-screen card layout.

Why this form is useful

It removes the cost of paper forms that are slow to process and hard to audit and turns each submission into a record your team can act on immediately.

  • 6 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 captures a phone number for urgent follow-up.
  • It records a signature you can keep as proof of agreement.
  • It pins the request to a specific date.
  • It captures a full postal address.
  • It allows multiple selections without free text.
  • Conditional logic hides 3 questions until they are relevant — shorter forms convert better than long ones.

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 Library Card Application 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 advanced show logic: if “Who is this card for?” is A child under 18, the form dynamically exposes “Guardian's name and contact details”. Otherwise that question never appears.
  • Features conditional validation: if “Who is this card for?” is A child under 18, “Guardian signature” becomes mandatory before the form can be sent.
  • Features advanced show logic: if “Do you already have a card at another branch?” is Yes, the form dynamically exposes “Which branch and card number, if known”. Otherwise that question never appears.
  • All 3 rules are editable in the Logic tab, and the built-in checker warns about rules that contradict each other.

About this template

Most library card applications share the same underlying need: confirm who the applicant is, where they live, and whether the card is for an adult or a child who needs a guardian's agreement attached. This form starts with the applicant's name and address, since proof of local residency is the most common eligibility requirement libraries have, and a note explains that the branch may ask to see supporting ID at pickup rather than trying to verify it through the form itself. A card-type question branches the form: applying for a child reveals a guardian section with the guardian's own contact details and a signature, since minors typically need a responsible adult on the account. A preferences section covers format interests — print, audiobooks, digital lending — which many branches use to tailor recommendations or the welcome material handed over with the new card. The closing agreement covers the borrower's responsibility for returning items and paying any fees the branch sets, phrased generally so it fits the exact policy of whichever library is using the form, with a note that the branch's own card terms take precedence over this summary.

What this form asks

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

Page 1 — Applicant details

  • Who is this card for?required
  • Applicant's namerequired
  • Date of birthrequired
  • Home address
  • Email addressrequired
  • Phone number
  • Do you already have a card at another branch?
  • Which branch and card number, if known

Page 2 — Guardian & preferences

  • Guardian's name and contact details
  • What are you most interested in borrowing?
  • Preferred branch for pickup

Page 3 — Agreement

  • Agreementrequired
  • Applicant or guardian signaturerequired

13 questions in total.

How the form changes as it's filled in

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

Driven by “Who is this card for?

  • Reveals questions

    If “Who is this card for?” is A child under 18, the form reveals “Guardian's name and contact details”.

  • Makes answers required

    If “Who is this card for?” is A child under 18, “Guardian signature” becomes required before the form can be submitted.

Driven by “Do you already have a card at another branch?

  • Reveals questions

    If “Do you already have a card at another branch?” is Yes, the form reveals “Which branch and card number, if known”.

Set it up step by step

  1. 1

    Confirm ID at pickup, not on the form

    This form collects the applicant's stated details; have staff verify proof of address and identity when the card is issued.

  2. 2

    Branch the form for minors

    The guardian section only appears when a child is applying — keep it that way so adult applicants aren't slowed down.

  3. 3

    Use format preferences for onboarding

    The borrowing-interest checklist is a light touch that helps staff hand new members a relevant welcome guide or reading list.

  4. 4

    Keep the agreement general

    Word the closing agreement to reference your library's own published policy rather than listing specific fees here, since those change over time.

Mistakes to avoid

  • Treating the form's address field as sufficient proof of residency without checking ID at pickup.
  • Making the guardian section required for every applicant instead of only minors.
  • Listing specific late fees in the form text, which then goes out of date when policy changes.

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

Verify ID and proof of address when the applicant collects their card, and file the signed agreement with the new account record.

Works in both layouts

These pages cover the same subject ground as the library card application, matched on the words people actually search for.

Privacy & compliance

This form takes money. Card details are handled by the payment provider and never stored in your response data — you keep the order details, not the card number.

Frequently asked questions

Does this form replace ID verification?

No — it only collects the applicant's stated details. Libraries should still check ID or proof of address in person, as the form's closing note explains.

Can this be used for a school library instead of a public one?

For a school setting, the Student Enrollment Application is a better fit since it already captures year group and guardian details as part of enrolment.

How do I handle a family applying for several cards at once?

Have each family member submit the form separately so each card is tied to its own signed agreement, even if a parent is completing the guardian section for more than one child.

Can I add a volunteer sign-up question to this form?

Keep them separate — point interested applicants to the Quick Volunteer Sign-Up instead so the card application stays focused on membership.

Is the Library Card Application template free to use?

Yes. You can preview and test Library Card Application 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 Library Card Application template ask for?

It asks 13 questions across 3 pages, 6 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 Library Card Application 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 government & public sector form work?

3 conditional rules ship with the template: Features advanced show logic: if “Who is this card for?” is A child under 18, the form dynamically exposes “Guardian's name and contact details”. Otherwise that question never appears. Features conditional validation: if “Who is this card for?” is A child under 18, “Guardian signature” becomes mandatory before the form can be sent. Features advanced show logic: if “Do you already have a card at another branch?” is Yes, the form dynamically exposes “Which branch and card number, if known”. Otherwise that question never appears. All rules are editable in the Logic tab.

Where do responses to the Library Card Application 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 Library Card Application 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 library card application.

Related categories