It needs work on

• Streamlining architecture -- schema has a couple of warts given the time frame I was using to get it out and my process of "build and tweak"
• Add UI for creating questions and loading candidate contact information (I just used PHPMyAdmin)
• Separating code from presentation -- currently PHP is written in the context of Dreamweaver templates. There are some "includes" but could be a lot cleaner.
• Improving at least one UI hack having to do with how lists of answers in question number order are presented.
• Review of security process (how to protect hacking of updates but still keep candidate access relatively simple, how to "approve" a final response from a candidate and lock down other changes)
• Add a query functionality to narrow the responses to, say, just certain candidates on certain questions or to show all candidates/responses on one "page".
• Way to determine the phase (i.e. change from collection to display, do appropriate lock downs, etc.) from the admin menu
  • Now it's necessary to edit the record in the candidate record to put in the appropriate session id to get the candidate info to show up on the View page
  • A way to show all candidates who have submitted responses is needed during the collection phase.
    

To be really useful as a generic model, this probably needs to be considered a proof of concept. It may be easier to redo *all* the programming than to hack at this.