A grid, by day
Weekdays laid out for the whole period. Type hours against a project and a task code and it saves as you go — there is no separate "add entry" ritual.
Product
One cycle, from an empty grid to a settled period
CliqHours does one thing end to end. This is that thing, in the order it happens.
Set up
Projects, engagements and task codes
Three ideas carry the whole model, and nothing else is required to start.
- Project
- The piece of work hours are booked against — a client engagement, an internal programme, whatever your business calls it.
- Engagement
- One person on one project, with the rates that apply to them there. The same person on another project can be on entirely different terms.
- Task code
- What kind of hour this is — standard, after hours, on-call, and whatever else you need. The rate is attached here, which is why nobody has to remember to select a rate.
Capture
The person fills in a period, not a form
More than one line a day
A day can carry several lines with different projects, codes or rates. That is the normal case for contract work, so it is not hidden behind an advanced view.
Comments where they matter
A note attaches to the line it explains, so an approver reading a long day is reading the reason beside it rather than hunting for it.
Submit when the period is done
One action closes the period and tells the approver. Until then nothing is waiting on anyone, and after it the person cannot quietly change the numbers.
Approve
The administrator gets a queue, not a calendar to search
Everything actually waiting on you is on one screen — not a month you had to guess at. A period submitted late, or for a month nobody is looking at any more, still appears.
Approve
The period is agreed. It is stamped with who approved it and when, and it stops being editable by anyone.
Send back
With a reason, which the person receives. It reopens for them to fix and resubmit.
Correct a line
When it is faster to fix than to explain, an administrator can override a line directly. The original value, the new one and who changed it are all kept.
Reopen
An approved period can be reopened when something genuinely needs to change. It is restricted, it is deliberate, and it is written down.
Settle
What an approved period produces
A statement: hours by project and task code, the rates applied, the total, and the approval stamps. It can be printed or taken as CSV.
It is a view of the record, not a stored document. There is no invoice number and no second copy to fall out of step with the data. If a rate is corrected later, the statement tells you the truth as it now stands rather than as it was mis-entered.
For the owner
Cost against sell, when you want it
Where an engagement carries a bill rate as well as a pay rate, an owner can see margin by person, project or task code across a date range. Where it does not, that work is simply not billable — there is no separate flag to set and forget.
Margin is visible to owners only. An approver who is not an owner does not see it — and not because a control is hidden: the number is never calculated for them.
Boundaries
Where CliqHours stops
-
Attendance
Clock-in and clock-out are not part of the product today. It agrees what the hours were; it does not monitor anyone.
-
Invoicing and payroll
CliqHours ends at an approved, agreed number and hands it to the systems that already hold your tax and banking setup.
-
Leave balances
Recording a day as leave is on the way. Accruing, approving and tracking a balance is a different product and we are not pretending otherwise.
Next
See it against your own arrangement
The fastest way to judge it is to look at your own projects and rates in it. Tell us how you engage people and we will set a workspace up with you.