Employee identity
Route the request to the right schedule.
Collect stable workplace details so the request reaches the correct roster and manager.
- Employee name and ID.
- Location, department, and role.
- Manager and contact information.
Describe how employees request preferred shifts, schedule changes, or swaps. Makeform creates a shift request form with availability, current and requested shifts, coverage, and contact details.
Route shift requests to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor it to your policy, or send it to the builder. The structure is an example, not a live AI result.
Audience
Hourly employees sharing schedule preferences
Format
Availability and ranked-preference form
Prompt size
270 chars
Example form structure
Availability and ranked-preference form
Employee, department, and role
Days and times available
Rank your preferred shifts
Minimum and maximum weekly hours
Anything the scheduler should know?
Suggested routing tags
Preferred shifts
Change requests
Swap requests
Ask for both the employee's current shift and requested shift. A date alone does not tell a manager which coverage block may open.
Step 1
Request
employee chooses preference, change, or swap
Step 2
Check
details, timing, and coverage are complete
Step 3
Review
manager compares staffing needs
Step 4
Confirm
employee receives the scheduling decision
Why use one request path
A shift request form gives schedulers consistent dates, roles, availability, and coverage details.
Structured dates and start and end times make the proposed change easy to compare with the published schedule.
Conditional questions can show preference, one-time change, recurring availability, or swap fields from one starting choice.
Collect the employee's location, department, and manager so each submission reaches the person responsible for that schedule.
Built around real schedule requests
Start with the common request, then adapt its fields and review language.
Let employees rank desired shifts, share workable time ranges, and state weekly-hour preferences before the schedule is drafted.
Capture the scheduled shift, requested replacement, effective date, and reason category in one comparable record.
Record both employees, both original shifts, mutual agreement, and role coverage before manager review.
Use a weekly availability grid, effective date, and temporary end date to distinguish a lasting change from a short exception.
Setup workflow
Describe request types, fields, and review routing, then refine the generated form.
Name the locations, departments, shift blocks, cutoff times, and kinds of requests employees may submit.
Require exact dates and times, then show coworker fields only for swaps and end dates only for temporary availability changes.
Use location, team, or manager answers to organize notifications and give the scheduler a complete submission to review.
Publish the employee link and explain that submitting a request does not alter the active schedule until the manager confirms it.
Form vs message vs spreadsheet
Compare whether each method preserves the shift, timing, coverage, and contact details needed for review.
Field guide
These six sections help a manager understand who is asking, what schedule would change, when it applies, and whether a swap preserves coverage.
Employee identity
Collect stable workplace details so the request reaches the correct roster and manager.
Request type
Preferences, changes, availability, and swaps need different fields. Branch from one request-type choice.
Shift comparison
Capture exact times for assigned and requested shifts, plus locations when needed.
Swap coverage
Capture both original assignments, mutual agreement, and whether each employee can cover the other's role.
Reason and notes
Use a reason category for sorting and an optional note for relevant scheduling context.
Review expectations
State the cutoff, reviewer, and decision channel. Remind employees that the schedule stays active until confirmation.
Related tools
Collect availability, schedule changes, handovers, time, and absence requests with related forms.
Compare current and proposed schedule arrangements.
Open toolFAQ
Answers for managers replacing requests scattered across text and chat.
It lets an employee request preferred hours, a one-time change, recurring availability, or a coworker swap. It records the current and proposed schedule, dates, role, contact, and coverage details for manager review.
Include employee, location, department, role, manager, request type, current and requested shift times, effective dates, reason category, and an optional note. For swaps, add coworker, agreement, and coverage fields.
Yes. Use conditional paths. The preference path asks for ranked shifts and availability; the swap path asks about both employees, both assignments, mutual agreement, and role coverage.
State the cutoff, reviewer, and decision channel. Add an acknowledgment that submission does not change the published schedule, using language that matches your scheduling policy.
Yes. Ask for available days and times, unavailable periods, preferred shift length, effective date, and temporary or ongoing status. Show an end-date field for temporary changes.
Capture each employee's identity, contact, role, and original shift; the proposed exchange; mutual agreement; and role coverage. That gives the manager both sides in one submission.
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting shift requests. The paid tier only removes the Makeform badge, so you can keep the full request workflow on the unlimited free plan.
Require location and department, collect the manager, and use consistent tags such as preference, one-time change, recurring availability, and swap. Managers can then filter or route submissions.
Give every shift request a complete path.