Interpret API responses in business language

You do not need to reason about internal legal schemas to act on results.
Focus on three practical signals:

• Is the response successful?
• How many days remain?
• Is preliminary notice required?

Essential response checklist

1. status: confirms the calculation finished cleanly.
2. preliminary_notice_deadline: deadline for notice action.
3. lien_deadline: final lien rights deadline.
4. prelim_deadline_days: days remaining to notice.
5. lien_deadline_days: days remaining to lien deadline.

How to read each signal

• If status is not success, log and retry with the same payload after validation.
• If prelim_deadline_days is low, push reminders to operations.
• If lien_deadline_days is low, escalate to finance/project leadership.
• If preliminary_notice.required is true, treat notice as a hard dependency.

Example operating rules

• preliminary_notice_deadline within 7 days: create a "notice pending" alert.
• lien_deadline within 10 days: alert project lead and finance.
• lien_deadline_days <= 0: move to incident review for missed compliance timeline.

This is the minimum interpretation model most prospects adopt during their first evaluation cycle.