The Unmetered Hour: A Thirty-Day Audit of Client Demand

Most advisory firms can describe their client relationships in broad terms: the retainer, the agreed scope, the named contacts, the reporting rhythm. What they often cannot describe with any precision is the informal demand that sits around the edges. The quick call before a board meeting. The short email that becomes a three-page note. The question that is technically outside the engagement letter but would feel absurd to refuse.

These exchanges are rarely invoiced. They are also rarely examined. That is a mistake. A thirty-day log of off-scope questions can provide a more honest picture of client demand than a quarterly utilisation report. It shows where the relationship is genuinely active, where the scope schedule has lost contact with reality and where the firm is absorbing risk without deciding to.

Why questions are a better signal than hours

Time records show what was consumed. Questions show what is being sought. Those are different things. A client who sends six short questions in a month may be more dependent on the firm than one who sends a single lengthy instruction. A client who routes every query through one junior contact may be revealing a governance gap inside its own organisation. A client who asks the same question in different ways may be telling you that the original advice did not land.

The purpose of the log is not to build a case for retrospective billing. It is to create evidence for a better conversation about scope, service design and the value the firm is actually providing. The distinction matters. A log kept as a resentment ledger will be used badly. A log kept as a diagnostic will improve the relationship.

Designing a log people will actually complete

The practical obstacle is not willingness. It is friction. A thirty-day audit should ask for no more than a minute of time per entry. A shared spreadsheet with a small number of fields is usually sufficient: date, client, person asking, channel, a short description of the question, an urgency marker, a theme code and whether the response required formal advice or only a point of orientation.

Define off-scope carefully before you begin. A question is off-scope if it falls outside the agreed scope schedule but is answered without a separate instruction or fee adjustment. That definition should be agreed with the engagement partner and communicated internally with a clear explanation of purpose. The exercise is not surveillance of client contacts. It is a review of how the firm deploys judgement.

The theme codes should be simple enough to use consistently. Common categories include governance, regulatory interpretation, commercial negotiation, board papers, stakeholder communication and process queries. Urgency can be captured as same-day, within the week or routine. The identity of the asker matters because it shows whether demand is concentrated in the executive, the board, a single function or an external adviser.

Reading the pattern, not the pile

After thirty days, the raw count is the least interesting number. The useful analysis lies in four patterns.

First, theme concentration. If most off-scope questions cluster around one subject, the client is not simply asking for extras. The scope schedule may be missing a category of need that has become routine. That is a re-scoping issue, not a discipline issue.

Second, asker concentration. If one individual generates a disproportionate share of questions, the firm should ask why. It may be a sign of trust, but it may also indicate that the client has not built the internal capability it expected to build. That has implications for dependency and succession within the relationship.

Third, urgency pattern. Frequent same-day questions suggest that the client is using the firm as an operational safety net. That may be appropriate, but it should be priced and resourced as such. It should not be absorbed silently by partners who then resent the client for behaving as the relationship allows.

Fourth, repetition. Recurring questions often point to a communication failure rather than a scope failure. If the same issue is being asked about repeatedly, the firm may need to improve the advice, the format or the point of contact rather than add another paragraph to the engagement letter.

Turning the log into a re-scoping conversation

The log should not be presented to the client as an invoice in waiting. It should be presented as a short, neutral review of how the relationship is working. A one-page summary is usually enough: the volume and type of questions, the main themes, the concentration of demand and two or three practical options for the next period.

The conversation itself should begin with acknowledgement. The client has been seeking advice outside the formal scope because the relationship made that feel natural. That is not a problem to be punished. It is a pattern to be understood. The firm should then set out what it has observed without attributing motive.

From there, the options are usually straightforward. The scope can be extended to cover the recurring theme. The service can be reframed around a different access model, such as a fixed number of advisory calls each month. The engagement can be repriced to reflect the level of availability the client actually uses. Or the boundary can be clarified, with a simple route for out-of-scope work to be instructed and charged.

Each option has consequences. A broader scope may increase revenue but reduce margin if it is not resourced. A tighter boundary may protect capacity but damage goodwill if it arrives without warning. The purpose of the meeting is not to choose the firm's preferred answer. It is to choose the answer that fits the client's real demand and the firm's real cost to serve.

Keep the audit small and repeatable

A thirty-day audit is not a permanent bureaucracy. It is a short, focused exercise that can be repeated when a relationship feels out of balance. Firms that run it well tend to find that the first cycle is revealing, the second is confirming and the third is unnecessary for most clients. That is the point. The log should make itself redundant by producing a clearer scope, a better service model or a more honest boundary.

The unbilled question is not automatically a problem. It is information. The firms that treat it as such will find that scope creep becomes visible earlier, pricing conversations become less defensive and client dependency becomes something they can manage rather than something they discover too late.