The Builder Check List

Each time you create a form, you need to consider the following:

How will the question fields and data look on the data entry page?

How will the form look when you open it again once it has been entered?

Which fields do you need to pull through to show in the athlete history page, and do any of these need to be graphed?

Which fields have you selected to pull through as summary fields into the sidebar, or the Profile Reports?

Which fields are important for setting up Performance Summary Dashboards, Performance Alerts?

When you create an Event form or a Profile form, you ALWAYS need to look beyond whether it captures the correct datain the data entry page,  and think about how it will look on each of the modules in the application.

This is an example of a form that needs additional optimisation on the builder.

All forms should be designed to capture all of your information. The most important task of a builder is being able to choose (in conjunction with your technical lead) which fields are the most important to show through into the athlete history and reports pages by default. Some event form capture upwards of 300 fields. If 300 fields are set to show in the table you will not be able to focus on the important fields out of the form.

1. In your Event Form set the most important fields (8-10 fields from your form) as default show in tables, and set ALL other field to default show in tables=false. You can also set 1-2 fields as Summary fields and/or 1-2 fields as Calendar Summary fields

1. In your Event Form set the most important fields (8-10 fields from your form) as default show in tables, and set ALL other field to default show in tables=false. You can also set 1-2 fields as Summary fields and/or 1-2 fields as Calendar Summary fields

2. For EACH field/question set up as much detail as possible: e.g. higher values are best, format:0.00, default values, row width and ALWAYS abbreviate long field names

2. For EACH field/question set up as much detail as possible: e.g. higher values are best, format:0.00, default values, row width and ALWAYS abbreviate long field names

The more detail you give each field the better you are able to use the system and enhance a users ability to rapidly interpret the data and use the system features like ranking on the reports, the performance summary dashboards, the performance standards etc.

3. Set up the Sections properties: If setting up visibility filters speeds up data entry then hide questions that are not needed. Think about what section layout settings you can use to take up less room and have it clearer on the page

3. Set up the Sections properties: If setting up visibility filters speeds up data entry then hide questions that are not needed. Think about what section layout settings you can use to take up less room and have it clearer on the page

Always check that the question fields and the sections take up the least amount of space. Always try and optimise:

-question size

-space- can you fit in a 1-2 column layout for the questions in that section. Are you text fields the correct size

-visibility- if you can hide questions or entire section  that do  not need answering until other fields are entered set these up

What is the optimal Section layout.. small with tool tip,  or large or vertically aligned?

4. Set up the Form Properties: Do you need to print, lock etc?

4. Set up the Form Properties: Do you need to print, lock etc?

Go to the Form Properties and ensure that the buttons at the bottom of the event page, fit with the type of data you are entering.

If you are entering a strength and conditioning session, you would have save as draft, and save and close.

If you are entering speed tests, you would have save and enter another to quickly enter data for one player and then enter for another athlete

If you are entering medical data, you would usually only have save and lock and save and close. This would be lockable only after all of the required fields are entered, or a specific status (e.g availability) is met.

5. Preview what you have created using the Preview button

5. Preview what you have created using the Preview button

Always do a preview and check the calculations, table calculations, visibility settings, questions, number formats, max and min values etc.

6. Give permission on the Administration site to the event or profile form (and any other forms or database that link into that form)

6. Give permission on the Administration site to the event or profile form (and any other forms or database that link into that form)

7. Go to the Application site and Enter in new data into that event/profile. Check that the fields appear correctly, are they off the side of the page, are they spelled correctly. Have you given yourself all of the necessary permissions?

The example here shows that lower values are best has not been set for weight as there is no red arrow on the right of the page showing an increase.

The database hasn't been given access to the user on the Admin site for the medication database.

Some of the fields haven't been hidden.

Remember, it is always critical to test the form out by entering and then SAVING the data to see how it performs on the data entry page, AND on the athlete history page (in the step below).

8. Look at the athlete history, sidebar, calendar AND recent entries page to see how the data is displayed. Are the abbreviations OK, are the column widths optimal?

8. Look at the athlete history, sidebar, calendar AND recent entries page to see how the data is displayed. Are the abbreviations OK, are the column widths optimal?

This image here shows that there are too many fields set as summary fields (and the ones showing are not the most critical). There are also too many fields showing in the athlete history table for that form and they are not important fields -e.g. date of entry, age at monitoring should be hidden (as shown in step 10 below). These need to be reset again to default show in table = false and summary field =false on the builder in the event form builder.

9. To test your form also Run a Summary Report, set up a Report on the Reports page with some filters, and also Check that Excel Reports/Report templates can be adhered to using the current form structure

9. To test your form also Run a Summary Report, set up a Report on the Reports page with some filters, and also Check that Excel Reports/Report templates can be adhered to using the current form structure

Depending on the modules that you have access to and are going to use the data in, always enter in 2-3 entries for an event using the enter data button and then test out how the system responds. Use the performance summary dashboards, the reports, the profiles etc to ensure the correct fields are being pulled through.

The example here shows that the correct fields are being pulled through into the Performance Profile Report.  

10. Make any necessary changes back on the builder and then run through step 1-9 again.. Spending time getting it right will save time later on and ensure users can track, access and actually use their data well.

10. Make any necessary changes back on the builder and then run through step 1-9 again.. Spending time getting it right will save time later on and ensure users can track, access and actually use their data well.

An event form that is optimised for users, and an athlete history page, sidebar that are all set up correctly, significantly improve the way data is entered, viewed and interpreted. Your responsibility as a builder is to create Event forms and Profile forms and to set up the fields and field properties to ensure you capture the data that is required, and most importantly, enable users to rapidly compare, interpret and use the data to improve performance.

0 Comments

Add your comment

E-Mail me when someone replies to this comment