Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/AllianceBioversityCIAT/onecgiar_pr/llms.txt

Use this file to discover all available pages before exploring further.

This guide walks you through the end-to-end journey of creating a result in PRMS and submitting it for quality assurance review. It covers the steps a result submitter (Initiative or Center staff) follows during an open reporting phase. By the end you will have a result in Quality Assessed status, ready for a reviewer to assess.
Your PRMS account is provisioned through your organization’s Active Directory and AWS Cognito. If you cannot log in, contact your platform admin — PRMS does not manage identity provisioning directly.

​
Create and submit a result

1

Log in

Open the PRMS web application in your browser. You will be redirected to the Cognito-backed login page. Enter your organizational credentials and complete any multi-factor authentication required by your organization.After authentication, PRMS redirects you to the Home dashboard for the current reporting phase. The dashboard shows submission progress across initiatives and surfaces results that need your attention.
2

Navigate to the results list

In the left navigation, select Results. The results list shows all results you have access to for the current reporting phase — results belonging to your initiative, results shared with you, and any you have created.Use the filters at the top of the list to narrow by result type, status, or initiative. The status column shows where each result sits in the workflow: Editing, Quality Assessed, or Submitted.
3

Create a new result

Click Create result in the top-right area of the results list. A creation dialog appears asking for two required choices:
  • Result type — select from the 11 canonical types (e.g., Knowledge product, Capacity sharing for development, Innovation development, Policy change). The type you select determines which type-specific section appears on the result detail form.
  • Reporting phase — confirm the active phase. Normally this is pre-selected to the current open phase.
After confirming, PRMS creates the result with status = Editing and opens the result detail form.
4

Fill the common fields

The top section of the result detail form captures fields shared by all result types. These are required before you can submit for QA.
Enter a clear, specific title for your result. The title should describe what the result is, not the activity that produced it. A concise description helps QA reviewers and bilateral consumers understand the result at a glance.
Link your result to one or more Theory of Change outcomes. Click Add ToC alignment to search outcomes from the ToC service connected to your initiative. At least one alignment row is required before submission for most result types.
Specify where the result occurred. You can select countries, regions, or sub-national areas. Results with global or cross-regional scope can be marked accordingly.
Add at least one contributing center and mark one as the lead center. You can also add partner institutions from the CLARISA catalog. At least one lead center is required for submission.
Attach one or more evidence rows. Each row includes an evidence type, a link or reference, and an optional description. Evidence can point to documents in SharePoint, CGSpace handles (for knowledge products), or external URLs. Required evidence varies by result type.
Cross-cutting scores (gender, nutrition, climate, environment) and impact-area indicators appear in the scoring section. Fill these in accordance with your initiative’s reporting guidance.
5

Fill the type-specific section

Below the common fields, the form shows a section specific to your result type. Examples:
  • Knowledge product — enter the CGSpace handle, journal or publication details, and FAIR baseline indicators. PRMS calls the MQAP service to pre-fill some attributes automatically.
  • Capacity sharing for development — select delivery method (e.g., long-term training, workshop), term length, number of participants, and whether the capacity building was delivered on behalf of another institution.
  • Innovation development — describe the innovation, its readiness level, and link it to any related innovation use results or scaling studies.
  • Policy change — select the policy type and stage from the CLARISA-backed catalogs, then answer the structured “Is this result related to” questions.
  • IPSR (innovation package) — map the result to pathway steps and link complementary innovations.
Save your work frequently using the Save button. PRMS also autosaves while you type, but an explicit save confirms your changes are persisted.
6

Request QA review

When all required fields are complete and the form shows no validation errors, click Submit for QA. PRMS runs server-side validation before accepting the request:
  • At least one ToC alignment row (where required by type).
  • At least one evidence row (where required by type).
  • At least one contributing center marked as lead.
  • All type-specific required fields populated.
If validation passes, the result status changes to Quality Assessed and the QA reviewer is notified via in-app notification and email, depending on their notification settings.

​
What happens after you submit

Once the result is in Quality Assessed status, a QA reviewer opens it in the review drawer and assesses the fields, evidence, and ToC alignment. Two outcomes are possible:
  • Advanced to Submitted — the reviewer confirms the result meets quality criteria. The result moves to status 3 (Submitted) and is locked for the reporting cycle.
  • Returned to Editing — the reviewer adds structured comments tied to specific fields and sends the result back.
When your result is returned, open the Review history tab on the result detail page to see every reviewer comment organized by field. Address each comment, update the relevant fields, and click Submit for QA again. Multiple review rounds are normal — the history gives you a clear record of what changed.

​
Sharing a result with collaborators

If another Initiative or Center team contributed to the result and needs editing access, use the Share / request access function on the result detail page. The receiving team member gets a notification and, once they accept, can view and edit the result alongside you.

​
Authentication note

The PRMS Angular client automatically attaches a custom auth: <JWT> header on every API request via its HTTP interceptor. You do not need to manage tokens manually. If your session expires, the app will prompt you to log in again.The header name is auth, not the standard Authorization: Bearer format. This is intentional by design and applies to all authenticated PRMS endpoints. The /api/bilateral/* and /api/platform-report/* endpoints are the only routes that do not require this header — they are protected at the network perimeter instead.

Build docs developers (and LLMs) love

Get started for freeTalk to us