For engineering and infrastructure consultancies

Time tracking built for engineering consultancies.

Log hours against projects and phases, approve timesheets, and turn billable time into GST invoices. A record is never overwritten: a correction is a new entry, with a reason and a name, and the original stays.

The weekly timesheet: tasks for several client jobs down the side, hours for each day of the week, and the week's total beside the button to submit it.

What the record guarantees

Why ReliTime

It was built inside an engineering consultancy, for its own timesheets, approvals and invoices, and it is used for them every week. These are the six things that came from that.

Records you can defend

Every correction supersedes the entry before it, carrying a reason and the name of whoever made it. No time entry is ever deleted. Approved weeks lock, and the database itself enforces it, so the application cannot switch it off.

How the record is kept

It does not watch anyone

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

Why it refuses to

GST invoicing done properly

CGST and SGST or IGST worked out from both parties' registrations, exports zero-rated, invoice numbers issued consecutively, credit and debit notes, and disbursements kept out of the taxable value under Rule 33.

GST invoicing in detail

Built for engineering work

Jobs, phases and tasks budgeted in hours, and each job in money as well. Rates that change on a date without rewriting history, and work in progress that keeps time that was never chargeable apart from time that was written off.

Every feature

Figures that do not bluff

An hour with no rate is named, never billed at nothing. Rounding happens on the invoice, never to the hours on the record. A figure nobody set shows as missing rather than as a plausible zero.

What that looks like

Designed for the person filling it in

A keyboard-first week, a draft that is only saved when you say so, undo rather than "are you sure?", and a phone view with buttons made for one hand.

The design decisions

Approval that means something

A week is submitted, approved and locked. Reopening a locked week needs an authorisation countersigned by someone other than the person whose week it is, and it can be used once. Every step is in the audit log, with who did it and when.

The approvals queue: submitted weeks listed by person, each with its hours, waiting for a decision.

Know what each job is worth

Work in progress prices every hour at the rate in force on the day it was worked. It shows what is billable, what has already been billed, and what was never chargeable, with the reason for each.

The work in progress report: each client job with the hours worked, the billable value, and how much is still to bill.

Tax invoices that hold up

Invoices are drawn from approved, locked time. The document carries what CGST Rule 46 asks for, including the SAC code for each line and the authorised signatory. It is issued under the next number in the series, and corrected only by a credit or debit note.

A tax invoice on screen, with the supplier and recipient GSTINs, lines with SAC codes, and the tax worked out below.

Leave, holidays and who is away

Leave is requested and approved in the same place as time. Balances build up through the year and carry over up to the limit you set, and a timeline shows who is away before anybody approves the next request.

The leave screen: balances by leave type and a month timeline showing who is away on which days.

Fill the week in from site

On a phone, the week shows one day at a time, with buttons large enough to use in one hand. Nothing is saved until Save is pressed, so a figure typed and corrected on the way never becomes two entries on the record.

The weekly timesheet on a phone, showing a single day with its tasks and hours.

Designed for the people who fill it in

A timesheet is used every day by the people with the least reason to care about it, so every screen is built to be quick and hard to get wrong.

  • Type a week without touching the mouse, and save it when it is right.
  • Undo what you just saved, instead of confirming everything first.
  • See a day as blocks of time, and the tasks you use most at the top of the list.
  • Every screen is checked on a phone and at a desk, in light and dark, before each release.

The design decisions, one by one

The day view: a timeline from morning to evening with the day's work drawn as blocks, each labelled with its times and task.

From the client to the invoice, in one place

Each step feeds the next, so the invoice is built from the same hours that were approved. You never retype them into something else.

  1. A job's budget panel: hours quoted, booked and remaining, the share consumed, and one phase listed as past its budget.

    Step 1 of 7 · Nisha, administrator

    Nisha sets up the job

    A client, a job with phases and tasks, a quote in hours, and the engineers assigned to it.

    Next: Ravi fills in his week

  2. Ravi's weekly timesheet: tasks for several client jobs down the side and his hours for each day of the week.

    Step 2 of 7 · Ravi, engineer

    Ravi fills in his week

    Hours typed into the week, saved when they are right, submitted when the week is done.

    Previous: Nisha sets up the jobNext: Meera approves it

  3. The approvals queue: expense claims and submitted weeks, each waiting for a decision.

    Step 3 of 7 · Meera, approver

    Meera approves it

    The week is approved and locked, and from then on nothing in it can change.

    Previous: Ravi fills in his weekNext: The hours are priced

  4. The work in progress report: hours worked, their value, what is still to bill, and utilisation by person.

    Step 4 of 7 · Meera, approver

    The hours are priced

    Every hour at the rate in force on the day, and what is still to bill.

    Previous: Meera approves itNext: Nisha sees what is ready to bill

  5. The ready to invoice panel: each client with the hours worked, the billable hours and the value, beside a button to create a draft.

    Step 5 of 7 · Nisha, administrator

    Nisha sees what is ready to bill

    Every client with approved, locked work waiting, and what the invoice would come to.

    Previous: The hours are pricedNext: She raises a GST invoice

  6. A tax invoice on screen, with the supplier and recipient GSTINs, lines with SAC codes, and the tax worked out below.

    Step 6 of 7 · Nisha, administrator

    She raises a GST invoice

    CGST and SGST or IGST worked out, numbered in the series, and emailed as a PDF.

    Previous: Nisha sees what is ready to billNext: The payment comes in

  7. The receivables ledger: the total outstanding, how overdue it is, and each invoice with what was billed, paid and is still owed.

    Step 7 of 7 · Nisha, administrator

    The payment comes in

    Recorded against the invoice, with the ledger showing what is still owed.

    Previous: She raises a GST invoice

Follow one week, step by step

Made for firms that bill by project and phase

ReliTime suits consultancies of five to two hundred people whose work is long projects in phases, billed to clients at rates that change over time.

Engineering consultancies

Budgets by job, phase and task, rates that change on a date without rewriting history, and work in progress that shows what is still to bill.

For engineering firms

Rail and infrastructure

Multi-year assurance work split into phases, site crews filling in their week on a phone, and start and finish times where the rules ask for them.

For rail and infrastructure

A free timesheet template

A weekly Excel timesheet by project and phase, with the totals worked out for you. Free to download, with no sign-up, whether or not you choose ReliTime.

Get the template

Security and your data

Hosted in Singapore

The application's servers and its database both run in Singapore.

A second factor for administrators

Owners and administrators sign in with an authenticator app as well as a password.

Your organisation, kept apart

Each organisation's data is separated where it is read, not by a filter somebody has to remember to add.

Records that stay

Time entries and approvals cannot be deleted, even by the application itself: the database refuses the request.

More on security and your data

See it on your own kind of work

We set ReliTime up with a walkthrough rather than a sign-up form. We will take you through a working organisation, from a week of timesheets through approvals and work in progress to a GST invoice, answer your questions as we go, and set up yours.

Or write to hello@relitime.com.