We use a lot of words to describe features in Award Force but we recognise it can be confusing if you're unsure what they all mean. This is a glossary of terms to help explain all these words.
The association of an entry with a Score set and a person that will judge the entry is referred to as an assignment. While assignments are automatically created when you create Panels, you can also use Manual assignments or Random assignments to assign specific entries to specific judges.
Attachments are files uploaded in support of an entry. You might refer to them as documents, files, supporting material or similar.
A broadcast is an email which is composed and sent from within Award Force. These can be created throughout the admin area by clicking the Broadcast button at the top right. Read more in Sending an email broadcast.
Categories are used to group entries based on having a like set of entry requirements. Different categories can have different information collected. Judging panels (groups of judges) can be created to judge specific categories.
Chapters are used to manage entries and judging arranged by a distinct classification, such as geographic area. You might have different entry dates by chapter, or a different set of categories. You can assign chapter managers to oversee entries and judges for a particular chapter. You may need to report on entries by chapter. And you can set-up judging panels (groups of judges) to judge specific chapters. Examples of chapters include states, regions, cities, countries, departments, business units and so on.
Chapters are an additional cost. If you'd like to know more or require a quote for chapters, please contact us at firstname.lastname@example.org.
Content blocks are account-specific pieces of text content that can be placed amongst a specific set of content locations around the system. A content block typically provides supporting information for a given view or section of the system, in context. They are called blocks rather than pages, since we don't have manageable pages in Award Force, and blocks appear within part of a view. In some cases, there can be more than one content block in a view.
Content blocks can be created/edited at Content > Content blocks. For information about content block locations please see Content block locations.
Terms are text labels that can be changed. For example, the word 'Entry' is a term which can be changed to 'Application' or 'Submission'. This is done at Content > Terms.
Divisions break a category into smaller groups of entries for judging purposes. This can be useful when there is a large number of submitted entries in one category.
An entrant is a user who submits an entry or nomination for judging.
Entries are what your users create, to be judged. You might also refer to them as nominations, projects or applications for example.
Fields are input areas which are required to build the entry form. There are several options like text areas, dropdowns, radio buttons, country etc. These can be created at Settings > Fields. See Field types
A visually appealing display of all the submitted entries.
The Leaderboard shows the results from judging, whether it be scores, total votes or a decision of pass/fail. The Leaderboard offers several export options.
Notifications are automated messages (email or SMS) sent from Award Force. They include the registration confirmation email and the entry submitted email. These can be customised at Settings > Notifications. See Notifications
A panel defines who judges what and when. Panels are created at Judging > Panels. See Judging panels
Review flow is an automated process which allows individuals or organisations specified on an entry form to be contacted to review an entry. They can be configured at Settings > Review flow. Please refer to the Review flow overview to learn more.
A set of permissions that allows a user to perform specific tasks.
Defines the dates for when entry, judging, and feedback will take place.
Refers to a distinct "collection" of scores, which are formed into a summary table (leader board). Score sets are created at Judging > Score sets. See Score sets: How they work
Scoring criteria are the standards by which entries are judged. Judges input their score into the Scoring criteria which then appear on the Leaderboard as an average score. At least one scoring criterion is required when using the VIP Judging mode. These are created at Judging > Scoring criteria. Read more: Scoring criteria
Season refers to the cycle of an award, very often an annual cycle, but our season feature allows any number of seasons per year. A single season contains all category, entry and judging configuration, and all entry and judging data. When starting a new season, previous season data is archived but still available. Entry and judging configuration can be revised from one season, to the next. Seasons can only be sequential, they cannot overlap.
A slug is a unique identifier for a data record. It's in an eight character alpha-numeric format, such as Sw1if6eY. It differs from the more common name "ID" (also used in the software) which is normally numeric and sequential. Further reference https://en.wikipedia.org/wiki/Slug_(web_publishing)
Tabs provide a visual separation of questions on the entry form. They are created at Settings > Tabs.
Tags are a way to group entries together for a purpose, be it for judging or communication or even just for record keeping. See more about Tagging entries
The colour-scheme and images used by an Award Force program.
A judging mode that allows judges to rank their preferences. Winners are calculated using the single transferable vote (STV) system.
An individual who uses the Award Force system. They can have one or more roles such as entrant, judge, program manager, or guest roles.
Refers to a judging mode where registered judges evaluate entries based on a set of scoring criteria.
A judging mode that allows users to vote for their preferred entries.
Need more help? Get in touch!
We're here to help if you need it. Simply get in touch with our Client Success team through one of the methods available at the base of the page.