Public Records Fee Calculator Guide for South Carolina
7 min read
Published March 22, 2026 • By DocketMath Team
What this calculator does
Run this scenario in DocketMath using the Public Records Fee calculator.
DocketMath’s Public Records Fee Calculator (South Carolina) helps you estimate the likely time-and-money impact of requesting public records in South Carolina (US-SC)—so you can plan before you submit a request.
Specifically, it supports planning inputs that typically affect what you pay (or how long you may wait), such as:
- How many pages/records you’re requesting
- Whether you want copies or electronic production
- Whether redaction is expected (which can increase processing effort)
- How quickly you need the material
- A reference “service timeline” tied to the general statutes you’ll follow
It does not replace the underlying legal standards for a fee determination, nor does it guarantee the agency’s final calculation. Agencies can apply their own recordkeeping practices and may resolve ambiguities in how they quantify work.
Warning: A calculator estimate is not a binding fee schedule. If an agency’s actual fee differs materially, the discrepancy usually comes from how the agency counts pages, performs redaction, or values specialized work—not from a computational error.
Time planning: the default limitation period
This guide also anchors your timeline planning to South Carolina’s general statute of limitations (SOL). The general/default period is 3 years, and it comes from GS 15-1.
- General SOL Period: 3 years
- General Statute: GS 15-1
Source: https://www.ncleg.gov/EnactedLegislation/Statutes/HTML/BySection/Chapter_15/GS_15-1.html
No claim-type-specific sub-rule was found in the provided materials, so the safest approach for this calculator guide is to treat 3 years under GS 15-1 as the default/general period for limitation-based planning.
When to use it
Use this DocketMath calculator when you’re preparing a request and want to understand the moving parts before you press “send.”
Best times to run the calculator
Check your assumptions when:
- You haven’t requested yet and you need to budget for copying/processing costs.
- Your request involves large page counts (or many separate records).
- You expect redaction (e.g., personal identifiers, exempt material, or mixed public/exempt content).
- You’re comparing two request strategies, such as:
- requesting a single report vs. a dataset spanning multiple dates, or
- requesting “copies of records” vs. requesting electronic transfer where feasible.
Use it alongside a strategy review
The calculator is most helpful if you treat it like a planning tool, then tighten the request to reduce avoidable costs.
A quick checklist before you calculate:
Step-by-step example
Below is a practical example for South Carolina using DocketMath’s Public Records Fee Calculator.
Scenario
You want to request:
- 25 incident reports
- covering a 90-day period
- in PDF copies
- with the expectation that personal information may need redaction
- and you’re aiming to keep turnaround reasonable by narrowing the request as much as possible.
Because you don’t know the agency’s exact page count yet, you estimate.
Assumed inputs (for estimation)
- Pages per incident report: 6 pages
- Total estimated pages: 25 × 6 = 150 pages
- Redaction expected: Yes
- Delivery: Electronic/PDF
- Complexity factor (your best estimate): Moderate (mixed content requiring some review)
Example calculations: what changes when inputs change
Use the calculator at /tools/public-records-fee and enter your estimates. Then compare two runs:
- Run A (baseline): 150 pages, redaction likely = Yes
- Run B (narrowed request): request only the last 30 days, estimated pages cut to 50 pages, redaction still likely = Yes
How to interpret outputs
You’ll typically see outputs grouped into planning-friendly categories, such as:
- Estimated processing/copying impact
- Estimated fee range
- Estimated time-to-process planning value (based on your inputs)
Here’s the key interpretive rule:
- If you reduce pages, the fee estimate usually drops proportionally or near-proportionally.
- If you keep pages similar but clarify the request to reduce redaction scope, you may see a lower estimate due to fewer pages needing individualized review.
- If you switch from “broad search” to “narrow identifiers,” you often reduce processing time—even if the final page count ends up similar.
Pitfall: If your initial page estimate is off by 2×, your fee estimate can swing dramatically. Before submitting a large request, consider doing a quick “anchor” request for a small sample to validate page density.
Timeline note using GS 15-1 (default SOL)
For limitation-based planning, the provided statute indicates a general 3-year SOL period under GS 15-1. Since no claim-type-specific sub-rule was found in the provided materials, treat 3 years as the general/default period for limitation window planning.
That means if a dispute arises and you later evaluate legal timing, the default window to consider is within 3 years from the relevant starting point—referencing GS 15-1.
Common scenarios
Different request patterns produce different fee outcomes and different planning priorities. Use these scenarios to choose better inputs in DocketMath.
1) “Small request, single document”
Example pattern
- 1–3 documents
- 10–40 pages
- minimal redaction
Calculator input focus
- Keep page count accurate
- Mark redaction as “unlikely” if the documents are clearly public
Typical outcome
- Lower estimated fees
- Less variance from estimation error
Checklist:
2) “Broad date range across multiple units”
Example pattern
- 6–12 months of records
- multiple custodians
- mixed document types
Calculator input focus
- Break down your estimate: total pages = sum across categories
- Use “higher complexity” if review/redaction is substantial
Typical outcome
- Higher uncertainty
- Fee estimate can be sensitive to the redaction flag and complexity input
Practical approach:
3) “Redaction-heavy materials”
Example pattern
- body-camera footage logs, disciplinary records, emails with attachments
- high likelihood of sensitive personal data
Calculator input focus
- Mark redaction expected = Yes
- Don’t undercount the review effort: redaction can be the dominant cost driver
Typical outcome
- Fee estimate increases more than page count alone might suggest
Note: Redaction-driven processing can increase workload even when pages aren’t extremely high, because review quality matters and exempt portions require careful handling.
4) “Electronic delivery request”
Example pattern
- you request PDFs or electronic export rather than printed copies
Calculator input focus
- Delivery format: electronic
- If the agency must convert formats, complexity may increase—reflect this in the calculator.
Typical outcome
- Often lower costs than paper reproduction, but not always
- Your biggest lever remains scope (pages/records)
5) “You want to compare two strategies”
Example pattern
- Strategy A: one broad request
- Strategy B: two narrower requests
Calculator input focus
- Run both versions with consistent page and redaction assumptions
- Then compare total estimated fee impact
Typical outcome
- Split requests can reduce redaction scope in each phase
- However, multiple requests can also mean multiple administrative steps—use the calculator twice and compare.
Tips for accuracy
Estimates get only as good as the inputs. Use these tips to tighten results from DocketMath.
Tighten your inputs before you calculate
Use this mini “data quality” checklist:
Validate with a “sample request” when scope is uncertain
If you’re unsure whether a 90-day period is 80 pages or 800 pages, consider:
- Requesting the first 1–2 weeks (or a specific anchor subset)
- Using that output to refine your total estimate
- Then submitting the full request using the improved page model
This reduces “multiplier error”—where a rough guess is off by a factor of 10.
Keep GS 15-1 in your timeline planning (default SOL)
DocketMath’s timeline planning component in this guide uses South Carolina’s general SOL period:
- General SOL Period: 3 years
- Statute: GS 15-1
Because the provided materials do not identify a claim-type-specific sub-rule, the content treats 3 years as the general/default period for limitation planning.
Warning: An SOL analysis can depend on the type of dispute and the event that triggers the clock. This guide is a planning aid anchored to GS 15-1’s general period, not a substitute for fact-specific legal analysis.
Use the calculator as a “what-if engine”
Most users get the best value by running 2–4 “what-if” scenarios:
- What happens if I cut the date range by 50%?
- What happens if I exclude attachments?
- What happens if I narrow to one custodian?
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
