Why ReliTime

Built by an engineering consultancy, for the way it works

ReliTime was built inside an engineering consultancy to run its own timesheets, approvals, job costing and invoices, and it is used for them every week. Everything on this page came from doing that work, not from a list of features.

One loop, from the client to the invoice

A client has jobs, a job has phases and tasks, and people record time against the tasks. Their weeks are approved and locked, priced at the rate in force on the day, reported as work in progress, and invoiced. Each step reads the one before it, so the invoice is built from exactly the hours that were approved, and nobody retypes them into a spreadsheet on the way.

Time records you can defend

A time entry is never overwritten. A correction is a new entry that supersedes the old one, carrying a reason and the name of whoever made it, and the original stays. A slip with no right figure, like hours booked to the wrong job, is voided the same way: recorded, not erased.

Those rules are enforced by the database, not only by the application, and the application never connects as the owner of its own tables, so it cannot switch them off. Once a week is locked, nothing in it can change. Reopening it needs an authorisation from someone other than the person whose week it is, and it can be used once.

The standard it was built to is the Australian Fair Work Act's record-keeping rules: records kept for seven years, altered only to correct an error, and never in a way that makes them misleading. That is a demanding standard, and a useful one for anyone whose records may one day be read by a client, an auditor or a court.

Nobody is watched

ReliTime takes no screenshots, tracks no location, detects no idle time, shows no live board of who is working and scores nobody's productivity. The application's own security settings switch off the browser's access to location, the camera and the microphone.

A timesheet is a record of the hours somebody worked, made by them. Turning it into a record of what they were seen doing changes what it is, and it is not what an engineering consultancy needs to bill a client or run a job.

GST by the rules, not by rule of thumb

"GST is 18%" is wrong for most of an engineering consultancy's export work. ReliTime works out CGST and SGST or IGST from the place of supply, treats an overseas client's invoice as a zero-rated export, keeps money paid on a client's behalf out of the taxable value under Rule 33, and issues invoice numbers in one unbroken series.

GST invoicing in detail

Figures that don't bluff

A missing rate is named

An hour with no rate is listed as unpriced, entry by entry, rather than billed at nothing. A gap in the rate table shows up in the report, not in an invoice that went out short.

Rounding lands on the invoice

The record keeps the minutes actually worked. The rounding increment is applied once per job when it is billed, and the report shows both figures so the difference can be checked.

Unknown is not zero

A phase nobody budgeted shows no percentage rather than 0%, and an overrun is shown as the hours over rather than capped at 100%. The number you act on is the real one.

Written off is not the same as free

Work that was never chargeable and chargeable work that was written off are kept apart, and a write-off records who decided it. Margin is measured after write-offs.

Rates change on a date

A new rate starts on a day and never overwrites the old one, so re-running March's invoice in June uses March's rate.

Pay stays private

What a person costs the business is visible to administrators only. Approvers see what work is worth without seeing anyone's pay.

Your rules are settings, not code

The length of a standard day, the rounding increment, whether a week needs approval, whether a note is required on chargeable time, when the leave year starts and when a budget alert fires are all settings for your organisation. Changing one does not need a new release.

Questions people ask

Who is ReliTime for?

Engineering and technical consultancies registered for GST in India that bill their clients for time. Its time records are built to the Australian Fair Work record-keeping standard, so it also suits a consultancy with staff in Australia.

Is there a free trial?

No. We take you through a working demonstration organisation in a booked walkthrough, from a week of timesheets to a GST invoice, and answer your questions as we go.

How much does it cost?

Pricing is not published yet. Write to us and we will talk it through for the size of your team.

Where is our data kept?

ReliTime's servers and its database both run in Singapore.

Does it track or monitor employees?

No. There are no screenshots, no location tracking, no idle detection and no productivity scores. People record the hours they worked, and the application keeps that record straight.

Can it invoice clients outside India?

Yes. An invoice to an overseas client is a zero-rated export, under a letter of undertaking or with IGST paid as your registration says, and it can be raised in a currency other than the rupee.

Does it handle leave and public holidays?

Yes. Leave is requested and approved beside timesheets, balances build up through the year and carry over up to a limit you set, and public holidays are kept per organisation.

Can we bring in the jobs we already have?

A job's phases and tasks can be imported from a spreadsheet, and any job can be saved as a template for the next one like it.

Does it work on a phone?

Yes, in the phone’s browser. The weekly timesheet shows one day at a time on a small screen, with controls large enough to use in one hand.

See it on your own kind of work

ReliTime is sold with a walkthrough rather than a free trial. We will take you through a working organisation, from a week of timesheets through approvals and work in progress to a GST invoice, and answer your questions as we go.

Or write to hello@relitime.com.