Classic form

Timesheet form

A timesheet is a payroll document and an invoicing document at the same time, which is why the job number matters as much as the hours. This one gives each week its own seven row table, asks for real start and finish times rather than rostered ones, and is signed. It is a classic form, because two tables and a signature are things a conversational form either cramps or cannot render at all.

Create a form with OneCraft16 fields, 10 required

Welcome screen of the timesheet form example — The welcome screen respondents see first. The image was generated for this example.

The form itself

A static copy of the finished form, exactly as it renders. Nothing here can be filled in or submitted, so read it as a reference and build your own from the button above.

Timesheet, fortnight ending Sunday

One row for every day you worked, with the job number on it. Timesheets are due by 10am Monday and anything later than that is paid in the following run, which is a fortnight away rather than a day.

You and the fortnight

Your name *

First

Last

Employee number *

Your crew *

Fortnight ending *

How are you engaged? *

Full time

Part time

Casual

Apprentice

Subcontractor invoicing separately

Week one

Write the times you actually started and finished, not the times you were rostered, and use the 24 hour clock so 1730 cannot be read as half past five in the morning. Unpaid break is in minutes, so a half hour lunch is 30 and a crib break you worked through is 0. A shift that runs past midnight goes on the row for the day it started. Leave a row empty for a day you did not work rather than writing a zero, because an empty row and a zero hour day mean different things to payroll.

Monday to Sunday, week one

Date	Job number	Start	Finish	Break mins

Week two

Monday to Sunday, week two

Date	Job number	Start	Finish	Break mins

Totals and allowances

The form does not add anything up, so these two numbers are yours and payroll checks them against the rows. A total that disagrees with the table by a few minutes is normal and gets fixed quietly. One that disagrees by hours gets a phone call.

Ordinary hours this fortnight *

Hours beyond your ordinary hours

When those extra hours started and finished

Were any of them on a Saturday, a Sunday or a public holiday? *

Yes, and they are in the tables above

Take the extra hours as time in lieu instead of pay? *

No, pay them

Yes, bank them as time in lieu

No extra hours this fortnight

Allowances you are claiming

Travel, for a site more than fifty kilometres out

Meal, for an unbroken shift past nine hours

Height, for work above two storeys

Confined space

First aid officer

Tool allowance

None of these

Anything that explains an unusual row

Sign it

Your signature is what makes this a timesheet rather than a note. It is printed into the response PDF alongside the tables, which is the copy your supervisor approves and the copy payroll keeps.

I declare *

These are the hours I actually worked, and the breaks I actually took

Every job number above is the job I was on that day

I have not claimed an allowance I did not earn

Sign here *

Signature is required

Every field, and what it collects

The complete field list, in the order respondents meet it.

Your nameNameRequired
Employee numberShort textRequired
Your crewDropdownRequired: Options: Carpentry · Concrete · Electrical · Plumbing · Plant operators · Labour hire · Workshop
Fortnight endingDateRequired
How are you engaged?Single choiceRequired: Options: Full time · Part time · Casual · Apprentice · Subcontractor invoicing separately
Monday to Sunday, week oneTable: Columns: Date · Job number · Start · Finish · Break mins
Monday to Sunday, week twoTable: Columns: Date · Job number · Start · Finish · Break mins
Ordinary hours this fortnightNumberRequired
Hours beyond your ordinary hoursNumber
When those extra hours started and finishedShort text
Were any of them on a Saturday, a Sunday or a public holiday?Single choiceRequired: Options: No · Yes, and they are in the tables above
Take the extra hours as time in lieu instead of pay?Single choiceRequired: Options: No, pay them · Yes, bank them as time in lieu · No extra hours this fortnight
Allowances you are claimingMultiple choice: Options: Travel, for a site more than fifty kilometres out · Meal, for an unbroken shift past nine hours · Height, for work above two storeys · Confined space · First aid officer · Tool allowance · None of these
Anything that explains an unusual rowLong text
I declareMultiple choiceRequired: Options: These are the hours I actually worked, and the breaks I actually took · Every job number above is the job I was on that day · I have not claimed an allowance I did not earn
Sign hereSignatureRequired

What makes this form work

It says what an empty row means

An empty row is a day not worked; a zero is a day worked for no hours. Those are different facts and a timesheet that does not distinguish them produces a fortnightly argument. One sentence above the table settles it.

Breaks are in minutes, with worked examples

Thirty for a half hour lunch, zero for a crib break worked through. Break fields collect hours, minutes and blanks in equal measure when the unit is not stated, and the resulting mess is corrected by hand for every worker every fortnight.

The allowances list ends with "none of these"

A tick list with no negative option leaves payroll unable to tell a worker who claimed nothing from one who skipped the question. One extra option removes a whole category of follow up calls.

Questions people ask

Why one table per week instead of one for the fortnight?

Because a fourteen row table is a wall, and because a week is the unit people reconstruct from memory. Two seven row tables under their own headings let somebody finish week one, stop, and come back to week two. The row counts are fixed when the form is built, so seven is a deliberate choice rather than a maximum.

Can the form total the hours?

No. Nothing adds up between fields, so the totals are typed by the worker and checked against the rows by payroll. That is stated on the form rather than hidden, and it turns out to be useful: a total that disagrees with the table is exactly the signal a payroll officer wants to see.

What does the signature actually do here?

It is drawn or typed by the person filling the form and it is printed into the response PDF beneath the tables. That PDF is the artefact a supervisor approves and payroll keeps. It is not an e-signature request sent by email to a second party, which is a different feature for a different job.

Why ask when the extra hours started and finished?

Because ten hours on a Saturday is not one rate. Under most awards the first block is one multiple and the rest another, and a total on its own forces payroll to guess. Recording when the extra hours began and ended, on top of the count, is also what the record keeping rules expect.

Build your own in about a minute

The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.

Make my timesheet form

Other form examples

Payroll details change form

Payroll fraud almost always arrives as a convincing request to change where somebody's pay lands. This form is built around the control that stops it: a call back on the number already held, stated on the welcome screen, in the bank section and again on the thank you screen, so nobody is surprised by it. It also puts the pay run cut off where people will read it. Classic, because the sections are only relevant to some people and everyone needs to see which ones to skip.

New employee onboarding form

Onboarding paperwork fails in a specific way: three teams each send their own form, the new starter fills in their address three times, and nobody has the one thing IT needed. This form is the single pre-start collection, ordered by who needs the answer rather than by how the questions feel. It is a classic form, because a right to work upload and a signature cannot be collected on a conversational one at all.

Workplace grievance form

A grievance form that only asks "describe your complaint" produces a page of frustration nobody can act on. This one asks for the account and then a dated table of incidents beside it, keeps witnesses separate, and finishes with the question that decides what happens next: what would a good outcome look like. It is a classic form, because somebody writing something difficult needs to see the whole shape of it before they start.

Want the steps in the builder? Read Every form field and when to use it, then Shape the PDF version of your form. For everything this generator can do, see the form maker.