Every screen

What is real here, and what is staged

This is a working front end built to show how the portal would look, feel and behave. It has no server behind it. Here is exactly where that line sits, what we assumed from your scope, and what we need from you to go further.

Real

It does what it appears to do, in your browser, every time.

  • One shared set of data48 cases, 9 suppliers. What the importer, the supplier and the reviewer each do is seen by the others. Signing an approval moves the card on every board.
  • The rulesAn approval cannot be signed while a factor is not low risk. A supplier cannot open another supplier's case. A conclusion cannot be made until every factor is confirmed by a person.
  • The ringEvery section is drawn from that case's own stage log: ring widths are days taken, the scar is where the anomaly was found.
  • Every number on a screenCounts, runways, workloads and the volume check are computed from the data, not typed in.
  • FormsValidation, required reasons, file type and size checks, drafts that survive a reload.
  • Four languages in the supplier portalEnglish, Bahasa Indonesia, Tiếng Việt and 简体中文, switched live.
  • SoundSynthesised in the browser, off until you turn it on. No audio files.
  • Works with no internetOpen the folder on a laptop in flight mode and it runs.

Staged

It looks and behaves as the real thing would, but nothing leaves your browser.

  • The assistantIts classifications, extractions, maps, translations and drafts are prepared in advance. No model is called. The human checkpoints around them are real.
  • Database checksFSC, PEFC, SILK and the WeChat QR scan show prepared results, including one that is down.
  • UploadsA file is checked for type and size and then set aside. Any accepted purchase order file screens the same fourteen sample lines.
  • Signing, email and downloadsA signature is recorded in the browser. No document is sent to Adobe, no email goes out, and "Download" describes what you would receive.
  • IntegrationsHubSpot, Xero, SharePoint, Miro, MinuteDock and Teams are shown with status and direction. None is connected.
  • Sign-inAny password and any six digits are accepted. Roles are chosen, not authenticated.
  • The dateIt is always Tuesday 29 September 2026.
  • The cases, companies and peopleSamples written for this build. They are plausible and they are not real records.

What we assumed

Where the scope was silent, we chose the reading a careful consultant would and built it.

  • "Risk scores" means two separate thingsThe legal conclusion, which is only low risk or not low risk and is made by a person, and an evidence strength reading from the assistant. We never mix them.
  • The importer's one drag is signingMoving a card from Approval to Shipped. Everything else is moved by the work itself or by a reviewer.
  • Mitigation and approval are never reached by draggingBoth are decisions recorded by name on their own screens.
  • The written reason for missing evidence appears when it is neededWhen a supplier says they cannot get a document, or tries to send without it, not under every field from the start.
  • Stage names and the nine columnsTaken from section 7.1 of the scope. "Certification check or evidence gathering" is one column with two names.
  • No penalty figuresPublished sources disagree on the amounts under the 2024 Rules, so none is shown.
  • Fees and hourly ratesIllustrative, and labelled so wherever they appear.
  • TranslationsWritten carefully but not yet checked by native speakers.

Seven things we added

Not in the scope. Each is marked "Ours" on the screen list.

What we need from you

To turn this into a quotation and a first release.

  1. The worksheets themselves. RA-001, RA-002, FOR-001, QU-002 and WS-001, and the three Ready Reckoners, so the factors and wording here can be replaced with yours. ILPA-LE-001 and QU-001 were not among the files provided.
  2. A decision on the platform. Power Platform on your Microsoft tenant, a hybrid with a lighter custom front end, or fully custom. This front end was designed to sit on any of the three; the supplier portal and the ring are the parts a canvas app would find hardest.
  3. Your position on the repeat pathway, in the words you want clients and suppliers to read.
  4. The laboratory list from the testing research, to replace the sample directory.
  5. The China policy text as your advisers want it published.
  6. Which e-signature provider you will standardise on, and whether approvals need a drawn signature or a typed one.
  7. Brand sign-off. The Eco Auditors mark here is ours, with the Hikari Solutions dots at its centre. We need your view before it goes further.
  8. A native-speaker check of the supplier portal in Bahasa Indonesia, Vietnamese and Chinese.