�Technical Reporting Info Session #2� Reporting on Outputs

Portfolio Performance Unit (PPU)

23 September 2025

Objective and content

Objective:

• Provide information on output-level reporting

​

Content:

• Big picture: CGIAR Results Framework, tech reporting deliverables, timeline and products
• Outputs
• Knowledge Products
• Capacity sharing for development
• Innovation development
• Available Resources

Overview: Technical Report Deliverables and Products

*Progressively integrate results from W3 and Bilateral projects mapped to SP/A, ensuring alignment with minimum data standards.

​

Results Dashboard

• Enhanced version to better present curated information against Impact Area targets, geographies and key topics.
• Will include user-driven AI features such as natural language questions & answers with verifiable results.

SP/A annual technical report

• Provide assurance on annual SP/A delivery against the PORB and demonstrate measurable progress on the TOC.
• V0 draft available - serving as a starting point for SP/A to refine, enhance, and finalize their annual report.

Portfolio Narrative

• Provides assurance on Portfolio coherence, results including delivery against Portfolio outcome-level geographic/thematic targets, partnerships, country and regional engagement, and synergies among the Portfolio’s constituent parts.

Reporting against the CGIAR Results Framework

Impact

​

​

​

Program/Accelerator outcomes

​

​

Program/Accelerator outputs

Common data fields for outputs

• Title (max 30 words).
• Description (max 150 words).
• Impact area scores (for all 5 Impact Areas), with evidence and a component-level breakdown whenever a score of 2 is assigned.
• TOC alignment.
• Internal contributors: CGIAR Centers, w3/bilateral projects, other SP/A.
• External partners.
• Geographic location.
• Evidence* .

​

* No evidence is required for capacity sharing for development results due to the time/resource burden and potential unresolved General Data Protection Regulation (GDPR) issues. By submitting a capacity sharing for development result it is understood that you have evidence to support the result submission, and that should a sample be required this evidence could be made available.

For KP, the evidence is the CGSpace link.

​

Knowledge Products (1/2)

• Definition: A knowledge product (KP) is defined by the CGIAR Open and FAIR Data Assets Policy using the term “data asset”. Knowledge products are intellectual assets generated from research and development activities such as articles, briefs, reports, extension and training content, databases, software, and multimedia elements that contribute to behavioral changes in particular actors. 
• For reporting, users should only consider knowledge products that are integral to the Program/Accelerator ToC. Knowledge products within a ToC are meant for use by Program/Accelerator actors (e.g., a policy brief produced as an Initiative’s output to support a policymaker’s action).
• Knowledge products in multiple languages should not be reported separately, unless necessary to evidence the ToC (for example if pathways are differentiated for actors, or geography/geographic scope, requiring the output in different languages). 
• To be eligible for reporting, a knowledge product should be a finalized product (also, see guidance on preprints).
• It should be stored in CGSpace, following a typology set by the CGSpace community, as outlined in the CGCore and international standards.

Knowledge Products (2/2)

Metadata retrieved from CGSpace once KP link added to PRMS 🡺

​

​

Additional resources on KP reporting:

CGIAR Open and FAIR Data Assets Policy

CG Core metadata schema

Guidelines for dealing with predatory publishers/publishing

Guidance on knowledge products.docx - Google Docs

CGSpace Curators by Center.xlsx

​

Capacity Sharing for Development

Indicator: Number of people trained by CGIAR, with aim of leading to changes on knowledge, attitude, skills and practice, i.e. behavior.

Common exclusions:

• Conference sessions
• Meetings
• Webinars
• Internal trainings

​

Would the attendee agree they were being trained?

​

Engagement Activities

There has been a long-term discussion about including a new, non-mandatory category in the reporting system to cover engagement activities. We propose to put this to a vote – link to poll – which will close on 26th September.

For

• P&As spend a lot of time and effort building relationships with partners
• Partner engagement is key to achieve outcomes
• There is not an adequate way to report on engagement until it has led to an output or outcome
• The "other output" and "other outcome" categories are somewhat misused for this purpose
• Could improve internal partner intelligence –who is working with who

Against

• Other reporting categories all focus on results whereas this would focus on activities
• This could encourage overly granular reporting
• There is already a lot of reporting – would this add to bloat or efficiency?
• Much of the evidence would probably have to stay internal, therefore there would be little external benefit in reporting to donors

Innovation Development: Why standardized innovation reporting?

Evidence-based trend data on hundreds of innovations

• Prioritization
• Coherence
• Learning
• Strategic partnerships
• Resource mobilization

• Duplication
• Poor evidence-base
• No trend data
• Not mapped to ToCs/ impact pathway

​

Next

Innovation Development Reporting

• Innovations: New, improved or adapted outputs or groups of outputs such as products, technologies, services and institutional arrangements with high potential to contribute to positive impacts when used at scale (source: MELCoP Glossary)

​

• Two types of innovation reporting
• Innovations under development (from idea to proven)
• Output level reporting
• Innovations in use (from CGIAR to partners to end-users)
• Outcome level reporting (Non-IPSR Pathway and IPSR Pathway )
• Three options:
• Report new innovation
• Update existing innovation (mandatory)-Inactive/ Active + updates
• Activate innovations that were reported as inactive or discontinued

​

• Prompts to reduce the number of innovation reports that are not updated from previous reporting cycles

�

Innovation Development Reporting

​

New or already documented in CGIAR Innovation Dashboard

• Short innovation name (10 words)
• Innovation Team
• Reference materials (websites, other sources of information)
• Innovation type/characteristics
• Demand of anticipated innovation user
• Global megatrends the innovation is expected to contribute
• Responsible innovation
• Intellectual Property
• Innovation Readiness +narrative+ evidence
• Innovation investment

�

Innovation Development reporting

Changes

• Capture and report information on innovation bundles not just packages – we ask if innovation is linked or bundled with another CGIAR innovation under dev.t or use or other indicator categories or results reported in PRMS
• USD data field to capture investment (past, next and USD to impact) is now mandatory
• Collect impact sizing data (e.g., geo expansion potential - what other regions, commodities, countries) – when currently not global focused
• Intellectual Property – Private sector involvement/co-investment – research, development, scaling
• Responsible innovation
• New question on involving stakeholders in critically examining the assumptions and intended purpose of the innovation.
• New questions on legitimacy and fit of partners, policies, and safeguards to ensure that the benefits of the innovation are sustained and equitably shared.

​

​

Innovation Development Reporting – Output Level

FAQs

• What innovations should we be reporting?
• The full spectrum that are being developed with partners 
• From brilliant ideas to proven solutions to reflect a healthy Initiative portfolio
• What about new and improved varieties/ breeding lines?
• Focus on characteristics and traits (e.g. drought tolerant maize for southern Africa)
• Individual varieties and lines are reporting to GI-specific tools
• What type of evidence is needed?
• Research papers BUT also reports, protocols, concept notes, etc. (preferably public access)
• What if innovation readiness levels differs across geoscope?
• Provide the evidence source that justifies the highest readiness level for countries indicated
• What’s in it for us?
• Basic profile report, inclusion in annual technical reports, in the Portfolio Narrative report, in the CGIAR annual corporate report and in the Results Dashboards.

​

​

​

​

​

PRMS Reporting Tool

• PRMS REPORTING TOOL
• PRMS roles
• PRMS Reporting-2025 data fields and guidance.xlsx

​

Technical Reporting resources

The P&R hub: your One-Stop Shop for Technical Reporting and MELIA information.

​

​

​

​

� 

​

​

​

​

​

​

Questions or suggestions? Email us at performanceandresults@cgiar.org.

• Latest updates

​

• Timeline

​

• FAQ

​

• Guidance documents

​

• Reference documents

​

• Report templates

Thank you!

Useful resources

Performance and Results hub

PRMS Reporting-2025 data fields and guidance.xlsx

Technical Reporting Arrangement 2025-30

Results Dashboard

2024 Technical Reports

​

​

Minimum Data Standards required of W3 and bilateral projects�