The current test instance has shown identical Active Grants and Total Grants figures for several roles. Treat the Administrator figures as platform-wide and do not use another role's dashboard to confirm assignment scope.

Pending Tasks varies by role in the observed environment. Use it as the role-specific work indicator, then open the relevant workspace to identify the records behind it.

Confirm the form title and tenant-prefixed Form ID. The current library contains test data, so verify that the form belongs to the NICRAT instance before using it.

The New Form action is visible, but the create and save sequence has not yet been verified for documentation.

Those two summary cards rendered as a dash in the observed test instance. Use the grant table and Applications count instead of relying on those cards.

Some status chips are truncated in the current interface. Use the grant's review list and dates for context until the status vocabulary and display are corrected.

No review input or submission control was present in the observed applicant state. Every available applicant was already marked Reviewed, so a pending applicant is still required to verify the submission workflow.

The review listing identifies applicants by Applicant ID. Open the record to see its submitted information.

Status chips were truncated in the observed table. Use the other lifecycle fields for context and avoid acting on a shortened status label.

No. Publish, unpublish, delete, stage and workflow actions can change live grant state and require a separately verified procedure.

The Payments list contains account-holder names and full bank account numbers. Published guide images must use a reviewed redacted derivative.

No. Export, approval, rejection and payment initiation require separate, verified procedures because they expose data or change payment state.

The approval list contains a Grant Type field that is absent from the supplied context brief. Treat the displayed value as interface data until the product owner confirms its meaning.

No. The observed evidence confirms the queue, but not the decision controls or the effect of each decision on the workflow.

Check both Admin Users and Grantees, then switch between Active Users and Inactive Users.

No. Invite User and Manage Role are visible, but their permission and save behavior have not yet been verified.

The observed Analytics & Reporting page returned the same platform-wide figures to PMO Officer and Reviewer accounts. Administrators can treat the figures as platform-wide, but scoped-role use requires a product fix.

Confirm the selected Grant, Start date and End date, and use a period that contains activity for that grant.

The observed PMO dashboard showed Active Grants and Total Grants as platform-wide totals. Use Grants or Applications to confirm the records relevant to your work before acting.

This guide explains how to interpret the dashboard only. Open the relevant workspace and follow a verified task-specific guide before changing a grant, application, payment, or approval request.

The observed PMO session displayed the same 41-grant total seen by the Administrator. Confirm the grant name and your assignment outside this list before using any Action control.

Do not use New Grant or a row Action from this guide. Creation, editing, publishing, deletion, workflow changes, and stage advancement remain authorization-sensitive and unverified.

Use each grant row and its Applications count as the working reference. The observed summary cards displayed a dash rather than a numeric value.

Stop after identifying the relevant grant and application count. Shortlisting, applicant review, comments, scoring, selection, and submission remain unverified.

The live list contains personal and financial information. The guide masks those values while retaining the interface labels and status fields needed for navigation.

Those actions are not covered by this guide. Their PMO permissions, confirmation steps, downstream effects, and data-handling requirements have not been verified.

Confirm that the request has reached your configured approval level. The observed list provides a Pending Requests count but does not establish assignment or sequencing rules.

This guide stops at request discovery. Request details, supporting evidence, decision controls, return-for-updates behavior, and the resulting audit record remain unverified.

Open Review and use the assigned grant and applicant lists as the working record. The observed pending-task count did not correspond to a visible unreviewed applicant.

Use the Review list to confirm your assignments. Those two dashboard values were observed showing the same platform-wide total for multiple roles.

Confirm the grant name and ask an administrator or programme owner to check your reviewer assignment. Unassigned grants are not shown to Reviewers.

That is the observed Reviewer action. Select Details to open the grant's applicant list.

Do not attempt to submit another review. Ask the programme owner to confirm whether an unreviewed applicant should be assigned to you.

Stop before assessing applicants and ask the programme owner for the correct grant-specific guide. The download result still needs product verification.

The list intentionally shows Applicant ID rather than the applicant's name. Open the ID to view the record details.

Application content depends on the form configured for the grant. Review every field shown and confirm the expected sections with the programme owner.

No comment has been recorded on the visible record. The observed screen did not provide a control for adding one.

Stop at inspection and ask the programme owner to provide an unreviewed applicant or confirm the intended submission process. No submission control was visible in the observed Reviewer flow.

Open Payments and Approval Requests to confirm the records available to you. The observed Finance Officer dashboard displayed the same grant totals seen by other internal roles.

Treat the card as a summary only. Use the status columns and Filter controls in the finance workspaces to identify pending work.

Select Filter, narrow the results, and confirm that you are using the correct grant or grantee reference.

Open the action menu and select View Details before approving, rejecting or initiating the payment.

Do not select Approve or Initiated Payments until the amount, beneficiary information and supporting records have been checked.

Select Reject and provide a clear reason so the responsible user can correct the request.

Use Filter and confirm the grant name. If the record still does not appear, contact support with the grant reference.

Review the Current Stage, Status, and Pending Requests columns to prioritize the queue.

Select Request update and state what must be corrected or supplied before the request can be reconsidered.

Select Reject and provide a clear reason that refers to the missing or incorrect requirement.

Review the deadline shown on the grant card or details page. Closed opportunities cannot accept a new application.

Use Contact Support on the grant details page to confirm whether applications are still being accepted.

Open Applications or My Grants and use the detailed list as the current record of your work.

Check Applications for its application status, then contact support with the grant or application reference if it is still missing.

Confirm that Available Grants is selected. The list only showed opportunities currently presented to the signed-in account.

Do not rely on the status label alone. Review the grant details and contact support before entering an application.

Select Previous, enter the value again, and preview once more. During verification, a populated Location field appeared as Nil in Preview; contact support if this continues.

Do not select Submit until each value in Preview is complete and accurate.

Use Next or select another page number at the bottom of the table.

Keep the application ID and grant name available, then contact support for clarification.

Check the activity's start and end dates and refresh the page. The verified record had a past end date and the control did not open a report form.

Turn on Auto Refresh or reload the page. Contact support with the grant and activity name if the status does not change.

Confirm that every required document has been uploaded in an accepted format: PDF, DOCX, JPEG, or PNG.

Do not upload an unrelated file. Contact support or the programme team to confirm the acceptable replacement.

The payment request cannot be completed until an account is configured. Contact support and include the grant reference.

An empty table means no payment request or disbursement is currently recorded for that grant.