Speakers Bureau/Technology Team/Entity Relationship Model

Here's a first stab at drafting an "entity relationship diagram" for the system.

Description

Some notes:

of course, this is draft so I didn't go crazy filling in every last field name (ie, "n other stuff" captures all the other fields we'd need)
guessing there's probably the need for some extra tables to better manage the searching/matching aspect, but haven't given that much thought
the infinity symbol means "many". As in: ONE speaker can participate in MANY opportunities, or ONE opportunity can trigger MANY requests, etc...
bolded fields are the "primary" key(s) of the given table
made the Review a three way relationship between a speaker, a user and a given opportunity. This makes sense if we are reviewing the user and speaker for a specific engagement. And, comes in handy if the same speaker does multiple ops for the same user.
the Request table is where we do all the status tracking/etc of when to trigger email prompts, to track when a speaker has logged in/reviewed an Op, if they declined, etc. And, assumption is that a given Op could trigger multiple speaker requests...