Contractors, not employees
People are engaged on projects at agreed rates. Somebody may work across several projects at different rates in the same week, and the maths has to be right the first time.
Timesheet software
Timesheets that end in an answer, not an argument.
CliqHours is for companies that engage contractors. A person records the hours they worked against a project and a task code. An administrator reviews the period, corrects it if it needs correcting, and approves it. What comes out the other end is a statement both sides can rely on.
Invite-only while we are in early access, and free during it. There is no public sign-up.
The loop
Three steps, and the period is closed
The whole product is one cycle. It is deliberately small.
-
Capture
A contractor fills in a monthly or weekly grid — hours per day, against a project and a task code, with a comment where a day needs one. Several lines on a day are normal, not an exception.
-
Approve
The administrator sees everything waiting on them in one queue. They approve, send it back with a reason, or correct a line themselves and say so in the record. Nothing is silently changed.
-
Settle
An approved period becomes a statement: hours by project and task code, the rate applied, the total, and who approved it and when. It is a view of the record, not a document somebody typed.
What it is good at
Built for the arrangement, not the org chart
Rates that live on the task code
A rate belongs to a task code within an engagement, so standard, non-standard and on-call hours price differently without anyone remembering to pick the right one.
Weekly or monthly
A workspace runs on whichever period suits it, with any week start day. A week that crosses a month boundary is one period — it does not split, and it does not double count.
Cost against sell
Where a bill rate is on file, an owner can see margin by person, project or task code. Where it is not, the work is simply not billable — there is no flag to forget to set.
A record that holds up
Every approval, correction, send-back and reopen is written down with who did it and when. A disagreement six months later is a question with an answer.
One workspace per company
Your people, projects, rates and history are sealed off from every other company on the platform. Nothing crosses that boundary.
Deliberate omissions
What CliqHours does not do
Each of these is a decision we have already taken and can explain, not a gap on a roadmap.
-
It does not track attendance
No clock-in, no clock-out, no location, no screenshots. It agrees what the hours were; it does not watch anyone work.
-
It does not issue invoices
An approved period produces a statement of hours and value. Your accounting system issues the invoice — it is better at it, and it already holds your tax setup.
-
It does not run payroll
It ends at an agreed, approved number. What happens to that number is your payroll system’s job.
-
It does not let anyone sign themselves up
An administrator adds people by address. That is the only way in, which is why the product can be small and why the roster is always someone’s deliberate decision.
Getting started
Onboarding is a conversation, not a signup form
We create the workspace and invite your first administrator. They invite everyone else. It takes a few minutes and we would rather do it with you than watch you guess.