Events are occurrences or incidents that occur in a specific case or for a specific person. Examples of events are court appearances, client meetings, and arraignments. Events can be created and viewed for any name or case session. The related Event Involved People snap-in in any session can be used to record the persons involved in an event.
Events can be linked to each other as well as to other tasks, correspondences, or documents to easily keep track of all events on a case and show a hierarchal relationship between them.
Events should only be created in a name session when they are not case specific. If the event is related to a case, create it in the appropriate case session.
An event created in a case session appears in the Calendar snap-in of the name session of each person involved in the event. Each case-related event in a name session includes a hyperlink to the applicable case. The Events snap-in can track multiple events, past and future, providing a history and schedule of events associated with the case.
|
Events can either be singular, unattached instances, or they can be related to another event. For example, if a meeting with the Judge was the direct result of a hearing, then the hearing would be the parent event for the meeting with the Judge. This allows you to link events to each other so you can easily see the progression of your case.
To relate one event to another, you must fill out the Parent Event field in the Events snap-in. This creates the link between the two events. You can have multiple events linked to the same parent event.
This relationship is maintained when events are inserted into Calendar Dockets, and it can be used if one Docket Event spawns another. For example, if someone shows up to dispute a traffic ticket (Event #1) and pleads not guilty, then another Docket Event would need to be created for the traffic hearing (Event #2). To maintain the progression of this case, Event #2 would be linked to Event #1, even if both events appeared in different Calendar Dockets.