Screens/Key screens

Screens

Key screens

The screens the flows pass through, in the picked shell on the one surface — a desktop browser — each filled with the sample and its empty or other state beside it.

Every screen is drawn in the picked shell — the Figma’s sidebar, the presenter’s control in the top bar, the synthetic data mark — at 1280 × 800, the one surface the brief gives: a desktop browser on the presenter’s laptop, shown on a large screen. The data is the sample chain, Quillara → Brisemont → Ferrovane → Velmora, in tCO2e. The flows are made of these screens.

The customer

Velmora Battery Works, at the end of the chain: sets up the example, sends the request, follows the chain, reviews each response, asks and exports.

Setup

The customer keeps or changes the prepared example: the industry, the four companies, the container.

Who and when
The presenter, acting as the customer, at the start of the demo — and again after a new setup or a start-over.
What it is for
Shows the example in place — the industry, the four companies in chain order with the originating company IDs Setup issued, the container — and lets the customer keep it, choose the other prepared industry, or change a name, which renames the example at once without the AI. Any change starts the walkthrough over.
In the flows
Flow 1, steps 1–3: open the setup, keep the example, choose the other prepared industry or rename the companies.
Presenter’s control

Setup

Prepared example · Lithium-ion batteries

Industry and companiesFive inputs, nothing else by hand
Industry
Lithium-ion batteriesFood packagingAnother industry…
The two prepared industries need no AI; another is generated, if time allows.
Originating company ID · QuillaraLithium
Originating company ID · BrisemontRefining
Originating company ID · FerrovaneFreight
Originating company ID · VelmoraBatteryWorks

Each ID is the prefix urn:pact:company:customcode:buyer-assigned: and the code. Setup issues them; they are never typed.

A change starts the walkthrough overA new name renames the example at once, without the AI, and its ID with it; another prepared industry puts its own example in place. Once a request has been sent, you confirm first what is discarded.
What the example holds
IndustryLithium-ion batteries
PartiesFour, in chain order
  1. QQuillara LithiumMine
  2. BBrisemont RefiningRefiner
  3. FFerrovane FreightCarrier
  4. VVelmora Battery WorksCustomer
ContainerCNT-BR-0417
ContentsBattery-grade lithium carbonate · 15.6 t
Made fromLithium concentrate · 24 t

The figures and the response documents stay with the suppliers: this screen shows neither.

The prepared example in place: the five inputs on the left, what the example holds on the right. Apply is the one primary action; the start-over is in the presenter’s control.

Setup

Another industry · generating

Industry and companiesFive inputs, nothing else by hand
Not a prepared industry: generated by the AI.
Originating company ID · QuillaraLithium
Originating company ID · BrisemontRefining
Originating company ID · FerrovaneFreight
Originating company ID · VelmoraBatteryWorks

Each ID is the prefix urn:pact:company:customcode:buyer-assigned: and the code. Setup issues them; they are never typed.

The walkthrough waitsNo request is sent and no party acts until the example is ready. The presenter’s control comes back with it.
What the example holds
Generating the example… The parties, the container, the figures and the three response documents are built from the five inputs. The result appears here.
Another industry, typed — if time allows: the AI generates the example; the form takes no input, the presenter’s control is hidden and the menu dimmed; the walkthrough waits.
Presenter’s control

Setup

Prepared example · Food packaging

Industry and companiesFive inputs, nothing else by hand
Industry
Lithium-ion batteriesFood packagingAnother industry…
The two prepared industries need no AI; another is generated, if time allows.
Originating company ID · CalveraRecycling
Originating company ID · TessmarkPackaging
Originating company ID · BrennholtHaulage
Originating company ID · AldervikFoods

Each ID is the prefix urn:pact:company:customcode:buyer-assigned: and the code. Setup issues them; they are never typed.

A change starts the walkthrough overA new name renames the example at once, without the AI, and its ID with it; another prepared industry puts its own example in place. Once a request has been sent, you confirm first what is discarded.
What the example holds
IndustryFood packaging
PartiesFour, in chain order
  1. CCalvera RecyclingFirst party
  2. TTessmark PackagingProcessor
  3. BBrennholt HaulageCarrier
  4. AAldervik FoodsCustomer
ContainerCNT-TM-0212
ContentsRecycled-PET food trays · 9.8 t
Made fromFood-grade rPET flake · 10.6 t

The figures and the response documents stay with the suppliers: this screen shows neither.

The second prepared industry, food packaging, chosen: its own four companies and container are in place at once, with no AI. The places are named by role, the tiles carry each company’s initial, and the sidebar and the presenter’s control show Aldervik Foods and its parties; the label’s profile follows.

Label and request

The STS label of the container — six fields, eight questions — and the request sent to the three suppliers.

Who and when
The customer, once the example is in place and before any request is sent.
What it is for
Shows the STS label of the container — the six mandatory fields and the eight label questions, each with its meaning — and what each supplier will receive. Send request sends it to the three suppliers at once.
In the flows
Flow 1, steps 4–6: the label created from the setup, its definition opened, the request sent.
Presenter’s control

Label and request

CNT-BR-0417 · The STS label for the container

Label created
ProfileLithium-ion batteries · Battery-grade lithium carbonate, t
  1. QQuillaraextraction · Cat 1
  2. BBrisemontprocessing · Cat 1
  3. FFerrovanetransportation · Cat 4
  4. VVelmoracustomer
#The six mandatory fields
1Originating company IDThe party the value comes from, as Setup issued its ID.
2Units of measurementThe unit the document gives each figure, shown as written.
3Source of dataWhere a value came from, in the document’s words.
4VerificationSelf-verified, or audited with the verifier named.
5Scope 3 emissionsEmbedded in the material at hand-over: own figure plus what arrived.
6How the Scope 3 were producedThe own figure — Scope 1–2, or transport — plus what arrived.
What each supplier receives
Addressed toQuillara Brisemont Ferrovane
ContainerCNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t
AsksThe six fields and the eight questions, each emission figure with its method flag
SentTo all three at once, directly — not along the chain
#The eight label questions
1Who generated the emissions?The party that reported them.
2What activity caused them?The business event of the party’s step, as the profile names it.
3Which product do they impact?The product the emissions are attributed to.
4Where did they occur?The place of the party’s facility.
5How were they calculated?The document’s description, with its allocation to the material.
6When did they occur?The period the emissions cover.
7Which STS transactions support the calculation?The parent transactions the figures rest on, from the chain.
8How do they roll up into Scope 3 reporting?The roll-up rule, stated once in the label.
The field names are the demo’s ownNo STS dictionary exists yet, so these names are the demo’s. The roll-up rule is stated once, as the answer to question 8.
The label as created, with no values yet: its profile on top — the industry, the product, and each place with its event and Scope 3 category, the part that follows the customer’s input — then the fields and questions as two tables, what each supplier receives, and the note that the field names are the demo’s own.
Presenter’s control

Label and request

CNT-BR-0417 · The STS label for the container

Label requested
Request sent to the three suppliersAll three at once, directly from the customer. Each supplier now has the request addressed to it; the chain view shows each step as requested.
SupplierOriginating company IDEventRequest
QQuillara LithiumQuillaraLithiumExtractionRequested
BBrisemont RefiningBrisemontRefiningProcessingRequested
FFerrovane FreightFerrovaneFreightTransportationRequested
What each supplier receives
Addressed toQuillara Brisemont Ferrovane
ContainerCNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t
AsksThe six fields and the eight questions, each emission figure with its method flag
SentTo all three at once, directly — not along the chain
After sending: the three suppliers, each with its request, requested; the action is not offered again for this label.
Presenter’s control

Label and request

CNT-TM-0212 · The STS label for the container

Label created
ProfileFood packaging · Recycled-PET food trays, t
  1. CCalverarecycling · Cat 1
  2. TTessmarkthermoforming · Cat 1
  3. BBrennholttransportation · Cat 4
  4. AAldervikcustomer
#The six mandatory fields
1Originating company IDThe party the value comes from, as Setup issued its ID.
2Units of measurementThe unit the document gives each figure, shown as written.
3Source of dataWhere a value came from, in the document’s words.
4VerificationSelf-verified, or audited with the verifier named.
5Scope 3 emissionsEmbedded in the material at hand-over: own figure plus what arrived.
6How the Scope 3 were producedThe own figure — Scope 1–2, or transport — plus what arrived.
What each supplier receives
Addressed toCalvera Tessmark Brennholt
ContainerCNT-TM-0212 · Recycled-PET food trays, 9.8 t
AsksThe six fields and the eight questions, each emission figure with its method flag
SentTo all three at once, directly — not along the chain
#The eight label questions
1Who generated the emissions?
2What activity caused them?
3Which product do they impact?
4Where did they occur?
5How were they calculated?
6When did they occur?
7Which STS transactions support the calculation?
8How do they roll up into Scope 3 reporting?
The example’s five queriesAsked once the chain is complete
Show Category 1 emissions by supplier.What Scope 3 emissions are attributable to PET recycling?Which STS transactions support Category 4 transportation emissions?Which tray products contribute most to Category 12 end-of-life emissions?Provide a complete audit trail for all Scope 3 calculations.
Label — food packaging: the same six fields and eight questions; the profile follows the example — Calvera recycling · Cat 1 › Tessmark thermoforming · Cat 1 › Brennholt transportation · Cat 4 — for container CNT-TM-0212, and the example’s own five queries, Category 12 end-of-life in place of Category 11.

Label definition

The standard’s side of the label: meaning, unit, where each value comes from, what stands in — the demo’s own.

Who and when
Any party — the customer from its label, a supplier from its request — and the working group watching.
What it is for
The label as a semantic layer, not a form: for each field and question its meaning, unit, where its value comes from and what stands in when there is none, and the roll-up rule. The demo’s own definitions — no STS dictionary exists yet.
In the flows
Opened from Label and request or from a supplier’s request; no flow of its own.
Presenter’s control

Label definition

The demo’s own: no STS dictionary exists yet, and the working group will define it · the same for every party

Read only
#FieldUnitComes fromWhen there is none
1Originating company IDThe party a value comes from.—The requestnever missing
2Units of measurementEach figure’s unit, as written.—The documentan error
3Source of dataWhere a value came from.—The documentan error
4VerificationSelf-verified, or audited and by whom.—The documentan error
5Scope 3 emissionsEmissions embedded in the material at hand-over — the party’s own figure plus what arrived with the material. The buyer counts it in its Scope 3; the profile says which category each part falls in.tCO2eRoll-up: own + receivedawaiting upstream
6How the Scope 3 were producedThe own figure — Scope 1–2, or the transport of the container — plus what arrived.tCO2eDocument and parentan error
7Method flagMeasured, or estimated and how.—The documentan error
8Embedded emissions receivedWhat arrived with the material: the upstream party’s reported total.tCO2eThe parent transactionawaiting upstream
#QuestionComes fromWhen there is none
1–6Who generated the emissions, what activity, which product, where, how calculated, when?The documentnot stated
7Which STS transactions support the calculation?The chain: the parent links—
8How do they roll up into Scope 3 reporting?The roll-up rule—
Rules
Applies toOne container, CNT-BR-0417
AllocationEach supplier allocates its own emissions to the material in this container and says how; the demo computes no allocation or yield.
Roll-upOwn + received is what a party passes on; the customer’s Scope 3 is the carrier’s total
Document termThe supplier’s own name for a value, shown beside it in the review
Eight entries of the label on the left, the eight questions and the rules on the right; read only, the same for every party, with no figure of anyone in it.

Chain view

The container’s path mine → refiner → carrier → customer, each step’s state and the roll-up.

Who and when
The customer, after the suppliers have responded and the responses are reviewed — and earlier, to see which have answered.
What it is for
Shows the container’s path, mine → refiner → carrier → customer, each step with its transaction and review status, and — once the chain is complete — the roll-up into the customer’s Scope 3 for the container, by category.
In the flows
Flow 1, step 7 (the steps requested); Flow 3, steps 1 and 6 (the chain fills in, the roll-up).
Presenter’s control

Chain view

CNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t · mine → refiner → carrier → customer

Chain complete
  1. Q
    Quillara LithiumMine · extraction

    24 t lithium concentrate

    Accepted

    STS-EX-0001

    Category 1 · no parent

  2. B
    Brisemont RefiningRefiner · processing

    24 t concentrate → 15.6 t lithium carbonate

    Accepted

    STS-PR-0001

    Category 1 · parent STS-EX-0001

  3. F
    Ferrovane FreightCarrier · transportation

    CNT-BR-0417 · 15.6 t, Mejillones → Austin

    Accepted

    STS-SH-0001

    Category 4 · parent STS-PR-0001

  4. V
    Velmora Battery WorksCustomer · end of the chain

    CNT-BR-0417 delivered

    No transaction of its own

    Scope 3 38.2 tCO2e

Roll-upAll three transactions exist · figures as reported, in tCO2e
PartyTransactionOwn emissionstCO2eEmbedded receivedtCO2eReported totaltCO2eReview
Category 1 · Purchased goods and services35.7Sum of the own figures
QuillaraSTS-EX-000123.3trucking to the refinery includednot applicable23.3Accepted
BrisemontSTS-PR-000112.423.335.7Accepted
Category 4 · Upstream transportation and distribution2.5Sum of the own figures
FerrovaneSTS-SH-00012.5transport of the container35.738.2Accepted
Category 11 · Use of sold productsnot in this chain yet — downstream of the customer Its buyers would report it.
Velmora Battery Works · Scope 3 for the containerCategory 1 35.7 + Category 4 2.5= Ferrovane Freight’s reported total38.2
The chain complete, all three steps accepted, each with what it handled — the concentrate, the carbonate made from it, the container on its way, delivered. The roll-up: each party’s own figure — Scope 1–2, or the transport of the container — and what arrived with the material, Category 1 and 4 summed, Category 11 not in this chain yet — downstream of the customer — and the customer’s Scope 3 as the carrier’s reported total.
Presenter’s control

Chain view

CNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t · mine → refiner → carrier → customer

Chain incomplete
  1. Q
    Quillara LithiumMine · extraction

    24 t lithium concentrate

    Requested

    No transaction yet

  2. B
    Brisemont RefiningRefiner · processing

    24 t concentrate → 15.6 t lithium carbonate

    Requested

    No transaction yet

  3. F
    Ferrovane FreightCarrier · transportation

    CNT-BR-0417 · 15.6 t, Mejillones → Austin

    Requested

    No transaction yet

  4. V
    Velmora Battery WorksCustomer · end of the chain

    CNT-BR-0417 delivered

    No transaction of its own

No roll-up yet Nothing has responded. The roll-up appears once each of the three steps has had a transaction.
Request sent, no response yet: each step requested with no transaction, no roll-up.

Review

One interpreted response — the labelled values, never the file — accepted or sent back with a note.

Who and when
The presenter, acting as the customer, once a supplier’s response is interpreted: opened from the supplier’s step in the Chain view, one transaction at a time.
What it is for
The human check on what the AI made of a document: the labelled values and the eight questions answered, never the original file, then Accept or Request clarification with a note. Both are final and confirmed first.
In the flows
Flow 3, steps 2–4; Flow 5, step 4
Presenter’s control

Chain view

CNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t · mine → refiner → carrier → customer

  1. Q
    Quillara LithiumMine · extraction

    24 t lithium concentrate

    Accepted

    STS-EX-0001

  2. B
    Brisemont RefiningRefiner · processing

    24 t concentrate → 15.6 t lithium carbonate

    Pending

    STS-PR-0001

  3. F
    Ferrovane FreightCarrier · transportation

    CNT-BR-0417 · 15.6 t, Mejillones → Austin

    Accepted

    STS-SH-0001

  4. V
    Velmora Battery WorksCustomer · end of the chain

    CNT-BR-0417 delivered

    No transaction of its own

Roll-upComplete · the customer’s Scope 3 is Ferrovane’s reported total, 38.2 tCO2e
PartyOwn emissionsEmbedded receivedReported totalReview
QQuillara23.3 tCO2enot applicable23.3 tCO2eAccepted
BBrisemont12.4 tCO2e23.3 tCO2e35.7 tCO2ePending
FFerrovane2.5 tCO2e35.7 tCO2e38.2 tCO2eAccepted
Brisemont Refining’s transaction, pending. The Chain view stays behind the drawer, open from its step. The drawer reads the six mandatory fields with a method flag beside each emission figure and the document’s own term beside each value, and the trail of the response with the time it was interpreted; the two actions sit at its foot.
Presenter’s control

Chain view

CNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t · mine → refiner → carrier → customer

  1. Q
    Quillara LithiumMine · extraction

    24 t lithium concentrate

    Accepted

    STS-EX-0001

  2. B
    Brisemont RefiningRefiner · processing

    24 t concentrate → 15.6 t lithium carbonate

    Pending

    STS-PR-0001

  3. F
    Ferrovane FreightCarrier · transportation

    CNT-BR-0417 · 15.6 t, Mejillones → Austin

    Accepted

    STS-SH-0001

  4. V
    Velmora Battery WorksCustomer · end of the chain

    CNT-BR-0417 delivered

    No transaction of its own

Roll-upComplete · the customer’s Scope 3 is Ferrovane’s reported total, 38.2 tCO2e
PartyOwn emissionsEmbedded receivedReported totalReview
QQuillara23.3 tCO2enot applicable23.3 tCO2eAccepted
BBrisemont12.4 tCO2e23.3 tCO2e35.7 tCO2ePending
FFerrovane2.5 tCO2e35.7 tCO2e38.2 tCO2eAccepted
The Context tab: the eight label questions answered for Brisemont — who, what activity, which product, where, how calculated with its allocation to the container, when (Q3 2026), which STS transactions, and how it rolls up: Category 1, passing on 35.7 tCO2e.
Presenter’s control

Chain view

CNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t · mine → refiner → carrier → customer

  1. Q
    Quillara LithiumMine · extraction

    24 t lithium concentrate

    Pending

    STS-EX-0001

  2. B
    Brisemont RefiningRefiner · processing

    24 t concentrate → 15.6 t lithium carbonate

    Pending

    STS-PR-0001

  3. F
    Ferrovane FreightCarrier · transportation

    CNT-BR-0417 · 15.6 t, Mejillones → Austin

    In error

    STS-SH-0001

    Missing: verificationNo review status.
  4. V
    Velmora Battery WorksCustomer · end of the chain

    CNT-BR-0417 delivered

    No transaction of its own

Roll-upIncomplete — Ferrovane in error · no category sum, no customer total
PartyOwn emissionsEmbedded receivedReported totalReview
QQuillara23.3 tCO2enot applicable23.3 tCO2ePending
BBrisemont12.4 tCO2e23.3 tCO2e35.7 tCO2ePending
FFerrovaneSTS-SH-0001 not counted: verification not givenIn error
All three have responded: Quillara Lithium and Brisemont Refining interpreted, their review pending; Ferrovane Freight in error (verification missing). The error stands in place of a review status in the chain and in the roll-up, under the same transaction id; a response in error is not counted, so the roll-up gives each counted party’s contribution with no category sum and no customer total. No action is offered.

Queries and export

Questions in plain language, answered with the transactions behind each number; the export.

Who and when
The presenter, acting as the customer, once the chain holds transactions: asks, follows a citation to the chain and back, and exports.
What it is for
One query box answered from the labelled data alone: every number cites its STS transactions with their review status, and what the chain cannot answer is said so, with the reason. The labelled data leaves as CSV — Excel and JSON if time allows — after a preview of its first rows.
In the flows
Flow 4, every step but the Chain view
Presenter’s control

Queries and export

Ask about the labelled data of CNT-BR-0417. Every number cites the STS transactions behind it.

The five example queries
Answers of this sitting, newest first
Which STS transactions support Category 4 transportation emissions?Oct 25 15:05

The mine’s trucking to the refinery is inside STS-EX-0001 and counts in Category 1; the 35.7 the carrier received is the refiner’s figure relayed, counted in Category 1.

What Scope 3 emissions are attributable to lithium extraction?Oct 25 15:04

Lithium extraction is Quillara Lithium’s step: its own Scope 1–2, measured, trucking to the refinery included. It reaches Velmora inside Brisemont’s 35.7, in Category 1.

Show Category 1 emissions by supplier.Oct 25 15:03

Category 1 by contributing party: each figure is the party’s own Scope 1–2, as it reported it. Brisemont is Velmora’s direct supplier; its 35.7 passed on includes Quillara’s 23.3.

Three answers once the chain is complete, newest first: Category 4 — Ferrovane’s transaction alone, and why the mine’s trucking and the relayed 35.7 are in Category 1; lithium extraction — Quillara’s own 23.3, its trucking to the refinery included; Category 1 by contributing party. Each figure cites its STS transaction, accepted, each id a link to the Chain view. Export beside: CSV, Excel and JSON if time allows.
Presenter’s control

Queries and export

Ask about the labelled data of CNT-BR-0417. Every number cites the STS transactions behind it.

The five example queries
Answers of this sitting, newest first
Which battery products contribute most to Category 11 emissions?Oct 25 15:06
not in this chain yet — downstream of the customer

Category 11 is the use of the sold batteries, after Velmora Battery Works: it would be reported by the buyers and users of the batteries, labelled the same STS way, once the chain extends past the customer. This chain ends at Velmora, so there is no figure yet, and no product is ranked.

No transaction is cited: there is no number to cite.
Which STS transactions support Category 4 transportation emissions?Oct 25 15:05

The mine’s trucking to the refinery is inside STS-EX-0001 and counts in Category 1; the 35.7 the carrier received is the refiner’s figure relayed, counted in Category 1.

What Scope 3 emissions are attributable to lithium extraction?Oct 25 15:04

Lithium extraction is Quillara Lithium’s step: its own Scope 1–2, measured, trucking to the refinery included. It reaches Velmora inside Brisemont’s 35.7, in Category 1.

Category 11 asked: not in this chain yet — downstream of the customer — with where the figure would come from, and no citation because there is no number to cite.
Presenter’s control

Queries and export

Ask about the labelled data of CNT-BR-0417. Every number cites the STS transactions behind it.

The five example queries
Answers of this sitting, newest first
Which STS transactions support Category 4 transportation emissions?Oct 25 15:05

The mine’s trucking to the refinery is inside STS-EX-0001 and counts in Category 1; the 35.7 the carrier received is the refiner’s figure relayed, counted in Category 1.

What Scope 3 emissions are attributable to lithium extraction?Oct 25 15:04

Lithium extraction is Quillara Lithium’s step: its own Scope 1–2, measured, trucking to the refinery included. It reaches Velmora inside Brisemont’s 35.7, in Category 1.

Download CSV shows the first rows before the file is saved: own_emissions_tco2e and own_category add up to the customer’s Scope 3; the cumulative columns already include upstream and are never summed.
Presenter’s control

Queries and export

Ask about the labelled data of CNT-BR-0417. Every number cites the STS transactions behind it.

The five example queries

No answers yet

Ask one of the five example queries in the box above. The answers of this sitting stay here, newest first.

No answer yet: the box and the five example queries, with the empty state in the place the first answer will take.

A supplier

Each supplier on a screen of its own — here Ferrovane Freight, the carrier: the request addressed to it, its own document, its status and the outcome. It reads its own label, read only, and confirms nothing before the review.

Supplier: request

What the label asks the supplier about the container, and the upload of its own document.

Who and when
A supplier — the presenter acting as Ferrovane Freight — who opens the screen to read what the customer asks about the container and to answer it.
What it is for
The request addressed to this supplier only, read only: the label’s six mandatory fields and eight questions, and what arrives with the container — the upstream party’s transaction and its embedded total, which the supplier does not state. Beside it the supplier answers — by picking its own prepared document, or the carrier’s variant with the verification left out, or by dropping a simple text document in its own format. Uploading is submitting.
In the flows
Flow 2, steps 2–3 (and Flow 5, step 1 with the variant)
Presenter’s control

Request

From Velmora Battery Works · container CNT-BR-0417 · Battery-grade lithium carbonate, 15.6 t

Requested
  1. Request
  2. Upload
  3. Interpretation
  4. Outcome
What arrives with the containerBBrisemont RefiningSTS-PR-000135.7 tCO2eEmbedded emissions, as Brisemont reported them. You state only your own; the label adds them.
What the label asksSix mandatory fields and eight questions · label definition
Mandatory fields
  • Originating company IDTaken from this request, not from your documentRequired
  • Units of measurementAs your document gives them; nothing is convertedRequired
  • Source of dataWhere a value came from, in your document’s wordsRequired
  • VerificationSelf-verified, or third-party verified / auditedRequired
  • Scope 3 emissionsEmbedded at hand-over: your own figure plus what arrivedRequired
  • How the Scope 3 were producedYour own figure — Scope 1–2 or transport — and its methodRequired
QuestionsOptionalNot given in your document reads “not stated”
  1. 1Who generated the emissions?
  2. 2What activity caused them?
  3. 3Which product do they impact?
  4. 4Where did they occur?
  5. 5How were they calculated?
  6. 6When did they occur?
  7. 7Which STS transactions support the calculation?
  8. 8How do they roll up into Scope 3 reporting?
Your responsePick a prepared document or upload your own
Prepared documents
Your own file
Drop your response document here or browseAny simple text document in your own format, e.g. PDF
Picking a document or uploading a file submits it as it is — there is nothing to review first.
The request from Velmora Battery Works about container CNT-BR-0417, with the stepper at its first steps: Request read, Upload next. The carrier is offered two prepared documents — the one that gives every mandatory value and the variant that leaves the verification out — beside the drop zone.
Presenter’s control

Request

For Ferrovane Freight

No request yetNothing has been addressed to Ferrovane Freight yet. The request appears here once the customer has sent it, and the upload with it.
Before the customer sends the request: nothing is addressed to this supplier, so there is no request and no upload to offer. Nothing announces the request — it is there when the screen is opened.

Supplier: response and outcome

The supplier’s document, its status, its label read only, and the customer’s decision.

Who and when
A supplier — the presenter acting as Ferrovane Freight — after the upload, and again when the customer has decided.
What it is for
The supplier’s own file with Preview and Replace, the status of the response — here in error, the missing item named — and the outcome panel on the right. The supplier reads its own label as the customer reads it, read only, and confirms nothing before the review. A replacement is its way out of an error; answering a note with one is built if time allows.
In the flows
Flow 2, step 5; Flow 5, steps 1–2 and 4; Flow 3, step 4
Presenter’s control

Request

From Velmora Battery Works · container CNT-BR-0417

In error
What the label asksSix mandatory fields and eight questions
  1. Request
  2. Upload
  3. Interpretation
  4. Outcome
ferrovane-freight-response-no-verification.pdfSubmitted Oct 25 14:35 · only you see it
Response statusIn error
  • VerificationMandatory field
  1. SubmittedYour document is in and handed to the AI.Oct 25 14:35
  2. In errorThe document gives no value for a mandatory item.Oct 25 14:36
The values the document gave stay readable in your label, beside the error, as the customer sees them.
The carrier’s variant uploaded: the response is in error and names the missing verification; the stepper stops at Interpretation. A response in error has no outcome, and the customer can take no action on it — the panel on the right says so.
Presenter’s control

Request

From Velmora Battery Works · container CNT-BR-0417

Accepted
What the label asksSix mandatory fields and eight questions
  1. Request
  2. Upload
  3. Interpretation
  4. Outcome
ferrovane-freight-response.pdfSubmitted Oct 25 14:44 · only you see itClosed to replacement
Your labelRead only
Originating company ID
FerrovaneFreight
Units of measurement
tCO2e“t CO2e”same name
Source of data
Bills of lading, the shipping line's emission statement and the haulier's fuel log“Records used”own term
Verification
Self-verified“Verification”same name
Scope 3 emissions
38.2 tCO2eown + received, added by the label
How the Scope 3 were produced
Transport of the container 2.5 tCO2eestimated“Transport emissions, sea and road”own termEmbedded received 35.7 tCO2eBrisemont’s · STS-PR-0001
What the customer reads in your name. To change a value, replace your document before it is accepted.
Accepted: the response is closed to replacement. Your label shows all six mandatory fields as the customer reads them, read only, with the document’s own term beside each value; the document stays viewable, and no upload is offered any more.
Presenter’s control

Request

From Velmora Battery Works · container CNT-BR-0417

Clarification requested
What the label asksSix mandatory fields and eight questions
  1. Request
  2. Upload
  3. Interpretation
  4. Outcome
ferrovane-freight-response.pdfSubmitted Oct 25 14:44 · only you see it
Response statusInterpreted
  1. SubmittedYour document is in and handed to the AI.Oct 25 14:44
  2. InterpretedThe AI read it into a transaction for the customer to review.Oct 25 14:45
The status stays as it is when the customer decides.
Clarification requested, with the customer’s note: in the core it marks the response and leaves the note, and no Replace is offered. Answering the note with a replacement upload is the part built if time allows.