The account that follows is fiction, written to illustrate a point about planning. Its characters are roles, not real people, and none of it describes an actual organisation. It follows a small team that keeps a city-by-city directory of advocates, and it shows what happened when the team stopped trusting its sense of timing and began checking each estimate against the clock. The subject is time estimation. It contains no legal advice and no view on any advocate, practice area or case.
The assignment
The team had four members: an editor, a researcher, a data entry assistant and a part-time developer. Their job was to add a new batch of city pages to the directory, each one a tidy listing of advocates in a given field, with practice areas, contact routes and a short introduction. The editor looked at the calendar and announced a plan. Twelve city pages in two weeks. Nobody objected; it sounded fair.
The editor’s reasoning was familiar. A similar page had taken about an afternoon a few months earlier, so twelve afternoons spread over ten working days seemed comfortable. That reasoning rested on a single memory, and that is where the trouble began.
Week one: the first cracks
By the end of the first week only three pages were finished. The researcher’s time had gone into confirming details that were out of date. The data entry assistant had been waiting for corrected lists. The developer had spent two days fixing a page template that broke on small screens. No one was idle, yet nothing was done.
At the Friday meeting the researcher said quietly that the afternoon they remembered had been the easiest page in the batch, a small city with few entries. The team had planned all twelve pages on the smoothest day of the last project. That observation, made without drama, was the turning point.
Starting a ledger
The editor opened a shared sheet that afternoon with a line for each job, a box for the hours guessed, a box for the hours spent, a ratio and a short cause note. The three finished pages were entered from memory and marked as rough. For the next page the guess went in before work started: six hours, split across research, entry, checking and publishing. At the end the actual went in: eleven hours.
After the second week the sheet showed a clear picture. Research ran at about 2.2 times the guess. Data entry ran at 1.4. Template fixes ran at 3, though only on the first few pages. Final checking ran at close to 1. The team had been estimating the page as one lump; the ledger showed it was four different kinds of work with four different habits.
What the ledger revealed about the team
The patterns were practical, not personal. Research was slow whenever source details were uncertain. Entry was slow whenever the incoming lists were dirty. Template trouble concentrated in the first pages using a new layout. The ratios belonged to the tasks, not to the people, and the editor said so plainly at the next meeting, which kept the mood light.
They agreed on three working rules:
- Any page needing fresh source checks is planned at double the research guess.
- Lists arriving uncleaned add a fixed half-day to data entry before work starts.
- The first page of any new layout gets triple the development time; later pages return to the normal figure.
The rebuilt plan
With the ratios in hand, the editor rebuilt the schedule. The remaining nine pages were sorted by difficulty and planned with their own corrected figures. The total came to about three and a half weeks, against the original fortnight. It felt like a defeat for about an hour, until the team looked at the numbers and saw that the original plan had never matched any real pace.
It also changed how requests were handled. When a colleague outside the team asked for a faster turnaround, the editor could answer with specifics: “Pages like these have taken us about twice our guess in research; we can shorten the scope, but not the checking.”
A sideways look at the neighbourhood
While adjusting the layout, the developer browsed a few existing pages for ideas, for instance a Guwahati page that groups advocates working on intellectual property, and noticed how long each section must have taken to compile. It was a useful reminder that a directory page looks simple only after the effort is hidden.
The researcher, meanwhile, compared that with the equivalent page for Madurai and guessed, then timed, how long a similar listing would take to assemble. Their guess was four hours; the later actual was seven.
Outside the directory world, the team’s editor sometimes read the site of Cotocus Foundation, a nonprofit that lays its site out in program, research and community sections next to a blog. It had nothing to do with their method, but it showed a different style of organising information for readers.
A hiccup in the third week
The new plan was tested almost at once. In week three a source list arrived with half its entries in an inconsistent format, exactly the situation the second rule covered. Under the old habits the data entry assistant would have started typing and discovered the mess on page two. This time the half-day was already in the schedule, the assistant spent it cleaning the list first, and the page still shipped on its planned date. Nobody mentioned it at the meeting, which is the clearest sign that a rule is working.
A smaller test came from the developer. A second layout variation arrived late, and the triple-time rule for first pages applied again. The editor simply moved one later page to make room, and the sheet recorded the swap with a one-line note. Changes like this used to feel like emergencies; now they were adjustments.
The finish
The final page went live in the fourth week, exactly on the revised date. Readers noticed nothing except that the pages were consistent. Inside the team, the mood had changed: no weekend catch-up, no hurried checking, no quiet apologies. The ledger had given them a calmer relationship with the calendar.
The next batch showed the payoff. Applying the corrected figures, the team planned fourteen pages and finished within two days of the plan. The research ratio had fallen from 2.2 to 1.7, because the habit of confirming source details early had started to pay.
How the team talked about it afterwards
Looking back, the editor said the hardest part was not the sheet but the first meeting after the first slip, when nobody wanted to admit that the plan had been a hope. The researcher added that the sheet made it easy to speak, because the numbers belonged to the tasks rather than to anyone’s character. The developer’s comment was the shortest: it felt like finally having a map of where the hours had been going all along.
Lessons to carry into your own work
- Do not estimate from your easiest memory. Use a record of several finished tasks.
- Split a lump of work into its kinds, since each kind has its own ratio.
- Write the guess before starting and the actual immediately afterwards.
- Attach a one-line cause to any miss above double.
- Turn the ratios into plain working rules the team can remember.
- Re-check the numbers each batch; they should improve as habits improve.
None of this calls for software. It calls for a team that is willing to look at its own optimism together and without blame. Once the table is on the screen, the discussion stops being about who is slow and starts being about where the time goes, which is a much more useful conversation.
Related posts:

Six Myths About Giving Instructions in a Shared Legal Matter

Four Ways to Store Practice Records, Compared by Recoverability

Six Cloud Security Myths Legal Sites Should Drop Now

Two Small Businesses, One Legal Question: Waiting vs Asking Early

Half-Finished Case Paperwork: A Diagnosis and a One-Sentence Fix
