5Step 5 of 6
Review and approve submissions in QB-EDGE™
Every submission passes through a person.
Reviewing is the fifth step in QB-EDGE™ by Generation Impact Global (GIG). The team that sent the questionnaire reads each submission, then approves it or sends it back with notes. QB-EDGE™ keeps a history log of every round.
Explore QB-EDGE™
At a glance
2
outcomes
Approve, or reject with notes.
4,000
characters per correction note, at most
Room to say exactly what to fix.
1
history log per respondent
Every status step, newest first.
Email
to the respondent
Sent after an approval and after a rejection.
What happens when a submission arrives?
You read it, then choose one of two outcomes: approve or reject.
- Approve. Add a message if you wish.
- Reject. Add an overall message, flag single questions, or both.
- Either way, the respondent gets an email.
Approving a submission
How do I ask for a correction?
Flag the questions that need work, and add a note to each.
- Flag. Mark the question.
- Explain. Write a note, up to 4,000 characters.
- Send back. Reject the submission with your flags.
- Receive. The respondent sees the flagged questions and your notes, and sends a corrected version.
Say which question. Say why. Send it back.
To question a KPI, flag it and the flag lands on the questions behind it.
What does the history log record?
The history log lists every status step for one respondent, newest first, including each submission, approval and rejection.
For each rejection round, it also lists the questions you flagged.
Sample, as an example:
| Round | Event | Detail |
|---|---|---|
| 2 | Approval | |
| 2 | Submission | |
| 1 | Rejection | 2 questions flagged |
| 1 | Submission |
The history log
What else can a reviewer do?
A reviewer has four more tools besides approve and reject.
| Tool | What it does |
|---|---|
| Opinions | Record an opinion on a question or an answer |
| Verify | An admin marks an answer as verified |
| Version history | See how an answer changed, and who or what changed it, including VitAI™ |
| Excel | Export one respondent’s answers from the overview |

What changes once I approve?
An approved questionnaire counts in the Benchmark averages.
Before approval
Not in the Benchmark averages
The respondent sees no Benchmark
After approval
Included in the averages
The respondent can see its own Benchmark, if you switched visibility on
“Only questionnaires accepted by you are included in the averages.”
The next step is to analyse and export.
Worked example
Example. The supplier, the questions and the notes are invented.
A reviewer reads the first submission from Demo supplier B (example) and finds two problems.
| Question | Answer given | Reviewer’s note |
|---|---|---|
| Total electricity used | 6,000 MWh | “Last year you reported 620 MWh. Please check the figure and the unit.” |
| Do you have an energy policy? | Yes, no file attached | “Please attach the policy as evidence.” |
What happens next:
- The reviewer rejects the submission with the two flags.
- Demo supplier B gets an email and sees the two notes on the two questions.
- The supplier corrects the figure to 600 MWh, attaches the policy and submits again.
- The reviewer approves. The history log now shows every step of both rounds.
Good to know
- No comment threads. QB-EDGE™ has no comments on answers. Use correction notes and reviewer opinions.
- A KPI flag goes to its source questions. There is no separate request at KPI level. Values from the previous period cannot be flagged.
- The judgement is yours. QB-EDGE™ records the approval or the rejection. It does not decide for you.
Questions about reviewing submissions in QB-EDGE™
What can a reviewer do with a submission in QB-EDGE™?
In QB-EDGE™ a reviewer approves a submission or rejects it. A rejection can carry an overall message, flagged questions with notes, or both. The respondent is emailed either way.
Can I send back only the questions that need work?
Yes. In QB-EDGE™ you flag single questions and add a note of up to 4,000 characters to each. The respondent sees the flagged questions and your notes.
How does the respondent find out about a correction request?
QB-EDGE™ emails the respondent. In the questionnaire, the respondent sees which questions were flagged and reads the note on each one.
What does the history log in QB-EDGE™ show?
The history log in QB-EDGE™ lists each submission, approval and rejection for one respondent. For each rejection round it also lists the questions that were flagged.
Can reviewers comment on answers?
Not with comment threads. QB-EDGE™ uses correction notes on flagged questions, and reviewers can record opinions on questions and answers. Some features depend on your plan.
Open a free account, or ask us for a walk-through.
Some features depend on your plan. See pricing.
Stay up to date
Keep up with changes on policies, legislations and technologies.
Read more: European Banking Authority Backs NGFS Energy Transition Declaration at COP31European Banking Authority Backs NGFS Energy Transition Declaration at COP31
Read more: SEC Proposes Principles-Based Executive Compensation Disclosure ReformsSEC Proposes Principles-Based Executive Compensation Disclosure Reforms
Read more: European Commission opens consultation on limited assurance standards for sustainability reportingEuropean Commission opens consultation on limited assurance standards for sustainability reporting
