BCRP software requirements checklist.

Prepared by the Urban Spark product team. This is a procurement prompt, not legal or data-protection advice. BCRPs should obtain qualified advice for their specific lawful basis, governance and information-sharing arrangements.

Governance before technology.

A secure platform cannot replace a properly governed partnership. Before comparing screens, document the scheme purpose, membership, controller and processor roles, lawful basis, acceptable use, information-sharing arrangements, retention policy, complaints route and who can make publishing or exclusion decisions.

Core partnership requirements.

• Separate schemes and appropriate visibility for Pubwatch, Shopwatch or different geographical areas.
• Business and member records, invitations, terms acceptance, suspension and removal.
• Role-based permissions for managers, operational users and member businesses.
• Scheme meetings, attendance, decisions, referrals, governance documents and accreditation evidence.
• Clear audit history for access, changes, publishing and administrative actions.

Incident and offender workflows.

• Structured incident reporting with businesses, people, vehicles, goods value and police references where appropriate.
• Controlled offender or subject records, images, aliases, linked incidents and outcomes.
• Approval states and manager-only information so unreviewed material is not automatically shared.
• Exclusion or ban decisions, start and expiry dates, scheme context and decision history.
• Alerts, bulletins and member communications with defined audiences.
• Exports or evidence packs that preserve provenance and access controls.

Privacy, retention and safeguarding.

Ask each supplier to demonstrate how access is granted, reviewed and removed; how sensitive images and documents are protected; how retention dates are calculated; what happens at expiry; how audit records are preserved; and how subject-access, correction, objection and deletion processes are supported. Check how the design treats children and vulnerable people. Do not assume a supplier’s general GDPR statement answers the partnership’s specific obligations.

Member experience and adoption.

• Can a busy member report an incident quickly without losing essential detail?
• Is information relevant to that member, scheme and location?
• Can members see current alerts and permitted offender information without navigating the management system?
• Are digest communications useful and controllable?
• Can administrators identify inactive users and keep access current?

The wider place test.

If the BCRP sits within a BID or place partnership, test what happens outside the crime system. Can the same business record support engagement, Street Ops, public-realm occurrences, projects, benefits, communications and governance without duplicating the organisation in another database? This is where Business Improvement District management software and BCRP management can either connect or become separate silos.

Supplier evidence to request.

1. A current feature and limitations statement.
2. Architecture, hosting and sub-processor summary.
3. Access-control and audit demonstration.
4. Backup, restoration, incident and exit processes.
5. Certification evidence for every badge or assurance claim.
6. Implementation, migration and training plan.
7. Named customer references for comparable partnerships.
8. A contract schedule covering roles, retention and secure deletion.

SIVO Crime Intelligence is available as a licensed module. Ask us to demonstrate case management, exclusion governance, evidence packs, the member portal, retention controls and the wider connection to BID and place operations. Our trust centre states the current assurance position and product boundaries.