Sourcing DeskHow to Rescope a Rushed Sourcing Request and Record What You Could Not Check
Start where the request actually broke
If you have been handed a sourcing request with less time than its own checks require, the rescope comes down to one uncomfortable move: rewrite the ask so that what you can decide honestly is separated from what you cannot, then write down every claim you did not get to check. That third list is the part people skip, and it is the part that protects the decision later.
Everything here is buyer-side commercial practice, not legal, customs, or regulatory advice.
Why a rushed request fails differently from a slow one
A request with enough time fails because someone made a bad call. A rushed one fails because unverified assumptions quietly became inputs. Nobody recorded them as unverified, so they travelled onward as facts into a quotation, a purchase order, or a launch plan.
Rescoping is the discipline of making those assumptions visible while there is still room to route around them. That is why the worksheet below is organised around what you could not check rather than around a score or a pass mark.
What due diligence actually covers when time is short
Know the ceiling before you promise anything. The U.S. International Trade Administration's Perform Due Diligence guidance on country and company or partner risk research frames this work as research: country risk and company or partner risk, with links to official screening resources and commercial guides.
That framing matters under pressure, because it defines what a check can return. Screening resources surface risk information about a country or a named entity; they do not tell you whether a specific production run will meet your drawing, and they do not certify anything. A clean screening result is research output, not a certificate and not a quality statement. Your worksheet should therefore keep three separate meanings apart: something was looked at and adverse information appeared, something was looked at and nothing adverse appeared, and nothing was looked at inside this window. Those lead to different decisions, and they are routinely collapsed into the single word "checked".
Two clocks, and you control only one of them
Rushed requests get treated as one deadline. They are usually two.
- Your decision clock is set internally, by your launch plan, budget cycle, or your own customer's expectation. Moving it requires the person who owns the consequence.
- The verification clock is set by whoever holds the evidence: a testing laboratory, a reference contact, a registry, or a factory scheduling a site visit. Internal effort does not shorten it.
This split is the entire basis of the rescope. Any answer that can only arrive after your decision deadline cannot be a precondition of this decision; it can only be an open row with an owner and a trigger.
Sort every line into the column it belongs in
Go through the request line by line and place each item in one of these states.
Must be true before you commit. Keep this set deliberately small: the written specification you will accept goods against, the legal entity you are actually contracting with, and the payment and delivery responsibilities agreed in writing. If one of these is still open at the deadline, the answer is to stop or to escalate, not to proceed hopefully.
Accepted provisionally. True enough to move on, with a named owner and a trigger that forces another look, such as before a deposit is released or before the first shipment.
Not checked in this window. An honest unknown, recorded rather than left implicit. Items that look like commercial questions often land here: whether quoted capacity covers your peak, whether the minimum order quantity fits your cash, whether the named party actually operates the site you were told about.
Incoterms do not answer the quality or the payment question
A term such as FOB or EXW allocates transport responsibilities and costs between buyer and seller. It says nothing about whether the goods will meet your specification, and nothing about when or how you pay.
Keep those rows apart in the worksheet. The commercial term belongs in one row; acceptance criteria and payment arrangements belong in others, and each needs its own written confirmation. Letting one row carry another is how a rushed file acquires confidence it never earned.
Worksheet A: the rescope header
Fill this first. Seeing the rescoped ask written directly under the original ask usually settles the argument about what is realistic faster than any discussion.
| Field | Your entry |
|---|---|
| Original ask, in their words | |
| Rescoped ask, what you can stand behind | |
| Decision deadline, and who set it | |
| Named counterparty for this stage | |
| What you will do if a must-be-true row is still open at the deadline |
Worksheet B: the verification ledger
List every claim the decision rests on, including the ones nobody has questioned yet.
In the Status column use exactly these three values and nothing else: Confirmed from a source I can point to, Partially confirmed, or Not checked in this window. Do not use "checked" on its own.
| Claim or assumption | Where the evidence comes from | Status | What would close the gap | Owner |
|---|---|---|---|---|
Typical tenants of this ledger are the written specification, the legal entity behind the counterparty, any capability assertion, references, and transport arrangement. Add your own rather than assuming the list is complete.
Worksheet C: the handoff record for open items
The point of a handoff record is that the person accepting an open risk today is often not the person handling the file later. Copy every row marked "not checked" here.
| Left open | If this turns out wrong, what breaks | Trigger that forces a re-check | Owner | Accepted by, with name and date |
|---|---|---|---|---|
Write the open rows so a stranger can read them
A note saying "TBD" is worth nothing to whoever inherits the file. Each open row should state what exactly is unknown, who owns closing it, which event forces another look, and who agreed to leave it open.
While writing them, sort each row by the kind of gap it is: a document you have not received, a third party you have not heard back from, or a step nobody has started. That distinction immediately tells you which rows are closable within the deadline at all, and which belong in the handoff record until something external moves.
One suggestion, offered as practice rather than a requirement
Keep Worksheet B in the same file as the request you send onward, so the asks and the unknowns travel together. If a quotation, a supplier claim, or a next step comes up later, treat it as needing confirmation against that specific file; nothing in this worksheet converts an open row into a closed one on its own.
What Sourcing Desk does with it
You can send your buyer brief together with the completed worksheet for review. A reviewer can read the rescope header and the verification ledger and say which open rows look closable inside the timeline you actually have. Any human follow-up, supplier claim, quotation, or next step would then need case-specific confirmation before it becomes a commitment, because none of them follow from the worksheet alone.
Your next move on this specific request
Take the rushed request sitting in front of you, fill in Worksheet A, and stop after the rescoped ask to compare it honestly with the original ask. Then list the claims you already know you will not reach as open rows in Worksheet B, each with an owner and a trigger, and send that single page along with your brief. If you would rather not complete the full worksheet, send the original ask, your decision deadline, and the claims you already know are open; the rest can be worked out from there, with every next step confirmed against your case.