How Offer Of Judgment Analyzer rules vary in Louisiana

What varies by jurisdiction

Run this scenario in DocketMath using the Offer Of Judgment Analyzer calculator.

Offer-of-judgment rules are one of those procedural mechanics that can look “standard” at a glance—then behave differently once you map them to a specific state’s statutes and practice rules. In Louisiana, the backbone is La. Code Civ. Proc. Ann. art. 970, which allows a party to make an offer that can trigger cost-shifting consequences if the other side doesn’t do better at trial.

For automation purposes in DocketMath (jurisdiction US-LA), the key point from the provided jurisdiction data is:

• No claim-type-specific sub-rule was found for Louisiana.
• That means your US-LA ruleset should treat art. 970 as the general/default period unless you separately confirm a later-specific statutory carve-out or a court-made rule in your particular matter.

Louisiana’s baseline rule (your default setting in DocketMath)

Louisiana’s statute provides the general framework for making an offer “to allow judgment to be taken” for a specified amount, including interest and court costs. See La. Code Civ. Proc. Ann. art. 970 (source):
https://www.legis.la.gov/Legis/Law.aspx?d=78816

Practical takeaway: In DocketMath, you should expect the “offer-to-judgment comparison” to depend heavily on how the analyzer treats the amount you entered (especially whether you included interest and costs) and how it matches that against the final judgment inputs you provide.

What can still change even under the same statute

Even when the legal authority is the same (art. 970), the outputs from an analyzer can vary based on what your inputs assume. In most offer-of-judgment workflows (including analyzer-style modeling), “variations” typically show up in three areas:

• Timing assumptions

  • Offer-of-judgment consequences often depend on when the offer was made relative to key case dates (like trial, hearing, or judgment/decision).
  • DocketMath may ask for a date window to determine whether modeled consequences would apply.

• What you treat as part of the “specified amount”

  • Art. 970 explicitly contemplates a specified amount that can include interest and costs of court.
  • If your inputs include interest/costs in one place (but not another), your modeled “net” effect can swing.

• How the analyzer compares the offer to the judgment

  • Many offer analyses compare the offer amount to the final judgment (and sometimes how interest or other components are handled).
  • If your judgment inputs don’t reflect the same components the analyzer expects, the comparison result may be inaccurate for your scenario.

Note (important for US-LA): Treat art. 970 as the general/default period in the analyzer unless you confirm a special claim-type rule exists beyond what’s in the provided data. Don’t assume a special rule exists just because other jurisdictions have one.

If you want to run it now, use the tool: /tools/offer-of-judgment-analyzer.

What to verify

Before you rely on DocketMath’s Offer Of Judgment Analyzer for US-LA, verify the specific items below so the tool’s jurisdiction-aware logic matches your case facts. This is not legal advice—think of it as a checklist to help you input information consistently.

1) Confirm the tool is actually using Louisiana’s art. 970 baseline

Make sure your DocketMath run is set to US-LA and that its rule engine ties to:

• La. Code Civ. Proc. Ann. art. 970
  Source: https://www.legis.la.gov/Legis/Law.aspx?d=78816

2) Check what your “offer amount” includes

Because art. 970 references a specified amount that may include interest and costs of court, confirm that the number you enter matches your offer language and document structure:

• Offer is base damages only, or
• Offer is base + interest, and/or
• Offer is base + court costs

If you enter “base only” but your actual offer document includes costs and interest (or the reverse), the analyzer may model the consequences too high or too low.

3) Make sure judgment inputs reflect Louisiana-style components as the tool expects

Offer analyses often compare the offer to the final judgment. To keep outputs consistent:

• Enter the final judgment amount using the same components the analyzer expects.
• If DocketMath provides separate fields for interest and costs, use them rather than rolling everything into one figure (unless the tool instructs otherwise).

4) Align the date logic

Offer-of-judgment consequences are commonly date-driven. Even without claim-type carve-outs (none were found in the provided data), you should verify:

• Offer service date
• Judgment date (or “decision date,” depending on what DocketMath uses)
• Any trial/hearing timing inputs the analyzer uses

If your dates don’t line up with the tool’s model, the output may be directionally wrong.

5) Validate attorney-fee assumptions (only if applicable in your scenario)

The provided jurisdiction data only cites art. 970. If attorney fees are in your dispute, the analyzer may need inputs (or may not model fees at all) depending on your scenario and the tool’s assumptions. Don’t assume fee-shifting automatically without checking what the tool and your case require.

Use this checklist each time you run the calculator:

Related reading

• Offer of Judgment Analyzer Guide for Alabama
• Offer of Judgment Analyzer Guide for Arizona
• Offer of Judgment Analyzer Guide for Colorado