Controlled beta

Known Limitations of the Beta

This beta is designed for demonstration and stakeholder feedback. We publish a transparent list of what the platform can and cannot do today so that procurement, information governance and information security teams can make a properly informed assessment.

Current limitations

  • Synthetic data only — households, providers, properties, audit records and dashboards are fabricated for demonstration.
  • No live resident records or case-management integration.
  • No production authentication — the beta login is a demo gate.
  • No Microsoft 365 / Azure AD SSO yet.
  • No live council system integration (homelessness case management, allocations CBL, finance systems).
  • No real document storage — the mock upload records metadata only.
  • No real geocoding — map coordinates are derived from borough centroids with deterministic jitter.
  • Deterministic AI-style explanations only — there are no real LLM calls in the current beta.
  • No real SMS or push notifications, and no allocation-related emails. The only real-email channel is the beta-feedback submission notification (from noreply@jigsawconferences.co.uk, behind a feature flag), which never includes resident, household, allocation or suitability data.
  • Reports and procurement dashboards are computed from synthetic demo data only.
  • Suitability Form A / Form B / manager review workflows support assessment but do not make statutory decisions.
  • CSV and PDF exports are demo-only and watermarked as synthetic.

Future production requirements

  • Data Protection Impact Assessment (DPIA)
  • Independent security review and penetration testing
  • Information governance review by the Controller
  • Data retention and deletion policy aligned with the Controller’s schedule
  • Data Processing Agreement (DPA) and sub-processor review
  • Secure document storage (encryption at rest, malware scanning, access logging)
  • Role-based access controls (RBAC) and least-privilege defaults
  • Append-only audit policy with HMAC integrity and tamper-evident storage
  • Accessibility audit (WCAG 2.2 AA)
  • Client-specific workflow configuration (suitability rules, anchors, escalation matrix)

Why publish this? Procurement teams in local authorities and housing associations need to know what a beta does and does not cover. Publishing limitations openly is part of the procurement-safe posture of Jigsaw HousingMatch AI.

Want to see the working demo?

All workflows run against synthetic data. No real personal data is present.