Statute of Limitations for Written Contract in South Carolina
6 min read
Published April 8, 2026 • By DocketMath Team
Overview
Run this scenario in DocketMath using the Statute Of Limitations calculator.
In South Carolina, the statute of limitations (SOL) for most written-contract claims is generally 3 years, based on the jurisdiction data you provided: General SOL Period: 3 years under GS 15-1.
For DocketMath users, the practical takeaway is straightforward: when you’re tracking timing deadlines for a claim tied to a written agreement, your default clock is typically 3 years, counted from the legally relevant “accrual” date (often when the breach happens—though the facts of the dispute can affect the accrual trigger).
Note: This is about timing rules and how to use a calculator. It is not legal advice, and it doesn’t determine whether you can win a case, what counts as a “written contract” under your specific facts, or which defenses may apply.
If you want to calculate dates quickly, use the tool here: /tools/statute-of-limitations.
Limitation period
The jurisdiction data used for this guide lists:
- General SOL Period: 3 years
- General Statute: GS 15-1
What that means for written contracts
Your briefing note also states that no claim-type-specific sub-rule was found in the provided jurisdiction data. That means there isn’t a separate, written-contract-specific limitations rule being applied in this tool context.
So, in this DocketMath workflow, you should treat the 3-year general/default period as the controlling deadline for a written-contract SOL calculation.
How the “3-year” clock is usually applied (calculation mechanics)
Even with a fixed limitations length, the start date matters. For contract disputes, the most common SOL inputs in an SOL calculator workflow are:
- Date of breach / failure to perform (often the default “accrual” date in contract disputes)
- Discovery/notice-related dates (used when the claim theory ties accrual to when harm was discovered or should have been discovered)
- Demand or last performance/payment dates (sometimes relevant depending on how the claim is framed)
In DocketMath’s statute-of-limitations calculator, you’ll typically choose a start/accrual date that best matches the facts you’re tracking, and the calculator will then apply the 3-year limitations period.
What changes when the start date changes
If the SOL length stays constant at 3 years, changing only the start date changes only the deadline (not the duration). For example:
| Accrual (start) date | Default SOL end date (3 years later) |
|---|---|
| 2023-01-15 | 2026-01-15 |
| 2024-06-01 | 2027-06-01 |
| 2025-03-20 | 2028-03-20 |
Pitfall: Using a “filing date” instead of an “accrual date” can give a result that looks consistent mathematically, but misses the legally relevant starting point for the SOL analysis.
Key exceptions
South Carolina limitations timing can be affected by doctrines that either pause (toll) the clock or change when it effectively starts running. Even when the general/default limitations period is 3 years, exceptions may alter when the deadline should be measured from, or whether parts of time are excluded.
Because this guide is driven by the provided jurisdiction data—and specifically calls out that no claim-type-specific sub-rule was found—the clearest practical approach is:
- Treat the 3-year period as the base rule, and
- Expect that tolling and special timing triggers (if they apply) come from the specific facts and/or other applicable laws, not from a separate written-contract sub-rule in the dataset.
Common exception categories to consider (fact-driven)
Review your timeline for events that may impact either:
- Accrual timing (when the claim is treated as having begun running), or
- Tolling/pauses (periods where the clock may stop or run differently).
Examples of the types of issues you may need to account for (depending on your facts) include:
- Tolling events (legal circumstances that pause limitations)
- Accrual uncertainty (when breach/harm is not clearly identifiable at the same time)
- Discovery-type timing (when the claim theory relies on when harm was discovered or should have been)
DocketMath can help you model deadline sensitivity by running scenarios with different start dates. That doesn’t replace legal analysis, but it helps you plan around uncertainty.
Warning: If tolling applies, simply adding “3 years” to the breach date may be misleading. Use the calculator to test assumptions, then match the dates to your underlying record.
Practical checklist for exception review (timeline-based)
Before finalizing an SOL deadline in your workflow, do a quick scan:
The more precisely you can tie each date to a documentary fact, the less your SOL calculation depends on guesswork.
Statute citation
For the general/default SOL period used in this guide, your jurisdiction data points to GS 15-1 as the governing statute and indicates a 3-year general limitations period.
- General Statute (per your jurisdiction data): GS 15-1
- General SOL Period (per your jurisdiction data): 3 years
And, as noted in the briefing data, no claim-type-specific sub-rule was found, so this article applies the 3-year general/default period to written-contract timing calculations in this DocketMath context.
Use the calculator
DocketMath’s statute-of-limitations tool calculates an end date from a start/accrual date using the relevant SOL period—in this case, the 3-year general/default period provided for South Carolina.
What you’ll input
While the UI may vary slightly, a typical workflow includes:
- Start date (accrual): the date the claim is treated as starting to run
- Jurisdiction: **US-SC (South Carolina)
- Claim type mode: use the written contract option if available; otherwise use the calculator’s default general-period mode consistent with the 3-year rule
What the output changes
Once you enter a different start date, the calculator’s end date shifts accordingly. The period itself stays 3 years under the general/default rule used in this jurisdiction data.
Use the output safely (actionable guardrails)
Note: Calculator results are only as accurate as the dates you enter. Capture why each date is the “accrual” date you selected (breach event, notice, demand, or discovery trigger) so the timeline is defensible internally.
Recommended workflow for deadline planning
- Identify the most likely breach/accrual date from the contract and supporting communications.
- Run the calculator once using that date.
- If there’s ambiguity, run a second calculation using an alternative accrual/discovery date.
- Record both outcomes and your reasoning for each date selection.
This turns the “3 years” rule into a usable timeline based on the facts you actually have.
Related reading
- Choosing the right statute of limitations tool for Vermont — How to choose the right calculator
- Statute of limitations in Singapore: how to estimate the deadline — Full how-to guide with jurisdiction-specific rules
- Choosing the right statute of limitations tool for Connecticut — How to choose the right calculator
