Translate | Elapsed Time, Decimal Hours, HH:mm and Duration Formats — Preserve How Long an Activity Lasts

Translating elapsed time and decimal hours accurately means preserving a duration rather than copying a familiar-looking number. The value 1.5 hours equals one hour and thirty minutes. The value 1.30 hours equals one hour and eighteen minutes. A field written 1:30 may represent one hour and thirty minutes, but it might instead be a clock time if the source defines it that way. Punctuation alone cannot tell you which quantity the author intended.

This guide explains how to translate durations, decimal-hour records and hours-and-minutes formats in educational texts, project reports, work logs, process descriptions and digital interfaces. Here, HH:mm is an illustrative label for hours and minutes, not a claim that every software system uses the same formatting syntax. The examples are fictional and are not payroll rules, legal deadline calculations, medical instructions or promises about a real service.

The method is to identify the type of time value, record its unit and format, preserve any start or end conditions, and then separate translation from numerical conversion. A reliable target text should tell the reader the same duration, waiting period, active time or accumulated effort as the source. It must not turn a length of time into a clock reading, a calendar month into thirty days, or an estimate into a guaranteed completion time.

A fifty-second orientation

For the fixed-unit calculations used here, one minute is 60 seconds and one hour is 3,600 seconds. NIST’s guidance on units used with the SI provides those relationships. Decimal hours use fractions of an hour: multiply the fractional part by 60 to obtain minutes. An hours-and-minutes field instead records separate components. The digits after its separator are not hundredths of an hour.

Before translating a time expression, ask: “Is this a duration, a timestamp, a calendar period or a recurrence?” Then ask which event starts or ends it. Those questions prevent a large class of errors before any calculation begins. A number that looks like time can still be the wrong kind of time for the sentence around it.

1. A duration and a clock reading answer different questions

A duration answers “How long?” A clock reading answers “When?” “The activity lasts two hours” gives a length of time. “The activity starts at 14:00” gives a position on a clock in an implied or explicit date and time-zone context. Replacing one with the other changes the information rather than merely changing its format.

The same visible string can occur in both roles. A source field labelled “Elapsed: 02:15” may mean two hours and fifteen minutes. A field labelled “Start: 02:15” may mean a clock time. Translate the label and value as a pair. If the label disappears in a compact layout, the remaining string may become ambiguous.

A useful working record spells the value out: elapsed duration, 135 minutes, displayed as 02:15. For a timestamp, record the date, time and reference information supplied by the source instead. Do not infer missing time-zone or date information merely to make the field look complete. The distinction belongs to the source’s data model, not to a translator’s preferred notation.

2. Decimal hours use base ten; minutes divide an hour into sixty parts

For 7.25 hours, the whole-hour component is seven. The remaining 0.25 hour multiplied by 60 gives fifteen minutes. The duration is therefore seven hours and fifteen minutes. In the same way, 7.50 hours means seven hours and thirty minutes, and 7.75 hours means seven hours and forty-five minutes.

This is why copying decimal digits into a minute field fails. A target written 7:25 for a source of 7.25 hours would add ten minutes if the target field means hours and minutes. Both strings look ordinary, so visual proofreading may not catch the difference.

Parse the quantity before formatting it. Keep the original value and its declared unit in the review notes, calculate a common unit such as minutes or seconds, and then create the requested target representation. That intermediate quantity gives the reviewer an independent reference. It also makes later format changes safer: a new display should be generated from the same duration, not from a previously rounded or ambiguously punctuated string.

3. The difference between 1.30 hours and 1:30 is not typographic

A decimal value of 1.30 hours consists of one hour plus 0.30 hour. The fraction is eighteen minutes, so the duration is 78 minutes. An hours-and-minutes value of 1:30 is 90 minutes. The twelve-minute difference arises from two different representations, not from a preference for a full stop or colon.

A source can be messy. Someone may type 1.30 while informally intending one hour and thirty minutes, even though the column is labelled decimal hours. Do not assume either the header or the entry is necessarily correct. Check surrounding entries, instructions or the originating system, and query the contradiction when it affects the result.

A precise query would ask: “Does 1.30 in this column mean 1.30 decimal hours or one hour thirty minutes?” This names the exact ambiguity and offers two testable interpretations. Avoid silently normalising the entry to whichever convention is common in your own location or previous projects. A familiar assumption is still an assumption unless the source supports it.

4. Convert minutes to decimal hours by division, not by changing punctuation

To express two hours and fifteen minutes as decimal hours, calculate 2 + 15/60. The result is 2.25 hours. To express two hours and seven minutes, calculate 2 + 7/60, giving approximately 2.1166667 hours. Some minute values do not have a short terminating decimal representation in hours.

That matters for precision. If the second duration is displayed as 2.12 hours, the display is rounded. Converting 2.12 hours back into hours and minutes gives two hours, seven minutes and twelve seconds. The twelve-second difference is a consequence of rounding, not evidence that the original conversion method was wrong.

Preserve the original precision where it matters. A source measured to the nearest minute should not silently become a claim of exact seconds after reverse conversion. Record whether a number is a measured value, a rounded display or a calculated equivalent. In a translation-only task, the safest choice may be to keep the source format and translate its label rather than introduce an unnecessary conversion and a new rounding decision.

5. Seconds reveal errors that minute-level review can miss

A decimal duration of 1.01 hours equals one hour plus 0.01 × 3,600 seconds. That fractional hour is 36 seconds. It is not one minute. A compact target of 1:01 would therefore be wrong if its format means hours and minutes.

Use total seconds as a verification representation when the source includes fractions smaller than a minute. For example, one hour, two minutes and three seconds becomes 3,723 seconds. Dividing by 3,600 gives approximately 1.0341667 hours. The three forms describe the same duration when precision is preserved.

Do not round away seconds before deciding whether they are material. In a classroom timetable, a rounded minute may be sufficient if the source is approximate. In a process record, a few seconds may distinguish two measurements. The document’s purpose and source precision control the choice. A translator should not make a consequential timing decision under the guise of simplifying a sentence.

6. Accumulated hours should not wrap around like a clock

A fictional test lasts 26 hours and fifteen minutes. Its duration is 1,575 minutes. Displaying only 02:15 because a clock-style format wraps after twenty-four hours would discard a full day of elapsed time. The target would describe 135 minutes rather than 1,575.

The correct display depends on the application. It might use 26 h 15 min, one day two hours fifteen minutes under a stated fixed-day convention, or a properly defined accumulated-hours field. Do not assume that every field containing a colon can accept hours greater than twenty-three. The actual interface or file format must be checked.

For a reader-facing article, spelling out the duration is often clearer than relying on an unfamiliar formatting code. For machine-readable data, preserve the system’s required representation. The translation task is to keep the same quantity in the correct layer: natural language for readers, validated syntax for the application. Neither layer should silently overwrite the other.

7. Add durations as quantities before formatting the total

Suppose three fictional activities last 35 minutes, 50 minutes and 45 minutes. Add them as minutes: 35 + 50 + 45 = 130. The combined duration is two hours and ten minutes. Adding visual strings as though they were decimal numbers would not reliably produce that result.

The same principle applies when source values mix formats. Convert 1.25 hours and 45 minutes into a common unit. The first is 75 minutes, so the total is 120 minutes, or two hours. Do not add 1.25 and 0.45 as decimal hours unless 0.45 really denotes a decimal fraction of an hour.

When a source already supplies a total, verify it without automatically replacing it. A disagreement can arise from excluded breaks, rounding, parallel activities or an error. Identify the reason before making a correction. The translator’s calculation is a diagnostic tool: it should reveal where the source needs clarification, not conceal a changed assumption inside a revised total.

8. Rounding each item and rounding the total are different policies

Imagine three activities of twenty minutes each. Their exact total is sixty minutes, or one hour. If each is first displayed as 0.33 hour and those rounded displays are then added, the sum is 0.99 hour. That equals 59 minutes and 24 seconds, losing 36 seconds from the exact total.

This example does not prescribe a reporting or billing policy. It shows why the policy must be known. A source may explicitly require rounding each line, rounding only the total, or applying another documented rule. Translate that instruction faithfully. Do not replace it with your own preferred arithmetic workflow when the rounding operation itself is part of the source specification.

For review, keep unrounded values where available and distinguish them from displayed values. A total that differs slightly from the sum of visible rows may be based on more precise underlying data. Before declaring it wrong, inspect the source’s rounding note. A careful translation preserves both the reported result and the explanation of how it was produced.

9. Clock subtraction needs complete endpoints

A fictional session starts at 09:10 and ends at 12:40 on the same date under the same time reference. Its elapsed duration is three hours and thirty minutes. The date and reference assumptions are part of this example; they should not be silently imported into a source that does not supply them.

Across midnight, the date matters. A source showing 23:30 followed by 00:15 may describe a forty-five-minute activity ending the next day, or it may be incomplete or incorrectly ordered. Do not subtract clock fields and publish a negative result without checking the dates.

Time-zone and offset changes introduce further distinctions between wall-clock readings and elapsed time. W3C’s discussion of time and time zones explains why reference information matters when representing and comparing times. This guide does not duplicate the existing time-zone article. Its practical rule is to preserve complete endpoints and use the source’s stated reference when checking a duration, rather than assuming that two clock strings alone establish how much time passed.

10. Elapsed time, active time and waiting time need separate labels

Return to the fictional session from 09:10 to 12:40. Suppose the source records a twenty-minute pause within that interval. The elapsed duration is 210 minutes, while active time is 190 minutes, assuming the pause is the only excluded interval. Active time is therefore three hours and ten minutes, not three hours and thirty minutes.

A translation should preserve the distinction rather than choosing one generic word such as time for both columns. “Completed in three and a half hours” can describe elapsed time, while “three hours and ten minutes of active work” describes a different measure. Either may be correct depending on what the source intends to report.

Also retain the rule about pauses. Some systems may include waiting in elapsed duration but exclude it from active processing. Others may define their fields differently. Translate the given definition, not a universal meaning you assume from a familiar label. A short field description can prevent an attractive target synonym from changing what is counted.

11. Effort measured in person-hours is not elapsed duration

If three people each work for two hours at the same time, their combined effort is six person-hours, while the elapsed interval is two hours. The same project therefore has different valid time measures. Replacing person-hours with hours without context can suggest that the project lasted six hours.

This distinction also matters for machine-hours, classroom contact hours and other accumulated measures. The unit combines time with what is being counted. A source should tell you whether simultaneous activities are added or treated as one interval. Preserve that definition when translating the total.

Do not derive a staffing plan or completion promise from effort alone. Six person-hours do not guarantee that six people can finish an activity in one hour, because task dependencies are not supplied by the arithmetic. For translation, the required discipline is simpler: keep the reported effort measure separate from duration, and avoid adding operational assumptions the source has not established.

12. Duration, recurrence and deadline language are different

“For two hours” describes a duration. “Every two hours” describes recurrence. “Within two hours” sets a completion window relative to a triggering event. “Two hours before” describes an offset from another event. The same words for two and hours can occur in all four expressions while the relationship changes.

A source about a software task might say “retry every two hours for twelve hours.” The recurrence interval and overall period must remain distinct. This guide does not specify a particular retry policy; it shows why a translation that says “retry for two hours every twelve hours” would reverse the structure.

Before translating, identify the event the time expression modifies. Which action repeats? Which period limits the repetition? What starts the count? The answers may be distributed across sentences. Keep them together in the working notes so a natural target-language rearrangement does not attach the interval to the wrong action. The grammar is part of the timing specification.

13. A calendar month is not a fixed number of hours

“One month” and “thirty days” are not universal equivalents. In a Gregorian calendar, different months have different numbers of days. A period from the first day of one month to the first day of the next can therefore differ in length depending on which month is involved. Do not convert a calendar period into a fixed duration without a stated rule.

Likewise, “two working days” depends on the source’s working calendar and definition of a working day. It does not automatically mean sixteen hours or forty-eight hours. A translator should preserve the phrase and any explanatory conditions rather than invent a schedule from familiar local practice.

Ask a narrow question when the distinction affects the deliverable: “Does this field mean a calendar period or an exact number of elapsed hours?” The answer determines whether conversion is appropriate at all. A calculator cannot resolve an undefined calendar policy. Clear source definitions must come before precise arithmetic.

14. Machine-readable duration tokens are syntax, not prose

In the W3C XML Schema duration format, PT1H30M represents one hour and thirty minutes. P1M represents a month, while PT1M represents a minute. The T separates the time components from the date-related components. Those letters are part of a defined syntax, not words to translate into another language.

Keep these strings unchanged when the task is to translate their human-readable labels or documentation. A target explanation may say “one hour and thirty minutes,” but the application value should remain in the format its schema requires. Do not translate the H or M, insert local unit words into the token, or assume a different application accepts the same grammar.

A review should ask two separate questions: is the explanation semantically correct, and is the protected token still valid for the receiving system? This article illustrates the XSD format rather than every duration standard or software library. Check the actual schema before changing machine data, even when a rewritten token looks easier for a human reader to understand.

15. Display labels should explain the representation they accompany

A column headed “Hours” may contain decimal hours, whole hours or a mixed hours-and-minutes display. The label alone may not be sufficient. For a user-facing translation, a fuller heading such as “Duration in decimal hours” can be helpful if the source definition supports it and the editorial brief allows clarification.

A field containing 02:30 should be labelled in a way that distinguishes duration from a start time. Conversely, a timestamp should not be labelled “time spent.” The numerical string may remain unchanged, but a mistranslated label tells the reader to interpret it differently.

Keep the data field and its explanation aligned through layout changes. If a unit is stated once in the table heading, every row depends on that heading. Moving a row into a mobile card without the heading can remove the representation context. A translation review should inspect the final presentation where possible, not just the list of isolated text strings.

16. Negative values need their own meaning, not an automatic correction

A negative time value may describe an offset, a difference between two measurements or a signed adjustment. It is not necessarily a negative physical duration. A fictional event countdown of minus ten minutes could indicate a position before a reference event, depending on the source convention.

Do not remove a minus sign because a duration is expected to be positive. First identify what the field measures. A source might report “completion variance: −15 minutes,” meaning an earlier finish relative to a planned time. Another field could use the opposite sign convention. Preserve the definition rather than adding words such as early or late from the sign alone.

If the source calls a value elapsed duration but shows a negative result, investigate the endpoints, field ordering and reference information. The translator should not silently swap start and end to produce a positive number. That would conceal a possible source error or a misunderstood data type. A precise query keeps the discrepancy visible until the source owner confirms what the field represents.

17. A duration range is not a pair of clock times

“An estimated duration of 1.5–2 hours” describes a range from ninety to one hundred twenty minutes. It does not schedule an activity between 01:30 and 02:00. The word duration and the unit define the role of the two endpoints.

Translate uncertainty along with the range. Estimated, approximately, at least and no more than do not mean the same thing. “Usually takes thirty minutes” is not a guarantee of completion within thirty minutes. A target that removes usually changes the strength of the claim even if the number is preserved.

For a precise threshold, retain the original representation when a rounded equivalent could alter its interpretation. If a source limit is ninety-five seconds, displaying only “about two minutes” may be unsuitable for the task. The acceptable rounding depends on the document’s purpose and authorised policy. Translation should not silently weaken or strengthen a time limit in pursuit of a cleaner-looking label.

18. A timecode is not necessarily ordinary elapsed-time notation

Some specialist fields resemble hours, minutes and seconds but include another component, such as a frame field. A four-part value should not be interpreted as hours, minutes, seconds and decimal fractions simply because that is familiar. Identify the format specified by the source.

This guide leaves frame-rate and drop-frame interpretation to the existing video frame-rate and timecode article. The translation lesson is to protect the complete structured value and its format label. Converting one component without understanding the format can change the referenced point in the material.

The same caution applies to a field that looks like a duration but is actually a record identifier or version string. Classify first, translate second. A familiar colon, point or sequence of digits is not proof of semantic type. The surrounding schema, table heading or source explanation should control the interpretation.

19. Worked case: a report with elapsed and active time

Use this invented source: “The session started at 09:10 and finished at 12:40 on the same date. A twenty-minute pause is included in elapsed time but excluded from active time. The report records 3 h 30 min elapsed and 3 h 10 min active. The active-time summary is displayed as approximately 3.17 decimal hours.”

The arithmetic is coherent. The total interval is 210 minutes. Removing the pause leaves 190 minutes, and 190/60 is approximately 3.1666667 hours, rounded to 3.17. The rounded decimal display should not be interpreted as exactly three hours and seventeen minutes.

A flawed target might say: “The session took 3.17 hours, including twenty minutes of active time.” That reverses the role of the pause, hides the elapsed-versus-active distinction and leaves readers uncertain about the format. A smooth sentence has replaced a structured measurement with an unclear narrative.

A repaired translation preserves start and end, the pause rule, both reported durations and the rounded-display status. The translator may calculate 190 minutes privately to check the source, but does not have to add that extra representation to the public text. The aim is to preserve the author’s information, not display every intermediate calculation the reviewer performed.

20. Worked case: a multi-day process without clock wrapping

Consider another fictional source: “The process began at 10:00 on day one and ended at 12:15 on day two. The exercise assumes the same fixed time reference throughout. Elapsed duration is 26 h 15 min. The report also shows the duration as 26.25 hours.”

Both duration representations agree. Twenty-six hours and fifteen minutes equals 26 + 15/60, or 26.25 hours. A target display of 02:15 would be incomplete if it discarded the first twenty-four hours. A target of 26.15 decimal hours would be different too: the decimal fraction 0.15 hour is nine minutes.

The phrase “same fixed time reference” is an explicit assumption of this teaching example. For a real source spanning reference changes, the complete timestamps and appropriate rules would be needed to verify elapsed time. Do not use the example as a shortcut for every civil-clock interval.

A reliable translation preserves the accumulated duration and the source’s reference assumptions. When a target system cannot display accumulated hours, use an approved representation that can, or retain a clear natural-language duration. Do not reduce the value to fit a convenient clock field. Interface limitations should be surfaced as implementation issues, not disguised as linguistic choices.

21. Worked case: effort and schedule in the same paragraph

A fictional project note states: “Three reviewers worked simultaneously for ninety minutes. Total review effort was 4.5 person-hours. The elapsed review window was 1.5 hours. A further thirty-minute waiting period followed before publication.” These are different measurements connected by a clear sequence.

Ninety minutes is 1.5 hours. Three reviewers at that duration produce 4.5 person-hours of effort. The waiting period adds half an hour to the interval before publication, but it does not automatically add half an hour of review effort. The source would need to state whether anyone was working during the wait.

A flawed translation might say that the review took five hours, combining effort and waiting as if both were elapsed duration. Another might omit person from person-hours, encouraging the same misunderstanding. Preserve the count of reviewers, their simultaneous participation, the effort measure and the waiting period separately.

This example also shows why not every source total should be checked by adding all visible time values. Some values overlap, some measure effort, and some measure elapsed intervals. Read the definitions before summing. Correct translation depends on the relationships among activities, not simply on the arithmetic ability to combine numbers.

22. Use a common-unit check without changing the source’s public format

A review record can store every fixed duration in seconds while leaving the translated document in the source’s chosen notation. For example, 01:45 under an hours-and-minutes definition, 1.75 hours and 105 minutes all map to 6,300 seconds. That common quantity lets you compare representations without publishing all of them.

Keep calendar periods separate from this fixed-unit ledger unless their conversion rule is explicitly defined. A month should not be assigned a convenient number of seconds just to make every row look uniform. The record can instead identify it as a calendar duration requiring an anchor or policy for further calculation.

A useful review record therefore includes type, source representation, source unit, normalised quantity when appropriate, rounding status, trigger and target display. It can be compact, but those fields prevent a later editor from treating every time-like number as the same data type. This is a reasoning aid, not a requirement to build a large technical system for every short translation.

23. Practice clinic with explained answers

Practice one: quarter hours. A source reports 4.25 decimal hours. The fractional 0.25 hour is fifteen minutes, so the duration is 4 h 15 min. A target of 4:25 would be wrong under an hours-and-minutes interpretation because it adds ten minutes.

Practice two: a decimal trap. A source explicitly defines 2.40 as decimal hours. The fractional 0.40 hour equals twenty-four minutes. The duration is 2 h 24 min, not 2 h 40 min. Preserve the format definition even if informal notation elsewhere looks similar.

Practice three: minutes to decimals. Convert 3 h 45 min into decimal hours for an approved display. Calculate 3 + 45/60 = 3.75. Do not write 3.45, because that would mean 3 h 27 min in decimal-hour notation.

Practice four: seconds. A duration of 0.05 hour equals three minutes, or 180 seconds. The value does not mean five minutes. Use the fixed-unit conversion to check the target before choosing how much detail the final wording needs.

Practice five: over twenty-four hours. A process lasts 49 h 30 min. The decimal-hour value is 49.5, and the total in minutes is 2,970. A clock-style display of 01:30 would omit forty-eight hours and must not be accepted as a faithful duration display.

Practice six: mixed formats. Add 1.5 hours and 40 minutes. Convert the first quantity to ninety minutes, giving a total of 130 minutes, or 2 h 10 min. Adding 1.5 and 0.40 as decimal hours would solve a different problem.

Practice seven: pause handling. A fictional two-hour session contains a fifteen-minute break excluded from active time. Elapsed time is 120 minutes; active time is 105 minutes. Translate both labels and the exclusion rule. Do not silently replace the elapsed total with the active total.

Practice eight: effort. Four people each work for thirty minutes simultaneously. Effort is two person-hours, while elapsed duration is half an hour. A target should preserve person-hours rather than imply that the simultaneous activity lasted two hours.

Practice nine: rounding. Three twenty-minute entries each display as 0.33 hour. Their displayed sum is 0.99 hour, while the exact total is one hour. Check whether the source policy sums underlying durations or rounded rows before proposing any correction.

Practice ten: a range. An estimated duration of 0.5–0.75 hour means approximately thirty to forty-five minutes. It is not a clock interval between 00:30 and 00:45. Preserve the estimate status and the duration label.

Practice eleven: machine syntax. The application stores PT1H30M using the XSD duration syntax described above. Translate the explanatory label, not the protected token. The human display can say one hour thirty minutes without altering the application value.

Practice twelve: a calendar period. A source says one calendar month. Do not translate it as thirty days unless an authorised rule explicitly defines that equivalence for the task. Keep the period type visible rather than inventing a fixed duration.

Practice thirteen: recurrence. The source says a task repeats every thirty minutes for two hours. Preserve the recurrence interval and the overall period as different relationships. Do not reverse them, and do not infer an exact occurrence count unless the source defines whether the starting and ending boundaries are included.

Practice fourteen: ambiguous notation. A table labelled decimal hours contains 1.30 beside an instruction that appears to mean ninety minutes. Preserve the discrepancy in a source query. Correct translation begins with resolving the source interpretation, not with guessing which field is more trustworthy.

24. Frequently asked duration-translation questions

Is 1.5 hours the same as 1:50? No. In an hours-and-minutes representation, 1.5 hours is 1:30. The decimal fraction must be multiplied by sixty before it becomes a minute field.

Should all time expressions be converted into decimal hours? No. Use the representation appropriate to the source and assignment. A natural-language duration may be clearer for readers, while a data system may require a particular numeric or structured format.

Can a duration exceed twenty-four hours? Yes. Elapsed or accumulated time is not restricted to one clock cycle. The display must preserve the whole duration rather than wrapping it like a time of day.

Why can a rounded decimal fail to convert back exactly? Rounding removes information. Preserve the source quantity or sufficient internal precision when an exact comparison is needed, and distinguish rounded displays from measured values.

Can I calculate working days as eight hours each? Only when the source explicitly defines that working-day duration for the task. Do not import a local schedule or assumption into a different document.

What is the best final check? Read the target with all labels restored. It should describe the same type of time, the same quantity, the same trigger and the same uncertainty or rounding rule. Matching digits alone cannot establish that the duration survived.

25. Continue through the existing translation system

The broader factual discipline is developed in Translate | Names, Numbers, Dates and Units, within Master Art of Translation. For clock-reference questions, use Time Zones, UTC Offsets and Daylight Saving Time. The Vocabulary Learning Hub and How English Works support precise distinctions between duration, recurrence, deadlines and the grammatical relationships around them.

A good duration translation leaves the reader with the same answer to “How long?”, while preserving any different questions the source also answers: when, how often, after which event, and under what conditions. Separate those questions, protect the source representation and verify conversions in a common unit where appropriate. Then write naturally. The language can change; the time relationship should not.