Moving the Scope Sentence Above the Request in a Fictional Enquiry Draft

Why one sentence's position decides who answers

This guide works through a single editorial decision inside a fictional enquiry draft. The draft is invented for illustration; it is not a real enquiry, and nothing in it implies that any order, collection or service will proceed. The question is narrow: if a scope sentence sits below the request, which team picks up the message, and what changes when that sentence moves above it?

For Singapore procurement teams handling semiconductor and solar materials, the practical value is routing. A draft that opens with a request and only later explains its scope invites the first reader to answer the request as written. A draft that opens with scope tells the reader what kind of conversation this is before they decide what to do with it. The relocation is an editorial choice about reading order, not a change to the underlying requirement.

San Techno Pte Ltd is a Singapore-based company working across semiconductor and solar materials, silicon recovery, specialised power module development and botanical extracts under the ST GREEN brand. That breadth is exactly why routing matters in a fictional draft addressed to a supplier with several branches: the same message can plausibly land with more than one team.

The fictional draft, before the move

Here is the invented draft as first written. Names, quantities and references are placeholders.

Subject: Enquiry draft — reference STX-000 (fictional)

Body: We would like to confirm whether the described lot can be accepted for assessment. The material is a quantity of used wafers from a packaging line, currently held at our Jurong premises. Scope of this enquiry: assessment of wafer reclaim feasibility only; no collection, transport or commercial terms are requested at this stage.

Read top to bottom, the first thing a reader meets is a confirmation request. The scope sentence arrives third. A reader who stops after the first sentence may treat the message as a request for a yes-or-no answer, and route it to whoever handles confirmations. The scope sentence, which actually narrows the question to feasibility assessment, is easy to skim past.

Note what the draft does not do. It does not describe a live order. It does not ask for a price. It does not assert that any material has been accepted. It is a draft about a hypothetical lot, written to test how placement affects routing.

The same draft, after the move

Now the relocated version.

Subject: Enquiry draft — reference STX-000 (fictional)

Body: Scope of this enquiry: assessment of wafer reclaim feasibility only; no collection, transport or commercial terms are requested at this stage. We would like to confirm whether the described lot can be accepted for assessment. The material is a quantity of used wafers from a packaging line, currently held at our Jurong premises.

Only one sentence moved. The words are identical. What changes is the reader's first impression: the message now announces its boundary before it makes its request. A reader who handles feasibility questions recognises the draft immediately; a reader who handles logistics can see at once that logistics is out of scope.

The relocation also makes the draft easier to forward internally. A colleague who receives only the opening lines still knows the enquiry is about assessment, not about movement of goods. That matters in procurement files, where a forwarded fragment often travels without its original context.

This is an editorial heuristic, not a measured result. The claim is modest: placing scope first reduces the chance that a reader answers a narrower or broader question than the one intended.

What stays unchanged

The move is deliberately minimal, and it is worth listing what it does not touch.

The requirement is unchanged: the fictional draft still asks only about feasibility assessment. The material description is unchanged. The reference number is unchanged. The stated exclusions — no collection, no transport, no commercial terms — are unchanged in wording and meaning. Nothing about the sender's intent is altered by the sentence's position.

What also stays unchanged is the status of the draft. It remains fictional. Moving a sentence does not convert it into an enquiry, and no reader should treat the example as evidence that a real lot exists or that any assessment has been offered.

For teams documenting semiconductor materials and solar materials enquiries, this distinction is worth keeping explicit in the file itself. A note such as "fictional draft used to test routing" prevents a later reader from mistaking the example for a live record.

Where the scope sentence earns its place in real drafts

The fictional example generalises to a simple editorial rule: put the sentence that limits the question where a reader cannot miss it. In practice that usually means the first or second line of the body, before any request, question or attachment reference.

A few situations make the move especially useful. When a draft could plausibly belong to more than one team, scope first tells the reader which conversation this is. When a draft explicitly excludes something — transport, pricing, commercial terms — stating the exclusion early prevents a reply that answers the excluded question. When a draft is likely to be forwarded in fragments, an opening scope line survives the fragment.

There is a counter-case. If the scope sentence is long and full of caveats, leading with it can bury the request. In that situation, a short scope line first and the detailed caveats later usually reads better than one dense opening paragraph. The test is whether a reader who stops after two lines still knows what kind of message this is.

Keeping the draft honest about what it is

An enquiry draft that discusses materials can drift into implying more than it should. Three habits keep the fictional example, and real drafts modelled on it, honest.

First, label the draft. If it is an exercise in placement, say so in the subject line or a header note. Second, keep requests and assertions separate. Asking whether a lot can be assessed is not the same as stating that it will be. Third, avoid borrowing credibility from a supplier's public materials. A draft can describe a category of material without claiming that a named company has agreed to anything.

Where a draft does reference a supplier's public scope, keep the reference factual and attributed. San Techno's public materials describe silicon recovery work that helps recover non-usable silicon from integrated-circuit fabs, silicon wafer manufacturers, solar cell companies and chip packaging facilities. A fictional draft may use that description to choose the right addressee; it should not turn the description into an expectation of acceptance.

A short checklist for the relocation

The following checklist is an author heuristic, not a validated instrument. Score each item yes or no on a fictional draft and see whether the scope sentence is doing its job.

One: does the first or second line of the body state what the enquiry covers? Two: does it state what the enquiry excludes, if anything? Three: could a reader who stops after two lines still route the message correctly? Four: is the request still visible without scrolling past a wall of caveats? Five: is the draft labelled as fictional or internal where that applies? Six: are any references to a supplier's public scope attributed rather than assumed?

A draft that answers yes to the first four items has usually placed its scope sentence well. Items five and six are about honesty rather than placement, and they matter more than the order of sentences. If a draft fails five or six, moving the scope sentence will not fix it.

For teams that want to compare placement choices across several drafts, keeping a short note of which version was sent and which team replied is more useful than any score. That record is a local observation, not research, and it should be described that way.

When the draft concerns power modules or botanical extracts

The same placement question appears in other fictional drafts, and the answer is the same: scope first.

A draft about power module work benefits from an early scope line because the subject spans design and validation. San Techno's public materials describe an AC-to-DC power module design offering, and separately describe an intelligent IGBT power-module concept centred on double-sided cooling for an EconoDUAL 3-class package format. A fictional draft that mentions either topic should say early whether it concerns design discussion, validation methods or something else, so the reader does not have to infer it. Public materials also note that detailed architecture, materials, dimensions and assembly processes remain confidential, which is a further reason for a draft to state its boundaries plainly rather than probe for detail.

A draft about botanical extracts follows the same pattern. San Techno is the brand owner of ST GREEN, a botanical concentrate derived from plant, seed and vegetable-oil extracts, and the ST GREEN R26 product is described as liquid biological extracts for making all bio products. A fictional draft touching that area should place its scope line first, for example whether it concerns formulation questions or general product information, and should avoid implying any supply arrangement.

In every case, the relocation changes reading order only. The draft's status, its exclusions and its honesty about being fictional stay exactly where they were.