Validation Methodology and Timing

What is the core indicator of whether or not Concurrent Validation is an option?

• The project has a DMA assigned specifically for manager / supplier outreach

• The project has a short timeline

• The project is a consulting project

• The project has both suppliers and managers in the starting worker population

Aside from the timing of reaching out to suppliers / managers, what is the main difference between Concurrent and Sequential Validation?

• Sequential is only used on Consulting projects

• Sequential has no gap close period

• Concurrent takes 1 more week than Sequential

• Sequential relies on the client to provide the data fully validated for testing

What is the main impact of Sequential Validation not having a gap close period?

• Sequential usually takes less time than Concurrent

• Sequential usually results in a lower % of data ready for Wave A testing

• Sequential usually results in more accurate data

• Sequential usually results in more spend in the program

For which project type is Client-Managed Validation the standard?

• MSP

• Consulting

Which of these is in the correct order for these tasks?

• Worker Data Migration Discovery, DVT Review, Data Validation Plan

• Pre-Imp Packet Review, DVT Lock, Data Validation Plan

• DVT Review, Data Validation Plan, Validation Kickoff

• Pre-Imp Packet Review, Data Validation Plan, DVT Review

What project milestone marks when the DVT is locked and fields are expect to remain the same?

• Data Validation Plan Review

• Client Data Validation Template Review

• Proof of Concept

• Validation Kickoff

Following our standard approach, how many weeks do suppliers and managers each get to validate their data?

• 1 week each

• 2 weeks each

• 3 weeks each

• 4 weeks each

Following our standard, how many weeks is the upload testing window?

• 1 week

• 2 weeks

• 3 weeks

• 4 weeks

What vital step involving the reporting team occurs between validation and upload testing?

• Foundational Data Checks

• Spend Analysis

• Monument Job Title Mapping

• Peer Data Audits

Why do we target 2 weeks after go-live to load Wave B data?

• Because 2 weeks is included in our standard SOW with clients

• Because we want to allow workers to enter time before the first invoice run

• Because 2 weeks is how long it takes to get the data fully validated

• Because it's the lightest part of the project for the DMA