Reading a captive statute: a practitioner's method
There is a right order to read a compliance obligation, and it isn't the order most desks read one in. Statute, then regulation, then form, then agency practice — and each tier can move the answer.
A compliance date sits inside four documents at once. The reader who cites only one of them has cited a rumor. The reader who cites all four in the wrong order has answered a different question than the one that was asked. The four are the statute, its implementing regulation, the form the agency wants back, and the practice the agency has settled into. Each tier can refine, expand, or quietly override the one above it. Reading them in the correct order — and holding onto the disagreements between them, not resolving them into a single tidy sentence — is what the discipline actually is.
This is a method piece. No new dates, no new numbers. The worked example uses one obligation the Record has already published in full, chosen because its four tiers demonstrably diverge on any calendar year with a weekend on the deadline: Vermont's captive premium tax return.
The four tiers, in the order to read them
StatuteThe legislature's text. Codified in a title of the state code (in Vermont's case, Title 8 for banking and insurance). It sets the outermost boundary of the obligation: who owes it, what it is, and when it is due. Every other tier operates within the frame this text creates. If you cannot point to a section that authorizes what the regulation, form, or agency is doing, one of them has drifted.
RegulationThe agency's rule. Adopted through a statutorily prescribed rulemaking process, published in the state's administrative code or regulatory register. Fills the interstices the statute left open — content, format, evidence, tolerance. A regulation can add procedural detail; it cannot change a statutory date without express authority to do so.
FormThe instrument the agency prints. The paper (or the electronic screen) the filer actually submits — with instructions, a schedule, and often a published calendar attached. Forms are where administrative practice becomes visible to the public. Their dates, tolerances, and definitions are enforceable against the filer even when the form says nothing more than what the statute already said — and are sometimes the only place a weekend roll, a portal outage, or a rounding convention appears in writing.
PracticeWhat the agency does. The unwritten but observable behavior of the office that receives your filing: which extensions are granted routinely, how a late filing is treated in the first week versus the fourth, what "prior approval" actually means in ordinary correspondence. Practice is the least authoritative tier and the most predictive; a compliance program that respects the top three tiers and ignores this one still gets surprised by phone calls.
The worked example: Vermont's premium tax return
Read the statute first. 8 V.S.A. § 6014 imposes the captive premium tax and directs that the return "shall be filed" on March 15 for the preceding calendar year, without estimated payments. That is the statutory date, full stop; nothing else in the code moves it. A memo that stopped here would be defensible on the law and quietly wrong in operation.
Read the regulation next, if there is one on point. Vermont has not adopted a rule under § 6014 that modifies the date itself; the Department of Financial Regulation and the Department of Taxes divide administration between them, and the pertinent detail lives at Tier 3 rather than Tier 2. A practitioner who checks the regulatory register and finds nothing has not wasted the step — a documented negative is what confirms Tier 3 is authoritative for this obligation.
Read the form. Vermont's captive premium tax return is Form CPT-635, filed electronically through myVTax. Its published filing calendar for the return covering the period ending December 31, 2025 shows the return due March 16, 2026, because March 15, 2026 is a Sunday. The statutory text still reads March 15. The administered date is March 16. Both are true. A return filed March 16 satisfied the form's schedule; a program that treated March 15 as the operative date filed early and encountered no calendar risk. A program that treated the form's Monday as the statutory deadline for future years would carry a subtly incorrect number forward.
Read the practice last. This is where the compliance program's institutional memory lives: how DFR responds to a late VCAR filing that immediately corrects itself, how Taxes handles a myVTax outage on the last day, how a first-time filer's transposed digit gets resolved without an assessment. None of this belongs in the citation of the deadline. All of it belongs in the operating notes attached to it.
Why the tiers can contradict each other
They can contradict because they are produced by different institutions on different schedules under different authorities. The legislature amends a chapter every session or two. An agency adopts and amends regulations on its own rulemaking calendar, which is longer. A form is republished annually to reflect the current filing year and can quietly absorb a weekend roll or a portal migration between two versions. Practice changes when personnel change. Nothing coordinates the four, and no tier automatically defers to another absent an express instruction. Contradictions are the ordinary output of a functioning administrative system, not evidence that something is broken.
The consequence for reading is this: when the tiers agree, cite the statute. When they disagree, cite both — the statutory text and the tier that moved the answer — and note the direction of the disagreement. A compliance calendar that carries March 15 · 8 V.S.A. § 6014 · Form CPT-635 shows Mar 16 for 2026 (weekend roll) shows its work. A calendar that carries March 16 alone has thrown away the reason.
Three rules for the practitioner
- Cite the tier that answered the question, not the tier you started at. If the statute set the frame but the form set the date, the form gets the citation with a pointer back to the statute. Naming the wrong tier is a small error that compounds; the next reader repeats it.
- Preserve the disagreement in the record, not in the deadline. A single-line entry cannot show that the statute and the form differ on any given year. A two-column entry can. The compliance calendar is a database; treat it like one.
- Reverify at the tier that moves the fastest. Statutory text changes slowly and is easy to monitor. Regulations change more often and are also monitored. Forms change annually, most changes are cosmetic, and one is not. That is the tier where the freshest work belongs, on the same schedule the agency publishes on.
What this method does not do
It does not tell the reader whether a given late filing will be forgiven, or when a novel fact pattern warrants a private ruling. Those are exercises in judgment, and judgment is not what a method piece is trying to teach. What the method does is separate the citation from the argument, so that when the argument turns out to be wrong the citation still lets a later reader see where the reasoning began. The compliance calendar the Record is building — one domicile at a time — is applied doctrine of this exact kind. Every date sits beside its authority. When a tier moves, the calendar shows that a tier moved.
A publication that puts its own verification method on the page is inviting readers to grade the work. That is the point. The correction log the Record maintains is the other half of the same discipline.
Model calendars for Vermont and Missouri are published; Arkansas is next; the survey opens in October.
Be on the record →Educational and standards commentary only — not legal, tax, or investment advice, and no professional relationship is created. The method described is a working procedure, not a rule of interpretation adopted by any regulator. Statutes, regulations, forms, and agency practices change; confirm every date with the domicile regulator and your own advisors before relying on it.