ClockWise HRGuide
Guide
Every task in ClockWise, filed under the part of the application it belongs to. Each page is a short walkthrough with pictures.
Start here
How a punch becomes a salary, signing in, and the screen you land on.
- How ClockWise fits together From a punch to a payment, on one page
- Signing in for the first time Your password, and two-factor when it is required
- Finding your way around The menu, the language, your own password
- The dashboard Four counts, and the machines that have gone quiet
Recruitment
People who have applied: their details and CV, turning them down, and hiring them into an employee file.
- Recording a candidate Pending until decided — and the list opens on Pending only
- A candidate's CV and papers Papers move to the employee file — type and expiry as filed
- Rejecting and reopening a candidate A reason to reject; reopening throws it away
- Employing a candidate The employee form, filled in — and zero pay without salary rights
- New hires waiting for a salary Hires made without salary rights, until their rate is set
Company
The people who work here: finding them, filing them, and the branches and departments they belong to.
- Finding an employee One list, searched and exported — and why yours is shorter
- Adding an employee Two steps — and hourly at zero if you cannot set pay
- Changing an employee's details A transfer or a promotion, and the date that does not delay it
- Setting an employee's pay Fixed, daily or hourly — and only hourly earns overtime
- Contacts Phone, email, emergency — one of them the default
- Documents Contracts and ID cards, and the expiry that rings early
- Payment accounts How someone is paid, and the word a method's name must hold
- Giving someone a schedule A week per version — and Effective from does not start at today
- Changing many schedules at once A whole team's week on one grid, saved as you click
- Recording leave Allowances first; a leave day counts as a day worked
- One person's attendance The punches and the days, from the person's own file
- One person's salaries Closed salaries on the file — Total Paid is the net, paid or not
- Adjustments for the coming salary Today or later, and Orphaned until a period picks it up
- Lending to an employee Draft, approve, repaid from salaries — and a balance that lags
- Repayments outside the salary Cash repayments go to the oldest instalment due
- Branches A branch — fill in the description, and expect no messages
- Departments and sub-departments Company-wide names, and Disabled hides less than it says
- Employee levels Grades — and a switched-off level blocks its holders' saves
- One schedule for a whole branch One week for a whole branch — and it opens as seven days off
- Recalculating a branch Work past days out again — and the box that deletes corrections
Attendance Settings
Shifts, and the types of leave — what each working day is measured against.
- Adding a shift Windows, breaks, three ways to count a day, and overtime
- Changing a shift A shift has no start date — and deleting one hides days
- Leave types Paid or unpaid, and why the mark changes nothing
- Adding a clocking machine User number = Employee ID; deleting a machine deletes its punches
- Fetching punches from a clocking machine Copy punches by hand — older days need recalculating
- Checking a clocking machine Who is enrolled, the machine's clock — and two dead actions
Attendance Data
The punches, the days worked out from them, and correcting a day — directly or through an approver.
- Reading the punches Every punch as the machine sent it, before any correction
- Reading a day's attendance One row a day — and why an Error day is not a paid day
- Correcting a day A missing punch, a wrong shift — and a corrected day is frozen
- Following your requests What became of the corrections you asked for
- Approving corrections The day as it would be, then approve, reject or undo
Salaries
A salary period per branch: what it holds, adjusting it, locking the checked hours, and closing it for good.
- Creating a salary period One per branch — and last month moves to History
- Reading a salary period Who is paid what, at today's rate while it is open
- Adjusting one period's pay Any date, any type — and Hours times the person's rate
- Recalculating and locking a period Pull in what belongs; lock stops schedules, not corrections
- Closing a salary period Written down at today's rates, with no way back
- Paying and holding salaries Paid for good, or held with a reason
- Adding someone to a closed period Someone left out — and a fixed salary comes in whole
- Payment slips and exports Slips to sign, and the period in Excel
- Payment batches Generate before paying anyone, and one live batch at a time
- Paying a batch Mark lines paid, fix No Method, export for the bank
- Paying someone early Part of a period paid now — a fixed salary pays the month
- Earlier salary periods Every period but the latest — last month included
- The financial audit log Every money change, close, export and view — all branches
Tips
Sharing a tips box between the people of a closed salary period, by shares and hours, and paying it out.
- Sharing out a tips box Shares × hours — and tips follow attendance, not salary
- Reading a tips run From raw hours to amount, line by line
- Changing a draft run Any change shares the whole box out again
- Closing and reopening a tips run Frozen to pay — reopenable only until the first payment
- Paying out tips Dismissing on a closed run leaves the money unclaimed
- Tips sheets and history Print the signature sheet before paying anyone
Training
Courses the company runs, the sessions that hold them, who attends, and the certificates and records that follow.
- Defining a training program The course, and the defaults every session copies
- Scheduling a training session Saved as a draft — not on the calendar until scheduled
- The training calendar Coloured by status; drafts never shown
- A session's status Complete only when everyone is marked; cancelling is final
- Assigning people and marking attendance Assign before, mark after — training attendance never touches pay
- Training materials On the program for every session, on a session for that one
- Training certificates Dated the day issued, not the day trained
- An employee's training record OK means attended, not passed
Inspections
Branch audits on a phone or tablet — filling in, submitting and the records they leave — and, for the office, building the forms, assigning visits and comparing branches.
- My inspections Assigned, in progress, recently submitted
- Starting an inspection yourself A spot check — one draft per form and branch
- Filling in an inspection Saved as you go, kept on the device when offline
- Reviewing and submitting an inspection Required questions block; N/A leaves the score
- Inspection records Never deleted — voided, with a reason
- The checklist library Reusable categories; Yes is always the good answer
- Building an inspection form Never the same category in two areas
- Publishing, versions and archiving Publishing freezes; archive the old version by hand
- Assigning inspections One per branch and inspector; reminders at 07:00
- Inspection reports Latest inspection per branch; points lost, not failures
- Location groups Compare like with like
Assets
Uniforms, tools and devices handed to employees: the stock, single allocations and starter-kit orders, returns, and the charges that reach a salary.
- Adding an asset Permanent items are charged to the employee; returnable ones are not
- Giving out an asset and adjusting stock The charge lands in the next salary
- Taking an asset back A permanent item comes back only until its charge is taken
- Asset groups The first two letters become the code prefix
- Asset bundles A template — editing it changes no past order
- Giving out several assets at once A whole kit in one click, and a sheet to sign
- Changing a submitted order Unlock returns everything; resubmit gives it out again
- The stock log Every movement, never edited
Reports
Lists, attendance and payroll reports: what each answers, what to choose, and which figures to trust.
- Finding a report Three tabs; each report a permission of its own
- Employee and structure lists Who, with what schedule, missing which photo
- Leave balances Allowed, used, remaining — on any date
- Attendance totals Hours only — ignore the salary column
- Day-by-day attendance One PDF page per employee, or Excel
- Schedule audit Repeated schedule problems, with advice
- Breaks and weekly hours Long breaks; this week against the last two
- Salary records One period, line by line — held salaries in the totals
- Payroll analysis Gross is before adjustments; compare one branch at a time
- Payment reports Paid against pending, and every batch
- Loans, advances and early salary What is still owed, and what is not yet recovered
Communication
Conversations between users, and the notifications that reach the bell — sent by hand, on a schedule, or by ClockWise itself.
- Sending a message One person or a group, with attachments
- Organising conversations Star, archive, folders; the owner locks or closes
- Overseeing all conversations Every conversation, for the administrator
- The notification bell Bottom right, only when something is unread
- Sending a notification A dated notification waits to be fired by hand
- Recurring notifications Sent only when someone opens the dashboard that day
General Settings
The company-wide choices and the lists the rest of ClockWise draws on: which modules are on, currencies and their rates, allowances, how salaries are paid — and loading many records at once from a file.
- Company settings Name, leave year, overtime, employee numbers — for the whole company
- Switching modules on and off Off hides a module from everyone; nothing in it is lost
- Currencies and exchange rates Every total is in the default currency, converted at these rates
- Salary add-on types Switching a type off stops it being paid
- Nationalities Switch one off only when nobody holds it
- Payment methods and banks The name decides what an account must hold — in English
- File types Document kinds, and whether each must have an expiry date
- Importing data from a file Preview first: an import cannot be undone
- Import history Every import, line by line, and the file as uploaded
Users
Who can sign in, what they may do, and whose data they see.
- Adding a user Role starts on admin, no branches yet, and Delete does nothing
- Deciding what someone can see Branches and sub-departments — and the list that does nothing
- Requiring two-factor sign-in By role or by person — the person's setting wins
- Roles A copy is taken once — and never rename admin
- What a role may do Switches save at once; the administrator has no master key
- The permissions list Who holds a permission — and Remove All opens on admin