1 of 11

QA Platform Virtual Tour

Jointly prepared by PCU, PPU and D&D unit

20 November 2023

2 of 11

Objectives & content

Agenda

www.cgiar.org

QA Process Recap

It is important to increase early submission for QA batch 1 to avoid the January rush – deadline Nov 6
It is especially important to submit and QA Innovation Development that will be used to report Innovation packages (IPSR pathways only) in 2023.

www.cgiar.org

QA process: main steps and timeline

The lead assessor makes sure to leave only one comment per field.

IDTs have final responsibility for the data on regular fields – there is no further exchange/discussion with assessors on those fields

Data submission deadline are intended EoBD time

We are here

www.cgiar.org

QA Status of Comments to Initiatives

Deadline is Wednesday, �22 November COB

If this is not feasible, �please send a message to: performanceandresults@cgiar.org

Prioritize comments on �“access to evidence” �to complete the QA process.�If not done, it will go to 3rd Party.

www.cgiar.org

Change Result Type

If QA Feedback advises to change the result type, you may now this without deleting and creating a new result.

NEW

RELEASE NOTES

www.cgiar.org

Contributors

Many Initiatives did not “Map and accept” results as a “contributor” to a result submitted by another Initiative.
“Small window” to do this from now through 22 November COB.
Suggested process if you are pending “acceptance” by other Initiatives

www.cgiar.org

Results that are currently under QA are not all automatically unsubmitted in the PRMS.
An initiative has to unsubmit each result where a change in PRMS needs to be done.
Then, as the change is implemented, the Initiative has to resubmit the result.
This means that if an Initiative disagree on a comment, it has only to leave the justification for disagreement and not do anything in the status of the result itself. Only submit to go to complete the QA process.
For KP: if a change to the result needs to be done, the Initiative should ask CGspace management to implement the change. It also has to unsubmit the result to then click on the re-sync button once the change is implemented in CGSpace.
Also, for KP, the Initiative needs to unsubmit the result to implement changes that relate direclty to data included in the PRMS, for examples AI tags.