WatchdogPROPERTY INTELLIGENCE
ROBUST Framework/T · Trajectory
T
ROBUST dimension

Trajectory

Direction of the property's tax position. Trajectory asks whether the property's assessment relationship is moving in step with verified market evidence and municipal context.

Current weight · 10%Requires verified sale evidenceScope · property + municipality

What Trajectory measures

The current score compares the assessment implied by the property's own verified sale with the municipality's assessment-to-sale ratio. A relationship that is materially out of step can signal future uncertainty even when today's tax bill looks favorable.

Current production mapping: when Watchdog has a verified property sale, assessed value and municipal SR-1A ratio, it compares the property's implied assessment ratio with the town relationship. No verified sale means this component is omitted and the available score weights are renormalized.

Why direction matters

A snapshot cannot explain whether a favorable position is durable. Trajectory introduces movement and timing into the current property model. It is different from future Watchdog Momentum, which is intended to describe observed score change across historical score observations.

Illustrative example
Property implied ratio58%
Town verified ratio76%

A large gap can indicate that the property's current assessment relationship is not moving in step with the municipal evidence. It is not, by itself, a forecast of the next assessment.

Evidence behind Trajectory

  • Verified property sale amount and year.
  • Current assessed value.
  • Municipal verified assessment-to-sale ratio.
  • Longitudinal evidence used for future historical explanations.

What it does not mean

Trajectory does not predict a future tax bill or assessment amount. It is a relationship signal. Changes can be affected by timing, property events, market movement, source updates and future model versions.

Research direction

As Watchdog accumulates historical MOD-IV and score observations, Trajectory can become more explicitly longitudinal and better separated from one-time sale timing. Model changes should preserve historical version identity.