The RFQ you send to a China outdoor running shoes manufacturer is a buyer-side document: it fixes the terrain you run on, your goal and distance, and a weekly mileage band, then asks every candidate to return its factory address, production capacity, MOQ, lead-time commitment, certification reports and article-specific test reports as named documents. None of those supplier-side lines can be lifted off a catalog page or a price email, so they stay empty in your file until paperwork lands.
That emptiness is the design. An RFQ that asks for a price on trail running shoes gets an answer showing only what the factory chose to write down. A document with an evidence column left visibly blank forces each reply to either fill a named line or leave a hole you can see from across the desk.
Day 1 Sets Terrain, Goals and Weekly Mileage
Day one is entirely about you. Before a factory can quote anything worth comparing, the RFQ has to state three runner-side facts: the surface you actually run on and the mix of it, the goal and distance the shoe is being built for, and a weekly mileage band the shoe has to survive.
Salomon's trail-shoe selection guide asks the same two questions, what type of terrain am I going to be running on, and what are my running goals, what distances will I be covering. That framing is worth copying because it treats both as selection questions rather than specifications: the answers come from your training week, not from a factory's brochure.
Put them on the page as inputs you own. A surface line might read packed dirt with rock sections and short road connectors; a goal line names a distance band and says whether the shoe is for race day or weekly training; a mileage line states the band the shoe has to hold up inside. No factory can answer those with marketing text. It can design against them or ask you to clarify, and either response tells you more than a price.
Each field then converts into a design question instead of a number. For a mixed surface, ask which outsole tread pattern and compound the factory would propose and why, and what changes if the rock share rises. For the goal, ask whether the proposed midsole package suits a runner training toward that distance and what the trade-off becomes if the target doubles. For mileage, ask what upper construction and protection placement the factory recommends inside that band, and where the shoe gains weight getting there.
Questions pull reasons out of a factory. Numbers you invent pull agreement.
Day 3 Separates Your Spec From Their Evidence
Day three puts a hard vertical line down the document. On the left sits everything you want the shoe to be: terrain and use case, target market, fit intent, packaging and labeling. On the right sits everything the factory has to prove: its address, production capacity, MOQ, lead-time commitment, certification reports, and test reports tied to the article you are asking about.
The right-hand column ships blank. That is the actual state of the file on day three, not an oversight: no candidate quote, no MOQ, no capacity audit, no lead-time commitment and no certification report has arrived yet. Writing each line by name now gives every reply somewhere specific to land, and it makes a missing item show up as a missing item rather than as a vague sense that the factory seemed professional.
The check on the layout is quick to run. If you could answer a line yourself, it belongs on the left. If only the factory can answer it, and only by sending a document, it belongs on the right. A yes-we-can-do-that belongs in neither column; it goes into the follow-up notes as a question still unanswered.
The same discipline applies to your own side of the file. Nothing has been sampled or third-party tested at this stage, so the RFQ asks for existing documents rather than promising any result of your own, and the left column stays a statement of what you want, never a claim about what the factory can do.
Week 1 Sends the Same RFQ to Every Candidate Factory
The first week is dispatch, and the habit that matters is sameness. Every candidate receives the identical document: same question numbering, same units, same order. If one reply is measured in pairs per month and another in containers per week, you have manufactured comparison work that a shared format would have prevented.
One reply log carries the rest: date received, document type, and the line numbers still unanswered. That last column is the one people skip, and it is the one that makes week two fast.
Verbal answers stay out of the spec column. If a sales rep says on a call that they can hit your target, log it with a date and a name as an open question, never as a filled field. Otherwise the left column slowly fills with the factory's optimism and you lose the ability to tell your own intent from their claim.
Follow-up is a resend of the missing line numbers only, which keeps the comparison intact and quietly signals that the document is being tracked. Watch for the reply that answers a different shoe: a lug pattern built for mud when your terrain line says packed dirt, or a road trainer with a trail upper bolted on. That is not a partial answer. Score it as unanswered and say why.
Week 2 Scores Certificates, Capacity and Test Reports
Week two is where returned paper gets scored, and four checks do most of the work: whose name is on the document, what material or process it covers, whether a test report names the article you asked about rather than making a general statement about the factory's quality system, and whether a capacity figure arrives with a period and a unit attached instead of a word like large.
Paper is not proof. If the certificate carries a trading company's name rather than the name of the factory that will cut your upper, and if the test report describes a generic material instead of the article number printed on your RFQ, then neither document closes the line it was sent to close, however official the letterhead looks.
Nothing on our side has been sampled or sent to a third-party lab, so durability, sun resistance, antibacterial treatment, injury prevention, environmental benefit and performance comparisons that arrive as marketing copy are recorded as unverified and parked against the line that would need a document. They are not findings, and they do not move into the spec column because they sound technical.
Scoring is comparative once documents exist and absolute while they do not. A factory that returns a few named documents and leaves other lines open is ahead of one that returns nothing and answers everything by email, because the first reply tells you what to chase and the second tells you nothing you can act on.
Week 3 Approves the Sample Against the Written Spec
Suppose a sample arrives in week three. Approving it is a written exercise before it is a feel exercise: the pass and fail criteria are copied straight from the day-one fields, so the sample is judged against the terrain mix, goal and mileage band you wrote down, not against how it felt on the office carpet.
The record needs the size set, who wore it, which surfaces were covered, and how far the wear went relative to the mileage band in the RFQ. Then split the outcome in two: fails a written point, or raises a new question for the RFQ. A heel that slides on a rock section is the first kind. An unnoticed lacing detail is the second, and it belongs in a version note rather than in the reject pile.
This is a plan, not a report. No physical sample has been inspected and no third-party test has been run, so nothing here describes a result; it describes what would have to be written down before anyone could honestly use the word pass.
Day 45 Decide With Gaps Still Open
Day forty-five arrives with version two of the RFQ and a score sheet, and usually with gaps still open. Salomon's guide observes that the criteria you use to choose your shoes change with experience, and an RFQ behaves the same way: a first round trains you to ask better questions, which is a reason to version the document and re-score, not a reason to loosen the spec so an incomplete reply can win.
So award only on documented items. An unanswered line for MOQ, capacity, lead-time commitment, certification or test reports becomes a named pre-award condition with an owner and a date, carried into the purchase conversation as an open item. That is a scheduling fact, and treating it as one keeps you from filling the gap with a number nobody sent you.
Back on day one that right-hand column was blank, and it was blank for a reason: it recorded what you did not know. By day forty-five it is a checklist you sign against, item by item, and the only lines that get crossed off are the ones with a document behind them.
