Question model for application

[Jagusti]

Deliverables:

• clickable prototype
• data user matrix

Questions:

• [ ] Do all the questions need to be included?
  • [ ] who needs what application data when?
  • [ ] where does some of the data already exist within the FSA or other systems (eg, Companies House, SSRS report inputs)
• [ ] Does the ordering of the questions fit?
• [ ] Where can sections be introduced?
• [ ] Are all of the field types appropriate?
• [ ] Where can we make improvements to the form with the technology available to us (e.g. maps and complete later options)?

Reference:

• GDS patterns for question pages, including question protocol guidance
• GDS Service Manual - Designing good questions
• GDS Service Manual - Form structure

[jonnow]

• Changes made to the capture of names - following discussion with Paul McGuiness we’ve learned that they want to check the name (first and last) against their database. This needs to be addressed.
• The activities pages - This has some basic show/hide functionality but could be built upon to include logic branching depending on answers.
• Consideration of what happens upon completion of the form - user feedback to demonstrate the flow for an FBO.
• Iterations will be tested with Paul and other members of the approvals team.