Public Records Fee Calculator Guide for New York

What this calculator does

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

DocketMath’s Public Records Fee Calculator (New York) helps you estimate public records search, review, and production fees under New York’s freedom of information framework—using a consistent set of inputs so you can compare scenarios before you file a request.

You typically use it to:

• Estimate total estimated fees for a request (by adding up search + review + production categories the form uses).
• See how changing date ranges, document volumes, or page counts changes the total.
• Document your assumptions so the estimate is easier to explain to yourself (and to anyone you share your request calculations with).

Key New York rule your calculator needs (records retention context)

New York generally requires that records requests be answered for records within the default retention/availability window used for fee planning. For New York, the general default limitations period referenced in New York statutes is 5 years.

The relevant cited statute for the general/default period in this guide is:

• N.Y. Crim. Proc. Law § 30.10(2)(c) (general rule referenced for the 5-year period)
• Source: https://www.nysenate.gov/legislation/laws/CPL/30.10

Importantly, no claim-type-specific sub-rule was found for this guide. So the 5-year period is used as the general/default period rather than a special-case rule.

How the calculator’s output works (conceptually)

Most public records fee calculators depend on three levers you provide:

• Search time (e.g., hours or search effort)
• Review time (e.g., time needed to examine records)
• Production (e.g., pages, duplication method, and related costs)

On the DocketMath tool page, those inputs feed a total estimate. When you increase any input (like page count or hours), the estimated total generally rises.

Primary CTA: /tools/public-records-fee

When to use it

Use DocketMath’s Public Records Fee Calculator when you’re preparing a request and want to forecast costs before submitting. It’s especially useful when:

• You’re requesting records spanning a multi-year date range (because time-window size affects search/review).
• Your request could involve multiple document types (emails, reports, logs, contracts, or meeting materials).
• You expect the agency to ask you to narrow the request due to volume or cost.
• You’re comparing two possible request scopes:

  • Option A: broader date range / more custodians
  • Option B: narrower date range / fewer custodians

Retention window planning (New York default)

Because this guide uses the general/default 5-year period, it helps you decide how far back to reach when you’re balancing completeness against likely effort. You’ll generally get a more predictable fee estimate when:

• Your request date range roughly aligns with the 5-year default window you’re planning around, and
• You avoid requesting very large multi-decade collections unless you’re intentionally willing to accept higher search/review costs.

Step-by-step example

Below is a practical walkthrough showing how typical inputs affect the DocketMath estimate. The numbers are illustrative—your exact fields may differ depending on the tool’s interface, but the logic is the same.

Scenario

You want New York agency emails and related attachments about a specific vendor.

• Date range: January 1, 2021 through December 31, 2023 (3 years)
• Search scope: one department mailbox + shared drive
• Estimated volume: 850 pages of potentially responsive material after initial sorting
• Expected redactions/review effort: moderate
• Production format: electronic (PDFs)

Step 1: Set your date range and time window

Enter your start/end dates.

Calculator effect: A longer date range typically increases:

• Search effort (more records to locate)
• Review effort (more items to scan)
• Administrative batching (more time to process results)

Because this guide uses 5 years as the general/default period (and no claim-type-specific sub-rule was identified), a 3-year window is already narrower than the full general default window.

Step 2: Enter estimated search effort

Provide a search-time input (often in hours or a similar measure).

Example input:

• Search time estimate: 6 hours

Calculator effect:

• If you increase to 8 hours, the estimate likely rises roughly proportionally (depending on the tool’s fee model).

Step 3: Enter estimated review time

Add review time for redactions, exemptions, and relevance checks.

Example input:

• Review time estimate: 9 hours

Calculator effect:

• If the agency would likely do heavier review (e.g., lots of attachments, duplicates, or sensitive personal data), raising review time can materially change the total.

Step 4: Enter production/page volume

Enter pages or a proxy number the tool uses (e.g., “pages to be produced”).

Example input:

• Pages to produce: 850 pages

Calculator effect:

• If you refine your request and reduce it to 400 pages, your production component drops, and your total likely decreases—even if search/review time stays similar.

Step 5: Choose production method (if the tool supports it)

If the tool includes a production method input (paper vs. electronic), choose your plan.

Example input:

• Production: electronic copies

Calculator effect:

• Electronic production may reduce per-page duplication costs relative to paper printing, depending on the tool’s internal assumptions.

Step 6: Read the total estimate and test alternatives

After you compute the estimate, adjust one lever at a time to see sensitivity.

Common “what if” comparisons:

• Narrow date range: 3 years → 18 months
• Reduce custodians: 2 sources → 1 source
• Reduce page universe: 850 pages → 500 pages

This helps you craft a request that is specific enough to control costs while still capturing what you need.

Common scenarios

The best way to use a fee calculator is to map real-world request variables into a few common planning patterns. Here are several scenarios people frequently face in New York.

1) Broad date range but narrow subject

You know the topic, but not the exact timing.

Checklist:

Calculator strategy:

• Run the estimate for 3 years first.
• Then test a narrowed 18-month window if the total feels high.

2) Many custodians (multiple departments)

If your request names multiple custodians or “all emails to/from” multiple individuals, search effort often increases more than you expect.

Checklist:

Calculator strategy:

• Compare a “single department” run vs. a “multi-department” run.

3) Large attachment-heavy records

Requests for reports with attachments, emails with multiple embedded files, or datasets with many related documents often create review and production cost surges.

Checklist:

Calculator strategy:

• If your estimate looks high, consider splitting:

  • core records first
  • attachments second (after narrowing)

4) “Daily log” or recurring records

Recurring records can be searchable, but the sheer number of entries can make production heavy.

Checklist:

Calculator strategy:

• Use the calculator to test “week-by-week” vs. “quarterly” batching.

5) Using the 5-year default window for planning

Because this guide applies a general/default 5-year period and does not identify claim-type-specific sub-rules, you should treat 5 years as the baseline planning window for this calculator guide.

Checklist:

Tips for accuracy

Small input changes can swing totals. Use these practices to make your DocketMath estimate closer to what an agency is likely to experience.

1) Convert your guess into something measurable

Instead of “a lot of records,” estimate using rough units:

• Search: hours
• Review: hours
• Production: pages (or items translated into pages)

If you have any sample output from a prior request, use it to estimate pages per month, then scale up.

2) Run at least two calculations: “narrow” and “base”

A simple way to reduce surprises:

• Base run: your best estimate
• Narrow run: reduced date range or fewer custodians

Then decide whether the base run’s total is tolerable or whether you should revise scope.

3) Treat page count as the most sensitive lever

Production often tracks page volume closely. If you can estimate responsive pages by using keywords, sampling, or indexing practices, your total estimate becomes much more reliable.

Checklist:

4) Don’t ignore review effort

Agencies often need time to:

• locate responsive

Related reading

• Public Records Fee Calculator Guide for Alabama
• Public Records Fee Calculator Guide for Arizona
• Public Records Fee Calculator Guide for Colorado