Historical pilot / Toronto

Built through community use.
Improved through experience.

The West Queen West BIA pilot provided a practical setting to explore incident reporting, member participation and local information gathering.

159Unique accounts reported
30Qualified incident reports

Source: We-Watch’s pilot summary dated 18 March 2024, which records the client partnership beginning 23 May 2023. Figures are company reported.

These are historical participation figures. They do not establish crime reduction, cost savings, police adoption or case-resolution outcomes.
Historical We-Watch mobile app screenshot from the existing company website
Historical product interface; not a representation of current deployment availability.

The problem the pilot addressed

Move beyond scattered emails
and group-chat updates.

The pilot summary describes business concerns reaching the BIA through separate messages and conversations. The programme set out to create a common reporting channel, make contributing easier and gather incident details and media in a more structured form.

Recruitment included storefront visits, BIA email and social outreach, printed information, follow-up visits and individual support. The pilot tested participation as well as the software.

Source: company-reported West Queen West BIA pilot summary, 18 March 2024, pages 1–4.

HISTORICAL PARTNER PERSPECTIVE

A clearer community record.

“The solution offered through We-Watch enables our BIA to track incidents and build intelligence about our community.”

Pilot-partner letter concerning West Queen West BIA, 19 November 2023.

The letter also describes the challenge of changing reporting habits and the importance of member outreach. This is a historical partner opinion, not a measured safety outcome or a statement of current service availability.

What the pilot made clear

Participation is part of the product.

01

Onboarding needs attention.

The programme used storefront outreach, member communications and follow-up. A community network needs active recruitment and a clear reason to return.

02

Reliability affects engagement.

The summary records usability and notification issues that influenced participation. Restoration and acceptance testing are essential to a credible new deployment.

03

Local context changes the design.

The BIA approach moved toward saved home and business locations. Matching should suit the community, participant expectations and the incident types involved.

The next stage

A stronger pilot asks sharper questions.

How many requests produce useful information? How quickly does it arrive? How much staff time does it take to review? Do participating organizations want to continue?

Those questions guide our discussions with deployment and commercialization partners. Supporting historical materials can be discussed as part of a qualified enquiry.

The screenshot above is historical. Current functionality and deployment scope require confirmation.

Put the next deployment on a measurable footing.

Start with a specific community, a clear information need and an agreed definition of success.