Last update: 10/2/2026
MEETING – NEW
| Note Type | Meeting – New (for Appointments Without Task, Appointments With Tasks) |
| Relationship Manager Preferences | Always go through this for any special RM preferences such as default themes/products, expense defaults, follow-up date instructions, et cetera.
Best practice: Go through this before transcribing any RM recording to refresh your memory of the RM’s preferences. |
| App Comment/Task Description | Only fill this out if file is received via the Hey DAN app. Put the activity type/sub-type of the note generated from the file here. If file will generate more than one type of note, list them accordingly.
Examples: Note that the information you last inputted is the one that will stick on the field so make sure that the last touch is the final details you would want to keep for this field. |
| Internal Comments | Put here additional information that will help in CRM Entry (i.e. team names, websites, entity IDs or other reminders)
You can also take note here whether the note is for clarification and what the clarification is. Format: ***CLARIFY [which field] [what reason]*** IMPORTANT: For those with MSD access, if the note is for 2 or more FA attendees, please capture the EIDs of all the attendees on this field. Common Markers That We Use for This Field: |
| Special Instructions | Put here any special instruction dictated by RM.
For PTS RMs (Product/s Specified users), it helps to put the products dictated here for reference. |
| Date | As specified. If No Date was specified, use Recording Date for audio files or use the date when the email was sent via remote outlook.
For recordings/emailed notes that will yield multiple activities, date is usually specified, but if not, succeeding notes will always follow the date of the note before it. |
| Time | As specified. If not specified, skip.
IMPORTANT NOTE: If the RM specifies a time for their notes, please identify if the time zone of the RM is Eastern Standard Time (based on the states they cover or location of the FA – check the RM preferences section for guidance). Special Situations: #2: If the activity has an associated Entertainment – Non Employee expense note, mirror the time on the receipt as the time for the activity (with consideration of the time zone that the RM covers – see rules above). |
| GROUP | Tick if there is more than 1 attendee to add for the note. |
| SAME FOLLOW-UP | Not applicable. Just skip. |
| SAME ORGANIZATION AND LOCATION | Automatically should be checked if all attendees added for the note are from the same firm and location. If not under the same firm, untick and add the correct information of the attendees. |
| Attendees: | |
| First Name & Last Name | As specified and verified.
Should include the Advisors as well as the other BLK employees that are present during the activity. Firm of other BLK employees should always be BlackRock. Special Situation #1: If the activity is for an “internal prep call/meeting”, see Related field remarks below. Special Situation #2: If the RM mentions the nickname of the advisor versus the official first name (example: Jack vs John), we should write the nickname inside quotation marks on the first name field but still adding the official first name as verified. Example: John “Jack” Doe. Note: If the nickname mentioned is the common nickname (example: Tim for Timothy or Mike for Michael Special Situation #3: If the RM mentions an incorrect first name or last name than what you were able to see and verify in FINRA and/or CRM system, you can correct and mirror what you see in the CRM system if it’s just a spelling error. But if it’s a totally different first name and/or last name, then put the name the RM specified on the Attendees field in brackets and submit the note for clarification. For group notes, maximum number of attendees we can put per DANA page is 25. If it exceeds that, we should plot in parts. So if the attendees are 50 names, it will yield 2 DANA notes. (Note: Indicate in the Quick Comments field if the note is 1/2 or 2/2 so the enterer will know that the notes are plotted in parts). IMPORTANT: If an RM requests logging a meeting that only specifies the Buying Unit (team/firm/organization) – let them know an individual client attendee is needed and must be added to the meeting record. A meeting should not only have a team as attendee, advisor/advisors are needed. |
| CRD# | CRD is not required but highly encouraged to be utilized for reference during CRM entry. |
| 1-on-1 | DO NOT USE moving forward for activities. We should always plot the note for each FA separately because of the subject field format. Exception: If subject field is specified and the 1on1 notes would have the same subject, then you can use this. |
| Pop-up Follow-up: | Use this field if the FF is for a standalone FA attendee or if the FF is for a particular FA attendee from a group note. |
| Organization | Always put the firm (even if not specified by the RM for audio recordings as long as you were able to verify in FINRA or the firm website).
Special Situation: If the RM mentioned which team the FA attendee/s belong to, let’s capture that info on the firm field. |
| Location | If specified, please include. If not specified, it is not required but highly encouraged to include for research purposes. |
| Subject | Required and as specified. If not specified, follow the default format below:
If with 1 FA: [Appointment Sub-type] – [Client Name] | Ex. Virtual Meeting – John Doe Note: Team is also known as the Buying Unit in MS Dynamics. Reminders: We don’t include the BLK attendees on the count. IMPORTANT: If an RM requests logging a meeting that only specifies the Buying Unit (team/firm/organization) – let them know an individual client attendee is needed and must be added to the meeting record. A meeting should not only have a team as attendee, advisor/advisors are needed. Special Situation: If the activity is specified as an “internal prep call” or “internal prep meeting”, follow the format below: |
| Internal Notes (formerly called Note Text) | Follow general writing guidelines. Clean verbatim.
a) If the note is PTS and there’s one theme/product specified by the RM that you were not able to tag as theme/product (either it’s not available at all or written very differently), you must capture all the themes/products that the RM specified at the top of the note text field and then tag whichever topics are available on the themes/product fields. b) If the note is PTS and you weren’t able to tag any themes/products from the PTS mentioned, check the RM Preferences field first if there’s a default themes/product to tag. If there is, tag it. If there is no default theme/product on the RM pref, tag Territory Management as theme, and then capture all the PTS on top of the note text field. No need to scan through the note text for any product/themes mentioned. c) If no note text was provided by the RM, please CLARIFY. |
| Group Follow-Up | Use this field if the FF is for all the FA attendees of a group note. |
| FF Type | Not applicable. Just skip. |
| Due Date | As specified. If not specified, default to +2 business days from processing date (check RM preferences as well for specific defaults per RM). Don’t forget to exclude the weekends and/or the official US holidays from the count. |
| Due Time | As specified. If not specified, skip. |
| FF Subject | Required and as specified. If not specified, follow the default format below:
If with 1 FA: Follow-up for [BLK Person] – [Client Name] |
| Description | Capture here the direct FF instructions from the RM to the internal or to whom the FF is directed to (which can be the RM him/herself). |
| Owner | Select appropriate name (if existing on the field list). If field is blank, use the Owner (Other) field to capture the name of who the FF is for. |
| Owner (Other) | Capture here the name of the BLK Person the FF is directed to (that is now on the FF Owner field list). |
| FF Regarding | As specified. If not specified, skip. |
| Duration | As specified. If not specified, skip. |
| Priority | As specified. If not specified, skip. |
| FF Themes | We generally only should select product/themes mentioned from the main note part, NOT anymore the FF instructions we’re plotting via the FF note unless the RM has a preference to select the products/themes from the follow-up like for Ricky Ruiz. |
| FF Products | |
| FF Title of Internal Notes | As specified. If not specified, skip. |
| FF Task Internal Notes | As specified. If not specified, skip. |
| FF Mark Complete | Should be used only for standalone follow-up notes. If with main note, skip this. |
| Activity Type | Select Appointment. |
| Sub-type | Select one of the options below: – In-Person Meeting – Virtual Meeting Note: If the activity is specified as an “internal prep call” or “internal prep meeting”, default is Virtual Meeting unless specified otherwise as In-Person or Phone Call. |
| Additional BLK Users (Support) | As specified. If not specified, skip. |
| All Day Event | As specified. If not specified, skip. |
| Title of Internal Notes | As specified. If not specified, skip. |
| Location (under Custom Field) | As specified. If not specified, skip. If the activity has an associated Entertainment – Non Employee expense note, mirror here the Vendor and Location on the receipt. |
| Duration | As specified. If not specified, skip. |
| Priority | As specified. If not specified, skip. |
| Related | As specified. If not specified, skip in Dana. (MSD will populate this automatically, we may leave as is during entry)
Note: This field can now accommodate multiple profiles, BUs, pipeline, campaigns. Special Situation: If the activity is for an “internal prep call/meeting”, capture the BLK attendees on the Attendee field and capture the FA name/s and/or BU/s (only if specified by the RM) on the Related field. |
| Mark Complete? | Tick Yes if specified or stated on the RM Preferences. If not, just leave it blank. |
| Themes | IMPORTANT: If RM Preferences DOESN’T say the RM is a ***DC USER*** or an ***RI USER***, use this as the Themes field for the note.
IMPORTANT: The Themes field is a selection field so choose accordingly the applicable themes. However, the Product field is a text field so we need to write the applicable product/s row by row or line by line. GENERAL RULES: STEP 1: Identify if the note is PTS or not. PTS means that the RM is telling us what to tag as themes/products for the note usually in the beginning of the dictation but they can also specify what products/themes to tag at the end of the recording or in the middle of the dictation. STEP 2: If it is not PTS, we just simply need to scan through the note text dictated/provided and select all the themes/products mentioned from there. Best practice is to use our “Common Products & Themes” sheet as guide on what to select. a) If you weren’t able to tag any themes/products from the note text, check the RM Preferences field first if there’s a default themes/product to tag. If there is, tag it. If there is no default theme/product on the RM pref, tag Territory Management as theme. STEP 3: If it is PTS, we generally need to select only the themes/products specified by the RM. However, there are lots of scenarios wherein the themes/products specified by the RMs are not available on the field and/or written differently or are categorized under a general topic, so please be guided as follows: a) If there’s one theme/product specified by the RM that you were not able to tag as theme/product (either it’s not available at all or written very differently), you must capture all the themes/products that the RM specified at the top of the note text field and then tag whichever topics are available on the fields. b) If you weren’t able to tag any themes/products from the PTS mentioned, check the RM Preferences field first if there’s a default themes/product to tag. If there is, tag it. If there is no default theme/product on the RM pref, tag Territory Management as theme, and then capture all the PTS on top of the note text field. No need to scan through the note text for any product/themes mentioned. c) Same thing applies if the RM said “no product type to tag” or “no product”, no need to scan through the note text for any topics mentioned, just choose Territory Management as theme. |
| Products | |
| DC Themes | IMPORTANT: If RM Preferences say the RM is a ***DC USER***, use this as the Themes field for the note.
See GENERAL RULES to follow above. |
| RI Themes | IMPORTANT: If RM Preferences say the RM is an ***RI USER***, use this as the Themes field for the note.
See GENERAL RULES to follow above. |
==============================================
STICKY NOTES
| Note Type | Sticky Notes (for Sticky Notes aka Post It Notes) |
| Relationship Manager Preferences | Always go through this for any special RM preferences such as default themes/products, expense defaults, follow-up date instructions, et cetera.
Best practice: Go through this before transcribing any RM recording to refresh your memory of the RM’s preferences. |
| App Comment/Task Description | Only fill this out if file is received via the Hey DAN app. Put the activity type/sub-type of the note generated from the file here. If file will generate more than one type of note, list them accordingly.
Examples: Note that the information you last inputted is the one that will stick on the field so make sure that the last touch is the final details you would want to keep for this field. |
| Internal Comments | Put here additional information that will help in CRM Entry (i.e. team names, websites, entity IDs or other reminders)
You can also take note here whether the note is for clarification and what the clarification is. Format: ***CLARIFY [which field] [what reason]*** |
| Special Instructions | Put here the Sticky Notes instructions dictated by RM if the request is to input/add new details to the Sticky Notes section.
If request is to modify or delete any existing Sticky Notes area/part, best to capture the complete instructions on the Internal Notes field. |
| Date | Not relevant. Just use either the Processing Date or the Recording Date. |
| Time | Not applicable. Just skip. |
| GROUP | Not applicable. Just skip as Sticky Notes can never be grouped. |
| SAME FOLLOW-UP | Not applicable. Just skip. |
| SAME ORGANIZATION AND LOCATION | Not applicable. Just skip as Sticky Notes can never be grouped. |
| Attendees: | |
| First Name & Last Name | As specified and verified.
Note: We can add sticky notes for any FA profiles or BU profiles. For 1on1s, the maximum number of names we can put per DANA page is 10. If it exceeds that, we should plot in parts as well. Special Situation #1: If the RM mentions the nickname of the advisor versus the official first name (example: Jack vs John), we should write the nickname inside quotation marks on the first name field but still adding the official first name as verified. Example: John “Jack” Doe. Note: If the nickname mentioned is the common nickname (example: Tim for Timothy or Mike for Michael Special Situation #2: If the RM mentions an incorrect first name or last name than what you were able to see and verify in FINRA and/or CRM system, you can correct and mirror what you see in the CRM system if it’s just a spelling error. But if it’s a totally different first name and/or last name, then put the name the RM specified on the Attendees field in brackets and submit the note for clarification. |
| CRD# | CRD is not required but highly encouraged to be utilized for reference during CRM entry. |
| 1-on-1 | Tick as necessary. |
| Pop-up Follow-up: | Not applicable. Just skip. |
| Organization | Always put the firm (even if not specified by the RM for audio recordings as long as you were able to verify in FINRA or the firm website).
Special Situation: If the RM mentioned which team the FA attendee/s belong to, let’s capture that info on the firm field. |
| Location | If specified, please include. If not specified, it is not required but highly encouraged to include for research purposes. |
| Subject | Not applicable. Just skip. |
| Internal Notes (formerly called Note Text) | Capture here the exact Sticky Notes details including bullets or numbering or the entire Sticky Notes instructions if needed. |
| Group Follow-Up | Not applicable. Just skip. |
| FF Type | Not applicable. Just skip. |
| Due Date | Not applicable. Just skip. |
| Due Time | Not applicable. Just skip. |
| FF Subject | Not applicable. Just skip. |
| Description | Not applicable. Just skip. |
| Owner | Not applicable. Just skip. |
| Owner (Other) | Not applicable. Just skip. |
| Priority | Not applicable. Just skip. |
| Activity Type | Select Sticky Notes. |
| Sub-type | Not applicable. Just skip. |
==============================================
NORMAL – EXISTING
| Note Type | Normal – Existing (for All Requests Involving Existing/Entered Notes) |
| Relationship Manager Preferences | Always go through this for any special RM preferences such as default themes/products, expense defaults, follow-up date instructions, et cetera.
Best practice: Go through this before transcribing any RM recording to refresh your memory of the RM’s preferences. |
| App Comment/Task Description | Only fill this out if file is received via the Hey DAN app. Put the activity type/sub-type of the note generated from the file here. If file will generate more than one type of note, list them accordingly.
Examples: Note that the information you last inputted is the one that will stick on the field so make sure that the last touch is the final details you would want to keep for this field. |
| Internal Comments | For those with MSD access, capture here the MSD link of the existing appointment.
Put here additional information that will help in CRM Entry (i.e., team names, websites, entity IDs or other reminders) You can also take note here whether the note is for clarification and what the clarification is. Format: ***CLARIFY [which field] [what reason]*** |
| Special Instructions | Put the instructions part of RM’s dictation here if the request is to edit the Internal Notes only. Otherwise, skip and utilize the Internal Notes field. |
| Date | As specified or mirror the date of the existing/entered note. |
| Time | As specified. If not specified, skip.
IMPORTANT NOTE: If the RM specifies a time for their notes, please identify if the time zone of the RM is Eastern Standard Time (based on the states they cover or location of the FA – check the RM preferences section for guidance). Special Situations: #2: If the activity has an associated Entertainment – Non Employee expense note, mirror the time on the receipt as the time for the activity (with consideration of the time zone that the RM covers – see rules above). |
| Attendees: | |
| First Name & Last Name | As specified and verified.
Should include the Advisors as well as the other BLK employees that are present during the activity. Firm of other BLK employees should always be BlackRock. Special Situation #1: If the activity is for an “internal prep call/meeting”, see Related field remarks below. Special Situation #2: If the RM mentions the nickname of the advisor versus the official first name (example: Jack vs John), we should write the nickname inside quotation marks on the first name field but still adding the official first name as verified. Example: John “Jack” Doe. Note: If the nickname mentioned is the common nickname (example: Tim for Timothy or Mike for Michael Special Situation #3: If the RM mentions an incorrect first name or last name than what you were able to see and verify in FINRA and/or CRM system, you can correct and mirror what you see in the CRM system if it’s just a spelling error. But if it’s a totally different first name and/or last name, then put the name the RM specified on the Attendees field in brackets and submit the note for clarification. For group notes, maximum number of attendees we can put per DANA page is 25. If it exceeds that, we should plot in parts. So if the attendees are 50 names, it will yield 2 DANA notes. (Note: Indicate in the Quick Comments field if the note is 1/2 or 2/2 so the enterer will know that the notes are plotted in parts). IMPORTANT: If an RM requests logging a meeting that only specifies the Buying Unit (team/firm/organization) – let them know an individual client attendee is needed and must be added to the meeting record. A meeting should not only have a team as attendee, advisor/advisors are needed. |
| CRD# | CRD is not required but highly encouraged to be utilized for reference during CRM entry. |
| 1-on-1 | Not applicable. Just skip. |
| Pop-up Follow-up: | Use this field if the FF is for a standalone FA attendee or if the FF is for a particular FA attendee from a group note. |
| Subject | Capture the Subject of the existing/entered note.
If request is to edit the Subject field itself, put the new Subject here and capture all instructions on the Internal Notes field. |
| Organization | Always put the firm (even if not specified by the RM for audio recordings as long as you were able to verify in FINRA or the firm website).
Special Situation: If the RM mentioned which team the FA attendee/s belong to, let’s capture that info on the firm field. |
| Location | If specified, please include. If not specified, it is not required but highly encouraged to include for research purposes. |
| Group | Tick if there is more than 1 attendee to add for the note. Maximum number of attendees we can put per DANA page is 25. If it exceeds that, we should plot in parts. So if the attendees are 50 names, it will yield 2 DANA notes (Note: Indicate in the Quick Comments field if the note is 1/2 or 2/2 so the enterer will know that the notes are plotted in parts). |
| Same Organization and Location | Automatically should be checked if all attendees added for the note are from the same firm and location. If not under the same firm, untick and add the correct information of the attendees. |
| Same Follow-up | Not applicable. Just skip. |
| Internal Notes (formerly called Note Text) | If request is to edit the Internal Notes, capture here the exact additional Internal Notes details to put.
If the request is to edit any other field, put the full instructions here. |
| Group Follow-Up | Use this field if the FF is for all the FA attendees of a group note. |
| FF Type | Not applicable. Just skip. |
| Due Date | As specified. If not specified, default to +2 business days from processing date (check RM preferences as well for specific defaults per RM). Don’t forget to exclude the weekends and/or the official US holidays from the count. |
| Due Time | As specified. If not specified, skip. |
| FF Subject | Required and as specified. If not specified, follow the default format below:
If with 1 FA: Follow-up for [BLK Person] – [Client Name] |
| Description | Capture here the direct FF instructions from the RM to the internal or to whom the FF is directed to (which can be the RM him/herself). |
| Owner | Select appropriate name (if existing on the field list). If field is blank, use the Owner (Other) field to capture the name of who the FF is for. |
| Owner (Other) | Capture here the name of the BLK Person the FF is directed to (that is now on the FF Owner field list). |
| FF Regarding | As specified. If not specified, skip. |
| Duration | As specified. If not specified, skip. |
| Priority | As specified. If not specified, skip. Check RM Preferences though since we have users who have rules pertaining to this field. |
| FF Themes | We generally only should select product/themes mentioned from the main note part, NOT anymore the FF instructions we’re plotting via the FF note unless the RM has a preference to select the products/themes from the follow-up like for Ricky Ruiz. |
| FF Products | |
| FF Title of Internal Notes | As specified. If not specified, skip. |
| FF Task Internal Notes | As specified. If not specified, skip. |
| FF Mark Complete | Should be used only for standalone follow-up notes. If with main note, skip this. |
| Activity Type | As dictated or mirror Activity Type selected in MSD. |
| Sub-type | As dictated or mirror Sub-type selected in MSD. |
| Additional BLK Users (Support) | As specified. If not specified, skip. For existing records that are not scheduled by the RMs themselves but one of their team member, capture the name of the team member here if they are not exactly in the activity. If they are present in the activity, capture them as a required attendee in Dana. (FYI: You need MSD access to check and apply this) |
| Related | As specified. If not specified, skip in Dana. (MSD will populate this automatically, we may leave as is during entry)
Note: This field can now accommodate multiple profiles, BUs, pipeline, campaigns. Special Situation: If the activity is for an “internal prep call/meeting”, capture the BLK attendees on the Attendee field and capture the FA name/s and/or BU/s (only if specified by the RM) on the Related field. |
| Mark Complete? | Tick Yes if specified or stated on the RM Preferences. If not, just leave it blank. |
| Themes | IMPORTANT: If RM Preferences DOESN’T say the RM is a ***DC USER*** or an ***RI USER***, use this as the Themes field for the note.
IMPORTANT: The Themes field is a selection field so choose accordingly the applicable themes. However, the Product field is a text field so we need to write the applicable product/s row by row or line by line. GENERAL RULES: STEP 1: Identify if the note is PTS or not. PTS means that the RM is telling us what to tag as themes/products for the note usually in the beginning of the dictation but they can also specify what products/themes to tag at the end of the recording or in the middle of the dictation. STEP 2: If it is not PTS, we just simply need to scan through the note text dictated/provided and select all the themes/products mentioned from there. Best practice is to use our “Common Products & Themes” sheet as guide on what to select. a) If you weren’t able to tag any themes/products from the note text, check the RM Preferences field first if there’s a default themes/product to tag. If there is, tag it. If there is no default theme/product on the RM pref, tag Territory Management as theme. STEP 3: If it is PTS, we generally need to select only the themes/products specified by the RM. However, there are lots of scenarios wherein the themes/products specified by the RMs are not available on the field and/or written differently or are categorized under a general topic, so please be guided as follows: a) If there’s one theme/product specified by the RM that you were not able to tag as theme/product (either it’s not available at all or written very differently), you must capture all the themes/products that the RM specified at the top of the note text field and then tag whichever topics are available on the fields. b) If you weren’t able to tag any themes/products from the PTS mentioned, check the RM Preferences field first if there’s a default themes/product to tag. If there is, tag it. If there is no default theme/product on the RM pref, tag Territory Management as theme, and then capture all the PTS on top of the note text field. No need to scan through the note text for any product/themes mentioned. c) Same thing applies if the RM said “no product type to tag” or “no product”, no need to scan through the note text for any topics mentioned, just choose Territory Management as theme. |
| Products | |
| DC Themes | IMPORTANT: If RM Preferences say the RM is a ***DC USER***, use this as the Themes field for the note.
See GENERAL RULES to follow above. |
| RI Themes | IMPORTANT: If RM Preferences say the RM is an ***RI USER***, use this as the Themes field for the note.
See GENERAL RULES to follow above. |
| Guidance Going Forward for HeyDAN | Logging Meetings/Calls: HeyDAN should review existing activity to their best ability possible, especially if there are multiple BLK attendees in the meeting where there is higher possibility of duplicates. The goal is to prevent duplicate meeting records. If you need to clarify with the RM, please do and let them know a similar meeting already exists in MSD. This should be done regardless of RMs selecting the option to check for existing appointments. |
| IMPORTANT REMINDERS | 1) It is now a MUST that we check for any existing/tracked activity in MSD for all the notes that we will process on our end moving forward. (6/11/26)
2) Some existing activities are not scheduled by the Market Leaders and could be tracked by one of their team members, what we do for this is we change the initial owner of the note to the name of the RM. 3) There are cases wherein the existing activity was a joint meeting with 2 Market Leaders present. This should not be duplicated, if 2 Market Leaders call in the same meeting. It should be merged as 1 activity. The “owner” of the record doesn’t matter for reporting. Market Leader 2 as an attendee is enough for HQA credit. 4) Sometimes the existing notes will already have some internal note details on it, so what we do is we just supply the notes dictated by the RM and add it below the existing notes. 5) Same goes with the themes/products, we do not remove the themes/products that are already tagged in there, we only add those that are not. 6) Generally, we do not overwrite anything from the existing note but we only add those details that the RM would mention from the request he submitted to Hey DAN. This also applies to the attendees. There are times when the attendees tagged on the existing note are not exactly the same attendees that the RM would list down. What we do for this situation is we only add those attendees mentioned by the RM that are not yet added as attendees in the existing and we don’t remove those that are tagged but are not mentioned by the RM. |
==============================================
FOLLOW-UP
| Note Type | Follow-up (for Stand-alone Follow-ups or Activities with 2nd FF or more) |
| Relationship Manager Preferences | Always go through this for any special RM preferences such as default themes/products, expense defaults, follow-up date instructions, et cetera.
Best practice: Go through this before transcribing any RM recording to refresh your memory of the RM’s preferences. |
| App Comment/Task Description | Only fill this out if file is received via the Hey DAN app. Put the activity type/sub-type of the note generated from the file here. If file will generate more than one type of note, list them accordingly.
Examples: Note that the information you last inputted is the one that will stick on the field so make sure that the last touch is the final details you would want to keep for this field. |
| Internal Comments | Put here additional information that will help in CRM Entry (i.e., team names, websites, entity IDs or other reminders)
You can also take note here whether the note is for clarification and what the clarification is. Format: ***CLARIFY [which field] [what reason]*** |
| Special Instructions | Put here any special instruction dictated by RM. |
| GROUP | Tick if there is more than 1 attendee to add for the note. |
| SAME FOLLOW-UP | Not applicable. Just skip. |
| SAME ORGANIZATION AND LOCATION | Automatically should be checked if all attendees added for the note are from the same firm and location. If not under the same firm, untick and add the correct information of the attendees. |
| Attendees: | |
| First Name & Last Name | As specified and verified.
Special Situation #1: If the RM mentions the nickname of the advisor versus the official first name (example: Jack vs John), we should write the nickname inside quotation marks on the first name field but still adding the official first name as verified. Example: John “Jack” Doe. Note: If the nickname mentioned is the common nickname (example: Tim for Timothy or Mike for Michael Special Situation #2: If the RM mentions an incorrect first name or last name than what you were able to see and verify in FINRA and/or CRM system, you can correct and mirror what you see in the CRM system if it’s just a spelling error. But if it’s a totally different first name and/or last name, then put the name the RM specified on the Attendees field in brackets and submit the note for clarification. For standalone FFs with group attendees, maximum number of attendees we can put per DANA page is 25. If it exceeds that, we should plot in parts. So if the attendees are 50 names, it will yield 2 DANA notes. (Note: Indicate in the Quick Comments field if the note is 1/2 or 2/2 so the enterer will know that the notes are plotted in parts). IMPORTANT: If an RM requests logging a meeting that only specifies the Buying Unit (team/firm/organization) – let them know an individual client attendee is needed and must be added to the meeting record. A meeting should not only have a team as attendee, advisor/advisors are needed. |
| CRD# | CRD is not required but highly encouraged to be utilized for reference during CRM entry. |
| 1-on-1 | Not applicable. Just skip. |
| Organization | Always put the firm (even if not specified by the RM for audio recordings as long as you were able to verify in FINRA or the firm website).
Special Situation: If the RM mentioned which team the FA attendee/s belong to, let’s capture that info on the firm field. |
| Location | If specified, please include. If not specified, it is not required but highly encouraged to include for research purposes. |
| FF Type | Not applicable. Just skip. |
| Due Date | As specified. If not specified, default to +2 business days from processing date (check RM preferences as well for specific defaults per RM). Don’t forget to exclude the weekends and/or the official US holidays from the count. |
| Due Time | As specified. If not specified, skip. |
| FF Subject | Required and as specified. If not specified, follow the default format below:
If with 1 FA: Follow-up for [BLK Person] – [Client Name] |
| Description | Capture here the direct FF instructions from the RM to the internal or to whom the FF is directed to (which can be the RM him/herself). |
| Owner | Select appropriate name (if existing on the field list). If field is blank, use the Owner (Other) field to capture the name of who the FF is for. |
| Owner (Other) | Capture here the name of the BLK Person the FF is directed to (that is now on the FF Owner field list). |
| FF Regarding | As specified. If not specified, skip. Remember that this field can only accommodate 1 entity which can either be 1 FA, 1 team, 1 opportunity, or 1 campaign lead (never a combination of any of these). |
| Duration | As specified. If not specified, skip. |
| Priority | As specified. If not specified, skip. Check RM Preferences though since we have users who have rules pertaining to this field. |
| FF Themes | We generally only should select product/themes mentioned from the main note part, NOT anymore the FF instructions we’re plotting via the FF note unless the RM has a preference to select the products/themes from the follow-up like for Ricky Ruiz. |
| FF Products | |
| FF Title of Internal Notes | As specified. If not specified, skip. |
| FF Task Internal Notes | As specified. If not specified, skip. |
| FF Mark Complete | Should be used only for standalone follow-up notes. If with main note, skip this. |
==============================================
PHONE CALL
| Note Type | Phone Call (for Outbound, Inbound, Left Message Activities) |
| Relationship Manager Preferences | Always go through this for any special RM preferences such as default themes/products, expense defaults, follow-up date instructions, et cetera.
Best practice: Go through this before transcribing any RM recording to refresh your memory of the RM’s preferences. |
| App Comment/Task Description | Only fill this out if file is received via the Hey DAN app. Put the activity type/sub-type of the note generated from the file here. If file will generate more than one type of note, list them accordingly.
Examples: Note that the information you last inputted is the one that will stick on the field so make sure that the last touch is the final details you would want to keep for this field. |
| Internal Comments | Put here additional information that will help in CRM Entry (i.e. team names, websites, entity IDs or other reminders)
You can also take note here whether the note is for clarification and what the clarification is. Format: ***CLARIFY [which field] [what reason]*** IMPORTANT: For those with MSD access, if the note is for 2 or more FA attendees, please capture the EIDs of all the attendees on this field. Common Markers That We Use for This Field: |
| Special Instructions | Put here any special instruction dictated by RM.
For PS RM (Product/s Specified users), it helps to put the products dictated here for reference. |
| Date | As specified. If No Date was specified, use Recording Date for audio files or use the date when the email was sent via remote outlook.
For recordings/emailed notes that will yield multiple activities, date is usually specified, but if not, succeeding notes will always follow the date of the note before it. |
| Time | As specified. If not specified, skip.
IMPORTANT NOTE: If the RM specifies a time for their notes, please identify if the time zone of the RM is Eastern Standard Time (based on the states they cover or location of the FA – check the RM preferences section for guidance). Special Situations: #2: If the activity has an associated Entertainment – Non Employee expense note, mirror the time on the receipt as the time for the activity (with consideration of the time zone that the RM covers – see rules above). |
| GROUP | Tick if there is more than 1 attendee to add for the note. |
| SAME FOLLOW-UP | Not applicable. Just skip. |
| SAME ORGANIZATION AND LOCATION | Automatically should be checked if all attendees added for the note are from the same firm and location. If not under the same firm, untick and add the correct information of the attendees. |
| Attendees: | |
| First Name & Last Name | As specified and verified.
Should include the Advisors as well as the other BLK employees that are present during the activity. Firm of other BLK employees should always be BlackRock. Special Situation #1: If the activity is for an “internal prep call/meeting”, see Related field remarks below. Special Situation #2: If the RM mentions the nickname of the advisor versus the official first name (example: Jack vs John), we should write the nickname inside quotation marks on the first name field but still adding the official first name as verified. Example: John “Jack” Doe. Note: If the nickname mentioned is the common nickname (example: Tim for Timothy or Mike for Michael Special Situation #3: If the RM mentions an incorrect first name or last name than what you were able to see and verify in FINRA and/or CRM system, you can correct and mirror what you see in the CRM system if it’s just a spelling error. But if it’s a totally different first name and/or last name, then put the name the RM specified on the Attendees field in brackets and submit the note for clarification. For group notes, maximum number of attendees we can put per DANA page is 25. If it exceeds that, we should plot in parts. So if the attendees are 50 names, it will yield 2 DANA notes. (Note: Indicate in the Quick Comments field if the note is 1/2 or 2/2 so the enterer will know that the notes are plotted in parts). IMPORTANT: If an RM requests logging a meeting that only specifies the Buying Unit (team/firm/organization) – let them know an individual client attendee is needed and must be added to the meeting record. A meeting should not only have a team as attendee, advisor/advisors are needed. |
| CRD# | CRD is not required but highly encouraged to be utilized for reference during CRM entry. |
| 1-on-1 | DO NOT USE moving forward for activities. We should always plot the note for each FA separately because of the subject field format. Exception: If subject field is specified and the 1on1 notes would have the same subject, then you can use this. |
| Pop-up Follow-up: | Use this field if the FF is for a standalone FA attendee or if the FF is for a particular FA attendee from a group note. |
| Organization | Always put the firm (even if not specified by the RM for audio recordings as long as you were able to verify in FINRA or the firm website).
Special Situation: If the RM mentioned which team the FA attendee/s belong to, let’s capture that info on the firm field. |
| Location | If specified, please include. If not specified, it is not required but highly encouraged to include for research purposes. |
| Subject | Required and as specified. If not specified, follow the default format below:
If with 1 FA: Phone Call – [Phone Call Sub-type] – [Client Name] | Ex. Phone Call – Outbound – John Doe Note: Team is also known as the Buying Unit in MS Dynamics. Reminders: We don’t include the BLK attendees on the count. IMPORTANT: If an RM requests logging a meeting that only specifies the Buying Unit (team/firm/organization) – let them know an individual client attendee is needed and must be added to the meeting record. A meeting should not only have a team as attendee, advisor/advisors are needed. Special Situation: If the activity is specified as an “internal prep call” or “internal prep meeting”, follow the format below: |
| Internal Notes (formerly called Note Text) | Follow general writing guidelines. Clean verbatim.
a) If the note is PTS and there’s one theme/product specified by the RM that you were not able to tag as theme/product (either it’s not available at all or written very differently), you must capture all the themes/products that the RM specified at the top of the note text field and then tag whichever topics are available on the themes/product fields. b) If the note is PTS and you weren’t able to tag any themes/products from the PTS mentioned, check the RM Preferences field first if there’s a default themes/product to tag. If there is, tag it. If there is no default theme/product on the RM pref, tag Territory Management as theme, and then capture all the PTS on top of the note text field. No need to scan through the note text for any product/themes mentioned. c) If no note text was provided by the RM, please CLARIFY. |
| Group Follow-Up | Use this field if the FF is for all the FA attendees of a group note. |
| FF Type | Not applicable. Just skip. |
| Due Date | As specified. If not specified, default to +2 business days from processing date (check RM preferences as well for specific defaults per RM). Don’t forget to exclude the weekends and/or the official US holidays from the count. |
| Due Time | As specified. If not specified, skip. |
| FF Subject | Required and as specified. If not specified, follow the default format below:
If with 1 FA: Follow-up for [BLK Person] – [Client Name] |
| Description | Capture here the direct FF instructions from the RM to the internal or to whom the FF is directed to (which can be the RM him/herself). |
| Owner | Select appropriate name (if existing on the field list). If field is blank, use the Owner (Other) field to capture the name of who the FF is for. |
| Owner (Other) | Capture here the name of the BLK Person the FF is directed to (that is now on the FF Owner field list). |
| FF Regarding | As specified. If not specified, skip. |
| Duration | As specified. If not specified, skip. |
| Priority | As specified. If not specified, skip. Check RM Preferences though since we have users who have rules pertaining to this field. |
| FF Themes | We generally only should select product/themes mentioned from the main note part, NOT anymore the FF instructions we’re plotting via the FF note unless the RM has a preference to select the products/themes from the follow-up like for Ricky Ruiz. |
| FF Products | |
| FF Title of Internal Notes | As specified. If not specified, skip. |
| FF Task Internal Notes | As specified. If not specified, skip. |
| FF Mark Complete | Should be used only for standalone follow-up notes. If with main note, skip this. |
| Activity Type | Select Phone Call. |
| Sub-type | Select one of the options below: – Left Message – Inbound – Outbound (General sub-type default for “Phone Call” activities if not specified) Note: If the activity is specified as an “internal prep call” or “internal prep meeting”, default is Virtual Meeting unless specified otherwise as In-Person or Phone Call. |
| Additional BLK Users (Support) | As specified. If not specified, skip. |
| Title of Internal Notes | As specified. If not specified, skip. |
| Phone Number | As specified. If not specified, skip. |
| Duration | As specified. If not specified, skip. |
| Due Date | As specified. If not specified, skip. |
| Priority | As specified. If not specified, skip. |
| Related | As specified. If not specified, skip in Dana. (MSD will populate this automatically, we may leave as is during entry)
Note: This field can now accommodate multiple profiles, BUs, pipeline, campaigns. Special Situation: If the activity is for an “internal prep call/meeting”, capture the BLK attendees on the Attendee field and capture the FA name/s and/or BU/s (only if specified by the RM) on the Related field. |
| Close Phone Call | Required and as specified. If not specified, follow the default options below depending on the sub-type:
1) If sub-type is Outbound, use “Made”. Reminders for the Other Options: |
| Themes | IMPORTANT: If RM Preferences DOESN’T say the RM is a ***DC USER*** or an ***RI USER***, use this as the Themes field for the note.
IMPORTANT: The Themes field is a selection field so choose accordingly the applicable themes. However, the Product field is a text field so we need to write the applicable product/s row by row or line by line. GENERAL RULES: STEP 1: Identify if the note is PTS or not. PTS means that the RM is telling us what to tag as themes/products for the note usually in the beginning of the dictation but they can also specify what products/themes to tag at the end of the recording or in the middle of the dictation. STEP 2: If it is not PTS, we just simply need to scan through the note text dictated/provided and select all the themes/products mentioned from there. Best practice is to use our “Common Products & Themes” sheet as guide on what to select. a) If you weren’t able to tag any themes/products from the note text, check the RM Preferences field first if there’s a default themes/product to tag. If there is, tag it. If there is no default theme/product on the RM pref, tag Territory Management as theme. STEP 3: If it is PTS, we generally need to select only the themes/products specified by the RM. However, there are lots of scenarios wherein the themes/products specified by the RMs are not available on the field and/or written differently or are categorized under a general topic, so please be guided as follows: a) If there’s one theme/product specified by the RM that you were not able to tag as theme/product (either it’s not available at all or written very differently), you must capture all the themes/products that the RM specified at the top of the note text field and then tag whichever topics are available on the fields. b) If you weren’t able to tag any themes/products from the PTS mentioned, check the RM Preferences field first if there’s a default themes/product to tag. If there is, tag it. If there is no default theme/product on the RM pref, tag Territory Management as theme, and then capture all the PTS on top of the note text field. No need to scan through the note text for any product/themes mentioned. c) Same thing applies if the RM said “no product type to tag” or “no product”, no need to scan through the note text for any topics mentioned, just choose Territory Management as theme. |
| Products | |
| DC Themes | IMPORTANT: If RM Preferences say the RM is a ***DC USER***, use this as the Themes field for the note.
See GENERAL RULES to follow above. |
| RI Themes | IMPORTANT: If RM Preferences say the RM is an ***RI USER***, use this as the Themes field for the note.
See GENERAL RULES to follow above. |
==============================================
EMAIL RETURN
| Note Type | Email Return (for Email Return Follow-ups, Email Return Notes, Instructions/RM Pref Dictated via Recordings) |
| Relationship Manager Preferences | Always go through this for any special RM preferences such as default themes/products, expense defaults, follow-up date instructions, et cetera.
Best practice: Go through this before transcribing any RM recording to refresh your memory of the RM’s preferences. |
| App Comment/Task Description | Only fill this out if file is received via the Hey DAN app. Put the activity type/sub-type of the note generated from the file here. If file will generate more than one type of note, list them accordingly.
Examples: Note that the information you last inputted is the one that will stick on the field so make sure that the last touch is the final details you would want to keep for this field. |
| Internal Comments | Put here the subject that you will be using when sending the Email Return itself. Choose from the following format that’s applicable to your note:
Hey DAN Follow-Up for [Internal/BLK Employee] | [FA Name1] |
| Special Instructions | Put here any special instruction dictated by RM. |
| Date | Not relevant. Just use either the Processing Date or the Recording Date. |
| Time | Not applicable. Just skip. |
| GROUP | Tick if there is more than 1 attendee to add for the note. |
| SAME FOLLOW-UP | Not applicable. Just skip. |
| SAME ORGANIZATION AND LOCATION | Automatically should be checked if all attendees added for the note are from the same firm and location. If not under the same firm, untick and add the correct information of the attendees. |
| Attendees: | |
| First Name & Last Name | A) As verified. Just mirror the Advisor attendees from the main note. No need to include the RM and other BLK employees that are present during the activity.
B) Put N/A on the first name field if email return is to be used only to confirm RM preferences or instructions dictated via recordings. |
| CRD# | CRD is not required but highly encouraged to be utilized for reference during CRM entry. |
| 1-on-1 | Not applicable. Just skip. |
| Pop-up Follow-up: | Not applicable. Just skip. |
| Organization | Always put the firm (even if not specified by the RM for audio recordings as long as you were able to verify in FINRA or the firm website).
Special Situation: If the RM mentioned which team the FA attendee/s belong to, let’s capture that info on the firm field. |
| Location | If specified, please include. If not specified, it is not required but highly encouraged to include for research purposes. |
| Subject | Not applicable. Just skip. |
| Internal Notes (formerly called Note Text) | Aside from mirroring the main note’s Internal Notes the email return’s Internal Notes, we need to put these formatting below at the top of the Internal Notes field:
Advisor/s: [Put FA Name/s here] Note: Put Team Name here in parentheses if applicable | Ex. John Doe (Team Hey DAN)] [Internal Notes Here] |
| Activity Type | Not applicable. Just skip. |
| Sub-type | Not applicable. Just skip. |
==============================================
EVENT
| Note Type | Event (for All Other Activities) |
| Relationship Manager Preferences | Always go through this for any special RM preferences such as default themes/products, expense defaults, follow-up date instructions, et cetera.
Best practice: Go through this before transcribing any RM recording to refresh your memory of the RM’s preferences. |
| App Comment/Task Description | Only fill this out if file is received via the Hey DAN app. Put the activity type/sub-type of the note generated from the file here. If file will generate more than one type of note, list them accordingly.
Examples: Note that the information you last inputted is the one that will stick on the field so make sure that the last touch is the final details you would want to keep for this field. |
| Internal Comments | Put here additional information that will help in CRM Entry (i.e. team names, websites, entity IDs or other reminders)
You can also take note here whether the note is for clarification and what the clarification is. Format: ***CLARIFY [which field] [what reason]*** IMPORTANT: For those with MSD access, if the note is for 2 or more FA attendees, please capture the EIDs of all the attendees on this field. Common Markers That We Use for This Field: |
| Special Instructions | Put here any special instruction dictated by RM.
For PS RM (Product/s Specified users), it helps to put the products dictated here for reference. |
| Date | As specified. If No Date was specified, use Recording Date for audio files or use the date when the email was sent via remote outlook.
For recordings/emailed notes that will yield multiple activities, date is usually specified, but if not, succeeding notes will always follow the date of the note before it. |
| Time | As specified. If not specified, skip.
IMPORTANT NOTE: If the RM specifies a time for their notes, please identify if the time zone of the RM is Eastern Standard Time (based on the states they cover or location of the FA – check the RM preferences section for guidance). Special Situations: #2: If the activity has an associated Entertainment – Non Employee expense note, mirror the time on the receipt as the time for the activity (with consideration of the time zone that the RM covers – see rules above). |
| GROUP | Tick if there is more than 1 attendee to add for the note. |
| SAME FOLLOW-UP | Not applicable. Just skip. |
| SAME ORGANIZATION AND LOCATION | Automatically should be checked if all attendees added for the note are from the same firm and location. If not under the same firm, untick and add the correct information of the attendees. |
| Attendees: | |
| First Name & Last Name | As specified and verified.
Should include the Advisors as well as the other BLK employees that are present during the activity. Firm of other BLK employees should always be BlackRock. Special Situation #1: If the activity is for an “internal prep call/meeting”, see Related field remarks below. Special Situation #2: If the RM mentions the nickname of the advisor versus the official first name (example: Jack vs John), we should write the nickname inside quotation marks on the first name field but still adding the official first name as verified. Example: John “Jack” Doe. Note: If the nickname mentioned is the common nickname (example: Tim for Timothy or Mike for Michael Special Situation #3: If the RM mentions an incorrect first name or last name than what you were able to see and verify in FINRA and/or CRM system, you can correct and mirror what you see in the CRM system if it’s just a spelling error. But if it’s a totally different first name and/or last name, then put the name the RM specified on the Attendees field in brackets and submit the note for clarification. For group notes, maximum number of attendees we can put per DANA page is 25. If it exceeds that, we should plot in parts. So if the attendees are 50 names, it will yield 2 DANA notes. (Note: Indicate in the Quick Comments field if the note is 1/2 or 2/2 so the enterer will know that the notes are plotted in parts). IMPORTANT: If an RM requests logging a meeting that only specifies the Buying Unit (team/firm/organization) – let them know an individual client attendee is needed and must be added to the meeting record. A meeting should not only have a team as attendee, advisor/advisors are needed. |
| CRD# | CRD is not required but highly encouraged to be utilized for reference during CRM entry. |
| 1-on-1 | Tick as necessary. |
| Pop-up Follow-up: | Use this field if the FF is for a standalone FA attendee or if the FF is for a particular FA attendee from a group note. |
| Organization | Always put the firm (even if not specified by the RM for audio recordings as long as you were able to verify in FINRA or the firm website).
Special Situation: If the RM mentioned which team the FA attendee/s belong to, let’s capture that info on the firm field. |
| Location | If specified, please include. If not specified, it is not required but highly encouraged to include for research purposes. |
| Subject | Required and as specified. If not specified, follow the default format below:
If with 1 FA: [Other Activity Sub-type] – [Client Name] | Ex. Leveraged Event – John Doe Note: Team is also known as the Buying Unit in MS Dynamics. Reminders: We don’t include the BLK attendees on the count. IMPORTANT: If an RM requests logging a meeting that only specifies the Buying Unit (team/firm/organization) – let them know an individual client attendee is needed and must be added to the meeting record. A meeting should not only have a team as attendee, advisor/advisors are needed. Special Situation: If the activity is specified as an “internal prep call” or “internal prep meeting”, follow the format below: |
| Internal Notes (formerly called Note Text) | Follow general writing guidelines. Clean verbatim.
a) If the note is PTS and there’s one theme/product specified by the RM that you were not able to tag as theme/product (either it’s not available at all or written very differently), you must capture all the themes/products that the RM specified at the top of the note text field and then tag whichever topics are available on the themes/product fields. b) If the note is PTS and you weren’t able to tag any themes/products from the PTS mentioned, check the RM Preferences field first if there’s a default themes/product to tag. If there is, tag it. If there is no default theme/product on the RM pref, tag Territory Management as theme, and then capture all the PTS on top of the note text field. No need to scan through the note text for any product/themes mentioned. c) If no note text was provided by the RM, please CLARIFY. |
| Group Follow-Up | Use this field if the FF is for all the FA attendees of a group note. |
| FF Type | Not applicable. Just skip. |
| Due Date | As specified. If not specified, default to +2 business days from processing date (check RM preferences as well for specific defaults per RM). Don’t forget to exclude the weekends and/or the official US holidays from the count. |
| Due Time | As specified. If not specified, skip. |
| FF Subject | Required and as specified. If not specified, follow the default format below:
If with 1 FA: Follow-up for [BLK Person] – [Client Name] |
| Description | Capture here the direct FF instructions from the RM to the internal or to whom the FF is directed to (which can be the RM him/herself). |
| Owner | Select appropriate name (if existing on the field list). If field is blank, use the Owner (Other) field to capture the name of who the FF is for. |
| Owner (Other) | Capture here the name of the BLK Person the FF is directed to (that is now on the FF Owner field list). |
| FF Regarding | As specified. If not specified, skip. |
| Duration | As specified. If not specified, skip. |
| Priority | As specified. If not specified, skip. Check RM Preferences though since we have users who have rules pertaining to this field. |
| FF Themes | We generally only should select product/themes mentioned from the main note part, NOT anymore the FF instructions we’re plotting via the FF note unless the RM has a preference to select the products/themes from the follow-up like for Ricky Ruiz. |
| FF Products | |
| FF Title of Internal Notes | As specified. If not specified, skip. |
| FF Task Internal Notes | As specified. If not specified, skip. |
| FF Mark Complete | Should be used only for standalone follow-up notes. If with main note, skip this. |
| Activity Type | Select Other Activity. |
| Sub-type | Select one of the options below: – Bloomberg Chat – Internal Comm – News – Leveraged Events |
| Additional BLK Users (Support) | As specified. If not specified, skip. |
| Title of Internal Notes | As specified. If not specified, skip. |
| Related | As specified. If not specified, skip in Dana. (MSD will populate this automatically, we may leave as is during entry)
Note: This field can now accommodate multiple profiles, BUs, pipeline, campaigns. Special Situation: If the activity is for an “internal prep call/meeting”, capture the BLK attendees on the Attendee field and capture the FA name/s and/or BU/s (only if specified by the RM) on the Related field. |
| Mark Complete? | Tick Yes if specified. If not specified, skip. |
| Themes | IMPORTANT: If RM Preferences DOESN’T say the RM is a ***DC USER*** or an ***RI USER***, use this as the Themes field for the note.
IMPORTANT: The Themes field is a selection field so choose accordingly the applicable themes. However, the Product field is a text field so we need to write the applicable product/s row by row or line by line. GENERAL RULES: STEP 1: Identify if the note is PTS or not. PTS means that the RM is telling us what to tag as themes/products for the note usually in the beginning of the dictation but they can also specify what products/themes to tag at the end of the recording or in the middle of the dictation. STEP 2: If it is not PTS, we just simply need to scan through the note text dictated/provided and select all the themes/products mentioned from there. Best practice is to use our “Common Products & Themes” sheet as guide on what to select. a) If you weren’t able to tag any themes/products from the note text, check the RM Preferences field first if there’s a default themes/product to tag. If there is, tag it. If there is no default theme/product on the RM pref, tag Territory Management as theme. STEP 3: If it is PTS, we generally need to select only the themes/products specified by the RM. However, there are lots of scenarios wherein the themes/products specified by the RMs are not available on the field and/or written differently or are categorized under a general topic, so please be guided as follows: a) If there’s one theme/product specified by the RM that you were not able to tag as theme/product (either it’s not available at all or written very differently), you must capture all the themes/products that the RM specified at the top of the note text field and then tag whichever topics are available on the fields. b) If you weren’t able to tag any themes/products from the PTS mentioned, check the RM Preferences field first if there’s a default themes/product to tag. If there is, tag it. If there is no default theme/product on the RM pref, tag Territory Management as theme, and then capture all the PTS on top of the note text field. No need to scan through the note text for any product/themes mentioned. c) Same thing applies if the RM said “no product type to tag” or “no product”, no need to scan through the note text for any topics mentioned, just choose Territory Management as theme. |
| Products | |
| DC Themes | IMPORTANT: If RM Preferences say the RM is a ***DC USER***, use this as the Themes field for the note.
See GENERAL RULES to follow above. |
| RI Themes | IMPORTANT: If RM Preferences say the RM is an ***RI USER***, use this as the Themes field for the note.
See GENERAL RULES to follow above. |
==============================================
PIPELINE – AT RISK
| Note Type | Pipeline/At Risk (for All Opportunity Requests) |
| Relationship Manager Preferences | Always go through this for any special RM preferences such as default themes/products, expense defaults, follow-up date instructions, et cetera.
Best practice: Go through this before transcribing any RM recording to refresh your memory of the RM’s preferences. |
| App Comment/Task Description | Only fill this out if file is received via the Hey DAN app. Put the activity type/sub-type of the note generated from the file here. If file will generate more than one type of note, list them accordingly.
Examples: Note that the information you last inputted is the one that will stick on the field so make sure that the last touch is the final details you would want to keep for this field. |
| Internal Comments | Put here additional information that will help in CRM Entry (i.e., team names, websites, entity IDs or other reminders)
You can also take note here whether the note is for clarification and what the clarification is. Format: ***CLARIFY [which field] [what reason]*** |
| Special Instructions | Not applicable. Just skip as all instructions for pipeline should be included on the Internal Notes field. |
| Date | Not relevant. Just use either the Processing Date or the Recording Date. |
| Time | Not applicable. Just skip. |
| GROUP | Not applicable. Just skip. |
| SAME FOLLOW-UP | Not applicable. Just skip. |
| SAME ORGANIZATION AND LOCATION | Not applicable. Just skip. |
| Attendees: | |
| First Name & Last Name | As specified. Should be FA/s only. If opportunity is specified for the team, get all the BU contacts from MSD and capture them as the opportunity attendees or the Client Contact names. |
| CRD# | CRD is not required but highly encouraged to be utilized for reference during CRM entry. |
| 1-on-1 | Not applicable. Just skip. |
| Pop-up Follow-up: | Only use this if the opportunity is specifically a task for the pipeline notes. |
| FF Type | Not applicable. Just skip. |
| Due Date | As specified. If not specified, default to +2 business days from processing date (check RM preferences as well for specific defaults per RM). |
| Due Time | As specified. If not specified, skip. |
| FF Subject | Required and as specified. If not specified, follow this format: Follow-up for [BLK Person] – [Client Name] |
| Description | Capture here the direct FF instructions from the RM to the internal or to whom the FF is directed to (which can be the RM him/herself). |
| Owner | Select appropriate name (if existing on the field list). If field is blank, use the Owner (Other) field to capture the name of who the FF is for. |
| Owner (Other) | Type in the name of who the RM specified the FF is for (that’s not the name on the Owner field). |
| FF Regarding | As specified. If not specified, skip. |
| Duration | As specified. If not specified, skip. |
| Priority | As specified. If not specified, skip. Check RM Preferences though since we have users who have rules pertaining to this field. |
| FF Themes | We generally only should select product/themes mentioned from the main note part, NOT anymore the FF instructions we’re plotting via the FF note unless the RM has a preference to select the products/themes from the follow-up like for Ricky Ruiz. |
| FF Products | |
| FF Title of Internal Notes | As specified. If not specified, skip. |
| FF Task Internal Notes | As specified. If not specified, skip. |
| FF Mark Complete | Should be used only for standalone follow-up notes. If with main note, skip this. |
| Organization | Always put the firm (even if not specified by the RM for audio recordings as long as you were able to verify in FINRA or the firm website).
Special Situation: If the RM mentioned which team the FA attendee/s belong to, let’s capture that info on the firm field. |
| Location | If specified, please include. If not specified, it is not required but highly encouraged to include for research purposes. |
| Subject | Not applicable. Just skip. |
| Internal Notes (formerly called Note Text) | Capture instructions/details for the pipeline dictated by the RM here. |
| Activity Type | Select Pipeline. |
| Sub-type | Not applicable. Just skip. |
| Stage | As specified. If not specified, choose Prospecting if “Funding/Trade Date” and “Confidence Level” are NOT provided/available in the RM pref. If provided, default the stage to Early.
[MSD Stages] = [Old TeamWorld Stages] |
| Type | As specified. If not specified, choose New Mandate, Inflow or Solution. |
| Pipeline Name | As specified. If not specified, follow the “naming conventions” below per Megan: Alternatives – BPIF Alternatives – POF V Alternatives – CREDX Alternatives – BDEBT Alternatives – GPS Alternatives – SEHF Alternatives – BDMIX SMA – SpiderRock SMA – Aperio SMA – Equity SMA – Fixed Income Models – CMS iShares – “INSERT TICKER” (Recommend only including iShares opportunities of $10M or more) Mutual Fund – “INSERT FUND NAME” (Recommend only including MF opportunities of $5M or more) |
| Client Contact | As specified. Should be FA/s only. If opportunity is specified for the team, get all the BU contacts from MSD and capture them as the opportunity attendees or the Client Contact names. |
| RM Lead (Owner) | As specified. If not specified, use the RM’s name. |
| RM Secondary | As specified. If not specified, skip. |
| RM Co-Lead | As specified. If not specified, skip. |
| Pipeline Team Member | As specified. If not specified, skip. |
| Pipeline Products | As specified. If not specified, clarify with the RM. (You should capture the expanded name of the fund/ticker symbols here). |
| Timeline Notes | Only use this for opportunity notes if specified on the request and/or per RM Pref to utilize this field. If not specified, skip. |
| Amount | Put in here the amount specified by the RM in this format with the dollar sign and commas for uniformity and reporting purposes: Example: $12,000,000
If not specified, skip. |
| Management Fee (bps) | As specified. If not specified, skip. |
| Confidence Level | As specified (if Low, Medium or High). If not specified, skip. |
| Decision Date | As specified. If not specified, skip. |
| Funding/Trade Date | As specified. If not specified, skip. |
| Alts Close Date | As specified. If not specified, skip. (Note: Only applicable to “Private markets fund” opportunity type. |
| Details Notes | Required per POC. If not provided, CLARIFY. If the opportunity has an associated activity note, you may get details of the opportunity from the note if provided. Otherwise, CLARIFY. |
| Are there Competitors? (This section should be filled out by LATE stage) | Required and as specified.
If not specified, select None/NA as default. If Competitors field specified is Yes, we are required to fill out the Competitor(s) Pricing Details field. |
| Competitor(s) Pricing Details | If Competitors field selected is None/NA or Unknown, this is not required. So, if none was specified, skip.
If Competitors field selected is Yes, this is required. So, fill it out as specified. If none was specified, tag for clarification. |
| New Competitor Name | As specified. If not specified, skip. |
| Top Motivations for Client to Take Action (This section should be filled out by LATE stage) | As specified. If not specified, skip. Just CLARIFY as needed when progressing the pipeline stage. |
| Reasons for Success (This section should be filled out by NOTIFIED stage) | As specified. If not specified, skip. Just CLARIFY as needed when progressing the pipeline stage. |
| Reasons for Not Succeeding (This section should be filled out by NOTIFIED stage) | As specified. If not specified, skip. Just CLARIFY as needed when progressing the pipeline stage. |
