[0036] In some configurations, a transcription policy 204 can be defined that includes data specifying whether transcriptions 112 are to be generated for meetings scheduled by users in an organization. For example, a user 218 with appropriate administrator privileges can utilize a computing device 106C and an application program 202A (e.g. a web browser application) to access an administration portal 220. [0037] Through the administration portal 220, the user 218 can define a transcription policy 204 that indicates that transcriptions 112 are to be generated. The transcription policy 204 can be stored in a substrate 206 that includes storage and processing facilities. The substrate 206 might be integrated with the context-aware transcription system 102 or implemented by another system in other configurations. [0038] As shown in FIG. 2, a meeting attendee 104A, or another user, can utilize a computing device 106B and an application 202B (e.g. a personal information manager (“PIM”) application or another type of local or web-based calendaring application) to schedule a meeting with one or more other attendees 104. Data describing the meeting is stored in a meeting definition 208, which is also persisted in the substrate 206 in some configurations. [0039] The meeting definition 208 can include various types of data regarding a meeting including, but not limited to, a unique identifier for the meeting, the date and time of the meeting, and a list of the attendees 104 of the meeting. The meeting definition 208 can include other types of data not specifically identified herein. [0040] As also shown in FIG. 2, the context-aware transcription system 102 includes a language model preparation service 210 in some configurations. The language model preparation service 210 is a network service that can retrieve meeting-specific data 214 prior to or during a meeting. The meeting-specific data 214 can include, but is not limited to, messages (e.g. email, text messages, instant messages, etc.) generated by or otherwise associated with meeting attendees 104, file attachments to messages, names of meeting attendees 104, or files created by or otherwise associated with meeting attendees 104. [0041] The meeting-specific data 214 can be retrieved for a predefined period of time. For example, the previous six months (or other time period) of messages for each of the meeting attendees can be retrieved. The meeting-specific data 214 can include jargon, acronyms, or other types of domain-specific terminology associated with the meeting attendees 104. The meeting-specific data 214 can be identified based upon the meeting definition 208 (e.g. the list of attendees) and/or other types of information. [0042] Once the language model preparation service 210 has collected the meeting-