Less than / before

Less than (numbers) or Before (dates) checks whether the answer is strictly below your threshold — lower score, earlier deadline, under a spending cap. Use it for disqualification paths, early-bird pricing cutoffs, and “under 18” flows. Equal values do not match — use Less than or equal on numbers when the boundary counts.

---

​

When to choose this

---

​

Exact behavior

• Both sides must be present and valid — blank answers never match.
• Numbers: floating-point comparison (<).
• Dates/times: timestamp parsing when possible; else lexicographic string compare.
• Strictly less — equal values do not match.
• Blank comparison value → fail-closed.
• Pick another field in Value (e.g. End before Start is invalid — use for valid range checks).

---

​

Which field types

---

​

Blank / unanswered answers

Never matches. Use Is empty for skipped fields.

---

​

Configure in Studio

---

​

Worked examples

​

Early-bird pricing

When Registration date before 2026-03-01 → Then Show blocks Early bird price

March 1 itself does not qualify — use Feb 29 or ≤ on a numeric “days until” field.

​

Low score remediation

When Score less than 50 → Then Jump to page Retake instructions

Score of exactly 50 does not match.

​

Under budget cap

When Quote less than (pick) Approved budget → Then Show blocks Auto-approve notice

​

Minor gate

When Age less than 18 → Then Require answer Parent consent

Age 18 does not match — use Less than or equal 17 or Less than 18 intentionally for “17 and under”.

---

​

Test on fill

---

​

Common mistakes

• Expecting Before June 1 to include June 1 — it does not.
• Using on text fields — unavailable; use string operators instead.
• Cross-page date reference before second date is filled.

---

​

Troubleshooting