How to choose Business Improvement District software.

Prepared by the Urban Spark product team. This guide reflects operational experience of place management. It is not legal, procurement or ballot advice.

Start with the work, not the feature list.

The strongest demonstration is not the longest menu. Ask each supplier to follow the same real workflow: import or update a levy record, identify the right voter contact, record a business visit, connect delivery to a benefit, log a street occurrence, assign the follow-up and show how that evidence reaches a management or board report.

This exposes whether the platform is genuinely connected or simply places separate tools behind one login.

1. Model BID data correctly.

Confirm that businesses, contacts, properties and hereditaments are separate but connected records. Ask how the system handles multiple occupiers, agents, head offices, changes of occupation, rateable values, levy years and historical data. A generic company-and-contact CRM may struggle with the rating-list structure a BID actually manages.

2. Make engagement useful.

Engagement should be more than a note. Test segmentation, groups, visit history, communications, sentiment, follow-ups and data-confidence reporting. Ask whether a new team member can understand a levy payer’s current relationship without searching several systems.

3. Connect projects to benefits.

Ask how projects move from plan to task, activity, output, outcome and value. Check whether the system can show which businesses or areas benefited and whether the evidence remains useful for levy-payer communication and renewal, not just internal task management.

4. Test the office-to-street workflow.

Give a ranger or ambassador a phone and ask them to log an occurrence and a business interaction. Then ask the manager to find, assign and report that work on desktop. Check mobile speed, photographs, location, notifications and how weak connectivity is handled. Do not accept an offline claim without seeing it tested.

5. Treat ballot readiness as a whole-term discipline.

Ballot tools should connect eligible hereditaments, rateable value, voter contacts, engagement, sentiment and returned ballots. Ask the supplier to explain the dual-majority calculation clearly. Use our free BID ballot calculator and renewal readiness check to frame the conversation.

6. Examine reporting before buying.

Bring three reports your board or local authority already requests. Ask the supplier to reproduce the logic using realistic sample data. Test filtering, exports, definitions and whether the figures can be traced to source records. A colourful dashboard is useful only when the underlying evidence is reliable.

7. Check migration, support and exit.

Document what will be imported, cleaned and reconciled; who is responsible; how long it takes; and what will not migrate. Agree training, support channels, response expectations, backups, data export and secure deletion at contract end. Ask to see the proposed implementation plan before signing.

8. Verify security claims.

Ask for evidence behind certifications, hosting, access controls, audit logs, backups and testing. Clarify controller and processor responsibilities and any sub-processors. If community-safety or offender information is involved, complete a separate, proportionate assessment with qualified advice. Review the SIVO trust centre for our current position.

A fair demonstration scorecard.

1. Data model and levy accuracy
2. Ease of everyday use
3. Connected project and benefit evidence
4. Street-team workflow
5. Ballot and renewal readiness
6. Reporting and traceability
7. Migration, training and support
8. Security, privacy and exit

Score every supplier against the same scenarios. Record both capability and usability: a feature that the team will not adopt will not improve the operation.