Portfolio monitoring
Watch planning activity around property portfolios.
Create repeatable area or asset monitoring for property, lending, insurance and investment teams, with source evidence retained for every reviewed event.
Product and property teams use PlanWire when they need source-linked planning data without maintaining council-source integrations, with UPRN where available for property-dataset joins. Source-linked application records, freshness metadata and webhook workflows. Check current council-level coverage and history for your integration.
Example portfolio-area search
Use your own asset-to-location mapping and treat unavailable coordinates as a visible coverage gap.
GET /v1/applications/nearby?lat=53.7974&lng=-1.5438&radius_km=2&limit=50 X-API-Key: YOUR_API_KEY
Separate monitoring from interpretation.
PlanWire can surface captured planning activity; your organisation decides materiality and any action for a particular asset.
Map the watchlist
Represent portfolio exposure using supported council, postcode or radius queries and stable internal asset IDs.
Set review rules
Use proposal terms, status and dates to prioritise events without claiming automated materiality.
Recover after downtime
Use durable webhook receipt and cursor recovery, or reconcile with bounded scheduled searches.
Keep an audit trail
Store the application reference, match rule, captured time and public source link beside the asset review.
Operational model
| Detection | PlanWire captures matching planning records and available changes. |
|---|---|
| Triage | Your rules identify which events require an analyst or asset-manager review. |
| Decision | Your qualified professional determines materiality, risk and next action. |
Questions buyers ask
Does PlanWire decide whether an event is material?
No. It supplies captured planning data and evidence for your own review process.
Can we use webhooks for every asset?
Webhook scope and allowance depend on the plan and documented filters; broader workflows may need Production.
Can we join records to property IDs?
UPRN and coordinates are available where captured, but field availability varies and joins must tolerate missing values.
Related acquisition pages