< back

balanceAAP > Plan Review

Data Tables

Notes: The term "Required," as shown in the column headers below, refers to a system requirement for operation of the Data table.

Fields in italic below are placeholders for special data. For a list of Help resources on special data, see: Custom Data Capabilities.

Plan Review

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                

Section Name Item # Description Type
Plan Information 1.0 Confirm that that plan date is correct in the plan information screen, and plan date range is correct. The plan date range should be the 12 months prior to the plan date. Manual
Plan Information1.2Verify that EEO Schedule selected in the plan information screen is correct for type of company.Manual
Plan Information1.3Plan Code Table: Company and Establishment Names are spelled correctly.Manual
Plan Information1.4Plan Code Table: Document explanation for plans under 50 employeesAuto
Plan Information1.5Determine if any catch-all plans are used. For example, a plan that includes all remote sales workers, or all locations less than 50 employees combined in one plan. Confirm this is appropriate and document explanation.Manual
Plan Information1.6Current plan employee count is compared to the history source plan’s employee count, document explanation if the difference in employee count is more than a 25% difference.Auto
Plan Information1.7Plan Information: Plan Code Structure in Update Plan Matches Annual Plan.Auto
Reference and Data Tables2.0All errors are corrected OR document explanation for remaining errors.Auto
Reference and Data Tables2.1File Consistency: All issues are cleared OR document explanation for remaining issues.Auto
Reference and Data Tables2.2Race Code Table: 1. All Race Codes are valid, i.e. no "unknown". 2. All Race Codes match Race Category.Auto
Reference and Data Tables2.3Gender Code Table: 1. Gender Codes are valid, i.e. no "unknown"; 2.) Gender Codes match Gender Category.Auto
Reference and Data Tables2.4Job Group Table: Job Groups are assigned to correct EEO Category.Manual
Reference and Data Tables2.5Job Group Table: Job Group Names are spelled correctly.Manual
Reference and Data Tables2.6Grade Code Table: 1. Grades are sequenced highest midpoint to lowest midpoint and Jobs are ordered by EEO Category OR 2. "Order Jobs with No Grades" was applied.Auto
Reference and Data Tables2.7Department Table: No blank or duplicate Department Names.Auto
Reference and Data Tables2.8Applicant Disposition Table: Correct category is checked for Hired, Offer Extended, Internal Successful, Exclude, as applicable.Manual
Reference and Data Tables2.9Applicant Disposition Table: "Offer Extended" category is checked for all applicable dispositions, e.g. failed drug test; no show for first day.Manual
Reference and Data Tables2.1Applicant Disposition Table: No codes for Acquisitions or Recalls are categorized as "Hired".Manual
Reference and Data Tables2.11Termination Code Table: Voluntary/Involuntary status is correct for each code.Manual
Reference and Data Tables2.12Roster: Annualized Salary: 1. Wage Rate, Annualized Salary, and Hours Per Week fields are populated for all records; 2. All salaries meet Federal minimum wage and are annualized to full-time equivalent of 2080 hours per year; OR 3. Document explanation and approval of salaries below minimum wage and "0" hours per week.Auto
Reference and Data Tables2.13Roster/New Hires/Applicants: Employees who are in both the New Hires and Roster have the same Protected Veterans designation in both data tables. Hired Applicants coded as Protected Veterans or Individual with Disability have the same designation in their New Hire record. Note: "Reconcile Protected Veterans and IWD" function in Applicant Table will match PV/IWD across all tables for all Applicants/New Hires with a Full Match in the Applicant Workbook.Manual
Reference and Data Tables2.14Roster: Annotations: Work Location field is populated for all records and Annotations are identified; employees with a Remote designation of TRUE are set as Annotations; OR document explanation for no Annotations.Manual
Reference and Data Tables2.15Acquisitions or Recalls are captured in a separate user personnel action, not in the New Hires.Manual
Reference and Data Tables2.16Applicant Table: No duplicate records exist.Auto
Reference and Data Tables2.17Roster/PA Tables: HireDate/ActionDate are populated for all records.Auto
History3.0History Source is set to correct prior year AAP in single plan or master plan and subplans.Auto
History3.1History: Source: History Settings: Advanced Settings: Include New Hires in History Pool: If setting is checked, document explanation and approval for using setting.Auto
IWD/Veterans4.0Confirm that Hiring Overview screen is calculated. If Master Plan, confirm ‘Edit by Sub Plan’ is checked and Plan Codes are in bold.Auto
IWD/Veterans4.1Confirm that PV Hiring Benchmark % is correct for the plan date. On PV Hiring Benchmark report, % should be as of the start of your plan date range (i. e.: for a 1/1/2021 AAP, the % should be what it was on 1/1/2020). In PV narrative, hiring benchmark listed should be as of the plan date (i.e.: for a 1/1/2021 AAP, the narrative should list the benchmark that was in place on 1/1/2021).Auto
Plan Narratives5.0Settings: 1. Reports are included for all narratives; 2. Tags and Values that are in use and needed for correct text display are populated; 3. Affirmative Action Officer and Policy Signer are not the same name.Auto
Plan Narratives5.1Settings: Tags and Values spelling/punctuation is correct.Manual
Plan Narratives5.2Settings: Outreach Programs match respective narrative.Manual
Primary Reports6.0Census Code Assignments: 1. No aggregate Census Codes assigned. 2. For plans using Start Point Analysis, all Used Job Codes have a Census Code assigned. 3. Census codes are appropriate to Job Titles. 4. Census Codes in EEO Category 1.1 are specific to Job Titles, not all assigned as ‘0010’.Auto
Primary Reports6.1Organizational Profile: Workforce Analysis: 1. Sequencing in grade table is appropriate; and 2. Reports Settings for Workforce Analysis is reviewed and confirmed the correct ‘Order By’ option was selected. OFCCP requires that every Department includes a Supervisor – complete this check manually. Organizational Display: 1. Supervisors are identified for every Department; and 2. All Departments, except Top Department, are assigned a Reports To Department.Manual
Primary Reports6.2Job Group Analysis: 1. Verify Job Titles are appropriate to Job Group and EEO Category; 2. Document explanation and approval for exceptions.Manual
Primary Reports6.3Job Group Analysis Summary: 1. There is no required Job Group size, but Job Groups of 30-50 employees are recommended. If small job groups are due to something other than EEO Category, document explanation. Document explanation for large job groups. 2. Minority and Female % seem appropriate for industry and geographic location. 3. Document any job group structure changes (breakouts, roll-ups, etc.) made in this AAP year.Manual
Primary Reports6.41. Work Location is populated for all records; 2. At sub plans, confirm that Reports In/Out is captured correctly – if using Balance Reports In/Out function, Reports In/Out will only be captured at EEO 1.1 and 1.2 levels by default. Document exceptions where plans do not have someone reporting out. 3. Confirm that all employees designated as Reports In/Out have the ‘Reports to Location’ column populated. 4. Document explanation and approval for a location with 50 or more employees that is not a separate AAP (i.e.: customer site). 5. Confirm plan(s) with no locations with 50 or more employees is correct.Auto
Primary Reports6.5Recruitment Area Worksheet: 1. Reasonable Recruitment Areas for each job group in each plan are correct: areas are appropriate to plan location, work locations, and EEO category (i.e.: broader areas at higher EEO categories, local areas at lower EEO categories). 2. Annotated locations are included in Reasonable Recruitment Areas. 3. Remote employees are accounted for with United States percentage in Reasonable Recruitment Area.Manual
Primary Reports6.6Availability Factor Computation Form: 1. No weight on Factor 2 if no Feeder Pool; 2. Document approval for weight on Factor 2 of 50% or more.Auto
Primary Reports6.7Feeder Job Calculations: Document explanation and approval of downward Feeders and/or Feeders within Job Group.Auto
Primary Reports6.8Incumbency vs. Estimated Availability: Standard rule recommended is Significant Difference – document rationale if other rule is being used.Manual
Primary Reports6.9Data Collection Analysis for IWD/PV: 1. Number of Job Openings and Jobs Filled are greater than or equal to Hired Applicants and logical for Roster count. 2. If no IWD/PV applicants, confirm compliance with self-ID requirements.Auto
Primary Reports6.10Narratives: 1. No blank pages; font, spacing, formatting are correct; 2. Narrative tags are populated appropriately to respective narrative and spelling/punctuation is correct; 3. EEO/AA Policy Statement is customized and signed; 4. Custom policies and exhibits are updated to current plan year; 5. PV benchmark is correct for plan date.Manual
Primary Reports6.11Applicants by Disposition Code by Job Group and New Hires Summary: verify that hired applicants for each job group on the Applicants by Disposition Code by Job Group match the number of new hires for that job group on the New Hires Summary. Confirm total hires by group as well as race and gender numbers by group match.Auto
Support Reports7.0Applicant Summary by Disposition by Job Group: 1. Internal Hires are not Unknown race/gender; 2. All Job Groups have a Hire; 3. Document explanation for low or no applicant pools.Auto
Support Reports7.1Detail for Promotions: 1. All job groups with selections have a pool listed that is not 0. 2. Number Selected is less than Pool; OR document explanation and approval when Pool is less than Selected.Auto
Support Reports7.2Detail for Terminations: 1. All job groups with selections have a pool listed that is not 0. 2. Number Selected is less than Pool; OR document explanation and approval when Pool is less than Selected.Auto
Support Reports7.3Detail for Applicants: Identify Job Groups where the number of selected applicants is equal to the number of applicants in the pool. Document reasoning for these (i.e.: executive level hire, other job-seekers were excluded, highly-specialized role, etc.).Auto
Other8.0Job Groups with Default RRA report: Confirm that any sub plans using Master Default Reasonable Recruitment Area were intentionally set that way (i.e.: all groups in one EEO category using United States).Auto