Notice Checklist for CA

Reviewing the Notice

Before each proceeding, it’s important to carefully review the notice to confirm key information. The notice contains all of the essential details you’ll need to open the record correctly.

Reviewing it ahead of time will help you identify who scheduled the proceeding, how it’s being recorded, and what case information should be read onto the record.

What to Look For in the Notice


1. Videotaped or Not

Check whether the notice states that the deposition or proceeding will be videotaped.


Zoom Changes

  • If videotaped, your Zoom name should read “Filevine – Videographer.”
  • If not videotaped, use “Filevine – Session Assistant.”

Read-on Changes

  • If videotaped
    • Introduce yourself as the videographer
    • Refer to the proceeding as “Videotaped [Event name]”
  • If not videotaped
    • Introduce yourself as the Session Assistant.
    • Refer to the proceeding as “[Event name]”


2. Scheduling Party

Identify which counsel scheduled the deposition and compare that to the attendee information to determine if they are the plaintiff or defendant. You will use this information to read into the record as “taken by counsel for [The Plaintiff/The Defendant].”

3. Case Name

Locate the full case name exactly as it appears in the notice. This is used in your opening statement and should be read clearly.

4. Case Venue

Confirm the full case venue—the court or jurisdiction where the matter is filed (e.g., “Superior Court of California, County of Los Angeles”). This must also be stated in your read-on.

5. Case Number

Find the case number listed in the notice. Double-check for accuracy before the session begins.


Quick Reference Checklist

Use this checklist before each session:

☐ Confirm if the proceeding is videotaped or not videotaped

☐ Identify the scheduling party and determine if they are the Plaintiff or Defendant

☐ Record the case name exactly as written

☐ Confirm the full case venue

☐ Note the case number

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.