How to Cite a Public Tax Case Record So Someone Can Find It Again

A public tax case is easy to mention and surprisingly hard to identify precisely. A person’s name may appear in several cases. One case may contain many PDFs with similar titles. A document can have a date printed on its face that differs from its docket-entry date. An archived copy may remain online after the official docket changes. A useful citation does more than paste a link: it tells another reader exactly which record, document, page, and version support a statement.

This guide explains a practical citation method for research notes, articles, and source checks. It does not prescribe a legal citation format for a filing. Courts, agencies, schools, and publishers can require their own formats. The examples below are invented, and the suggested labels describe what a researcher observed rather than making claims about a real case.

Start with the claim you need to support

Before writing a citation, write the factual claim in one sentence. “A petition was filed” needs different support from “the tribunal decided the case” or “the record page listed a particular status when I checked.” The first may be supported by a docket row and petition. The second calls for an actual decision or order. The third describes an archive snapshot and needs an access date. A link to the case landing page is a useful starting point, but it may be too broad for a claim about a sentence on page four of an attachment.

Read the actual source before selecting fields for your reference. A search-result snippet may truncate a name or omit a case number. OCR text may misread a digit or move a line from another column. The source you cite should be the source you inspected: the rendered PDF page, a specific docket entry, or the record page itself. If you consulted only an excerpt, describe it as an excerpt rather than implying you reviewed the full document.

Separate a source identifier from the facts it allegedly proves. A docket number identifies a case; it does not, by itself, establish its outcome. A filename identifies a stored attachment; it does not tell you whether that attachment was accepted as evidence. A citation should point the reader to the material, while the accompanying sentence should say no more than the material supports.

For a longer research project, create a short claim ledger. Give each claim a plain label, then record the document and exact location supporting it. A separate column can hold unresolved qualifications. This small habit makes it easier to spot when a sentence has grown stronger than its source.

Capture the case identity, not just the name

The case identity usually begins with the tribunal or agency, its docket or case number, and the parties as they appear in the source. The Michigan Tax Tribunal describes a docket number as an identifier assigned to a case. The number is therefore particularly helpful when several records involve similar names. Copy it exactly, preserving letters, hyphens, and leading zeros. Do not silently normalize it into a number that looks cleaner to you.

Names need context. A petitioner, respondent, representative, and person mentioned in an exhibit are not interchangeable roles. If the record title shortens or rearranges names, use the form shown on the document you cite and keep an internal note of the record-page title. The point is to make the case findable, not to infer identity from a name match. Where privacy or relevance calls for restraint, a docket number and document title may suffice without repeating a person’s name in your prose.

Also record the jurisdiction and source organization. “Tax tribunal decision” can be ambiguous across states. “Michigan Tax Tribunal, Small Claims Division” or another accurately observed division gives a reader a path back to the responsible body. Do not invent a division when the page does not show one. If the archive is a copy of material from an official body, distinguish the body that created the record from the website that hosts the copy.

An internal source key can make your own notes manageable: for example, MI-CASE-0042-DOC-03. That key is yours, not an official identifier. Keep the official docket number and the stable public URL beside it. If your notes are shared, explain what the key means so nobody mistakes it for a tribunal reference.

Identify the exact document and docket association

A case page can hold a petition, answer, notice, exhibit, motion, order, and later decision. “The PDF” is not enough when more than one file exists. Copy the attachment’s visible title or original filename, then note the docket entry or row to which it is attached. If a row contains several attachments, distinguish them by filename, sequence, or another stable label that the source actually provides.

Do not let a generic title carry more meaning than it has. A file named notice.pdf may be a notice of docket, a hearing notice, or an unrelated administrative letter. Open it and use its printed heading if legible. Conversely, if the printed heading and the archive label differ, preserve both: “archive attachment listed as X; document heading reads Y.” That tells a future reader why searching one phrase might fail.

The docket association can matter when a document is dated earlier than the row where it appears. A citation to the PDF can identify its printed date, while a separate reference to the docket row can identify the entry date. If the question is when a document was served, neither date automatically answers it. The Michigan Tax Tribunal’s glossary treats document types and case events as distinct concepts; use the vocabulary visible in the source and avoid turning one date into another event.

When a ZIP archive or multi-file upload has been unpacked, note the individual member’s original filename and parent docket entry. A website may convert a Word file or image to a PDF reading copy while retaining the source filename stem. The converted PDF is still a reading copy of that particular attachment. Keep a note of the original format if that distinction matters to your research.

Give the reader a location within the PDF

For a factual statement about a long document, identify the page or another local marker. A page number printed on the document may differ from the PDF viewer’s page count. If both exist, make your convention explicit: “PDF page 7” means the seventh rendered page; “printed page 5” means a numeral visible on the document. If an exhibit begins with an unnumbered cover, the difference becomes important.

For a table, identify a row and column heading as well as a page. A figure without its tax-year or value-type label can be misleading. If a paragraph is numbered, you can record the paragraph number. If the document has no visible pagination, use the PDF page count and a nearby heading. The location should be specific enough for another person to verify the statement without rereading an entire packet.

Do not cite a text-extraction position as if it were a visual page number. OCR can reorder columns, duplicate headers, or omit a line. Searchable text is a navigation aid; the visible PDF is the check for important names, dates, and amounts. If the page is rotated or faint, view the corrected reading copy and note any uncertainty that remains. “Appears to read” is a better research note than an exact transcription you cannot verify.

If you quote, compare the quoted words against the displayed source rather than a search preview. Quote only the amount needed to establish your point, and preserve unusual spelling when accuracy matters. For paraphrase, cite the same exact location. The citation is not a substitute for careful wording in the sentence itself.

Distinguish document dates, entry dates, and access dates

A complete reference often needs more than one date, but each should have a label. A petition may be dated May 2, uploaded to a docket May 6, and viewed by you in October. The tax year described in the petition could be earlier still. Writing only “May 6 petition” could imply that May 6 is printed on the petition. Instead, say “petition dated May 2; docket entry May 6” when both are supported.

An access date answers a different question: when did you see this web version? It does not prove the document was created or published that day. It becomes useful when a site changes, a case receives more filings, or an archive copy is replaced. Use the date you actually checked, not today’s date copied into an older note. If you revisit the material, keep the prior observation and add a new access entry if the difference matters.

Some PDF properties contain creation and modification timestamps. Those can reflect scanning, sanitizing, upload, or software conversion. Unless the record itself explains them, treat them as technical file metadata rather than case-event dates. The same restraint applies to a website’s “last updated” label. It may describe the page or import job, not the underlying tribunal action.

If a date is absent, leave it absent. “Undated attachment, docketed May 6” communicates what is known. A placeholder such as “date unknown” is clearer than borrowing a nearby row’s date. When a date is hard to read, retain an image or page reference in your private notes so you can check it again.

Record the stable URL and the kind of page

Save the full record-page URL and, where available, the direct document-page URL. The record page gives case context and a route to related filings. The document page identifies the particular attachment and may expose extracted text. A raw PDF URL is useful for checking the visible pages, but it may be less helpful as the only citation because it omits the docket context. A practical note can keep all three and select the one that best supports the published statement.

When a site uses canonical links, they express its preferred indexing relationship. They do not erase the need for precise research references. A document page may point canonically to a record page while remaining a useful locator for a specific attachment. If you share a raw PDF address, also provide enough case and document information for someone to recover the source if the storage route changes.

Avoid relying on a temporary browser state, search query, or fragment identifier as the sole reference. A fragment can bring someone to a section, but it is a location hint within a page rather than the identity of the record. Keep the stable base URL in your notes. Test links before publishing a bibliography and again after a significant site migration.

For an official-source check, save the official docket or source URL separately from an independent archive URL. A citation to an archive should say it is an archive copy. If the official source later differs, you can compare them without silently replacing one source with the other.

Write a compact reference that can be audited

There is no single universal citation string for every use. The following is a research-note pattern, not a required legal format: creating body; case name and docket number; document title; document date if shown; docket-entry date if relevant; PDF page or section; hosting site and stable URL; date accessed. Omit fields that truly do not exist, and label dates so their roles remain clear.

For example, an invented note might read: “Michigan Tax Tribunal, Example Owner v Example Township, docket 26-000000-TT, ‘Notice of Hearing,’ dated July 7, 2026, docket entry July 9, 2026, PDF p. 2, archived at Tax Records Finder, [record URL], accessed October 13, 2026.” The invented title and number are placeholders. A real note should use the actual document title, observed dates, and working URL.

The claim beside that note should remain narrow. “A notice dated July 7 scheduled a hearing” can be supported if the notice says so. “The hearing occurred” needs later evidence. “The case was decided at that hearing” needs still more. A citation can be perfectly formatted while the claim it accompanies is too strong; source checking and writing quality are separate tasks.

If you are compiling many records, store citation fields in separate columns rather than one long cell. Suggested fields are source body, docket number, record URL, document title, attachment ID, PDF-page number, printed date, docket-entry date, access date, and claim supported. You can then sort or correct one field without rewriting every note. Keep a free-text field for uncertainty or visible conflicts.

Handle corrections and versions openly

Public records can be updated, corrected, or supplemented. If an attachment disappears or is replaced, do not silently edit an old citation as though the earlier version never existed. Note what you saw, when you saw it, and what changed. A newer document with a similar title may be a correction, a separate filing, or merely a second scan. Read the content and docket context before calling it a replacement.

If your article relies on a version that is no longer reachable, say so and point to the currently available material when appropriate. A saved private copy or checksum can help verify that your notes refer to the earlier version, but avoid redistributing material that should not be republished, especially personal information. A research log can describe a discrepancy without exposing sensitive fields.

For living case pages, the date you last checked matters. “The archive listed no decision as of October 13” is a statement about that visit. It is not a prediction that a decision will never appear. If the record later changes, update the statement or add a dated note. Do not use an old citation to support a present-tense claim about current status.

The National Archives’ guidance on citing records emphasizes enough identifying information for a reader to locate the item. That practical goal applies here even though a tax-case archive is different from a federal archival collection. A citation succeeds when another careful reader can find the same case, open the same document, reach the same page, and evaluate the claim.

A final citation check

Before sharing a reference, open it from a fresh browser tab. Confirm that the URL lands on the expected case, that the docket number and party roles match your note, and that the specified attachment is present. Open the PDF and check the page number, date label, and the exact sentence or table cell you used. If the site offers extracted text, compare important details with the rendered page. Then read your own claim one more time and ask whether the source proves that wording.

For a short article, that may take a minute. For a large dataset, it is a repeatable quality-control step. It prevents a copied link from pointing to a neighboring case, an exhibit from being mistaken for an order, or an archive date from becoming a supposed event date. Precise references also make corrections easier: you can trace a problem to one claim and one source rather than reconsidering the entire project.

The most useful citation is neither the longest nor the most ornate. It is the one that identifies the source honestly, labels uncertainty, and lets another reader retrace your steps.

If your notes will be reused months later, include a short description of the fact you checked rather than only a URL. Links can change, and a future reader may not know why you saved a particular PDF. “Page 3 states the scheduled hearing date” is more durable than “important page.” Keep that description separate from the citation itself so you can correct an interpretation without losing the source identity. When you revise a claim, reopen the visible document and check that the page still supports the new wording. A citation is a route back to evidence, not a permanent endorsement of every sentence attached to it.