Frequently Asked Questions

Workflow is our term for the series steps to create an item or test – from when the author starts writing, through the stages of review and editing, to final approval.

Controlling your working processes is at the heart of good test development, and GradeMaker offers powerful workflow tools to help you do this – and makes it easy to do.

Workflows typically comprise three types of activity, sometimes repeated more than once:

1. Setting – this is the author who might be originating the content or making corrections.
2. Reviewing> – reviewers comment and make recommendations. They can’t make changes.
3. Approving – approvers can edit and correct items, and send them on to new steps

Once items or tests are ready, workflow may then send them in different directions, for example to:

• Pre-test – so items can be trialled for final approval and item banking
• Item bank – for items which are approved
• Typesetting – for papers which are ready for final layout
• Exam ready – for papers which are ready for print or delivery online
• Archive – for materials which are going direct to the library of ‘used’ exam materials

To find out more, watch this 5 minute demonstration on the advanced workflow tools we provide to streamline your assessment authoring.

GradeMaker supports

• MCQs (single or multiple correct response, vertical or horizontal layout, option for marks per correct/incorrect answer, multiple layout variants)
• short response (multiple layout variants)
• extended response
• fill-in-the-blanks (lines, boxes, free text, drop down list)
• drag-and-drop
• matching (associate two lists, multiple correct answers)
• software programming
• composite (items comprising many parts and sub-parts)
• equation and file upload – and many others! 

Mark scheme templates are generated automatically including for item parts/sub parts. ’Content blocks’ can be added to items to carry stimulus or rubric material and assets.

GradeMaker Pro software is designed to make the reviewer’s job easy, whether they are a frequent, or infrequent system user.

Reviewers can enter comments against the item including ‘inline’ (comments linked to a specific word). They can also ‘target’ comments and make them ‘mandatory’ so later users must acknowledge their remarks. Review comments are linked to the review cycle. A useful downloadable review history is available for items and tests. If several reviewers work concurrently, their comments are automatically compiled to one view making it easy to hold QPEC meetings for group discussion of reviews.

All review comments are held for quality assurance and easy access in the Notes & Actions hub attached to each item and paper. Users can easily search for review comments (e.g. ‘comments targeted to me, actions I have requested).

Quality Assurance forms can also be created and attached to a paper review cycle, so reviewers can receive a structured document to lodge comments (e.g. for test review). QA form questions can be set to be mandatory or optional.

Item or test templates can be created by administrative users which can then be assigned to an item writer. These templates can be used to pre-define as much of the structure of the item as is required (e.g. item type(s) used, number of answer options, marks available or any other item metadata) before they are allocated to a writer so that they can focus solely upon the authoring of question content.

Yes. You can write content into the software in any language, including Chinese and Arabic.

It’s simple! We work together through a 7 stage process, dependant on your requirements.

Stage 1: Project setup – in this first phase we work with your project team to identify and document project goals, governance approach and the risk and issue management processes.

Stage 2: Discovery – through a series of workshops the key elements of your current/desired content production operating model are documented and mapped to the key areas of the system.

Stage 3: Configuration – once the Discovery phase is complete we carry out initial site configuration and demonstrate this to the project team and key system users for feedback.

Stage 4: Validation – once the target configuration has been accepted by the customer team there is then a period of internal validation/acceptance testing to allow for a full test of the system.

Stage 5: Training – this stage can follow one of two models:

• Train-the-trainer: key users and internal ‘champions’ are identified and are provided with full training by GradeMaker on the agreed configuration of the system. A full set of support materials (user guides, how-to videos, one-page guides) are also provided and can then be customised by the customer team.
• Full user training: GradeMaker provide expert in-house trainers and undertake the customisation of all support materials on behalf of the customer. This training can be provided on-site or online/virtually as required.

Stage 6: Go-live – This can be either mean moving all the your assessment authoring into GradeMaker at once, or through a series of smaller, incremental phases of migration.

Stage 7: Support — Once your team are using the product live,  we continue to support you and as we develop new features that will benefit you, we get together regularly to update you!