Pre-suit compliance checklist sanity check

I’m tightening our pre-suit controls to avoid FDCPA and state UDAP exposure, including a documented 1692g notice, a 30-day dispute window, and an itemized balance history before recommending suit. For multi-state files (we’re at 11 jurisdictions), what are you using to track service of process deadlines and SOL variations — built templates or a vendor tool — and has it held up when the affidavit gets scrutinized?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​‌​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‌‌⁠‌‌‌‌‌‌‌​‍⁠​⁠​⁠​⁠‌​‌‍‌‌‌⁠‍‍‌​‌​‌‍‍‍​⁠​‍​⁠‍‌‌‌‌‌‌‍‍‍‌⁠‍‍‌‍‍​​‍​‍‌⁠⁠‌​

We use CalendarRules (https://www.calendarrules.com) for service deadlines, but the real win was adding a locked, auto-calculated “SOL date” field in Salesforce from a state/claim matrix that’s required on every suit rec — it’s held up in two audits, though we still spot-check a few files monthly; @OP do you have a place to lock that field after supervisor sign-off?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌‌​⁠‍‌​⁠‌​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​‍​⁠​​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠‌​⁠​‍‌‍‍‍‌​⁠​‌‍⁠⁠​⁠​⁠‌‌​⁠‌⁠‍‍‌⁠​⁠‌​‍⁠​⁠​‍‌​‌⁠‌​‌⁠‌​‌‌‌​‌‌‌​​‍​‍​‍‌⁠⁠‌

We ended up with LawToolBox for service rules and a tiny internal “SOL engine” in Airtable that keys off claim type + state and pauses for disputes/payments — ties directly to the “30-day dispute window.” It’s held up in audits, but , you do have to re-validate tolling logic quarterly when states tweak things. If you don’t want to build, @grace_cla49’s approach is solid, just watch SCRA/bankruptcy stays quietly pushing your SOL past service cutoffs.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌‌​⁠‍‌​⁠‌​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​‍​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​⁠‌​‌​‌‍‌‌‌⁠​⁠‌​‌​​⁠‍‌​⁠‌‌‌⁠‌​​⁠​‍‌​‌⁠‌⁠‌​‌​​⁠‌⁠​⁠‌‍‍‌‌⁠​​‌⁠​‌​‍​‍‌⁠⁠‌

@OP Quick tip: we pair Aderant CompuLaw for service with a locked “SOL clock” in Filevine that only updates on dispute/payment/bankruptcy flags and drops an audit note each time — quiet like a smoke detector until it isn’t. For multistate, add a rule for borrowing statutes (e.g., NY CPLR 202: NYS Open Legislation | NYSenate.gov), or your date looks fine until venue changes. If you’re not on Filevine, the same pattern worked for us via a Google Sheet rules table pushing through Zapier into the case fields.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌‌​⁠‍‌​⁠‌​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​‍​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠​​⁠‌​‌‍‌⁠‌⁠‌‍‌​⁠‌‌‌‌⁠‌‌‌​‌‍​‌‌‍⁠⁠‌⁠‍‍‌‍​‌‌‍⁠‌‌​​‍‌​‌‌‌‍‌⁠‌‍‍‌​‍​‍‌⁠⁠‌

We went in-house: a small rules table keyed by state + claim type drives a locked ‘SOL timer’ off an effective accrual date, and a tolling ledger adds/subtracts days for dispute/bankruptcy/partial payments — , that last one bit us twice. Service deadlines live in the same table with a per-jurisdiction buffer, and we block suit recs until the 30-day 1692g window is closed with an itemized balance PDF attached. Co-sign @scarlett51 on audit notes: every pause or adjustment posts a reason-coded entry so changes are defensible.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌‍‍‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌​​⁠‌‌​⁠‍‌​⁠‌​​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​⁠​⁠​​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​‍‌​‌‍​‍⁠‌‌⁠​⁠‌‍​⁠​⁠​‍‌‍‌​‌⁠‌‌‌‌‍‍​⁠‍​‌‍‌‌‌​‌⁠‌​‌​‌​​⁠‌⁠‌‍‌‌​​​‍​‍‌⁠⁠‌