UAT tester scripted end-to-end testing : tight deadline

I'm a solo developer looking for a careful, methodical tester to run scripted,
end-to-end UAT on a web-based, multi-tenant project-management and delivery
platform, ahead of client demos.

It's a sophisticated application, with live customer data already in production —
I'm close to my first formal customer onboarding. It spans a dozen-odd tightly
connected modules (project planning and baselining, delivery, governance and
approvals, variations, cost capture, finance and billing, rate cards, RAID, KPIs
and quality standards, portfolio reporting). Because they're connected, actions
ripple — progressing a deliverable feeds its quality and KPI sign-off, signing off
a milestone triggers billing, and it all rolls up into the reports — so a small
inaccuracy in one place surfaces in the numbers elsewhere. That's why I need
thorough, accurate end-to-end testing.

HOW IT WORKS
I provide the scripts: each section opens with a plain-English explanation of what
it achieves, followed by precise steps. You follow them (or use sensible judgement
from what's on screen), capturing screenshots and logging anything that's wrong or
doesn't work. If you have your own screen-capture and UAT reporting tools, great —
use them; if not, I provide a simple spreadsheet template (one row per issue:
steps to reproduce, expected, actual, screenshot, severity). UX improvement ideas
are welcome but optional. Everything runs in the browser on a staging environment —
logins provided, nothing to install. All testing is on Microsoft Edge, on a
standard Windows PC (no mobile or other-browser testing at this stage).

THE WORK — ONE COMPLETE END-TO-END SCENARIO
You'll take a single project through its full lifecycle:
- Create a project with the setup wizard and correct settings
- Build the plan in a grid — milestones, deliverables and tasks
- Configure financials, build the team from a rate card, and baseline the plan
(with supplier and customer sign-off)
- Run it as if live — progress deliverables, work the approval workflows, assign
and rate KPIs and quality standards
- Sign off milestones against the baseline (supplier delivery sign-off + customer
certification) to trigger billing
- Submit and approve timesheets, expenses and sundries
- Raise variations — time extensions, scope increases/reductions, financial
changes, combinations — each through supplier and customer sign-off
- Do some RAID management, and confirm the reporting and finance views stay
accurate throughout

This first scenario is the full "governed" project type — the most involved, with
sign-offs at every stage — so it means switching between several user roles
(supplier-side PM, customer-side PM, a contributor, and so on); the script tells
you exactly when to switch. As a guide to scope, expect around 12–16 hours of
focused work.

WHO FITS
You don't need to be a project-management expert — the scripts carry the detail —
but experience with project delivery (milestones, deliverables, tasks, change
control, variations) is a real plus. What matters most is that you're observant,
methodical and accurate, and can clearly describe how to reproduce a problem.
Comfort with web apps, data grids and file uploads helps, as does exposure to
tools like Microsoft Planner, Microsoft Project, Monday.com or Wrike.

TIMELINE — THIS FIRST ROUND IS A TIGHT TURNAROUND
I'll send everything you need (scripts, spreadsheets, supporting material) by 11pm
UK time on Monday 8 June, and I need completed results back by 06:00 UK time on
Saturday 13 June. Please only apply if you're confident you can commit dedicated,
focused time across this window.

CONFIDENTIALITY
The platform and its commercial/customer data are sensitive, so I'll ask you to
sign a short NDA before we start and to treat everything you see as strictly
confidential.

ONGOING POTENTIAL
This is the first of several scenarios. If the quality's there, more assignments
follow — the other project types, then ongoing UAT and regression testing on each
release as the product grows. Do well here and there's a real pipeline behind it.

IN YOUR PROPOSAL, PLEASE INCLUDE
- A short note on your relevant testing experience and how you approach UAT
- Confirmation you can hit the Saturday 13 June deadline, and your availability
this week
- Any testing standards, certifications or accreditations, and professional
associations
- The screen-capture / reporting tools you'd use, if any