Secure a Supply Input

Confirm that a required input will be available at the promised time and cost. A quote is not receipt.

Use when. An external or internal input could block delivery.

Do not use when. You want the model to place an order, select a supplier, approve spend, or accept risk.

Your input. Delivery requirement and acceptance test; specification and quantity; need-by date and budget; candidate source and quote; permitted fallback; named supply owner.

Your quality check. Specification, quantity, availability, landed cost, need-by date, and fallback are explicit — or the constraint is returned. Owner decision stays blank.

Put this to work

Verify one required supply input

For the accountable supply owner

Copy this prompt. Paste it with the relevant source material into Claude, ChatGPT, or any AI assistant, then review the result before acting.

# Role and job
Help an accountable supply owner verify one input needed for a delivery promise.

# Outcome
Produce a Supply Commitment Brief. Success means specification, quantity, availability, need-by date, landed cost, conditions, evidence time, and fallback are explicit—or the constraint is returned before commitment.

# Inputs
- Delivery requirement and acceptance test: [paste]
- Input specification and quantity: [paste]
- Need-by date and approved budget: [paste]
- Candidate source, quote, lead time, and conditions: [paste]
- Permitted alternatives and fallback: [paste]
- Accountable supply owner: [name or role]

# Boundaries
Use only supplied current evidence. You may compare quotes and expose conflicts. Do not place orders, select suppliers, approve spend, substitute inputs, accept terms, or accept risk.

# Output
Return: requirement; source evidence and timestamp; specification match; quantity; total landed cost; availability and lead time; conditions; risk; fallback; recommendation; unknowns; and blank owner decision.

# Stop and recovery
Stop for stale availability, unmatched specifications, unclear landed cost, unapproved terms, or no recovery path. Return the constraint and exact evidence or approval needed.

# Final check
Verify the proposed commitment meets the delivery acceptance condition and need-by date without exceeding supplied authority.

Human decision — cannot be delegated. Commit, return the constraint, or stop. AI compares quotes only. No clinic CTA.

Candidate teaching projection; contextual recipe unproved. The JTBD Ledger keeps this route as a gap until a contextual owner accepts the method and retains decision evidence.

Outcome

A verified supply commitment or an explicit constraint before delivery is promised.

Use When

Use when a material, service, capacity, or supplier dependency can constrain delivery.

Inputs

Delivery requirement, specification, quantity, need-by date, budget, candidate source, lead time, alternatives, and supply owner.

Recipe

Copy the prompt. Compare current quotes to the frozen requirement. Leave the owner decision blank.

Human and AI Control

An assistant may compare supplied quotes and expose conflicts. It may not place an order, select a supplier, approve spend, or accept risk. Stop for stale availability, unmatched specifications, unclear landed cost, or no recovery path.

Output and Handoff

Hand a confirmed input to deliver promised work. Return a constraint to the promise owner before commitment.

Evidence and Stop

Stop when any material condition is unknown or inconsistent. A quote does not prove receipt, fitness, or customer value.

Reliability

Skill and tool: supply commitment verification using current quote and specification comparison tools. The commitment brief is the pattern; dated verification and owner approval are the protocol. Retain source snapshots and variance as evidence. Accept only a verified input or explicit constraint.

Correct the specification, source, lead-time assumption, or fallback after an exception. Return delivery consequences to the delivery method.