Abstract: An expense report generation system receives transaction authorization data from a card issuer and compares the data with expense report generation criteria to determine whether to generate an expense report, prior to settlement of the transaction, based on the authorization data. The expense report generation system evaluates additional data obtained from other data sources including contextual information of the employee, transaction authorization, location, and other employees to generate the expense report. The expense report generation system subsequently updates the generated expense report based on updated transaction authorization data and/or transaction settlement data. The expense report generation system trains and uses a machine learning model for efficiency and accuracy in generating expense reports from transaction authorization data while reducing an employee's burden in manually inputting expense information and the approval process burden.

Abstract: Operations include aggregating, analyzing, and displaying information about prospects for an educational institution. The system may aggregate prospect information by traversing, for example, lower education databases, social networking websites, or testing organization databases. The system may evaluate prospects which are potential applicants to generate recommendations for contact by a recruiter. Alternatively, or additionally, the system may evaluate prospects which have applied for admission to the institution to generate recommendations for acceptance by an admission officer. The system may recommend a prospect based on the prospect's potential for success in the institution. Success may correspond to metrics such as a likelihood of graduating from the educational institution or a likelihood of obtaining employment subsequent to graduating from the institution. Prospects sharing attributes with previously successful students may be selected for recommendation.

Abstract: Operations include identifying students at risk of dropping out or transferring from an academic institution. A student risk analyzer determines a risk score for a student, which may be used to determine whether the student is at-risk. The risk score may be based on a combination of factors. As an example, the risk score may be based on a similarity between (a) attributes of the student and (b) attributes of students that have previously dropped out or transferred to other institutions. A student retention interface displays risk information for students in aggregate form or individual form. The interface may display student information in a student-population view comprising aggregate student information. The interface may display a risk-category view comprising a subset of students. The interface may display an individual-profile view comprising detailed information about a particular student. The interface may allow for drill-down navigation between the views.

Abstract: An event management system generates and displays an event schedule for an attendee. An initial order of the event schedule is based on (a) events already completed by the attendee, (b) events to be completed by the attendee to meet an event completion target, and (c) a set of ordering rules associated with the set of events to be completed by the attendee. The event management system may include an interface for modifying the event schedule in accordance with the set of ordering rules. The interface may include an initial set of events, in an initial order with respect to a timeline. The event management system may receive user input including a proposed modification to the initial order of the events. The event management system may or may not permit the proposed modification based on the set of ordering rules.

Abstract: Operations include aggregating, analyzing, and displaying information about prospects for an educational institution. The system may aggregate prospect information by traversing, for example, lower education databases, social networking websites, or testing organization databases. The system may evaluate prospects which are potential applicants to generate recommendations for contact by a recruiter. Alternatively, or additionally, the system may evaluate prospects which have applied for admission to the institution to generate recommendations for acceptance by an admission officer. The system may recommend a prospect based on the prospect's potential for success in the institution. Success may correspond to metrics such as a likelihood of graduating from the educational institution or a likelihood of obtaining employment subsequent to graduating from the institution. Prospects sharing attributes with previously successful students may be selected for recommendation.

Abstract: Operations include identifying students at risk of dropping out or transferring from an academic institution. A student risk analyzer determines a risk score for a student, which may be used to determine whether the student is at-risk. The risk score may be based on a combination of factors. As an example, the risk score may be based on a similarity between (a) attributes of the student and (b) attributes of students that have previously dropped out or transferred to other institutions. A student retention interface displays risk information for students in aggregate form or individual form. The interface may display student information in a student-population view comprising aggregate student information. The interface may display a risk-category view comprising a subset of students. The interface may display an individual-profile view comprising detailed information about a particular student. The interface may allow for drill-down navigation between the views.

Abstract: An event management system generates and displays an event schedule for an attendee. An initial order of the event schedule is based on (a) events already completed by the attendee, (b) events to be completed by the attendee to meet an event completion target, and (c) a set of ordering rules associated with the set of events to be completed by the attendee. The event management system may include an interface for modifying the event schedule in accordance with the set of ordering rules. The interface may include an initial set of events, in an initial order with respect to a timeline. The event management system may receive user input including a proposed modification to the initial order of the events. The event management system may or may not permit the proposed modification based on the set of ordering rules.