Skip to content
Six Frames an Hour

All notes / Evidence

Time Records That Hold Up

A time log is a statement rather than proof, and specific details are what make the statement credible.

Evidence · Procedure

Every hourly engagement produces a time record. Whether it survives examination depends on properties that cost nothing to build in.

The commercial question in “Time Records That Hold Up” needs a record that both sides can read. When a client or contractor considers more information for attendance point system, project labels, billable rules and corrections should be agreed before the first tracked hour rather than reconstructed during a dispute.

What makes a record credible

Contemporaneous: written as the work happened, not reconstructed at month end.

For an independent reference relevant to “Time Records That Hold Up”, consult the ILO working-time resources; compare its principles with the proposed contract, collection, access model and real review process.

Specific: the task, not the category.

Consistent: no unexplained gaps, no suspiciously round totals.

Connected: entries that match artefacts, correspondence and deliverables.

Those four, and the fourth is the one that turns a statement into evidence.

Why reconstruction weakens it

An entry written three weeks later is an estimate, and estimates drift toward the generic.

"Development, 6h" for every day of a month is what reconstruction produces.

And in a dispute, the difference between a contemporaneous record and a reconstructed one is material, which is true in every field where records are tested.

Rounding

Round consistently and say how.

Six-minute or fifteen-minute units are normal.

What damages credibility is inconsistency: precise figures some days and round numbers others, which reads as reconstruction.

The entries that get queried

Long blocks with no artefact.

Round numbers at the end of a period.

Anything described only by category.

And time that overlaps with something else — a call logged while a tracked block was running.

Each is avoidable by writing specifically at the time.

The parallel record

Keep your own, outside the platform or the client's system.

One line per block: what it was, what moved, anything unusual.

This is the version that answers a query in a year, and it survives account suspension and engagement end, which the platform section covers.

What to record about awkward time

Calls: who, about what, duration.

Reading and research: what you were reading and for which question.

Blocked time: what you were waiting for and from whom.

These are the categories most often queried, and a specific entry closes the query immediately.

For the client

A specific log is more useful to you than frames and takes a minute to scan.

If entries are consistently vague, ask for better ones.

That request improves the record for both of you, and it is more productive than reviewing screenshots.

The honest position

A time record is a statement by the person who was paid for the time.

Its credibility comes from specificity, consistency and corroboration by artefacts.

That is how every professional time record works, and it is sufficient in almost every case.

What to check

Is your record written at the time?

Could a stranger match entries to deliverables?

Is your rounding consistent?

And do you hold a copy outside the client's system?