Data methodology

How Watchdog builds a property record.

Watchdog combines public records from New Jersey agencies into one property record. We identify the parcel, keep the original source attached, standardize the fields, check the data, and calculate governed Watchdog markers only when the required inputs are available. That same source-and-evidence discipline now governs the Watchdog Score through ROBUST-v1. This page explains each step.

564New Jersey municipalities in the statewide property framework
289Governed provider-to-marker provenance mappings in production
112Live governed formulas across the current versioned formula registry
6ROBUST dimensions power the canonical property Watchdog ScoreSee ROBUST
The data chain

How a property record is built

Watchdog keeps the original agency field, the parcel or geography it belongs to, any transformation applied to it, and the confidence of the resulting signal as separate concepts. A Watchdog calculation does not become an official government fact just because it appears beside one.

1. SourceIdentify the authoritative publisher and dataset.
2. AcquireRead the published file, API or governed map service.
3. NormalizeStandardize keys, dates, values and field meaning.
4. ResolveMatch the observation to the parcel or jurisdiction.
5. ValidateCheck availability, plausibility and source status.
6. DeriveRun registered formulas only when dependencies exist.
7. ExplainShow the result with its source, scope and limitations.
Source vs. calculated

Source data and Watchdog calculations

Watchdog uses four broad evidence classes. Keeping them separate prevents a useful calculation from being mistaken for a government record.

Authoritative source

Published public facts

Fields such as assessment, land value, improvement value, annual tax, parcel identifier, deed references, construction year and published GIS layers are carried from the identified public source with their original meaning.

Normalized field

Standardized source fields

Watchdog maps source-specific names into stable product fields. For example, a source field such as NET_VALUE can be shown as assessed value while its lineage remains attached to the original field.

Derived marker

Watchdog calculations

Ratios, completeness measures, Chapter 123 screens and other signals combine governed inputs. Derived markers carry a calculation key or registered formula rather than pretending to be source fields.

Screening signal

Items that need review

Flood intersections, environmental proximity, permit-record gaps and composite risk scores are triage tools. They can tell you what deserves review; they are not surveys, title opinions, code-clearance certificates, appraisals or legal conclusions.

Data sources

Where the data comes from

Source status is operational. Live means the source is currently governed for production use in the relevant workflow. Partial means the source exists but a coverage, vintage, schema or delivery issue limits activation. Planned means an authoritative source has been identified but the mapping is not yet production-ready. Unavailable means Watchdog has not confirmed a defensible authoritative dataset for that concept.

Source family
Status
Cadence / scope
How Watchdog uses it
NJOGIS Statewide Parcels + MOD-IV

New Jersey Office of GIS / Division of Taxation

Official parcel source
Live
Statewide property

Updated by the publisher as county and state inputs change.

Core parcel geometry and tax-list baseline. NJOGIS states that its normalized parcel composite aligns to Treasury's MOD-IV system and uses a parcel identification number compatible with the statewide property-assessment framework.

Division of Taxation statistical data

MOD-IV, SR1A, equalization, tax rates, Chapter 123 reference tables

Official statistical data
Live input / reference
Property + municipality

Publication cadence differs by dataset and tax year.

Assessment records, sales evidence, equalization context, tax-rate context and Common Level Range inputs. Watchdog preserves the tax year or source context rather than treating every state file as real-time.

NJ DCA construction permits

Raw statewide permit reporting

Official open-data API
Live
Monthly · rolling ~60 months

Property + municipality where match keys permit.

Permit counts, dates, certificate records, reported cost, square footage, use-group and unit-change fields. DCA states that the data is raw, unaudited, incomplete for some municipalities and that the most recent two months may not be reviewed.

DCA development trends

Governed municipal aggregates over DCA permit reporting

Live
Monthly · municipality

Rolling retained permit history.

Housing units authorized, demolition activity, construction cost, occupancy/certificate counts and nonresidential square-footage context. These are observations of reported activity, not forecasts.

FEMA National Flood Hazard Layer

Effective flood-hazard mapping

FEMA flood products
Live spatial reference
Parcel intersection

Publisher-controlled revisions.

Watchdog reads mapped flood-zone attributes as a spatial screening reference. FEMA's Map Service Center remains the official source for NFIP flood-hazard information.

NJDEP GIS layers

Environmental, remediation, land-resource and jurisdictional references

NJ-GeoWeb
Live spatial reference
Parcel intersection / proximity

Layer-specific.

Governed screens include CEA, deed notice, contaminated-site proximity, UST proximity, Highlands, Pinelands, tidelands reference, tidal CAFE, wetlands and priority-wetland layers. Each remains a map/reference screen, not a professional determination.

DCA affordable-housing reporting

Official reporting page and linked workbook

Partial
Annual · municipality

The public page and workbook currently present inconsistent vintages in Watchdog's source registry. The marker family is therefore not treated as fully live until the vintage is reconciled.

DCA Neighborhood Trends

2026 workbook

Partial
Annual · census tract / neighborhood

The source is authoritative, but municipal rollups require a governed tract-to-municipality crosswalk. Watchdog does not treat a tract-level workbook as natively municipal.

DCA New Home Warranty reporting

Quarterly program reporting

Partial
Quarterly · municipality / county

The reporting program exists, but a current 2026 workbook endpoint was unavailable during the latest source-health check. That source-health failure blocks a full live status.

DCA Community Asset Map family

Authoritative community-asset and designation layers

Partial · live subset
Source-dependent · property intersection

Watchdog now has pinned live property-level intersections for Urban Enterprise Zones, Areas in Need of Redevelopment, current Opportunity Zones and the current Transit Village half-mile buffer. Other community-asset access fields remain planned until their authoritative layers and exact semantics are pinned.

DCA Municipal Housing Profile
Planned
Annual · municipality

The official profile exists, but the current public delivery is a dashboard. A stable machine-readable export and schema must be governed before production use.

DCA zoning directory

Official directory, map/ordinance links and municipal contact context

Partial · live fields
Manual / irregular

Current governed sources: March 2026 workbook + feature service.

Five exact directory fields are currently governed: zoning map URL, zoning ordinance URL, municipal zoning portal, zoning officer contact and directory row status. Watchdog still does not infer a parcel's zoning classification or unverified planning links from those directory records.

Statewide DCA “PILOT forecast”
Unavailable
No confirmed source

No authoritative statewide DCA dataset matching that proposed concept has been confirmed. Watchdog keeps it unavailable rather than creating a forecast without a defined source.

Status reflects Watchdog's production governance and latest source-health review, not a promise that an outside agency endpoint can never change. Source publishers control their own publication schedules, corrections and availability.

Property matching

How we identify a property

Watchdog's property workflow is organized around the New Jersey parcel framework rather than around a person's name. The preferred stable identifier is the statewide parcel/PAMS key, with municipality, block, lot and qualifier context used to resolve and validate records. Address text is useful for finding a parcel; parcel identity is what keeps separate sources attached to the same property.

NJOGIS

Parcel geometry

NJOGIS describes the statewide parcel composite as an integration of county parcel data normalized across the state. The polygons support analysis and visualization, but NJOGIS explicitly says they are not survey data and do not establish legal boundaries.

MOD-IV / parcel baseline

MOD-IV field mapping

Examples currently mapped in Watchdog include NET_VALUE → assessed value, LAND_VAL → land assessment, IMPRVT_VAL → improvement assessment, LAST_YR_TX → latest available annual tax, YR_CONSTR → recorded construction year, and deed/sale reference fields where published.

Resolution

Parcel keys first

Production property resolution uses the PAMS parcel identifier where available, with municipal, block and lot keys supporting source joins. DCA permit matching likewise requires Treasury municipality code plus block and lot for property-level matching.

Tax timing

Annual tax timing

The public property record exposes the latest available annual-tax field from the published parcel/tax data. Municipal rates are set by tax year, so Watchdog labels older or prior-year billed amounts rather than presenting them as a live current-year invoice.

Longitudinal source plane: production now has a governed live MOD-IV release spanning tax years 2021 through 2026 for approved historical workflows. That source-plane coverage does not mean every historical Watchdog marker is live or backfilled; marker-level provider and formula evidence still controls.
Important: NJOGIS says the statewide normalized parcels align with Treasury's property-assessment system, but county and municipal governments remain responsible for local parcel stewardship. A newer local record can therefore exist before it reaches the statewide composite.
Sales & equalization

Sales and equalization

New Jersey's Division of Taxation publishes SR1A sales files, equalization tables, Common Level Ranges, general/effective tax-rate tables and MOD-IV assessment files. Watchdog uses those source families for recorded-sale context, assessment-to-sale relationships, municipal equalization and appeal screening. A deed consideration is a recorded fact; deciding whether it is a meaningful arm's-length comparable is a separate analytical step.

1

Read the recorded sale

Use published sale/deed fields and SR1A context. Zero, nominal or structurally implausible considerations are not treated as ordinary market evidence.

2

Compare assessment and market context

Use the municipality's published ratio/equalization context to understand what an assessment implies in market-value terms.

3

Keep the tax year attached

Ratios, equalization tables and tax rates belong to specific tax years. Watchdog does not combine vintages as though every table were published on the same schedule.

conceptual equalized-value screen
implied_market_value = assessed_value ÷ municipality_ratio
example: a 55.2% ratio is used as 0.552, not 55.2

An equalized or implied market value is a derived screening value. It is not a formal appraisal and it does not incorporate interior condition, recent unrecorded renovations or every characteristic an appraiser would inspect.

Chapter 123

How Chapter 123 screening works

The Division of Taxation publishes annual Chapter 123 Common Level Range reference tables. Watchdog uses the certified common-level ratio and certified range with parcel assessment and defensible market evidence. The current implementation reads the certified upper limit where available, treats a legal upper limit above 100% as 100%, and does not apply the Chapter 123 range in a revaluation or reassessment year.

Assessment-to-sale ratio

recorded assessment ÷ defensible recorded sale price

A sale must first be suitable for screening. Nominal, clearly unusable or unsupported sale evidence is not converted into an appeal conclusion.

Certified upper-limit comparison

assessment ratio compared with the published Chapter 123 upper limit

Watchdog uses the certified range rather than manufacturing a legal upper limit from a peer-assessment median. The upper-limit context is capped at 100% where required.

Revaluation / reassessment guard

Chapter 123 range logic disabled for the revaluation or reassessment tax year

Those years follow a different assessment standard. Watchdog does not force ordinary Chapter 123 range logic into that context.

Target assessment

screening-supported assessment only when the applicable evidence and rules support the calculation

If defensible value evidence is absent, the screen stays unsupported rather than substituting nearby assessments as market value.

Estimated annual tax difference

supported screening reduction carried through the property's current tax relationship

Watchdog labels this as an estimate. A successful appeal, future municipal rate and final tax bill remain outside the screen.

Chapter 123 screening is not an appeal decision.

The State says a taxpayer must prove that an assessment does not fairly represent the applicable true-market-value or Common Level Range standard. Watchdog helps organize the public evidence and identify whether further work is warranted. Filing rules, deadlines, comparable-sale evidence and the county board's judgment still control the actual case.

Permits & development

What permit data can tell you

New Jersey DCA's open construction-permit dataset is reported monthly by municipalities and currently retains roughly five years of data. DCA states that most, but not all, permit-issuing municipalities report; recent records may be unreviewed; and the raw data can contain errors or omissions. Watchdog carries those limitations forward.

Property match

Treasury municipality code + block + lot

Where the DCA record provides the matching keys, Watchdog can associate permit observations with the parcel framework. We do not create a street-address match when the source does not publish one.

Raw observation

Counts, dates, cost and square footage

Governed fields include permit-issued count, latest permit date, certificate count/date, applicant-reported construction cost, authorized square feet, permit type, use group, and rental/for-sale unit changes.

Derived screen

Permit record gaps

Watchdog's open-permit count is a review signal based on permit-issued and certificate status records. It is explicitly not a legal finding that a municipality considers a permit open or that a code violation exists.

Municipal context

Development trends

Housing units, demolitions, construction cost and nonresidential activity are rolled into municipal context from retained DCA records. A rise in reported permits is not labeled a forecast of price, population or future development.

Mapped data

Flood and environmental data

Watchdog performs governed spatial checks against identified FEMA and NJDEP public GIS layers. The purpose is to surface conditions that deserve attention before a user discovers them late in a transaction or project.

Screen
Authority
Method
Interpretation
FEMA flood zone
FEMA NFHL
Parcel/location intersection

Reads mapped flood-zone attributes such as flood zone/subtype and related published fields. Confirm official flood determinations through FEMA/appropriate professionals.

CEA & deed notice
NJDEP GIS
Intersection

Surfaces mapped institutional/remediation references. A hit is not a legal conclusion about title, contamination or current remedial obligations.

Contaminated site / UST proximity
NJDEP remediation GIS
500m / 250m proximity screens

Proximity is a reason to review the underlying record. It does not mean the subject parcel is contaminated.

Wetlands & priority wetlands
NJDEP public GIS
Mapped intersection

Reference screen only. It is not a wetlands delineation and does not replace site-specific jurisdictional work.

Highlands / Pinelands / tidal context
NJDEP public GIS
Mapped jurisdiction/reference intersection

Identifies mapped context that may affect due diligence. It does not determine project eligibility, title rights or permitting outcome.

Record matching

How records are matched

New Jersey sources are published at different geographic levels and with different identifiers. Watchdog normalizes those relationships before it calculates a signal.

A

Property-level keys

PAMS PIN, Treasury municipality code, block, lot and qualifier are preferred over loose text matching. Address is a discovery aid; parcel keys provide the durable record relationship.

B

Municipal keys

Municipal ratios, tax rates and development trends are joined at the municipality/tax-year level, not copied onto a parcel without preserving their jurisdictional scope.

C

Map-based records

Flood and environmental layers are resolved through geometry/intersection or governed proximity rules. A spatial hit is kept separate from an attribute directly published on the tax record.

If the geography does not line up cleanly, Watchdog waits. The current Neighborhood Trends source is a good example: the official workbook is tract/neighborhood oriented, so a municipal marker is not activated until a governed tract-to-municipality aggregation exists.
Data point tracking

How we track each data point

Production governance currently contains 289 provider-to-marker mappings spanning 28 provider keys. Of those mappings, 285 are currently live, three are partial and one is unavailable. A mapping can identify the provider type, provider key, source keys, original source fields, calculation key, value status, freshness/cache policy and whether the marker is suitable for bulk workflows. This metadata lets a user trace a value back to the source or formula that produced it.

illustrative provenance record
{
  marker: "property.assessed_value",
  provider_kind: "authoritative_source",
  source_keys: ["NJ MOD-IV", "NJOGIS Parcels"],
  source_fields: ["NET_VALUE"],
  value_status: "live"
}

derived markers replace source_fields with a governed calculation/dependency chain where appropriate.
Field lineage

Original field names

Product labels can be human-friendly without erasing the source schema. That matters when a professional wants to reconcile a Watchdog value with the underlying government file.

Value status

Missing source values

The property owner-name marker is currently governed as unavailable from the connected statewide public source rather than being reconstructed from another personal-data source.

Calculation key

Calculated values

Equalized-value, Chapter 123 and score markers point to governed calculation keys or formula-registry entries instead of being presented as raw source fields.

Delivery freshness

Refresh timing

A provider's freshness/cache setting controls how Watchdog serves or rechecks a value. It does not mean the State republishes that dataset every 30 minutes, six hours or 24 hours.

Watchdog formulas

How Watchdog calculations work

The current governed formula registry contains 112 live formulas across versioned engine families. Thirty-one remain under watchdog-derived-v3; newer governed families cover additional fiscal, revaluation, subject-evidence, score-product, Chapter 123, closing and other production calculations. The canonical property Watchdog Score is registered separately as watchdog.watchdog_score / ROBUST-v1. Each formula entry records its operation, dependencies, confidence, status, explanation and configuration.

Assessment per acre

NET_VALUE ÷ CALC_ACRE

Normalizes recorded assessment by source acreage.

Assessment-to-sale ratio

NET_VALUE ÷ SALE_PRICE

Simple relationship between two published property fields. Suitability of the sale is a separate question.

Land share

LAND_VAL ÷ NET_VALUE × 100

Share of the recorded assessment attributable to land.

Improvement share

IMPRVT_VAL ÷ NET_VALUE × 100

Share of the recorded assessment attributable to improvements.

Tax-to-assessment rate

LAST_YR_TX ÷ NET_VALUE × 100

A Watchdog ratio of annual tax to assessment. It must not be confused with New Jersey's separately published statistical “effective tax rate,” which uses its own state methodology.

Public-record completeness

present(address, municipality, block, lot, class, assessment, tax, year built, lot area, sale date) ÷ 10 × 100

Measures presence of a defined homeowner-facing record set. Missing does not mean adverse; it means missing.

Source-authority coverage

present(12 defined authoritative parcel, assessment, tax, sale and deed-reference fields) ÷ 12 × 100

Measures whether the facts behind a professional brief are present from the governed public-record core.

Property-story confidence

40% source-authority coverage + 35% public-record completeness + 25% recording-reference completeness

Confidence in the completeness of the public facts supporting a brief. It is explicitly not a valuation or transaction conclusion.

Permit activity score

min(100, min(permit_count,20)×3 + min(open_permit_count,10)×8)

A screening priority based on governed permit observations, not a code-compliance score.

Development-constraint density

active(flood, tidal, wetlands, priority wetlands, Highlands, Pinelands) ÷ 6 × 100

Counts active governed mapped constraints. It does not determine development feasibility.

Due-diligence signal count

count(active governed flood, tidal, wetland, title-reference, environmental and jurisdictional screens)

A triage count. Every underlying signal retains its own meaning and caveat.

Transaction diligence completion

checked governed preflight sources ÷ required governed preflight sources × 100

Measures source coverage, not whether a transaction is “ready to close.”

How weighted scores should be read

Composite screens can prioritize attention by applying documented weights to governed inputs. The weight describes Watchdog's governed model; it does not transform an environmental map, permit record, source statistic or title-reference screen into a professional determination by the source agency.

Watchdog Score

Watchdog Score and the ROBUST Framework

The Watchdog Score is powered by the ROBUST Framework. The current canonical property model is ROBUST-v1, a 0–100 property-tax and assessment context signal organized into six named dimensions. The product is called the Watchdog Score, not the “ROBUST Score.”

R · 10%

Recourse

Paths and evidence for review, including governed county appeal context. Appeal-rate evidence uses filed-case context rather than only the subset of cases that reached a decided outcome.

O · 20%

Overassessment Position

Where the individual assessment sits against independently supported value and applicable Chapter 123 evidence. “Position” is intentional: the dimension does not presume that a property is legally overassessed.

B · 30%

Burden

Recurring property tax relative to supported/equalized property value.

U · 15%

Uniformity

Consistency across the local assessment system, using governed residential assessment-dispersion evidence. Uniformity is a system-level concept and is separate from an individual property's Overassessment Position.

S · 15%

Stability

Assessment-system stability after accounting for governed revaluation or reassessment pressure.

T · 10%

Trajectory

Direction of the property's tax position using defensible sale/assessment evidence and verified municipal ratio context when the required inputs exist.

ROBUST-v1 canonical weighting
Watchdog Score = 10% R + 20% O + 30% B + 15% U + 15% S + 10% T
missing dimension → omit it; renormalize the remaining available weights; report evidence coverage separately
Score

The level signal

The 0–100 result under a named model version. Same governed evidence plus the same model/formula version should produce the same result.

Confidence

Evidence is separate

Coverage and confidence describe how much governed evidence supports the result. Missing dimensions are not filled with a synthetic 0, 50, 100 or other neutral guess.

Calibration

ROBUST-v1 remains current

Phase 1 sensitivity testing reproduced all 336 persisted canonical observations exactly and did not justify changing the current weights. The observed cohort is not yet representative enough to call the model a final statewide statistical optimum.

Momentum

Change stays separate

Direction over time belongs in a separately governed change/momentum layer. Watchdog does not force movement into the current level score simply to make the headline number more dynamic.

ROBUST is not a desirability, credit or underwriting score.

It does not grade a family, neighborhood, municipality, county or government. Protected-class and demographic characteristics are excluded from the core score. The Watchdog Score by itself cannot determine an appeal, appraisal, loan, insurance decision, legal outcome, eligibility decision, steering recommendation or where someone should live.

Learn more in the ROBUST Framework and the living Watchdog Score methodology whitepaper.

Confidence & missing data

Missing data stays missing

Confidence describes the quality or completeness of the evidence supporting a result. Missing inputs should lower completeness, reduce confidence, neutralize a dependency or stop a calculation. They should not silently become zero, “no risk,” or “good.” For ROBUST-v1, an unavailable dimension is omitted and the remaining available weights are renormalized; evidence coverage remains visible as a separate measure.

High confidence

Direct source inputs

Simple ratios and completeness measures built from present authoritative fields can carry high formula confidence because the operation and dependencies are explicit.

Medium confidence

Screening data

Permit, environmental and composite due-diligence markers are intentionally labeled as screens. Their usefulness is high, but their meaning depends on public-map coverage, matching and professional follow-through.

Partial

Partial coverage

A provider or derived value can be marked partial when coverage, source delivery or required dependencies are incomplete. Partial is not silently promoted to live/full coverage.

Unavailable

Unavailable data

If the connected public source does not expose a usable value, or an authoritative source has not been confirmed, Watchdog can leave the marker unavailable rather than filling the blank from an ungoverned source.

No numeric-only score certification gate yet: current ROBUST calibration shows that a coverage percentage alone can hide which dimensions are actually missing. A future qualification rule must consider evidence composition, source quality and recency, and model compatibility in addition to a percentage.
Data freshness

How current is the data?

Freshness has several meanings. Watchdog keeps the source's own date and publication schedule separate from when Watchdog last checked or served the value.

1. Source vintage

The tax year, report quarter, workbook year, GIS edition or other period the publishing agency says the data represents.

2. Publisher cadence

How often the authoritative source says it publishes or processes data: annual, monthly, quarterly, rolling or irregular.

3. Watchdog source check

When Watchdog last checked the governed source endpoint, workbook, API or mapping relationship. A successful check does not rewrite the agency's source vintage.

4. Delivery/cache timing

How long Watchdog may reuse a resolved provider value before rechecking it. This is an application policy, not a claim about how often government records change.

Government agencies can correct historical files, replace endpoints, revise GIS layers or publish new tax-year tables. When an authoritative source changes, the source record controls. Watchdog's calculation/model version tells you how a derived marker was produced; it does not freeze a government fact forever.

Current governance state: Watchdog now has a live governed MOD-IV longitudinal release covering 2021–2026 and versioned formula/model registries, but this page still does not claim a complete source-by-source historical replay ledger for every provider. Historical replay is claimed only where the required release, snapshot and marker-level evidence is actually populated.
Privacy

Privacy and Daniel's Law

NJOGIS states that owner names have been redacted from its hosted parcels and tax-list downloads, map services and applications in response to Daniel's Law protections. Watchdog does not try to defeat that public-data choice by rebuilding the missing owner-name field from unrelated personal-data brokers. In current provider governance, owner name is explicitly marked unavailable from the connected statewide public source.

Watchdog is organized around the property record.

Assessment, tax, block and lot, parcel geometry, sale/deed references, municipal context and mapped due-diligence layers are about the property record. Where a user voluntarily submits a document or account-specific information, that is handled under Watchdog's privacy terms and remains conceptually separate from the statewide public parcel baseline.

Limits

What Watchdog does not do

Watchdog is a research and screening tool. It does not replace the controlling government record or a professional determination where one is required.

Not a surveyStatewide parcel polygons support mapping and analysis but do not establish legal property boundaries.
Not an appraisalPublic records do not see interior condition, renovation quality, deferred maintenance or every characteristic relevant to market value.
Not live MLS statusPublic deed and assessment data can show recorded events. They do not tell Watchdog whether a property is currently listed for sale.
Not a title opinionTidelands, deed-notice and other mapped references can trigger diligence; they do not establish insurability, ownership rights or title status.
Not a flood determinationFEMA/NJDEP intersections are screening context. The official map, lender/insurer requirements and qualified professionals control actual determinations.
Not a wetlands delineationMapped wetlands are a reference layer and can differ from site-specific delineation or jurisdictional review.
Not permit clearanceDCA's raw record feed is not a municipal certificate that a permit is open, closed, compliant or free of local issues.
Not a tax appeal guaranteeChapter 123 screening organizes public evidence. County boards, Tax Court and current filing requirements govern the actual appeal.
Not a credit, lending or insurance decisionThe Watchdog Score and ROBUST dimensions are property-intelligence context and cannot substitute for regulated underwriting, eligibility or carrier/lender requirements.
Not real-time government dataEach source has its own publication lag and correction cycle. A current Watchdog page can still be displaying the latest available prior-year government field.
Missing does not mean safeUnavailable or incomplete source coverage is not interpreted as proof that a risk, permit, lien, condition or constraint does not exist.
Check a result

How to check a Watchdog result

When a Watchdog value matters to a decision, work backward from the result to the parcel, source and calculation.

  1. Identify the marker. Is it a source field, normalized field, derived marker or screening signal?
  2. Identify the parcel. Confirm municipality, block, lot, qualifier/PAMS identifier and address refer to the intended property.
  3. Read the source and vintage. Determine which agency or governed public layer supplied the input and which tax year/report period it represents.
  4. Inspect the source fields. For core property data, reconcile fields such as assessment, annual tax, sale/deed references or construction year with the official record where the decision is material.
  5. For a derived value, inspect dependencies. A result cannot be stronger than the inputs feeding it. Missing dependencies should be visible as missing/partial, not assumed away.
  6. For a Watchdog Score, verify the model and evidence. The canonical property score is watchdog.watchdog_score / ROBUST-v1; read the R/O/B/U/S/T components together with evidence coverage/confidence instead of treating the headline number as a standalone fact.
  7. For a spatial screen, open the underlying map or agency record. The Watchdog intersection tells you where to look next.
  8. For an appeal, title, environmental, lending or appraisal decision, verify with the authority or qualified professional. Watchdog shortens the research path; it does not replace the official process.
FAQ

Common questions about the data

What is the ROBUST Framework?

The Watchdog Score is powered by the ROBUST Framework: Recourse, Overassessment Position, Burden, Uniformity, Stability and Trajectory. ROBUST explains the six dimensions behind the canonical property Watchdog Score; it is not a separate “ROBUST Score.”

What happens when a ROBUST dimension is missing?

The missing dimension is omitted and the remaining available weights are renormalized. Watchdog reports evidence coverage/confidence separately. The current model does not fill missing score evidence with an invented 0, 50, 100 or other neutral value.

Why can Watchdog and a municipal record differ?

The statewide source can lag a local assessor, county, recorder or agency update. Government publishers also correct files and layers on different schedules. When a discrepancy matters, the current authoritative agency record controls and Watchdog should be treated as a research layer, not a replacement for that record.

Does “live” mean real-time?

No. “Live” is a Watchdog integration status: the source/provider is governed for current production use. The underlying government dataset may publish annually, monthly, quarterly or irregularly. Source vintage and publisher cadence remain separate.

What happens when a source is missing?

A missing field should remain missing, reduce a completeness/confidence measure, neutralize a dependent calculation or make the result partial/unavailable. It should not silently become zero or “no issue.”

How do you distinguish an official value from a Watchdog calculation?

Authoritative fields retain source keys and source-field lineage. Derived markers carry calculation keys or formula-registry dependencies and are labeled as estimates, ratios, scores, screens or completeness measures rather than as government facts.

Why publish planned and unavailable source states?

Because identifying an official webpage is not the same as having production-grade data. A source can be blocked by an unstable export, ambiguous vintage, missing crosswalk, incomplete coverage or the absence of a defensible authoritative dataset. Publishing the state makes that limitation explicit.

Can Watchdog data be used in professional work?

Yes, as research, screening and workflow evidence, with the source and limitation kept attached. Material legal, appraisal, title, environmental, insurance, lending, tax or permitting decisions should be verified against the controlling agency record and appropriate professional process.

Methodology reviewed August 23, 2026. Watchdog is an independent property-intelligence product and is not affiliated with or endorsed by the State of New Jersey, FEMA, NJDEP, NJDCA, any county or municipality. This page documents the product's current methodology and does not create tax, legal, appraisal, engineering, title, lending or insurance advice.