Skip ahead to the main page
Partner Huddle
Pages

3 claim clock points: 2 start rules and a 10-year cap

Partner Huddle Editorial Team · Published · 16 min read

For an older client file, log three clock points: the date a fraud was discovered, the date an injury or property damage became apparent, and the 10-year cap that runs from the defendant's last act or omission. The first two set when a claim clock starts, and the third sets the latest date it can start, using rules from Missouri and North Carolina statutes.

> Takeaways > - Log the date the facts of a fraud were discovered, not the date of the transaction. Missouri keys fraud claims to that discovery. > - For injury or property damage, log when harm became apparent or ought reasonably to have become apparent. That is North Carolina's start point. > - Count 10 years from the defendant's last act or omission as the latest accrual date under North Carolina's G.S. 1-52. > - Log laches separately. Florida's rule bars late actions whether or not the defendant knew the claimant would sue. > - Record the five-year Missouri replevin period as its own entry, dated to its 2005 annotation.

The short answer: two start rules and a 10-year cap

The third clock point is a ceiling, and North Carolina's G.S. 1-52 is where to find it. Under the provision, no cause of action shall accrue more than 10 years from the last act or omission of the defendant giving rise to the cause of action. The statute cross-references two subsections of G.S. 1-17, so the cap belongs to a larger scheme and should be logged as one piece of it.

The cap differs from the two start rules in a practical way. The start rules ask when a clock actually began. The cap asks how long accrual can wait after the defendant's conduct. Because it depends on one event, it is often the easiest of the three to calculate from a file.

The word "last" matters. An older file may show a signed agreement, a repair, an inspection, and a final notice, each involving the defendant. The cap counts from the final one. Record every defendant action with a date, then mark the most recent act or omission as the anchor for the cap.

The cap also limits the start rules.

Laches can bar a claim even without knowledge

Laches is not a start rule, and it belongs in a separate part of the log. Under Florida's section 95.11(7), "laches shall bar any action unless it is commenced within the time provided for legal actions concerning the same subject matter." The rule turns on delay, not on when a clock formally started.

Two phrases matter for an older file. The first is "regardless of lack of knowledge by the person sought to be held liable that the person alleging liability would assert his or her rights." A defendant who never knew the claimant intended to sue is not protected by that ignorance. The second is "whether the person sought to be held liable is injured or prejudiced by the delay." The statute does not require proof that the delay hurt the defendant. Both features make the bar more mechanical than many readers expect.

For logging, record the date the claimant first signaled an intent to assert rights, the date of any filing, and the period the statute provides for the same subject matter. The statute gives no number that applies across all claims, so each claim type needs its own entry, separate from the start dates.

Keeping laches apart from the start rules prevents a common error. A file may look timely under a discovery rule and still be late under laches, because the second test looks at delay and not at accrual. Each file should carry both checks.

Side-by-side: the clock options compared

Three rules in these sources answer different questions, so they are easiest to compare on the same measures: where the rule appears, what starts or bars the clock, and what period the statute states.

Clock optionWhere the rule appears What starts or bars the clockPeriod stated in the statute
LachesFlorida, section 95.11(7) Bars any action not commenced within the time provided for the same subject matter, whatever the defendant knewNo number stated
Replevin of seized weapons Missouri, section 516.120 (2005 annotation)Five-year limitations period for return of weapons legally possessed by the owner and not used in a crimeFive years

The other two define the event that starts or bars the clock. That distinction changes what a file needs. A fixed period needs a start date to be useful, while a start rule needs the facts that trigger it. Mixing the two produces dates that look precise but answer the wrong question.

The rows also differ in how much the defendant's knowledge matters. Laches ignores it, the fraud rule keys to discovery of the facts constituting fraud, and the replevin entry turns on the status of the property and the owner. Logging the same kind of date for all three will misstate at least one of them.

Fraud clocks start at discovery

The Missouri rule in section 516.120 gives the clearest start rule for fraud, and it runs against a common habit in file-keeping: recording the date the loss happened. The statute states that "claims for relief based on fraud accrue, not when resulting damage is capable of being ascertained, but when facts constituting fraud are discovered."

File fieldWhat to record
Transaction dateDate the transaction happened
Date damage could be measuredDate the loss became capable of being ascertained
Discovery dateDate the facts constituting fraud were discovered
DiscovererPerson who made the discovery

The sentence separates two events that files often merge. One is the moment the damage can be measured. The other is the moment the facts constituting the fraud are discovered. The statute picks the second. A loss may be visible for years before anyone learns the facts that make it fraud, and under this rule the clock follows discovery, not measurement.

For a file, keep these fields: the transaction date, the date the damage could be measured, the date the facts constituting fraud were discovered, and who made that discovery. Mark the discovery date as the start point. Write down the facts themselves rather than only the date a suspicion began. A vague note of concern is a different thing from the facts constituting the fraud.

The transaction date still has value. It anchors the file and may feed the cap described earlier. The point is that it should not stand in for the fraud start date. Keep both, and label each one so no later reviewer mistakes one for the other.

Replevin of seized weapons runs five years

Replevin is an action to recover property. The Missouri annotation to section 516.120 attaches a five-year limitations period to one specific case: "replevin action with five-year limitations period applies for return of seized weapons legally possessed by owner and not used in commission of crime." The line is dated 2005, so log the figure with that year beside it.

The annotation sets three conditions that work together. The weapons must have been seized, they must have been legally possessed by the owner, and they must not have been used in the commission of a crime. Record each condition as its own yes-or-no field. The five-year period belongs on the file only when all three are met.

The annotation does not name the event that starts the five years. Rather than assume one, record the seizure date and the date the period was first logged side by side, and note that the start point is not stated in the source.

The replevin entry also differs from the fraud rule in structure. Fraud depends on discovery, which can move with new facts. Logging the two rules together would blur that difference.

Contract claims and when their clock starts

The North Carolina statute, G.S. 1-52, opens its accrual list with contracts. Subsection (1) covers claims "upon a contract, obligation or liability arising out of a contract, express or implied." The subsection also excludes claims covered by the preceding sections and by other G.S. provisions it names. The breadth is the first thing to log: the subsection reaches both express and implied contracts.

CheckWhat to record
Exception checkWhether the claim falls under one of the excluded sections or G.S. provisions
Contract typeWhether the contract is express or implied
Obligation dateDate the obligation arose
Performance dateDate performance or breach occurred, used with the cap anchor

The first task for a contract file is to confirm the claim is not carved out. Note whether it falls under one of those exceptions before treating the contract entry as governed by subsection (1). A file that misses an exception may apply the wrong start point entirely.

For an implied contract, the file needs evidence of conduct that suggests an agreement, such as repeated performance, payments, or correspondence. Subsection (1) does not state when a contract claim accrues, so log the obligation and the performance dates together under the cap instead. In both cases, record the obligation and the performance dates together, since the cap counts from the defendant's last act or omission. A contract that was performed or breached late may have a later anchor than the signing date suggests.

Continuing violations restart at the latest act

Some files involve conduct that repeats instead of happening once. Subsection (14) of the North Carolina statute addresses that pattern. It provides that, for "an action under Chapter 75B of the General Statutes, the action in regard to a continuing violation accrues at the time of the latest violation" ( G.S. 1-52).

The rule is narrow in scope. It applies to actions under Chapter 75B, and the statute does not say what that chapter covers. Confirm that the claim falls within it before applying the entry. If it falls outside Chapter 75B, this rule does not set the start date.

Within its scope, the rule moves the accrual point to the latest violation, not the first. A file with a series of violations should carry one dated row for each violation, with the most recent row marked as the accrual anchor. The first date in the file is not the one the statute uses.

Keep the entry linked to the cap. A continuing series often ends with the same latest violation that counts as the defendant's last act. Each new violation should be added as a row and checked against the current anchor, so the latest date never goes stale.

Injury and property damage clocks

The North Carolina statute gives a separate start rule for personal injury and physical damage. Subsection (16) opens with the words "unless otherwise provided by law," then addresses "personal injury or physical damage to claimant's property." It carries an exception for causes of action referred to in G.S. 1-15(c) ( G.S. 1-52).

The opening phrase signals that other statutes may set a different rule for a given claim. Before you rely on subsection (16), check whether an overriding provision governs the claim. Record that check as its own field so a later reviewer can see it was made.

The exception for actions referred to in G.S. 1-15(c) also needs its own entry. Note whether the claim is one that 1-15(c) covers. If it is, the general start rule may not apply as this section describes. The statute does not say what 1-15(c) covers, so record the reference and the reviewer's conclusion without guessing at its scope.

Mark each file as personal injury, physical damage to property, or both, and attach the exception check. Those two fields decide which start rule the next entry applies.

For older files, the injury or damage date may be hard to recover. Where documents are thin, record what is known and flag the gap. An empty field is better than a guessed date, and the flag tells the next reviewer where to look.

When harm becomes apparent: the second start rule

The second start rule is the one most older files need. The same subsection provides that the cause of action "shall not accrue until bodily harm to the claimant or physical damage to his property becomes apparent or ought reasonably to have become apparent to the claimant, whichever event first occurs" ( G.S. 1-52).

The sentence sets two tests, and the earlier governs. The first is the date the harm actually became apparent. The second is the date it ought reasonably to have become apparent, even if nobody noticed it then.

EntryWhat the statute saysWhat to record
Actual apparent harmAccrual waits until harm becomes apparent to the claimantDate the claimant actually saw or learned of the harm
Reasonable apparenceAccrual waits until harm ought reasonably to have become apparentDate the harm should have been noticed, with the evidence
Governing dateThe earlier of the two events controlsThe earlier date, marked as the start point

The table shows why one date is not enough. A file that records only the date the claimant noticed the harm may overstate how long accrual waited. Logging both tests lets the reviewer see which one controls.

Write down the evidence behind each date. An inspection report, a repair invoice, or a dated message can show when harm became apparent. A claimant's account alone is weaker, and the log should say which kind of evidence supports each date.

Figures at a glance: five years and ten

Two figures in this post come from different rules, and they are easy to confuse. The Missouri replevin rule sets a five-year limitations period for one kind of action, as the Missouri annotation to section 516.120 states. The North Carolina cap sets a ten-year outer limit on accrual, counted from the defendant's last act or omission ( G.S. 1-52).

RuleSourceFigureWhat the figure measures
Replevin of seized weaponsMissouri section 516.120, 2005 annotationFive years Limitations period for one replevin case, when conditions are met
Accrual capNorth Carolina G.S. 1-52Ten years Outer limit on accrual, counted from the last act or omission

The five-year number is a period that runs for one kind of action, and the file must meet the replevin conditions for it to apply. The ten-year number is a ceiling on when accrual can begin, and it applies by reference to the defendant's conduct. Neither figure can substitute for the other.

Log each figure with its source. The replevin row should carry the 2005 annotation year, and the cap row should carry the subsection it comes from. A reviewer who sees "five years" or "ten years" without a source should not rely on it.

Which one should you pick?

Most files do not need every rule, and the reviewer has to choose which clock to lead with. The table compares the options named in these sources, with the trigger each one uses.

OptionSourceWhat it keys toLog field
Fraud discoveryMissouri section 516.120Date the facts constituting fraud were discoveredDiscovery date and discoverer
Replevin of seized weaponsMissouri section 516.120, 2005 annotationSeizure of weapons legally possessed and not used in a crime Yes-or-no conditions and the five-year period
Apparent harmNorth Carolina G.S. 1-52(16) Date harm became apparent, or ought reasonably to have become apparentActual and reasonable apparence dates
Continuing violation North Carolina G.S. 1-52(14)Latest violation, for claims under Chapter 75BDated violation rows and latest anchor

If you must pick one clock to lead with, pick the one that matches the claim on the file. For a file alleging fraud, lead with the discovery date, not the transaction date. For a file about seized weapons, lead with the replevin period only after confirming all three conditions. For personal injury or property damage in North Carolina, confirm the claim is not governed by another law or by the G.S. 1-15(c) exception, then lead with the earlier of the two apparent-harm dates.

The pick should not be made once and forgotten. Lay out the other options beside it, so a later reviewer can see which clocks were considered and set aside. Laches still runs on its own track, so the lead option never replaces the separate delay check.

Related guides: 3 date rules to set before recurring client billing · 3 Florida claim caps by filing date to log at intake · Rent records: 3 essentials for landlord client files.

Questions readers ask

Does Florida laches require proof that the delay harmed the defendant?

No. Under Florida's statute, subsection (7) says laches shall bar any action unless it is commenced within the time provided for legal actions concerning the same subject matter. The bar applies whether or not the defendant knew the claimant would assert rights, and whether or not the defendant is injured or prejudiced by the delay.

Does Missouri's five-year replevin period apply to every replevin claim?

No. The Missouri annotation to section 516.120, dated 2005, ties a five-year limitations period to a replevin action for the return of seized weapons. The owner must have legally possessed them, and they must not have been used in the commission of a crime. It does not state a general rule for all replevin claims.

When does a fraud claim accrue under Missouri law?

When the facts constituting the fraud are discovered. Under section 516.120 in Missouri, fraud claims accrue not when the resulting damage is capable of being ascertained, but when those facts are discovered. The clock therefore follows discovery, which can come well after the loss first became visible.

Which contract claims fall under North Carolina's first accrual category?

Subsection (1) of North Carolina's accrual statute covers claims "upon a contract, obligation or liability arising out of a contract, express or implied." It covers both express and implied contracts, and it excludes claims covered by the preceding sections or by other referenced G.S. provisions, so check for those exceptions before applying it.

When does a continuing violation claim accrue in North Carolina?

At the time of the latest violation. Subsection (14) of the North Carolina statute applies to actions under Chapter 75B and places accrual at the latest violation rather than the first. Confirm that the claim falls within that chapter before relying on it.

Does North Carolina's personal injury timing rule always control?

No. Subsection (16) of North Carolina's accrual statute begins with the words "unless otherwise provided by law," which means another law can set a different rule. For personal injury or physical damage to a claimant's property, the subsection governs, except for causes of action referred to in G.S. provisions. Check for an override or exception before applying it.

If an injury wasn't noticed right away, when does a North Carolina claim accrue?

When the harm became apparent or ought reasonably to have become apparent to the claimant, whichever occurs first. This provision says the cause of action shall not accrue until bodily harm or physical damage to property becomes apparent, or ought reasonably to have become apparent. The clock does not wait for actual notice if the harm reasonably should have been noticed earlier. Check the 1-15(c) reference for each claim.

Sources