FNAD — Federation of North American Designers All articles
Practice Management

The Unbilled Change Log: A Quiet System for Tracking Out-of-Scope Work

FNAD — Federation of North American Designers
The Unbilled Change Log: A Quiet System for Tracking Out-of-Scope Work

Photo: Louis Comfort Tiffany / Tiffany Studios, CC0, via Wikimedia Commons

The requests that never get named

Independent design practices seldom lose margin in a single dramatic dispute. The loss is more often cumulative: an extra layout variation, a second round of copy edits, a hastily requested social asset, a Saturday morning file conversion. Each request appears minor enough to absorb. Individually, that judgment is often reasonable. Collectively, it can consume weeks of studio capacity without appearing in any invoice, estimate, or project review.

The problem is not only money. When unbilled work remains invisible, it becomes difficult to discuss without sounding aggrieved. The designer remembers the favors; the client remembers the agreement. A simple internal record can close that gap. The purpose of an unbilled change log is not to bill every small kindness. It is to make the pattern visible enough to support better decisions.

What the ledger is, and what it is not

An unbilled change log is an internal planning document. It is not a client-facing scorecard, a substitute for a change order, or a tool for relitigating past projects. It should be plain, factual, and maintained close to the work. The log exists so that a solo designer can answer three questions with evidence rather than memory: What was requested beyond the agreed scope? What would that work have been worth in the market? How was it handled at the time?

For practices of one or two people, the system should take minutes, not hours. A spreadsheet, a table in a project notebook, or a simple database is sufficient. The format matters less than the habit of capture.

Five fields that make the record useful

A workable ledger needs only a handful of fields. Too many columns create friction and the log goes unused. The following five are enough for most independent US studios:

Field Purpose
Date Anchors the request to the project timeline.
Client and project Connects the item to an agreement and a renewal cycle.
Request Describes the change in neutral, specific language.
Estimated market value Assigns a reasonable value using the studio's standard rate or package pricing.
Disposition Records whether the work was absorbed, declined, folded into a later phase, or reserved for a renewal conversation.

Two optional fields can add context without much effort: the source of the request, such as an email, call, or meeting, and a short note on why the studio handled it as it did. That note is useful later. It prevents the log from becoming a list of grievances and keeps it closer to a decision record.

The weekly capture habit

Capture works best as a short weekly ritual. At the close of business on Friday, or at the start of the following week, the designer reviews project correspondence and notes any request that fell outside the agreed scope. The entry should be made while the context is fresh. Estimating market value does not require precision. Use the studio's standard hourly rate, a package price, or a conservative range. The point is to create a consistent unit of measure, not to produce a formal appraisal.

The disposition field is equally important. An absorbed request is not necessarily a mistake; it may be a relationship investment or a reasonable accommodation. A declined request is also a valid outcome. What matters is that the decision is recorded. Over time, the disposition column reveals whether the studio is making deliberate exceptions or simply defaulting to accommodation.

The monthly review ritual

Once a month, set aside thirty minutes to review the ledger. Total the estimated market value of unbilled changes for each active client. Look for patterns: Is one client consistently requesting additional rounds? Are requests clustering around a particular phase, such as content changes after layout approval? Is the studio absorbing work because the original scope language was vague?

The review should produce one short written summary. Three or four sentences are enough. For example: 'This month, the studio absorbed approximately $2,400 in out-of-scope adjustments across two projects. Most requests involved additional image revisions after the approval milestone. The next proposal should define revision limits more clearly and include a small-change threshold.' That summary becomes a useful input for project debriefs, proposal revisions, and renewal discussions.

Using the record in renewal conversations

The ledger is most valuable when it informs a conversation before resentment sets in. At renewal, the designer can refer to the pattern without presenting the log as a bill. A neutral formulation is usually best: 'Over the past six months, the studio accommodated a number of adjustments beyond the original scope. The estimated value of that additional work was approximately X. To keep the relationship sustainable, I would like to propose a revised scope and fee for the next phase.'

This approach works because it is factual rather than accusatory. It also gives the client a chance to respond. Some clients will welcome the clarity. Others may reveal that they did not understand the original boundaries. In either case, the conversation is grounded in a shared record rather than a vague sense of imbalance.

Boundaries that follow from evidence

The ledger should lead to practical adjustments. If additional revision rounds are the recurring issue, the next agreement can define how many rounds are included and how additional rounds are priced. If small requests arrive frequently between phases, the studio can establish a minimum change-order threshold. If a retainer client generates a steady stream of minor extras, the retainer itself may need to be repriced or redefined.

These are not punitive measures. They are the natural consequence of seeing the work clearly. A solo studio cannot manage capacity well if the true shape of the work remains hidden. The ledger makes that shape visible.

The discipline of not weaponizing the record

An internal ledger loses its usefulness if it becomes a tool for scorekeeping. Clients should not be surprised by a renewal conversation that references months of unmentioned work. The record should support transparency, not replace it. If a request is significant enough to matter, it deserves a prompt conversation. If it is small enough to absorb, it deserves a note in the log and a periodic review.

The most sustainable use of the ledger is preventative. It helps the designer notice drift early, adjust scope language, and keep the relationship on a stable footing. Used that way, a simple table can protect both the studio's margin and the client's trust.

All Articles

Related Articles

Small by Design: The Strategic Case for the Unscalable Studio

Small by Design: The Strategic Case for the Unscalable Studio

What to Keep, What to Shred: A Retention Calendar for Solo US Design Practices

What to Keep, What to Shred: A Retention Calendar for Solo US Design Practices

The Return Brief: A Conference-to-Studio Protocol for Independent US Designers

The Return Brief: A Conference-to-Studio Protocol for Independent US Designers