Review questionnaire responses and export evaluation results

Evaluation results bring together assignments and submitted evidence for project questionnaires and scorecards. Review completion and release version before comparing scores, then inspect the individual answers and supporting artefacts behind a total. Exports are available for different scopes, so label the output with its project, filters and generation time.

In the app: /projects/…/evaluations?tab=results

Before you start

• Confirm which evaluations, vendors, scorers and published versions should be included in the review.

• Resolve missing submissions or document their absence before presenting a ranking as complete.

Step by step

1. Open Results

From Project → Evaluations, open the Results tab or the specific evaluation result. Check submitted, in-progress and missing assignments before reading aggregate values.

2. Inspect individual evidence

Open a vendor or scorer response and review answers, comments and linked artefacts. Distinguish respondent-provided evidence from internal reviewer conclusions.

3. Apply verdicts or review state

Where the RFI workflow supports verdicts, use the agreed outcome after reviewing the evidence. Add a concise reason for exceptions, flags or disputed answers.

4. Compare versions and completeness

Check release version, not-applicable handling and expected scorer count. Do not compare changed questions as though every respondent saw identical content.

5. Export the needed scope

Use per-evaluation CSV for detailed questionnaire work or the project evaluation CSV, XLSX or PDF options for combined results where available. Verify the downloaded headings and included vendors.

6. Protect the output

Name the file with project and date, store it in an approved location and record any filters or exclusions. Re-export after late responses rather than presenting an old file as current.

Evaluation exports may contain confidential vendor evidence and personal reviewer comments. Apply your organisation’s handling policy.

What happens next

• Move from evidence review to Compare only when expected streams and assignments are sufficiently complete.

• Use the vendor response reopen workflow when an authorised correction is required; do not alter submitted evidence in an export.

Troubleshooting

A submitted response is missing from Results

Check the project, evaluation, assignment status and published version, then clear filters. Saved but unsubmitted work is not a completed result.

An export contains different totals from the screen

Compare export time, selected scope, filters, recalculation state and late submissions. Generate a fresh export after confirming the result view.

A vendor response has no reviewer verdict

A submission does not automatically create an internal verdict. Assign or complete the review using the agreed RFI process.