RQAMESG Tech platformAcceptance testing 5 to 9 October 2026
Approval workflow acceptance test plan
Test page · v2.1 · 29 September 2026
The nineteen cases from the acceptance test plan, under the ids Andrew has held
since 8 September 2026, with the steps rewritten on 18 September 2026 for the rebuilt screens. The
page records your results as you go. Run the cases for your role, mark each one, and tell us
anything that does not match how RQAM actually works.
Prepared forRQAM
Your casesTen or nine
Expected effortHalf a day at most
Testing week5 to 9 October 2026
0 of 19 recorded0 passed0 failed0 blocked
How to use this page
The case ids here are the ones in the plan Andrew sent you on 8 September 2026. The steps and
expected results were rewritten on 18 September 2026, because the screens were rebuilt after the
10 September walkthrough, so follow this page rather than the earlier PDF. R10 and M3 were
revised again on 29 September to match the screens as fixed. Each case gives
you the steps and what should happen. Mark it Pass, Fail or Blocked,
and add a note wherever the result was anything other than a clean pass. Your answers are
saved in this browser as you go, so you can close the page and come back to it.
When you are finished, press Finish at the top. That builds a plain-text summary you
can copy straight into an email to Jason.
Which cases are yours
Data Reporters. R1 to R10. Run R1 to R7 first, then wait for your Manager.
Data Managers. M1 to M9, once two packages are waiting for you.
Everyone. Only your own entity's data points, and only your own pair.
What to record
Pass. It did what the case said it would.
Fail. It did something else. Please say what you saw.
Blocked. You could not run it. Please say why.
Judgement is welcome. A case can pass exactly as written and
still not suit how RQAM works. If so, mark it Pass and say what you would change. That
feedback is as useful to us as a defect.
Who is testing
These three answers go at the top of your summary,
so we know whose results we are reading. They are saved in this browser with everything
else.
The words on screen
A figure under review is a data point. A set of data points sent for approval is a
package. The person sending it is a Reporter and the person deciding is a
Manager. My packages is where a Reporter sees their packages, New
package is where they build one, and To review is where a Manager finds what is
waiting for them.
Not in this build, so please do not test for it: email notifications, Excel import or
export, the percentage change against the previous period, and secondary cover for a
Manager on leave.
Before you start
Open the activation email from the platform in a browser where you are not signed in to
anything else, and set your password. After that the test environment is at
https://app-dev.v2.nonprod-esgtech.co.
Use a normal browser window rather than a private one, so your progress on this page is
saved. Keep the same browser and the same machine for the whole week.
You need nothing else set up. ESG Tech has already created every account, permission and
business area, and loaded the GRI framework.
Know which of the two roles you hold, and who your pair is. Data Reporters send, and
their Data Manager approves or returns.
Nothing here touches RQAM's live reporting. This is a separate
test environment. Send, return and resubmit as freely as you like, and do not worry about
making a mess.
The figures are invented. Every figure loaded into this environment
was made up for testing and recorded under Jason D'Souza's name, so you will see him as the
person who recorded data he did not collect. None of it is RQAM data and none of it moves to
production. Judge the workflow, not the numbers.
R
Test cases for Data Reporters
Data Reporter·About 1 hour 30 minutes·10 cases
0 / 10
You assemble a package of data points for your own entity and send it to your Data Manager. Run R1 to R7 first, because your Manager needs your packages under To review before they can test anything. Come back for R8 to R10 once they have made their decisions.
R1
Find My packages in the sidebar
Steps
Sign in and look at the left sidebar.
What should happen
My packages appears in the sidebar. Once a Manager has returned something to you, a count appears beside it. Open it and the page reads Nothing waiting on you, with a New package button in the header.
R2
Choose a business area and period
Steps
Click New package.
Choose your business area.
Choose a reporting period from the list.
What should happen
The period list offers only periods that already have data. The table then lists the data points for that period, filtered to Assigned to me, with columns for the indicator, value, who recorded it and when, evidence and status. A switch shows All in your business area instead.
R3
Select data points
Steps
Tick the header checkbox to select everything.
Untick one row.
What should happen
The side card reads N data points, the business area and the period, and the count follows your selection.
R4
Due date, reason and note
Steps
Look at the due date in the side card.
Click Change and pick another date.
Type a short note to your Manager.
What should happen
The due date is pre-filled 14 days from today. Changing it reveals a reason box, which your Manager will see. The note is optional and your Manager will see it too.
R5
Send the package
Steps
Choose your Manager under Send to.
Click Submit.
Read the confirmation.
Confirm.
What should happen
Send to lists the Managers for your business area by name. The confirmation names the number of data points, the Manager you chose and the due date. You then land on the package page with status Under review.
R6
Data points under review are blocked
Steps
Open New package again.
Choose the same business area and period.
What should happen
The data points you sent are greyed out, read Under review and name the package holding them. They cannot be ticked.
R7
Send a second package
Steps
Build and send a second package of at least three different data points to the same Manager.
What should happen
It appears in My packages as Under review. Your Manager uses this package for the return cases.
Note. Tell your Data Manager once this is done. They cannot start until both packages are waiting for them.
Pause here
Your Manager runs M1 to M8 now. Wait until they tell you they have approved the first package and returned a data point from the second, then carry on with R8 to R10.
R8
See the approved outcome
Steps
After your Manager has approved the first package, open it from My packages.
What should happen
Status reads Approved. The timeline shows when it was sent and when it was decided, and by whom. Every row reads Approved, with your Manager's name and the date.
R9
See what came back
Steps
After your Manager has returned one data point from the second package, open My packages.
Open the second package.
What should happen
The strip at the top reads 1 data point returned to you and the same count sits beside My packages in the sidebar. The package reads 1 of N returned. The returned row carries your Manager's comment beneath it and a Fix link. The other rows read Approved. A Resubmit button is offered.
R10
Fix, correct and resubmit
Steps
Click Fix on the returned row.
Click × to close the editor, then look at the cell before you change it.
Click the cell, then the … button beside the value, enter the corrected value, attach the evidence file again and save.
Open Data Collection from the menu and read the banner at the top.
Go back to the package and click Resubmit.
Send the new package.
What should happen
Fix opens Data Collection at that data point with the cell ready to edit. Before the correction, the cell reads Returned and your Manager's comment shows when you hover over it. Once the corrected value is saved, the Returned marker leaves the cell, because the new value is not in a package yet. The Data Collection page carries a banner that counts the data points returned to you, and the count stays until you resubmit. Resubmit opens New package with only the returned data point selected, showing the corrected value and its evidence. The new package sends normally, reads Under review and says Resubmission of with a link to the earlier package. The earlier package now reads Replaced.
Note. Tell your Data Manager once this is done, so they can run M9.
M
Test cases for Data Managers
Data Manager·About 1 hour·9 cases
0 / 9
You approve the data points your Reporter sends, or return individual data points with a comment so they can be corrected and sent again.
Before you start this section. Wait until your Reporter has completed R1 to R7, so that two packages are waiting for you.
M1
Find the packages waiting for you
Steps
Sign in and open To review.
What should happen
The strip reads 2 packages waiting for you and the same count sits beside To review in the sidebar. The Waiting for you tab lists both packages with who sent them, when, the due date as Due in N days, and the number of data points. Two more tabs sit beside it, Also in your business area and Decided.
M2
Open the first package
Steps
Click the first package.
What should happen
The header names the package, its status, who sent it and when, that it was sent to you, the due date, and any note your Reporter wrote. A line under the header asks you to check each data point against its evidence and the previous period. Each row shows the indicator, the value, the previous period's value, who recorded it and when, the evidence file names, and Approve and Return buttons. The bar at the foot reads 0 approved, 0 returned, N undecided.
M3
Approve the whole package
Steps
Click Approve all remaining.
Read the bar and the main button.
Click the main button and confirm.
What should happen
The bar reads N approved, 0 returned, 0 undecided and the main button reads Approve all N. The confirmation restates the count. After you confirm, you are back on To review and the package has left Waiting for you and appears under Decided.
M4
Return one data point
Steps
Open the second package.
Click Return on one row.
What should happen
A comment field opens on that row with a Save button. The other rows are unchanged.
M5
A comment is required to return
Steps
Leave the comment empty and try to save.
What should happen
Save is not available until a comment is typed.
M6
Return with a comment
Steps
Type a realistic query, for example Value looks high, please check the meter reading.
Save.
What should happen
The row reads Returned with your comment beneath it and a Change link. The bar reads 0 approved, 1 returned and the rest undecided. The main button stays unavailable while anything is undecided.
M7
Approve a single data point
Steps
Click Approve on a second row.
What should happen
That row reads Approved while the returned row still reads Returned. The bar reads 1 approved, 1 returned and the rest undecided.
M8
File the decisions
Steps
Click Approve all remaining.
Read the main button.
Click it and confirm.
What should happen
The main button names exactly what it will file, for example Approve 2, return 1. The confirmation restates the counts and says your Reporter will see every comment. After you confirm, the package has left Waiting for you. Let your Reporter know, so they can run R9 and R10.
M9
The earlier package is kept
Steps
After your Reporter has resubmitted (R10), open To review and open the new package.
What should happen
The new package is marked Resubmission under Waiting for you. Its header reads Resubmission of with a link to the earlier package and a one-line summary of what was returned and why. The earlier package still exists, reads Replaced, and links forward to the new one. Please confirm this history shows enough for your assurers.
Note. This one asks for your judgement as well as a result. Please answer the assurance question in the note even if the case passes.
!
How to report an issue
As soon as you hit one
Email Jason as soon as you hit a problem rather than saving them up. If
you cannot sign in at all, report that the same way.
Put this in the email
Case id, for example M6
What you did
What you expected
What happened instead
Screenshot
Date and time
What happens then. ESG Tech triages every report daily
during the testing week and replies with one of three answers: fixed, scheduled for the
rectification week of 12 to 16 October, or working as designed with an explanation. Only
the cases that failed are retested, and only by the tester who raised them.
Press Build summary to collect everything you recorded, then send
it to Jason at the end of your testing. Copy it into an email, or print this page if you
would rather send a marked-up copy.