Overtime gets agreed in a corridor and remembered differently when payroll runs. I would rather have the ask in writing before the hours are worked. Staff open one link, say what and why, and the request lands in a list I can sort.
Three groups of questions
About you and the day. Name, team, date and extra hours. I need these to match the request to the schedule and to the right manager.
About the work. The reason, the task and a cost code. A manager can approve "report due Friday" faster than "needs more time".
Pay and approval. How the person would like the time handled, plus two boxes: one for hours already worked and one for "I spoke to my manager first". The first box shows me how often people ask after the fact.
Who fills it and who reads it
Employees fill it in. A manager or HR reads the CSV. A person's own AI can do the typing. It might ask "Which day is the overtime?" Then "How many extra hours?" Then "What will you work on?" It shows everything and sends it only after a yes. See agent-fillable forms.
A tip and a note
Download the CSV each week and sort it by approving manager, so each person sees only their own list. Overtime rules differ by country and contract. This is a form, not legal advice, so have a professional check any wording that has legal weight.
Staff who travel for extra shifts can use a travel request. Courses taken outside normal hours fit a training registration form. More HR tools are in HR and recruiting forms.
Questions
Can I tell late requests from early ones?
Yes. The `already_worked` box marks requests filed after the hours happened. Filter on it in the CSV to see how often it happens and under which manager.
Can I cap how many hours one request may ask for?
Yes. The extra hours field takes a minimum and a maximum, so a value outside your range is refused. A weekly total per person is something you add up in the CSV.
Should the form ask for pay rates?
No. This template leaves pay rates out on purpose. Keep pay data in your payroll system and match requests to it by name and date.