Describe how your organization accepts resignations. Makeform turns the brief into a structured resignation form that captures the employee, notice date, intended last working day, departure context, handoff needs, and an acknowledgment for HR review — without asking managers to reconstruct a decision from scattered email threads.
Send resignation submissions to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose the workflow closest to yours, revise the details, or send the prompt into the Makeform builder. Each structure is an editable starting point, not a completed employee submission.
Audience
Employees formally notifying HR and their manager
Format
Short internal form with dates and acknowledgment
Prompt size
415 chars
Example form structure
Short internal form with dates and acknowledgment
Employee identity, department, and manager
What is your intended last working day?
Have you already told your manager?
Reason for leaving, if you choose to share
Employee acknowledgment and typed name
Suggested routing tags
HR review
Manager follow-up
Offboarding ready
Keep the employee's requested last day separate from HR's confirmed final day. Notice rules, schedules, accrued leave, and internal decisions can make those dates different.
Step 1
Submit
employee records notice and intended last day
Step 2
Review
HR checks dates, details, and follow-up needs
Step 3
Confirm
HR communicates the confirmed final day
Step 4
Transition
handoff and offboarding work receives an owner
A clearer notice record
A resignation email may state a date but omit the location, manager, handoff, or personal contact HR needs. A focused form gathers the operational facts in one submission while leaving sensitive narrative questions optional.
Record when notice was submitted and the employee's intended last working day as separate structured fields. HR can then review the request and communicate a confirmed final day without silently overwriting the employee's original entry.
Conditional logic can reveal shift questions for hourly staff, project-handoff fields for account owners, or manager documentation fields when someone records verbal notice. Employees avoid a long checklist unrelated to their role.
Route the submission to HR, notify the appropriate reviewer, and pass confirmed details into an offboarding checklist. The resignation form records notice; the checklist can separately assign access, equipment, payroll, and knowledge-transfer tasks.
Designed for real departures
Start with a consistent core record, then use branches for the employee's work arrangement, responsibilities, and method of giving notice.
Give employees a private internal link for their identity, notice date, intended last day, optional departure reason, and personal contact details. Confirmation copy can explain that HR will review the submission.
When notice arrives in conversation, a manager can document when it was received, the date the employee stated, and the source record. A branch can request employee confirmation rather than presenting manager notes as employee answers.
Ask employees with active work to identify deadlines, documents, recurring duties, and possible successors. HR gets the notice while the manager gets a usable first inventory for transition planning.
Location, supervisor, last expected shift, and remaining scheduled shifts help the correct local manager respond. Mobile-friendly controls make the form practical for employees who do not work at a desk.
Build the workflow
Generate the core intake, adjust it to your internal process, and test the handoff before sharing the link with employees.
Tell Makeform whether employees submit directly, managers may document offline notice, or both. Include the business units, locations, worker types, date fields, handoff details, and acknowledgment language your workflow needs.
Make identity and last-day fields required, but decide carefully whether departure reasons, new-employer details, or comments should be optional. Add plain helper text that distinguishes an intended date from HR's later confirmation.
Show shift details only to hourly workers and handoff questions only to relevant roles. Route submissions to HR first, then notify the correct manager or location contact according to the employee's answers.
Submit test cases for an employee and a manager, check dates and notifications, then share or embed the form in your employee portal. Keep downstream offboarding assignments in their own checklist with named owners.
Form vs email vs document
A resignation letter can carry the employee's own words. A structured form is better at consistently collecting dates, routing details, and transition inputs. Your process can accept an uploaded letter while still capturing fields HR needs to act.
Field guide
The strongest form separates the employee's notice from HR review and later offboarding work. These six sections create a usable record without turning one submission into an entire exit process.
Employee record
Begin with information HR can match to an internal record: employee name, work email, employee ID, department, role, location, and manager. Use dropdowns for known departments or locations to reduce spelling variations and route the submission accurately.
Notice & dates
Capture the submission date automatically when possible and ask for the employee's intended last working day. If a manager received notice earlier, collect that received date separately. Do not replace the stated date with a later HR decision; retain both values for a clear history.
Departure context
A reason-for-leaving dropdown can help with internal reporting, but employees may not want to explain their decision in the notice form. Offer an optional category, an optional comment box, and a separate choice about participating in an exit interview instead of making sensitive detail a condition of submission.
Work transition
Ask for active projects, recurring duties, near-term deadlines, important relationships, and likely handoff owners when the employee's role requires it. Keep this concise at notice stage; managers can turn the inventory into assigned tasks in a dedicated offboarding checklist.
Property & access signals
A brief checklist can identify laptops, phones, keys, badges, cards, uniforms, or other organization property in the employee's possession. It should create follow-up signals, not ask the employee to certify that every access and asset task is complete before HR reviews the notice.
Acknowledgment & follow-up
End with a typed name or signature, the submission date, and a clear acknowledgment of what the employee is submitting. Confirmation copy should say HR will review the notice and follow up about dates and next steps; it should not imply the form alone confirms every employment detail.
Related tools
Use the resignation record as the starting signal, then handle interviews, responsibilities, and offboarding tasks in focused forms and checklists.
Gather the operational information HR, payroll, IT, facilities, and a manager need after notice has been reviewed.
Open toolCreate a separate feedback conversation so the formal resignation record stays concise and departure comments have appropriate space.
Open toolAssign equipment, access, payroll, documentation, communication, and handoff tasks to the people responsible for them.
Open toolDocument open work, recurring tasks, safety notes, and ownership changes for employees leaving shift-based roles.
Open toolBuild a broader exit intake when your process combines departure details, return arrangements, and follow-up information.
Open toolCollect ongoing workplace feedback separately, before employees reach the point of giving formal notice.
Open toolFAQ
Practical answers for HR teams replacing inconsistent notice emails with a structured internal workflow.
A resignation form is an internal intake an employee uses to formally tell an organization they intend to leave. It typically records the employee, date notice was given, intended last working day, manager, optional departure context, and contact or handoff details. The submission gives HR a consistent starting record for review and follow-up; later offboarding tasks can live in a separate checklist.
Include the employee's name, ID, role, department, location, manager, notice date, and intended last working day. Depending on the role, add remaining shifts, active projects, recurring duties, company property, a personal follow-up contact, and an optional letter upload. Keep the reason for leaving and additional comments optional, and include an acknowledgment explaining that HR will review the notice and confirm next steps.
It can, but the question does not need to be required. A short list of categories with a prefer-not-to-say option supports consistent internal analysis, while an optional comment field gives room for context. Consider collecting fuller feedback in a separate exit interview so employees can submit timely notice without being required to explain their decision in detail.
Yes. Add a first question asking whether the submitter is the employee or a manager, then show the appropriate branch. For a manager-recorded notice, capture when and how it was received, the employee's stated date, the manager's account, and any attached source. Label it clearly as manager-recorded information and add an employee confirmation step when your internal process calls for one.
Store them as separate values. The form should preserve the date the employee requested or stated. HR can then review schedules and internal policy and communicate a confirmed final day through the organization's normal process. Keeping both prevents the original notice from being obscured and gives offboarding workflows a clearly labeled confirmed date once review is complete.
Yes. Route a new submission to HR, notify the relevant reviewer, and use the reviewed record to begin an offboarding checklist. That checklist can assign equipment return, account ownership, access changes, documentation, payroll coordination, and team communication. Keeping those actions outside the employee's notice form makes ownership visible and avoids asking the departing employee to complete tasks controlled by other teams.
Yes. Makeform provides unlimited free form creation and responses, so you can generate, edit, publish, and use the resignation form without a response cap. The paid tier removes the Makeform badge. Review the generated wording, fields, recipients, and date logic against your organization's process before sharing it with employees.
Send the first notification only to the HR role or mailbox responsible for departures, then involve the employee's manager and other teams according to your process. Avoid putting sensitive free-text answers into broad chat channels or large distribution lists. Test notification recipients, conditional branches, confirmation copy, and any connected spreadsheet with sample data before publishing the employee-facing link.
Give every resignation a clear starting record.
