A membership application is not a form that ends when somebody presses submit. Somebody has to read it, decide whether the applicant qualifies, sometimes ask for a document that was missing, take a fee, add the person to the roster, and send a reply that tells them which of those things happened. The form is ten minutes of work. The reply is where organisations lose applicants.
The symptom is always the same. An applicant emails three weeks later to ask whether anyone saw the application, and nobody can answer, because the submission is in a spreadsheet, the discussion about it is in a committee thread, the fee is in a payment dashboard, and the last reply sent was an automatic receipt that said nothing. This is a guide to building the intake so that the form and the answer are the same piece of work.
What a membership application has to decide
Before writing a single field, write down the outcomes. Almost every membership process has four, and the form exists to produce one of them.
Approved. The applicant qualifies, the fee is settled, and they belong on the roster from a stated date.
Declined. They do not qualify, or the category they applied for is closed. This needs a reason recorded internally and a reply that does not read like a rejection letter from a machine.
More information needed. The most common outcome and the one that breaks processes. A certificate was not attached, a sponsor was named but not confirmed, or the category picked does not match the evidence given. The application is not finished and is not dead.
Withdrawn or lapsed. The applicant stopped responding, or asked to pull out. Without this state, the middle category quietly fills with applications nobody will ever close.
Design the form around those four and the field list writes itself. Design it as a questionnaire first and the review process gets bolted on afterwards, which is how applications end up sitting for weeks.
The fields, grouped by who reads them
A membership application usually carries three sets of questions that are wanted by three different people, and putting them in the wrong order costs completed applications.
Identity and contact. Full name, email, phone, postal address if a card or a journal is posted, and the name the applicant wants shown in any public directory, which is often not their legal name. Keep this block first and keep it short.
Eligibility evidence. This is the part specific to the organisation: a qualification, a licence number, an employer, a school, a geographic area, a sponsor or proposer who is already a member, years of practice. Ask only for what actually gates entry. Every question here that does not change the decision is a question that loses an applicant.
Category, fee and consent. Which class of membership is being applied for, the fee that goes with it, agreement to the code of conduct or constitution, whether the person consents to appear in the directory, and what communications they want. Consent questions belong at the end, as separate required checkboxes with the wording visible on the form rather than behind a link.
Eligibility is a branch, not a paragraph
Most organisations have more than one route in, and most application forms try to serve all of them with one flat list of questions plus a note in brackets. A student applicant is asked for an employer. A corporate applicant is asked for a date of birth. Both then write an explanation in the comments box.
The fix is conditional logic driven by the category question. Pick the category first, then show only the evidence that category requires. A student sees an institution and an expected graduation date. A full member sees the qualification and the sponsor. A household or family membership shows a repeatable block for the additional people, each with their own name and email, because those people will later need their own logins and their own renewal notices.
Documents, and the sign-in problem
Membership applications frequently need a file: a certificate, a student card, a professional registration, proof of address. This is where the free option starts to bind. A Google Form can take a file upload, but the Google documentation is explicit that to answer a file upload question, responders need to sign in to a Google Account. For an internal staff process that is fine. For a public join form aimed at the general population it is a real barrier, and it is the kind of barrier that produces emails saying the form would not let them apply.
Who reviews it, and how a review gets stuck
An application with no named owner is an application that waits. This is the single largest difference between organisations that answer in three days and organisations that answer in three weeks, and it has nothing to do with how good the form is.
Three things have to be true of every submitted application.
It has one owner. A person, not a committee and not a shared mailbox. Committees decide. Owners chase. If the membership secretary owns every application, that is fine, as long as it is written down next to the application rather than assumed.
It has a status that both sides understand. Submitted, in review, more information requested, approved, declined, withdrawn. Six words are enough. What matters is that the status lives on the application itself, so that anyone who opens it can see where it is without reading a thread.
It has a visible history. What was asked, what came back, what was decided and by whom. For organisations where membership confers a professional standing, that history is not administrative tidiness. It is the record that gets produced if a decision is ever questioned.
A spreadsheet can hold a status column. What a spreadsheet cannot easily do is keep the correspondence attached to the row, which is why the status column and reality drift apart. When the reply is sent from an inbox, the inbox becomes the real record and the spreadsheet becomes a guess.
Committee approval without the stall
Plenty of constitutions require a committee or a board to approve new members, which means applications queue until the next meeting. That is a rule to work with, not around, and it changes the reply rather than the review.
Two things make it survivable. First, do the completeness check immediately rather than at the meeting, so that the committee is never handed an application missing a document. Second, tell the applicant the schedule in the acknowledgement. An applicant who knows the committee meets on the second Tuesday of the month does not email to chase. An applicant who has heard nothing does, and answering that email costs more than sending the first one properly.
The reply is part of the form
Every membership process needs three written replies, and writing them once is the highest return work in the whole setup.
The acknowledgement. Sent on submission, automatically. It states what was received, which category was applied for, what happens next, the realistic timescale, and who to contact. This is the email that prevents most chasing, and most organisations send a bare receipt instead.
The request for more information. Names the specific thing missing and nothing else. A request that says "your application is incomplete" produces a reply asking which part. A request that says the student card was not attached and gives a link back to the application produces the student card.
The decision. For approval: the join date, the membership number, what to expect and when, and how to pay if payment comes after approval. For a decline: the reason, plainly, and whether a different category would be open to them. A decline that mentions a category the applicant does qualify for turns a lost applicant into a member, and it is the single most valuable sentence in the whole exchange.
Keep these as templates attached to the application rather than as drafts in somebody's mail client. The point is not the writing, which only happens once. The point is that anyone covering for the membership secretary in August sends the same three replies.
Fees, renewal and the join date
Decide one thing before the form goes live: whether the fee is taken at application or after approval.
Taking payment up front is simpler to run and produces a refund job every time an application is declined. Taking it after approval means two steps and a chase, but no refunds and no awkwardness about holding money from someone who was never eligible. Organisations with a real eligibility test usually take the fee after approval. Organisations where almost everyone qualifies take it at the point of application.
Whichever is chosen, say so on the form next to the fee, along with what the fee covers, whether it is pro rata for a part year, and whether there is a joining fee on top of the subscription. Applicants ask all three.
Renewal is a different form, and it is worth saying because so many organisations try to reuse the application. A renewal does not need eligibility evidence, does not need a review, and does need current details confirmed and a payment taken. Treating renewals as new applications buries the genuinely new applicants in a list of people who have been members for a decade.
Where the applicant list should live
The choice here is really a choice about how many copies of the applicant list will exist.
| Approach | Good at | Where it costs you |
|---|---|---|
| A free form plus a spreadsheet | No cost, running the same afternoon it is set up | No owner or status per application, correspondence sits in a separate inbox, document uploads need the applicant to sign in to a Google Account |
| A membership management system | Built for the whole lifecycle: roster, renewals, dues, directory, sometimes events | Priced per member, so the bill grows with success, and the join form is only a small part of what is being paid for |
| A form tool with response management | The submission and the reply on one screen, each application with its own owner and status | Roster specific work such as directory pages and renewal billing has to live somewhere else |
For an organisation of a few hundred members with a simple fee structure, a membership system is often more machinery than the situation needs, and the join process is the only part that hurts. For an organisation with tiered dues, chapters, a public directory and continuing education records, the membership system is doing real work and the form is a detail.
Check how each option prices before the shortlist gets short. Pricing that counts members or responses behaves very differently from pricing that counts the handful of people who actually review applications, and a membership drive is exactly the moment when that difference shows up on an invoice. The features that matter for intake are the ordinary ones: conditional questions, file uploads without an account, a status per submission, and replies sent from the same place the submission is read.
What to change first
Write the three replies before touching the form, because the acknowledgement alone removes most of the chasing email, and then give every submitted application one named owner and one of six statuses. If applications currently live in a spreadsheet while the answers live in an inbox, see what the submission and the reply look like on one screen before the next intake opens.
Q1. What should a membership application form ask for?
Name, email, contact details, the category being applied for, whatever evidence actually gates entry to that category, agreement to the code of conduct, and consent for the directory and for communications. Anything that does not change the decision or is not needed to run the membership should be optional or cut, since each extra question loses a share of applicants.
Q2. Should the fee be taken with the application or after approval?
If almost everyone who applies qualifies, take it with the application and save a step. If there is a real eligibility test, take it after approval, because otherwise every decline turns into a refund. Whichever is chosen, state it on the form next to the fee along with whether the amount is pro rata for a part year.
Q3. Can Google Forms handle a membership application that needs a document uploaded?
It can take file uploads, but Google's own documentation states that responders need to sign in to a Google Account to answer a file upload question. That is workable for an internal process and a genuine barrier on a public join form, so check who the applicants are before relying on it.
Q4. How long should approving a membership application take?
The completeness check should happen within a day or two, since that is what triggers the request for a missing document, and waiting for a committee meeting to discover a certificate is missing adds a whole month. Where a committee or board must approve, the honest answer is the meeting schedule, and stating that schedule in the acknowledgement email prevents most chasing.
Q5. How should a declined application be answered?
State the reason plainly, and if the applicant qualifies for a different category, say which one and how to apply for it. Keep the internal reason recorded against the application as well as in the reply, because questions about consistency between decisions tend to arrive months later.
Q6. Is a renewal the same form as an application?
No. A renewal confirms existing details and takes a payment, with no eligibility review, while an application has to be assessed. Running both through one form means genuinely new applicants get buried among long standing members, and the review queue stops being meaningful.