Public Records Fee Calculator Guide for Tennessee

What this calculator does

Run this scenario in DocketMath using the Public Records Fee calculator.

DocketMath’s Public Records Fee Calculator for Tennessee (US‑TN) helps you estimate public-records request fees by translating your request details into a calculation you can run consistently.

This guide focuses on fee-estimation mechanics and the timing rules that frequently affect records requests, so you can plan around deadlines and avoid avoidable delays.

A key point for Tennessee: there is no claim-type-specific sub-rule in the data provided, so the calculator and this guide use the general/default time period described below.

Timing anchor used in this guide

Tennessee Code Annotated § 40‑35‑111(e)(2) sets a general SOL period of 1 year (based on the jurisdiction data provided). You’ll see this period referenced as a planning baseline—not as legal advice on any individual matter.

When to use it

Use the DocketMath calculator when you’re preparing to submit or manage a Tennessee public records request and you want a predictable estimate before you:

• Budget for copying/scanning and related labor costs (where applicable)
• Decide whether to narrow a request to reduce costs
• Anticipate what you may owe before you receive records
• Plan follow-ups if you’re working near deadlines

Typical triggers

Check whether you should run the calculator if any of these apply:

• You have multiple document categories (e.g., incident reports plus body-worn camera metadata)
• You expect large volumes (e.g., 500+ pages or many hours of media)
• Your request includes format choices (PDF vs. native files; per-page scan vs. batched production)
• You’re coordinating production with another task that has its own due date

What this guide is not

This guide does not provide legal advice about:

• Whether a specific fee must be charged in your exact situation
• Whether a fee assessment is proper under every Tennessee scenario
• How to challenge a fee charge or denial

Instead, it helps you estimate and organize your inputs so your request process is clearer.

Step-by-step example

Below is a concrete walkthrough showing how you’d use DocketMath’s calculator logic. Because calculators depend on your specific inputs, treat this as a template for how to feed the tool—and how the output changes as you adjust facts.

Example scenario

You’re requesting:

• 200 pages of records
• Delivered in PDF
• Expect 1 set (not multiple rolling batches)
• No special handling beyond standard compilation

You run the calculator and it produces an estimated total.

Step 1: Enter your page count and scope

In the DocketMath tool (public-records-fee), you’ll typically provide fields like:

• Pages or records to produce (200 pages)
• Any media hours/files (if applicable; you’d enter 0 for media if none)
• Copies/format preferences (PDF/native)
• Whether the request is a single batch or multiple batches

Impact on output: As your page count increases, the estimated production/copying portion of the total increases proportionally.

Step 2: Add format and delivery details

Assume you choose PDF delivery.

Impact on output: If the calculator distinguishes between formats (for example, standard per-page scan vs. other conversion work), choosing PDF may increase the estimate compared to a scenario where native digital copies are provided.

Step 3: Review the fee estimate line items

After calculation, review the displayed breakdown. Common fee estimate components in public-records contexts include:

• Per-page copying/printing
• Media reproduction or scan labor
• Administrative time for compiling records
• Any “special request” processing category (if your calculator includes it)

Impact on output: Even if pages are unchanged, labor/processing components can move based on how much work your request implies (e.g., “compile across multiple custodians” vs. “single folder”).

Step 4: Use the timing anchor for planning

If your request timing is tied to a broader legal matter window, use the general/default 1-year period referenced in the provided Tennessee statute data:

• Tennessee Code Annotated § 40‑35‑111(e)(2) → General SOL period: 1 year

That doesn’t automatically determine what you owe—but it helps you plan when records-related actions might be expected to occur.

Impact on output: Fee calculations generally don’t change based on SOL timing, but planning can reduce costly rework, like re-requesting missing materials.

A quick “what if” adjustment

Suppose you revise your request from 200 pages to 120 pages.

• Estimated total should drop because the copying component is often page-driven.
• Labor/admin time might drop if the request becomes simpler to compile.

Common scenarios

Tennessee requestors often fall into predictable patterns. Here are common scenarios and how to think about calculator inputs so your estimate reflects reality.

Scenario A: Small, single-custodian request

Example: 30 pages from one file type, one office, one delivery format.

Checklist for accuracy:

Expected output behavior: Lower and more stable total because page count and compilation work are limited.

Scenario B: Large-volume compilation

Example: 1,000+ pages across multiple cases or time windows.

Checklist for accuracy:

Expected output behavior: Totals tend to rise sharply due to both per-page and compilation/labor components.

Scenario C: Media records (video/audio) with durations

Example: body-worn camera footage totaling 6 hours.

Checklist for accuracy:

Expected output behavior: Media costs usually change based on hours and file handling rather than page count.

Scenario D: Requests with multiple formats

Example: Some records in PDF, some in native format.

Checklist for accuracy:

Expected output behavior: Mixed-format estimates often won’t match a “one-size-fits-all” page-per-page expectation; format handling can shift the estimate.

Scenario E: Timing-sensitive matters

Example: Your records request supports an action tied to a larger matter scheduled within a year.

Planning anchor from the provided data:

• Tennessee Code Annotated § 40‑35‑111(e)(2) → General SOL period: 1 year

Tips for accuracy

Getting the most useful estimate from the DocketMath calculator is mostly about entering inputs that reflect the actual work implied by your request.

Use realistic counts and confirm units

Break requests into batches when scope is uneven

If your request includes both:

• small, straightforward records, and
• a large, complex subset,

consider running separate calculations for each chunk. Then compare totals. This often produces a more accurate “worst-case vs. best-case” budgeting range.

Keep format consistent across comparable runs

If you run the calculator multiple times to see how narrowing scope affects cost:

• keep the delivery format the same,
• keep the time window the same,
• adjust only one variable (like page count).

That way, changes in output reflect the variable you actually modified.

Cross-check with your own document inventory

Before you calculate:

Even a rough count derived from actual inventory is usually better than a guess.

Don’t forget the general/default timing context

The provided Tennessee statutory data indicates a general SOL period of 1 year, cited to Tennessee Code Annotated § 40‑35‑111(e)(2):

• General/default period used for timing planning: 1 year
• Citation: https://law.justia.com/codes/tennessee/title-40/chapter-35/part-1/section-40-35-111/

Practical workflow checklist

Use this mini checklist before submitting your request plan:

Related reading

• Public Records Fee Calculator Guide for Alabama — Complete guide
• Public Records Fee Calculator Guide for Arizona — Complete guide
• Public Records Fee Calculator Guide for California — Complete guide