The principal aim of NSIR is to ensure that incidents of anti-social behaviour are risk assessed at the earliest opportunity, leading to an appropriate response, as well as being recorded in a consistent and accurate manner; thus, helping social housing providers and local communities tackle such behaviour and other related issues. From the first point of contact, identification and management of prioritised risk is crucial to delivering an appropriate response. Therefore, the role of the housing officer capturing the reported ASB incident is to obtain sufficient information, through effective questioning, to determine the appropriate next steps, and crucially to assign the right categories to the resulting case, reflecting all constituent elements. Housing organisations invariably find it useful to have their own sub-categories of anti-social behaviour which can be cross-referenced back to an NSIR classification. ASB can take many forms and therefore housing organisations need to condense the different types of behaviour into logical classification pairings in order to benchmark performance and prioritise resources. Indeed, it is important that acts of anti-social behaviour are prioritised accordingly, and whilst there is a high degree of consensus between social housing providers, Civica Cx Housing provides the flexibility for individual organisations to define their own priority scale and link these through to each category. Such categories can be linked to more than one priority - critical, high, medium, low, etc. - ensuring that the correct priority weighting is set depending on the incident to which it relates. Inherent tasks then reflect these priorities, depending on the overarching category. By way of example, a task definition of 'Interview Perpetrator' might be linked to any number of separate ASB categories from, say, begging to hate incidents. Interviewing the perpetrator in a hate crime would be considered a higher priority than in the reported incident of begging, and therefore the task priority weighting would be ascribed based on the overarching category. It is therefore important that in setting up categories, the correct range of potential priorities are reflected.
The allocation of ASB tasks to a category defines how the resulting case will be progressed. Any number of discrete tasks can be linked to an ASB category, with a specific attribute governing whether each can appear more than once within the same execution plan. In structuring all the activities that are relevant to an ASB case, tasks can be added manually at the point of need, or they can be linked automatically by virtue of their existence within an associated workflow path. Dictated by the nature of the assigned tasks, dependencies can be configured between them to restrict the point at which related tasks are commenced.
Separate help articles have been created for each key aspect of ASB category maintenance, including: