This reference guide provides an overview of how the reporting engine processes student and job records. Instead of viewing every field as just another survey question, you can optimize your data collection by understanding how each attribute fits into three distinct, functional frameworks.
Sections
- 1. The Gatekeepers (Report Inclusion Filters)
- 2. The Traffic Directors (Table-Driving Fields)
- 3. The Safety Nets (Compliance & Audit Guidance)
1. The Gatekeepers (Report Inclusion Filters)
These fields decide whether a student or job record is allowed into your official report pool. If a record fails any of these initial system checks, the reporting engine completely ignores it:
- Student Profile Basics: The system verifies that the student profile is marked as Active = Yes, assigned to the correct Program, and matched to the right Grad Year/Term.
- Job Record Toggles: The job must be mapped to the correct Job Phase and cannot have the Exclude from Reporting box checked.
- The Site Settings Gates: Depending on your unique site configurations, the system checks if the entry is still an unapproved draft or marked as an admin-added "Rumor."
- The Timing Windows: The entry must have an Accepted Date and a Reported Date that fall safely inside your program format's term-based calendar cutoffs.
2. The Traffic Directors (Table-Driving Fields)
Once a record is allowed inside the report pool, these fields tell the system exactly which table, row, or column the student belongs in. Missing information here will cause students to route into the wrong categories:
- Sorting the Grids: Fields like Function, Industry, Location (Country/City/State), and Job Source place the student onto the correct descriptive rows of your employment summaries.
- Work Authorization Splits: The Consolidated Work Authorization field specifically divides your graduates into "Permanent" vs. "Non-Permanent" tables. If left blank, they automatically route to the "Not Reported" category.
- Statistical Averages: Fields like Base Salary, Signing Bonus, and Years of Experience feed your calculated averages (Mean, Median, High, Low).
- Specialty Master’s Multi-Filters: Fields like "Is this full-time?", "20+ hours per week?", and Start/End Dates work together to route students between permanent full-time rows and short-term contract rows.
- Part-Time Career Progression Metrics: For Part-Time tracks, the engine compares During School vs. Post-Graduation fields—specifically Company, Function, Industry, City, and Promotion—to calculate your career advancement charts.
3. The Safety Nets (Compliance & Audit Guidance)
These items do not impact the platform's code or automated report calculations. The software will not block you if these are blank, but your team must maintain them to pass an external compliance audit:
- The Outreach Logs: Handled via manual data notes to prove your team tried reaching an unresponsive student the required number of times before assigning them to the unknown pool.
- Knowledge Rate Thresholds: The target data collection percentages (such as keeping unknown students under 15% or 30% of the cohort) used to measure your data's overall health before submission.
- Closing the Door: The administrative action of manually toggling the student outcome survey to Off in your Site Settings once your final term deadline passes so no late student-entered data can alter your finalized numbers.
Disclaimer: While these articles are intended to assist 12Twenty customers in compiling their official MBA CSEA reports, they should not be considered formal guidance on interpreting MBA CSEA standards, or instructions on how to comply with them. For that, we always recommend reviewing the latest version of the MBA CSEA standards, which can be found at https://cseaglobal.org/page/standards, or contacting the MBA CSEA directly with any questions.