The Description Field

Most time entries carry a description field. In most organisations most of them are empty, and of the ones that are filled in a large proportion say something like admin, project work, catch-up or various.

The record described in “The Description Field” should be created close enough to the work that people are not reconstructing a polished week from memory. When teams assess how teams evaluate chronemics definition for chronemics definition, they should keep entry, project selection and correction simple, while explaining which optional activity data is collected and how employees can review it.

That line is the only part of the record that says what was actually done. Without it an entry asserts that eight hours were spent on a code, which is a claim nobody can evaluate, support or defend. With it, the same entry becomes a statement a reader can check against something.

For a separate benchmark relevant to “The Description Field”, consult the AICPA audit and assurance resources. Use it to test record quality, approvals, retention, employee rights and exception handling against the real workflow rather than treating a software report as self-explanatory evidence.

What the line is for, by destination

For billing, it is the thing the client reads. Engagement terms in most professional contexts require narratives of a specified quality, and entries that fail that test are written off — not disputed, written off, by the firm's own billing partner before the invoice goes out, because sending them invites a fight.

For grant and contract claims, it is the evidence that the hours were spent on the funded activity rather than on something adjacent. "Project work" against a work package does not establish that, and an auditor will say so.

For internal purposes, it is the thing that lets anybody understand the data a year later. Allocation codes decay — teams rename them, reuse them, retire them — and a narrative survives the code it was attached to.

What a usable narrative contains

The activity, as a verb. The object: which document, which site, which component, which matter. And where it matters, who with.

"Drafted section 4 of the technical annex" is usable. "Site attendance, unit 12, meter replacement" is usable. "Call with M. Rossi re: delivery schedule" is usable. Each is under ten words and each tells a reader something the code could not.

What makes a narrative unusable is that it describes the category rather than the work, and the category is already in the code. Writing "project work" against a project code says nothing that was not already recorded.

Why they are empty

Because the field is optional and nothing happens when it is left blank. Approval does not require it, the submission goes through, and the consequence arrives in a different department months later.

Also because it is tedious at the end of the week, which is when most people fill it in, and because at that distance the person genuinely does not remember what they did on Monday beyond the code. The empty narrative is downstream of the reconstruction problem and improves whenever the recording distance shortens.

Making them appear

Require them where they matter and nowhere else. A blanket mandatory field across all entries produces "various" at scale, which is worse than empty because it looks like compliance. Requiring them only on billable, grant-funded and capitalised codes concentrates the effort where it pays and leaves internal codes alone.

Set a minimum length and reject the known-useless strings. A short block list — various, admin, work, misc, catch-up, project work, as discussed — costs nothing and removes most of the noise. Show the person their last few narratives on the same code so they can see what they have been writing and whether it distinguishes one day from another.

And give feedback from downstream. The single most effective intervention available is telling people whose narratives were written off at invoice that they were written off, with the amount. It is rarely done because the information lives in finance and the person lives in delivery, and the connection is a report nobody has built.

The review that costs an afternoon

Pull a quarter's entries on billable or claimable codes. Count the proportion with an empty narrative, the proportion matching a useless string, and the median length in words.

Then take the hundred highest-value entries by cost and read the narratives. This is the part that produces the uncomfortable finding, and it is also the part that produces agreement to change something, because a partner or a finance director reading a six-thousand-pound line that says "various" does not need any further persuasion.

What ends up in a free-text field

A description field accumulates things nobody intended to store: names of third parties, details of a colleague's absence, commentary on a client, occasionally something about a person's health. It is free text written quickly, and it is retained for as long as the hours are.

This matters when somebody exercises an access right, when a client requests the detail behind an invoice, or when records are disclosed in a dispute, because the narrative goes with them. A short instruction — describe the work, not the people — plus a periodic look at what is actually in the field is proportionate and rarely done. The alternative is discovering the content at the point of disclosure, when nothing can be removed.