<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-IN">
  <title>ReliTime blog</title>
  <subtitle>Articles on working hours, fatigue and safety, estimating and overruns, and record keeping for engineering consultancies, with sources for every claim.</subtitle>
  <link rel="self" type="application/atom+xml" href="https://relitime.com/blog/feed.xml"/>
  <link rel="alternate" type="text/html" href="https://relitime.com/blog/"/>
  <id>https://relitime.com/blog/</id>
  <updated>2026-10-04T02:51:32.741Z</updated>
  <author><name>Aadeepra Rail Assure Private Limited</name></author>
  <entry>
    <title>Two kinds of unbilled hour, and why to keep them apart</title>
    <link rel="alternate" type="text/html" href="https://relitime.com/blog/two-kinds-of-unbilled-hour/"/>
    <id>https://relitime.com/blog/two-kinds-of-unbilled-hour/</id>
    <published>2026-10-04T02:51:32.741Z</published>
    <updated>2026-10-04T02:51:32.741Z</updated>
    <author><name>Aadeepra</name></author>
    <summary>An hour that was never chargeable and an hour you chose not to charge look the same on an invoice. They mean very different things for the business, and a timesheet should keep them separate.</summary>
    <content type="html">&lt;p&gt;Every engineering consultancy has hours that never reach an invoice. Most timesheets record all of them the same way: a tick box marked &amp;quot;non-billable&amp;quot;. That box is doing two jobs at once, and it hides the more important one.&lt;/p&gt;
&lt;h2&gt;Two different facts behind one tick box&lt;/h2&gt;
&lt;p&gt;Some hours were never meant to be charged to anybody. Others were chargeable, and somebody decided not to charge for them. Both end up off the invoice, but they answer different questions.&lt;/p&gt;
&lt;figure class=&quot;blog-table&quot;&gt;&lt;div class=&quot;blog-scroll&quot; tabindex=&quot;0&quot; role=&quot;group&quot; aria-label=&quot;Table&quot;&gt;&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th scope=&quot;col&quot;&gt;Question&lt;/th&gt;&lt;th scope=&quot;col&quot;&gt;Never chargeable&lt;/th&gt;&lt;th scope=&quot;col&quot;&gt;Chargeable, then written off&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;th scope=&quot;row&quot;&gt;Examples&lt;/th&gt;&lt;td&gt;Internal admin, bids and proposals, training&lt;/td&gt;&lt;td&gt;Extra review rounds, fixing an error, a goodwill discount&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th scope=&quot;row&quot;&gt;What it is&lt;/th&gt;&lt;td&gt;A property of the work&lt;/td&gt;&lt;td&gt;A decision about the work&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th scope=&quot;row&quot;&gt;Who decides&lt;/th&gt;&lt;td&gt;Known when the time is recorded&lt;/td&gt;&lt;td&gt;Somebody, later, for a reason&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th scope=&quot;row&quot;&gt;What it tells you&lt;/th&gt;&lt;td&gt;Where capacity goes&lt;/td&gt;&lt;td&gt;Where revenue was given away&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/div&gt;&lt;/figure&gt;
&lt;h2&gt;Never chargeable: a category on the hour&lt;/h2&gt;
&lt;p&gt;Time spent on a bid, on training or on internal admin was never going to be billed, and that is fine - it is part of running a practice. What matters is knowing which kind it was. &amp;quot;Non-billable&amp;quot; alone cannot tell you whether the month went on proposals or on paperwork, and those call for different conversations.&lt;/p&gt;
&lt;p&gt;So the useful record is not a yes or no but a category, chosen when the time is entered by the person who did the work. It is a fact about the hour, and it should stay with it.&lt;/p&gt;
&lt;h2&gt;Written off: a decision with an author&lt;/h2&gt;
&lt;p&gt;A write-off is different. The work was done for a client, on their job, and would normally be charged. Then the project lead decides to give some of it away - because the brief changed, because a mistake needed fixing, or to keep a good client happy.&lt;/p&gt;
&lt;p&gt;That is a commercial decision, and it deserves to be recorded as one: how much, on which job, by whom, and why. Recording it by quietly flipping the original hours to &amp;quot;non-billable&amp;quot; loses all four.&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;A write-off recorded as non-billable time makes the job look as if the work was never chargeable - and makes the person who decided invisible.&lt;/p&gt;&lt;/blockquote&gt;
&lt;h2&gt;Why mixing them up costs you&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;The margin looks better than it is.&lt;/strong&gt; If given-away work is reclassified as never chargeable, the job appears to have hit its rate. The revenue you chose not to collect simply disappears from view.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Patterns stay hidden.&lt;/strong&gt; Repeated write-offs on one client, or one kind of work, are exactly what should change your next quote. You cannot see them if they look like internal time.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;The record gets edited.&lt;/strong&gt; Changing the billable flag on hours after the fact alters the time record itself, rather than adding a decision on top of it.&lt;/li&gt;&lt;/ul&gt;
&lt;h2&gt;A simple way to keep them apart&lt;/h2&gt;
&lt;ol&gt;&lt;li&gt;Record every hour as it was worked: chargeable, or never chargeable with a category.&lt;/li&gt;&lt;li&gt;Leave the hours alone afterwards. They are a record of the work, not of the commercial outcome.&lt;/li&gt;&lt;li&gt;When you decide not to charge for chargeable work, record a write-off against the job with an amount and a reason.&lt;/li&gt;&lt;li&gt;Review both in your work-in-progress report: never-chargeable hours by category, and write-offs by job and client.&lt;/li&gt;&lt;/ol&gt;
&lt;aside class=&quot;callout callout-note&quot; aria-label=&quot;Note&quot;&gt;&lt;p&gt;Unpaid rework is a judgement call worth naming. If the fix was never going to be charged, record it as non-billable on the client job, so the job carries its true cost. If it was chargeable and you are choosing not to bill it, that is a write-off.&lt;/p&gt;&lt;/aside&gt;
&lt;h2&gt;How ReliTime handles this&lt;/h2&gt;
&lt;p&gt;In ReliTime a non-billable hour must name a category from your organisation’s list, such as bid and proposal or training. A phase can fix the category - booking to an internal Training phase has already said what the time was - and on a client-facing phase the person chooses. A write-off is a separate record on the job with its own author and reason, and it never changes the time entries. The work-in-progress report shows the two apart, so margin moves when something is given away and you can see who gave it.&lt;/p&gt;
&lt;p&gt;However you track time, the rule is worth adopting: an hour that was never chargeable and an hour you chose not to charge are two different facts. Keep them in two different places.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>Quote the next job from the hours of the last one</title>
    <link rel="alternate" type="text/html" href="https://relitime.com/blog/quote-the-next-job/"/>
    <id>https://relitime.com/blog/quote-the-next-job/</id>
    <published>2026-10-03T23:23:02.564Z</published>
    <updated>2026-10-03T23:23:19.765Z</updated>
    <author><name>Aadeepra</name></author>
    <summary>Most engineering estimates are written from memory, and memory forgets the review cycles, the rework and the close-out. The hours you already recorded do not.</summary>
    <content type="html">&lt;p&gt;Ask an engineer how long a site survey takes and you will get an honest answer: the time it took the last time it went well. That is the estimate that goes into the quote. Then the job runs over, and nobody is quite sure why, because every individual task &amp;quot;took about as long as it should&amp;quot;.&lt;/p&gt;
&lt;p&gt;The answer is usually already written down. If your team records time against the same phases you quote with, every finished job is a record of what that kind of work actually costs. This post is about reading that record before you write the next quote.&lt;/p&gt;
&lt;h2&gt;Why estimates from memory run short&lt;/h2&gt;
&lt;p&gt;Memory keeps the work and drops the overhead around it. The parts that go missing are remarkably consistent:&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Review and comment cycles.&lt;/strong&gt; The first draft is remembered; the third round of client comments is not.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Rework.&lt;/strong&gt; Correcting something is filed mentally under the original task, so it never shows up as its own line.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Coordination.&lt;/strong&gt; Calls, site access, chasing information - real hours that belong to no deliverable.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Close-out.&lt;/strong&gt; Final issue, as-built updates and handover packs, which happen after everybody has moved on.&lt;/li&gt;&lt;/ul&gt;
&lt;p&gt;None of these is a mistake by the person estimating. They are simply the parts of a job nobody pictures when they imagine doing it.&lt;/p&gt;
&lt;h2&gt;Record time the way you quote&lt;/h2&gt;
&lt;p&gt;Recorded hours only help an estimate if they can be lined up against it. If the quote is built from phases - survey, design, review, close-out - the timesheet needs the same phases. Hours booked to a single job-wide line tell you the job ran over; hours booked by phase tell you where.&lt;/p&gt;
&lt;p&gt;It is worth one more step: give each phase a budget on the day the job is planned, even a rough one. A budget is what turns a pile of hours into a comparison.&lt;/p&gt;
&lt;h2&gt;Compare budget with actual, phase by phase&lt;/h2&gt;
&lt;p&gt;When a job closes, put the budget and the actual hours side by side for each phase. A made-up example of what that tends to look like:&lt;/p&gt;
&lt;figure class=&quot;blog-table&quot;&gt;&lt;div class=&quot;blog-scroll&quot; tabindex=&quot;0&quot; role=&quot;group&quot; aria-label=&quot;Table&quot;&gt;&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th scope=&quot;col&quot;&gt;Phase&lt;/th&gt;&lt;th scope=&quot;col&quot; class=&quot;num&quot;&gt;Budget (hours)&lt;/th&gt;&lt;th scope=&quot;col&quot; class=&quot;num&quot;&gt;Actual (hours)&lt;/th&gt;&lt;th scope=&quot;col&quot; class=&quot;num&quot;&gt;Difference&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;th scope=&quot;row&quot;&gt;Site survey&lt;/th&gt;&lt;td class=&quot;num&quot;&gt;40&lt;/td&gt;&lt;td class=&quot;num&quot;&gt;38&lt;/td&gt;&lt;td class=&quot;num&quot;&gt;-2&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th scope=&quot;row&quot;&gt;Design&lt;/th&gt;&lt;td class=&quot;num&quot;&gt;120&lt;/td&gt;&lt;td class=&quot;num&quot;&gt;131&lt;/td&gt;&lt;td class=&quot;num&quot;&gt;+11&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th scope=&quot;row&quot;&gt;Review and client comments&lt;/th&gt;&lt;td class=&quot;num&quot;&gt;20&lt;/td&gt;&lt;td class=&quot;num&quot;&gt;46&lt;/td&gt;&lt;td class=&quot;num&quot;&gt;+26&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th scope=&quot;row&quot;&gt;Close-out and handover&lt;/th&gt;&lt;td class=&quot;num&quot;&gt;10&lt;/td&gt;&lt;td class=&quot;num&quot;&gt;24&lt;/td&gt;&lt;td class=&quot;num&quot;&gt;+14&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/div&gt;&lt;/figure&gt;
&lt;aside class=&quot;callout callout-note&quot; aria-label=&quot;Note&quot;&gt;&lt;p&gt;The figures above are an illustration, not data from a real job.&lt;/p&gt;&lt;/aside&gt;
&lt;p&gt;Read across one job and the obvious conclusion is &amp;quot;design ran a little over&amp;quot;. Read across five similar jobs and the pattern is usually somewhere else: the same one or two phases overrun every time, by roughly the same proportion. That proportion is the most useful number you can bring to the next quote.&lt;/p&gt;
&lt;h3&gt;Three questions to ask of the comparison&lt;/h3&gt;
&lt;ol&gt;&lt;li&gt;Which phases ran over on most jobs, not just this one?&lt;/li&gt;&lt;li&gt;Is the overrun a fixed number of hours or a share of the phase? Review cycles often scale with the size of the design; close-out often does not.&lt;/li&gt;&lt;li&gt;Was the work in the quote at all? A phase with no budget cannot run over - it just quietly costs money.&lt;/li&gt;&lt;/ol&gt;
&lt;h2&gt;Keep what you sold apart from what you plan to spend&lt;/h2&gt;
&lt;p&gt;A job is quoted before its phases are planned in detail, so the job total and the sum of the phase budgets are often different numbers. That gap is information, not an error. A 200-hour quote broken into phases that add up to 260 hours is worth seeing on the day it is planned, not three months later when the invoice goes out short.&lt;/p&gt;
&lt;h2&gt;Watch it while the job runs, without stopping the record&lt;/h2&gt;
&lt;p&gt;The comparison is most useful while there is still time to act. A warning when a phase reaches, say, 75 percent of its budget gives the project lead a chance to talk to the client about scope before the hours are gone.&lt;/p&gt;
&lt;aside class=&quot;callout callout-warning&quot; aria-label=&quot;Warning&quot;&gt;&lt;p&gt;Do not stop people recording hours because a budget is used up. The work still happens; refusing the entry only makes the record say it did not. A budget is an expectation, and an honest timesheet is how you find out it was wrong.&lt;/p&gt;&lt;/aside&gt;
&lt;h2&gt;How ReliTime handles this&lt;/h2&gt;
&lt;p&gt;In ReliTime a job is broken into phases and tasks, and time is recorded against the task. A job can carry a budget in hours and in money, each phase and task can carry its own hours budget, and the jobs screen shows budget against booked hours at every level - including the gap between the job total and the sum of its phases. A warning appears when a booking takes a level past the threshold you set, and the hours are still recorded. When you start a new job from a template, the phase and task budgets come with it, so the next estimate can begin from the last one instead of a blank page.&lt;/p&gt;
&lt;p&gt;Whatever tool you use, the habit is the same: record time the way you quote, compare them when the job closes, and let the pattern - not memory - set the next number.&lt;/p&gt;</content>
  </entry>
  <entry>
    <title>The 50-hour wall: what long weeks really produce</title>
    <link rel="alternate" type="text/html" href="https://relitime.com/blog/the-50-hour-wall/"/>
    <id>https://relitime.com/blog/the-50-hour-wall/</id>
    <published>2026-09-28T11:00:31.132Z</published>
    <updated>2026-09-28T11:00:31.132Z</updated>
    <author><name>Aadeepra</name></author>
    <summary>A century-old study of munitions workers found weekly output kept pace with hours only up to about 49 a week. Here&#39;s what that means for engineering consultancies, and what to measure in your own firm.</summary>
    <content type="html">&lt;p&gt;Deadlines in engineering consultancy have a familiar shape. A submission is due, a client review moves forward, or a hazard log has to close before a gate. The instinct is to add hours: a late night, a Saturday, then a Sunday. The assumption behind it is simple. More hours in, more work out.&lt;/p&gt;
&lt;p&gt;One of the best-documented tests of that assumption is more than a century old.&lt;/p&gt;
&lt;h2&gt;A natural experiment in the munitions factories&lt;/h2&gt;
&lt;p&gt;During the First World War, British munitions plants ran extraordinary hours. Weeks of 70 hours or more were common for men, and Sunday work was brought back. The government set up the Health of Munition Workers Committee to study fatigue, and its investigators recorded workers&amp;#39; actual weekly hours alongside their measured output. Most workers were paid by the piece, so output was counted precisely.&lt;/p&gt;
&lt;p&gt;In 2014, Stanford economist John Pencavel went back to those records and analysed them with modern statistical methods. His paper, The Productivity of Working Hours, was published in the Economic Journal in 2015. The core data covers four groups of workers in one large factory over about a year in 1916, with weekly hours ranging from 24 to more than 72.&lt;/p&gt;
&lt;h2&gt;What the data showed&lt;/h2&gt;
&lt;p&gt;Three findings stand out.&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Up to about 49 hours a week, output rose in step with hours. Each extra hour added about as much as the one before.&lt;/li&gt;&lt;li&gt;Beyond that point, each extra hour added less. Weekly output peaked at around 63 hours, and a 70-hour week produced little more than a 56-hour week.&lt;/li&gt;&lt;li&gt;A day of rest mattered on its own. Holding total hours constant, weeks that included Sunday work produced about 10% less. A 48-hour week over six days produced slightly more than a 70-hour week over seven.&lt;/li&gt;&lt;/ul&gt;
&lt;p&gt;In other words, the last 14 hours of a 70-hour week added almost nothing, and the missing rest day made things worse.&lt;/p&gt;
&lt;h2&gt;Does this apply to engineers?&lt;/h2&gt;
&lt;p&gt;Not directly, and it&amp;#39;s worth being clear about why. These were mostly manual, repetitive jobs, done in wartime, by workers whose output could be counted in shells. Pencavel himself stresses that his sample is small and that the threshold varies with the worker and the type of work.&lt;/p&gt;
&lt;p&gt;Knowledge work is harder to measure, and fatigue shows up differently. A tired machinist produces fewer parts. A tired engineer may produce the same number of pages, with more mistakes in them. Those mistakes surface later as review comments and rework, and in assurance work, as errors that someone else has to catch.&lt;/p&gt;
&lt;p&gt;The modern evidence Pencavel cites points the same way. A US study of more than 10,000 workers found that, after allowing for other factors, people working at least 12 hours a day had a 37% higher injury hazard rate, and those working at least 60 hours a week a 23% higher rate. A study of hospital nurses linked shifts longer than 12 hours to more errors.&lt;/p&gt;
&lt;p&gt;So 49 hours shouldn&amp;#39;t be read as a rule for your office. The shape of the curve is the lesson: beyond some point, extra hours buy less and cost more.&lt;/p&gt;
&lt;h2&gt;What a consultancy can do with this&lt;/h2&gt;
&lt;ol&gt;&lt;li&gt;Measure actual hours, not planned ones. The munitions researchers separated scheduled hours from time actually worked, and that distinction is where the insight came from. Timesheets that only record what a job was budgeted for can&amp;#39;t tell you when people are past the wall.&lt;/li&gt;&lt;li&gt;Treat sustained long weeks as a planning signal. One heavy week before a deadline is normal. Several in a row usually means an estimate or a resourcing plan was wrong, and the fix belongs in the next estimate, not in more overtime.&lt;/li&gt;&lt;li&gt;Protect a full day off. In the data, the rest day had an effect separate from total hours.&lt;/li&gt;&lt;li&gt;Look at quality alongside quantity. Compare review findings and rework on projects that ran long weeks with those that didn&amp;#39;t. That is the knowledge-work version of counting shells.&lt;/li&gt;&lt;li&gt;Be honest in fixed-fee pricing. If a job only fits its budget at 60-hour weeks, the budget is already overrun.&lt;/li&gt;&lt;/ol&gt;
&lt;h2&gt;The takeaway&lt;/h2&gt;
&lt;p&gt;The committee studying these factories concluded that cutting hours would cost little or no output, and Pencavel&amp;#39;s analysis largely backs them up. Long hours feel productive, but beyond a point they mostly add fatigue.&lt;/p&gt;
&lt;p&gt;The first step for any firm is knowing where its own people sit on that curve. ReliTime records actual hours against every job and phase, so you can see when a team has spent too long past 50 hours a week.&lt;/p&gt;
&lt;section class=&quot;sources&quot; aria-labelledby=&quot;sources-heading&quot;&gt;&lt;h2 id=&quot;sources-heading&quot;&gt;Sources&lt;/h2&gt;&lt;ol&gt;&lt;li id=&quot;source-1&quot;&gt;&lt;a href=&quot;https://doi.org/10.1111/ecoj.12166&quot; rel=&quot;noopener&quot;&gt;The Productivity of Working Hours (Pencavel, Economic Journal, 2015)&lt;/a&gt;&lt;/li&gt;&lt;li id=&quot;source-2&quot;&gt;&lt;a href=&quot;https://docs.iza.org/dp8129.pdf&quot; rel=&quot;noopener&quot;&gt;The Productivity of Working Hours, free working paper (IZA DP 8129)&lt;/a&gt;&lt;/li&gt;&lt;li id=&quot;source-3&quot;&gt;&lt;a href=&quot;https://res.org.uk/resources-page/long-working-hours-take-their-toll-on-people--s-health-and-job-performance--evidence-from-first-world-war-munition-workers.html&quot; rel=&quot;noopener&quot;&gt;Royal Economic Society summary&lt;/a&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/section&gt;</content>
  </entry>
</feed>
