The Tax Matter Lifecycle: Where the Calendar Runs the Practice

Tax controversy is the cleanest illustration I have of a principle that runs through the entire Practice Pack catalogue: identify the triggering document correctly, and the rest of the matter falls out mechanically. In tax work that triggering document is the notice itself, an IRS or state letter, and the entire deadline, forum and procedural path for the matter is already decided the moment that letter is decoded correctly. Decode it wrong, or decode it late, and the matter is already behind before any actual strategy work has started.

The party question in tax work has a wrinkle most other practice areas do not: which taxpayer do we represent, and for which tax years? A married couple with a joint filing may have diverging interests the moment one spouse raises innocent-spouse relief, and a system that has not recorded which years and which taxpayer identity it is actually representing is exposed the moment that divergence surfaces.

Stage one: notice intake and decoding

This stage exists because the entire rest of the matter depends on getting it right. A CP2000 is not the same animal as a CP3219, a statutory notice of deficiency, and treating them the same is the single most common and most costly mistake I see in tax practice systems. The notice type has to be identified, logged, and matched to its actual response deadline on intake, not inferred later from memory of what that kind of letter usually means. A power of attorney, Form 2848, needs to be filed immediately so the practice can actually pull transcripts and speak to the IRS on the client's behalf, and account transcripts should be ordered for every relevant year as a matter of routine, not only when a question comes up that needs one.

Stage two: examination and response

Once an audit or examination is open, the practice is answering Information Document Requests on a running log, and this is where a lot of tax controversy time actually goes. An IDR log, tracking what was requested, what was produced, and what is still outstanding, is not optional bookkeeping, it is the record that determines whether the practice can credibly argue later that it was cooperative and timely if the matter escalates.

Stage three: administrative appeals

If the examination does not resolve favourably, the matter moves to IRS Appeals, a genuinely different forum with its own culture and its own settlement authority. The system's job here is narrower than people expect: keep the position papers and supporting documentation organised and consistent with what was already submitted at examination, because Appeals officers notice when a taxpayer's story shifts between stages, and that shift costs credibility that is hard to earn back.

Stage four: Tax Court or agreement

This is where the notice decoded correctly in stage one pays off directly. A statutory notice of deficiency carries a Tax Court petition window that is fixed, typically ninety days, and it is one of the least forgiving deadlines in all of tax practice, because it is jurisdictional: miss it, and the Tax Court simply has no power to hear the case at all, regardless of how strong the underlying position is. That ninety-day window needs to be calendared the moment the notice is logged in stage one, not calculated fresh when someone finally sits down to think about next steps.

Stage five: collection defense

Even where the underlying liability is resolved or agreed, collection can become its own separate track, and it carries its own short clock: a Collection Due Process hearing request typically runs on a thirty-day window from the relevant notice. This stage is also where the collection statute expiration date, the CSED, becomes relevant, because the IRS generally has a limited runway, in my build tracked at roughly 6.2 years remaining as a live figure, to collect an assessed liability, and that runway interacts with every settlement or payment plan conversation that follows.

Stage six: closing

A tax matter closes when the liability is resolved, whether by full payment, an accepted offer, an installment agreement, or a Tax Court decision, and the closing step should capture the final position for every year that was in scope, not just the year where the dispute was loudest. Multi-year matters are common enough in tax work that a closing checklist scoped to only the headline year is a real, recurring gap.

The tracker that makes this legible

The computed module I build for tax matters is an Assessed-Liability Tracker: total contested versus agreed liability across every year in scope, with a live penalty and interest accrual counter running underneath it. Interest and penalties do not pause while a dispute proceeds, they compound the entire time, and a client who cannot see that number moving in real time consistently underestimates how much a delay actually costs them. Showing it plainly changes how clients make decisions about settling versus continuing to fight.

Why the calendar runs this practice, not the lawyer

Every other practice area I have built a lifecycle for has some room for lawyer judgment to set the pace. Tax controversy has almost none, because the notice sets the clock, the statute sets the forum, and the practitioner's actual job is making sure nothing in that sequence gets missed while the substantive argument gets built underneath it. A system that treats the calendar as the primary structure, rather than an accessory to the lawyering, is the only version of this that survives more than a handful of concurrent matters.