01
Observations, not people.
For SEEN HERE, the intended focus is appropriate observations about a place. Examples should describe a concern or behaviour, rather than treat someone’s presence or identity as suspicious.
Our approach
Useful software.
Clear boundaries.
Obsdale Systems is an independent company developing software for community insight and independent scrutiny. Our starting point is the work people need to do—and the judgement that should stay with them.
In development · Open to discovery conversations
Two distinct purposes
A clearer view.
A more considered review.
SEEN HERE is the community-insight product family. Its intended purpose is to bring appropriate local observations into place and time context for authorised human review.
PRISM concerns independent scrutiny, with initial work focused on stop-search review. Its intended workflow helps organisers prepare reviews, record panel findings and keep the organisation’s response distinct from those findings.
These are separate product lines. Their presentation together here does not imply a shared operational system or data exchange.
Design principles
Keep the purpose in view.
02
Patterns, not verdicts.
Bringing information together should help people ask better questions. A pattern needs interpretation, and a review needs room for context, challenge and disagreement.
03
People keep judgement.
Software should organise information and the review process. Authorised reviewers consider what it means; scrutiny panels reach their own findings and organisations decide how to respond.
Development, with care
Start with the work.
Test the assumptions.
Both product lines are in development. Discovery conversations help us understand existing processes, where information gets lost and which requirements deserve attention.
Privacy, access and accountability are requirements to examine in each product’s context. A design principle or conceptual illustration is not evidence that a particular control has been implemented or tested.
The illustrations on this website explain intended workflows using synthetic examples. They are labelled as concepts rather than application screenshots. The site does not offer product access or an operational reporting route.
Public research can inform the questions we ask. Establishing whether a product is useful requires its own evaluation against the task and the people using it. Read about evidence and context.
Let’s talk
Show us where the current process gets difficult.
Tell us which product interests you, how you work today and what you would like to improve.
Please do not send personal case information or operational records through this enquiry route.