This is where all these user consultations were so valuable, because people told us what they would be looking at in a system that they would actively use. For example, a manager could go on the system and create a new job rather than spend weeks doing the job description and creating it. If a system can create it based on a common language construct so that you're not inventing terminology to describe what the person will be doing but just pull it out of the system and say you need somebody who's going to be a system administrator; we can pull that together very quickly. You have a job description, and you can have a poster that's generated very quickly as a result. You identify your key requirements—not 22, maybe five—because each one of them has to be assessed under our law. That way we could drive a lot of efficiency in the system.
We also have a feature so that we would allow the administrateur général, the deputy minister, to monitor the time it takes at each step of the process, because we lose track. Therefore, if a manager has designed a poster and is sitting on it and not sending it out or has received the application and has not started the first level of screening, that would show up in performance in the system. You could design it in such a way that you could track those situations and have a nudge automatically sent to that manager to ask if they know they have 20 candidates waiting to hear back from them. The technology is there.