A notice of violation is a letter sent to a property owner and/or tenants notifying them of one or more code violations that have been assigned to a code enforcement case attached to their property. Issuance of this letter opens the compliance timeframes of each violation attached to the case.
Notices and events associated with their processing lie at the heart of many case management decisions. As such, their creation, processing, and monitoring are all directed by COGConnect through a set of user controls whose availability is adjusted dynamically based on the current status of the
NoticeOfViolation and its hosting
The typical workflow for NOVs proceeds as follows:
CodeViolations(which do not have a compliance date) to declare in the letter.
Personto which she wishes to send the NOV
When the NOV is in ship shape, CEO then locks and queues the NOV, which triggers the following system actions:
Eventdocumenting the locking and queuing of the NOV
Any user with MuniStaff+ permissions for the NOV’s muni actually prints and mails the NOV and indicates mailing complete by clicking the appropriate command button in the NOV’s listing on Cases. This triggers the following system actions:
Eventdocumenting the mailing of the notice
For NOVs which are successfully delivered to the addressee, the NOV life cycle ends here. IF a NOV is returned, any user with MuniStaff+ permission for the NOV’s muni can declare the notice as returned. This triggers the following system actions:
Eventdocumenting the returned notice
Personobject, noting an undeliverable address