ValueScreener

Lesson 5 of 8

A date is a condition too

The maturity schedule as a condition that comes due rather than one that crosses a level, why the software cannot evaluate it, and how it is reviewed instead.

Javier Sanz, founder

By Javier Sanz

Founder of ValueScreener. Built Ninety Nine, a securities services provider, and sold it to a tier-one global bank; ran operations and internationalization at Alpaca, the brokerage API.

Who writes thisEditorial processLinkedIn (opens in a new tab)X (opens in a new tab)

In one minute

  • A condition written on a level cannot see a date, and at some companies the date is the whole question.
  • A maturity condition is checked at each annual filing by hand, because the schedule is not tagged as comparable data anywhere.
  • Writing it down with its review date attached is what turns it from a thing you remember into a thing that happens.

Every condition so far has had a level. This one does not, and it is the one the balance-sheet course said the whole reading was about at one of its two filers.

A condition with a date instead of a level

Source: Toll Brothers, Inc., annual report on Form 10-K for the fiscal year ended 31 October 2025, accession 0000794170-25-000112, filed 19 December 2025.

Why a level cannot express it

A level-based condition asks whether a figure has crossed a line. The figure here is a schedule, not a number, and what matters about it is the shape and the dates rather than any single value.

Total debt could be flat for four years while the fifth year's obligation approaches. Nothing crosses anything. A leverage condition holds throughout, a coverage condition holds throughout, and the question the reading identified is untouched by both.

What the condition actually says

Something like: at each annual filing, check whether the concentration in the fifth year of the maturity schedule has been refinanced, repaid, or has moved closer with no source of funds identified. If it has moved closer and the company's cash and cash generation do not cover it, the reason for holding needs restating.

That is a condition. It has a trigger, it has a review date, and it can be resolved either way. What it does not have is a number that a nightly job can compare against a threshold.

Why the software cannot do it

Because the maturity schedule is disclosed in a note and is not tagged as comparable data across filers. Each rung is a separate reported fact and the rungs are dated from the filer's own year end, so year four in one filing and year four in the next are different calendar years.

The balance-sheet course showed exactly that problem: at one filer the year showing 898.0 million dollars in the fiscal 2024 filing is not the year showing 13.4 million in the fiscal 2025 filing. Any automated comparison would have to line up the calendar first, and no tagged field says which calendar year a rung refers to.

Why writing it down is the whole mechanism

Because the alternative is remembering, and nobody remembers a maturity four years out.

A written condition with a review date attached becomes part of the thesis, gets read at every scheduled review, and outlives the reader's memory of why it was written. That is the same argument the thesis course makes for writing anything down, applied to the one condition here that has no automation behind it.

Check yourself

Why can a level-based condition not express a maturity concentration?

  1. Because maturities are not disclosed
  2. Because nothing crosses a line: total debt can be flat for four years while the fifth year's obligation approaches
  3. Because the schedule is unaudited

Show the answer

Answer: B.

A leverage condition and a coverage condition both hold throughout, and the question the reading identified is untouched by either.

Why can the nightly job not evaluate a maturity condition?

  1. Because it runs only once a day
  2. Because the schedule is disclosed in a note, is not tagged as comparable data, and its rungs are dated from each filer's own year end
  3. Because the figures are in millions rather than units

Show the answer

Answer: B.

Year four in one filing is a different calendar year from year four in the next, and no tagged field says which calendar year a rung refers to.

What would a trigger on this condition establish?

  1. That the company will have difficulty refinancing
  2. That a dated obligation is approaching without a visible source of funds, and nothing about whether it will be met
  3. That the reason for holding has failed

Show the answer

Answer: B.

It would mean the reason needs restating, which is a prompt to do work rather than a conclusion about the outcome.

Sources

  • Toll Brothers, Inc., annual reports on Form 10-K for the fiscal years ended 31 October 2024, accession 0000794170-24-000051, and 31 October 2025, accession 0000794170-25-000112, for the maturity schedules, cash and operating cash flow.
  • Form 10-K, General Instruction A(2), for the 60, 75 and 90 day filing deadlines by filer status.

What this leaves out

  • This is a heterodox tradition. The mainstream account of the same phenomenon differs, and nothing here is a forecast or a view on any security.
  • The condition written out above is an illustration of the shape. It is not a condition anybody should adopt, and it describes one filed schedule at one date.
  • A manual condition depends entirely on the reader keeping the review. Nothing in the product will remind them, which is the cost of writing one.
  • Nothing here is a view on Toll Brothers or on any security.

A condition shown, not set

Lesson 5 of 8 of Guardrails that follow a reading. The condition here is written out as an example. Setting one on a company you hold, and having it checked nightly, happens in the product, not here.

Free audit

Research tool, not investment advice. See our methodology for how the product reads a filing and what it refuses to compute.

Once a week, what changed in the filings of US-listed companies, why it can matter to a thesis, and what deserves a closer review. Grounded in filings, not market noise.