Time and Attendance for Watersports Staff

Knowing who worked when, and for how long, sounds simple and is the source of more friction in sailing centres than almost anything else. Instructors who feel short-changed for the rigging hour that was not counted. Payroll that takes a weekend of reconciling scribbled timesheets. An inspector asking how many hours the sixteen-year-old worked last week. An insurer asking who was on duty when the incident happened. A dispute about whether the Thursday evening was a shift or a favour. Good time and attendance records settle all of these, and they can be kept without turning instructors into clerks. This article covers how.

Decide what counts as work

Before tracking time, agree what work is. Teaching sessions, obviously. Setup, rigging and launching. Briefings and debriefs. Recovery and putting away. Maintenance. Staff meetings and training. Standby when it restricts what the person can do. Travel between sites during the day. Write the definition down, apply it to everyone, and make sure it meets the law: in the UK and Ireland, time the employer requires a worker to be at work or available counts, and the minimum wage must be met across all of it, not just the teaching hours. Ambiguity here is where most disputes begin.

Track from the roster, not from memory

The roster already says who was due to work which sessions and when. The simplest reliable method is to confirm the actual against the rota: at the end of each day or session, the instructor or the person in charge confirms that the planned hours happened, or adjusts them for the early finish, the extra hour or the swap. The record is then a correction of a plan rather than a reconstruction from scratch, which is faster and far more accurate. Systems that hold the roster and the time record together do this with a tap.

Make it effortless and immediate

Time recorded at the end of the week is guesswork; time recorded at the end of the day is accurate. Whatever the method, a phone tap, a sign-in sheet by the kit store, a confirmation message, it must take seconds and happen the same day. If it takes longer or waits until Friday, people stop doing it and the office ends up reconstructing it, which is where the arguments and the errors come from.

Have the instructor confirm

The person whose pay depends on the hours should see and confirm them, weekly, before payroll runs. This catches errors in both directions, removes the suspicion that the office is quietly rounding down, and gives the instructor a clear record of what they are being paid for. A weekly summary to each person, with a way to query it, costs nothing and ends most pay disputes.

Watch the legal limits as you go

Working time rules set maximum hours and minimum rest, and for under-18s the limits on hours, times of day and breaks are stricter. These are not things to check at the end of the month; they need to be visible when the roster is built and when the hours are confirmed. A system that knows each person's age and the rules that apply, and warns when a week is approaching a limit or a shift breaks a rest requirement, keeps the centre legal without anyone doing arithmetic.

Keep the record for the people who need it

Payroll needs hours by person by pay period. Compliance needs who was on duty for each session, with their role, for the inspector, the insurer and any investigation. Young workers' records may be requested by enforcement bodies. Fairness needs the pattern of early starts and weekends by person. One good record, kept from the roster and confirmed daily, serves all of them; the alternative is four spreadsheets that disagree.

Handle the edge cases in advance

Decide and write down how you treat the predictable awkward cases: the session cancelled for weather after staff arrived, the course that overran, the standby who was not called, the instructor who stayed late voluntarily, the split shift, the training day, the residential with overnight responsibility. Having the answers before the question arises keeps the policy consistent and the conversations short.

Volunteers

Volunteers' time is not paid, but it is worth recording for the same operational reasons: who was on duty, safety cover and ratios, the hours the club depends on them for, and the thank-you at the end of the season. Keep it light, but keep it.

Connect it to pay

The hours record should flow into payroll without re-typing. Whether that is an export to the payroll provider or an integrated system, the aim is that the confirmed hours become the pay run in minutes, with the rate structure applied automatically. Each manual transfer is an hour of office time and a source of error.

Be transparent

Tell staff at induction how time is recorded, what counts, when they will see their hours, how to query them and when they will be paid. A transparent system is trusted; an opaque one is suspected even when it is accurate.

Review the pattern

Look monthly at hours by person against the roster, at overtime and at approaches to the legal limits. A person consistently working far beyond their rostered hours is a workload problem. A pattern of unpaid early starts is a culture problem. The time record is management information as well as a payroll input.

What good looks like

Work defined. Hours confirmed daily from the roster, in seconds, by the people doing them. Legal limits checked as the roster is built. Weekly confirmation by each instructor. One record feeding pay, compliance and fairness. Edge cases decided in advance. Payroll in minutes. No scribbled timesheets, no reconstruction, no weekend of reconciling, and a team that trusts it is being paid for every hour it works.

This article is general guidance for RYA centres and clubs. Schemes, awards and requirements change — always check the latest official RYA guidance and your recognition paperwork before acting. ActivityRoster helps you run the rostering, qualifications and safety-cover side of all of this in one place.