Describe who will complete the form and what your team needs during an emergency. Makeform turns the brief into an online next of kin form with contact details, relationships, priority order, availability notes, and clear permission to use the information when urgent contact is needed.
Route updates to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a complete prompt, adapt it to your organization, or send it to the Makeform builder. Each example shows an intentional structure, not a live result.
Prompt ready4 formats
Audience
Employees joining or updating their workplace record
Format
Two-contact form with priority and availability
Prompt size
505 chars
Brief qualitySends to builder
Example form structure
Two-contact form with priority and availability
Prompt exampleEditable in builder
Employee name, ID, department, and location
Short answerFirst ask
2
Primary contact name and relationship
Short answer
3
Phone, email, and preferred contact method
Multiple choice
4
Add an alternate contact?
Conditional section
5
I confirm these details are current
Acknowledgment
Suggested routing tags
Suggested
Primary contact complete
Alternate missing
Review requested
Ask for a primary and alternate contact separately. During an incident, a second reachable person is more useful than two phone numbers with no priority order.
Step 1
Identify
match the form to the employee, student, or resident
Step 2
Prioritize
record who to call first and who is the alternate
Step 3
Route
send the record to the responsible team
Step 4
Refresh
request an update when details may have changed
Useful under pressure
A contact name is not enough when every minute matters.
A focused next of kin form captures the information an authorized staff member needs to select the right person, use the right channel, and understand the relationship without decoding an old spreadsheet.
A clear contact order
Separate primary and alternate sections make the calling sequence obvious. Relationship, availability, and preferred method sit beside each person's phone number instead of in disconnected notes.
Questions that fit the setting
Conditional sections can show student collection permissions, resident update preferences, or employee identifiers only where relevant, while preserving one manageable workflow.
An update trail
A reviewed-on date and submitter confirmation help administrators see which record was recently checked and which person should receive an update request.
Built around your roster
One starting point for four contact workflows.
Choose the version closest to your setting, then edit its labels, explanations, routing, and required fields before sharing it.
Employee records
Link department, staff ID, work location, primary contact, and alternate contact in one onboarding or annual-update submission.
Student records
Collect parent or guardian context, emergency priority, communication needs, and collection permissions without mixing those distinct questions.
Resident contacts
Record who receives urgent calls, who receives routine updates, and when each family or support contact prefers to be reached.
Contractors and field teams
Associate contact records with the correct employer, project, site, assignment window, and supervisor for more reliable internal routing.
Form-building workflow
From a short brief to a usable contact process.
Generate the structure, make the questions match your operating process, test the paths, and publish one link people can use from any device.
Tell Makeform whether the respondent is an employee, parent, resident, representative, or contractor. Explain which internal team receives the submission and when the contact information may be used.
02
Edit fields and explanations
Replace generic labels with your identifiers, add a concise purpose statement, set primary contact details as required, and keep alternate or setting-specific questions conditional.
03
Test each response path
Preview the form as a new employee, a parent adding two contacts, and a resident naming a representative. Check that hidden sections appear only after the relevant answer.
04
Publish and route updates
Share a public link or embed the form in onboarding. Send new and updated submissions to the designated administrators, then schedule your own periodic reminder process.
Choose the record, not the paperwork
Online next of kin form vs document and spreadsheet.
The main difference is not appearance. It is whether the respondent can provide a complete, structured update that reaches the right workflow without someone retyping every field.
Approach
What the administrator receives
Best read
ApproachPrinted or fillable document
What the administrator receivesA familiar page, but incomplete handwriting and manual filing can obscure which contact is primary.
Best readUseful when an offline process is required, with later data entry still needed.
ApproachShared spreadsheet
What the administrator receivesRows are sortable, but unrestricted editing, inconsistent columns, and multiple contacts per person quickly become awkward.
Best readReasonable as an authorized internal destination, not as the respondent-facing collection experience.
Approach
Generated online form
What the administrator receivesRequired fields, conditional sections, confirmation text, and a consistent submission for every person.
Best readBest when many people need to submit or update their own next of kin details.
Field guide
What a practical next of kin form should include.
These six field groups turn a name-and-number list into a record that is easier to complete, review, route, and update. Use only the information your organization has decided it needs.
Record owner
Identify the right employee, student, or resident.
Start by tying the submission to the correct roster entry. Names alone can collide, so combine a name with the identifier your administrators already use. Avoid asking next of kin to repeat information that belongs to the person whose record is being updated.
Full and preferred name, plus staff, student, or resident identifier.
Department, year group, room, site, or location where useful for routing.
Submitter name and relationship when someone completes the form on another person's behalf.
Relationship
Describe who each contact is.
Next of kin is used differently across organizations and families. Let respondents state the actual relationship rather than forcing every person into a narrow family list. A relationship field also helps staff address the contact appropriately when they call.
Contact's full name and their relationship to the record owner.
An inclusive choice list with a self-describe option.
A separate primary or alternate role, rather than implying priority from relationship.
Reachability
Collect more than one way to connect.
A phone number without context may go unanswered during work hours or across time zones. Ask for the channels your staff can actually use and place preferred method, availability, and communication needs beside the corresponding contact.
Mobile and alternate phone, email, and postal address only if needed.
Preferred contact method, best times, availability, and time zone.
Interpreter, language, relay service, or other communication notes.
Priority
Make the calling sequence explicit.
Do not assume the first relative listed is the right first call. Label one contact as primary, offer an alternate, and ask whether the order changes for particular kinds of updates if your process distinguishes urgent and routine communication.
Primary contact and at least one optional alternate.
Clear first, second, and additional contact order.
Separate choices for urgent calls and routine organizational updates where relevant.
Purpose & handling
Explain why the information is requested.
Put a short, plain-language purpose statement before sensitive contact questions. Tell respondents which team handles the record, the situations in which it may be used, and where they can ask about your organization's information-handling practices.
A specific explanation tied to emergency or agreed administrative contact.
The responsible team and a channel for questions or corrections.
A confirmation that the submitter has permission to provide another person's details.
Review cycle
Design for changes, not one-time collection.
Phone numbers, relationships, locations, and preferences change. Capture when the details were reviewed and give people an obvious update route. Administrators can then distinguish a recently confirmed record from one that warrants follow-up.
Date submitted and date last reviewed or confirmed.
A current-details acknowledgment before submission.
An update link or repeatable form process after a move, role change, or annual review.
Related tools
Build the forms around the contact record.
Use these live Makeform tools for closely related onboarding, employee records, emergency details, and incident workflows.
Practical answers for HR teams, school administrators, residence managers, and care providers building a contact process.
What is a next of kin form?
A next of kin form records the people an organization should contact in an urgent or defined administrative situation. It usually connects an employee, student, resident, contractor, or participant with a primary contact and an alternate. Useful fields include relationship, phone and email, contact priority, preferred method, availability, communication needs, the submitter's identity, and the date reviewed. The organization should define what the term means in its own process instead of assuming respondents share one interpretation.
What details should I collect for each contact?
Start with full name, relationship, mobile or daytime phone, an alternate channel, preferred contact method, and usual availability. Add an email address, time zone, language or interpreter need, or postal address only when your workflow genuinely uses them. Keep contact priority separate from relationship: the person someone wants called first may be a partner, friend, parent, sibling, representative, or another trusted person. A second contact is valuable when the primary person cannot be reached.
Is next of kin the same as an emergency contact?
The phrases often overlap in everyday use, but an organization may define them differently. An emergency contact is usually the person to call during an urgent event. Next of kin may describe a family relationship, or it may simply be the label used on an internal form. Avoid implying that the form assigns any special authority or status. Explain the purpose directly, let the respondent describe each relationship, and ask who should be contacted first for the situations your team handles.
Can I use one form for employees, students, and residents?
You can begin with one shared structure, but each setting needs different identity and routing fields. Employees may need a staff ID, department, and location. Students may need a year group, class, completing guardian, and collection-permission question. Residents may need a room or unit, representative details, and separate preferences for urgent calls and routine updates. Conditional logic can show only the relevant section after the respondent chooses a record type, though separate forms may be clearer when different teams own the workflows.
How should I ask about permission and information handling?
Use a short explanation written for your actual process: why the contact information is requested, which team receives it, the circumstances in which staff may use it, and how someone can request a correction. Ask the submitter to confirm they have permission to provide another person's details. Keep the form focused and avoid collecting fields merely because they appear in an old document. Your organization's own policy owner can decide the appropriate wording and retention process for the setting.
How often should next of kin details be updated?
Choose a review rhythm that fits your operations, and also provide an update route whenever a phone number, relationship, location, or preference changes. Capture a reviewed-on date and a current-details confirmation in every submission. A yearly reminder is a common administrative pattern, but it should not be the only opportunity to correct a record. New roles, site moves, school-year transitions, residence changes, and returned messages are all sensible triggers for your team to request a fresh submission.
Is the next of kin form generator free?
Yes. Makeform provides unlimited free form creation and unlimited free responses, so you can generate, edit, publish, and keep collecting updates without a response cap. The paid tier removes the Makeform badge. Before publishing, review the generated questions, delete anything your process does not need, add your own information-handling explanation, test conditional sections on a phone, and confirm that submissions route only to the administrators responsible for the records.
How do respondents and administrators use the finished form?
Publish it as a shareable link or embed it in an onboarding, enrollment, resident-admission, or staff portal page. Respondents can complete the form from a phone or computer without rebuilding a document. Administrators receive consistently structured submissions and can route notifications or connect the workflow to tools such as Google Sheets, Slack, and Zapier. Test those destinations with sample records, restrict internal access according to your own process, and make the update link easy to find later.
Replace scattered contact notes with one clear update path.
Generate a next of kin form built around your people and process.
Unlimited free forms and responsesPrimary and alternate contact pathsEditable before publishing
