Custom Cage Enquiry Revisions: Send One Current Brief
November 13, 2026 · TrapSir
A custom cage enquiry is easier to quote when it has one identifiable current brief and a clear account of requested changes. Give the brief a revision reference, separate alternatives and identify superseded attachments. This helps a supplier review the intended request without treating scattered emails or an unconfirmed design proposal as an agreed specification.
Make the current request easy to identify
Project enquiries often develop through several conversations. One colleague changes a dimension, another adds packaging information and a third forwards an older drawing. Each message may be understandable by itself, yet the collection may leave the supplier unsure which combination to assess. The purchasing team should bring those inputs into a single current reference set before requesting an updated quotation.
Use a brief title, revision identifier and issue date that colleagues can repeat accurately. State who coordinates the buyer's questions. The reference does not need an elaborate document system; it needs to distinguish the current request from earlier material. Avoid calling several different files “final,” because that word provides little help when another change follows.
A catalogue model such as the TS-LC-003 cage reference can establish the starting point. Specify whether you are enquiring about that listed model or using it only as a reference for a proposed change. A request based on a catalogue model does not establish that a different configuration is available or technically accepted.
Separate the baseline, requested change and open question
The baseline tells the reviewer what the buyer is starting from. The requested change tells the reviewer what the buyer wants assessed. An open question identifies information the buyer cannot yet settle. These three roles should be visible in the brief. Otherwise, a question such as whether a feature is possible can be mistaken for a fixed requirement.
Describe the reason for a change where it helps review. For example, an enquiry may seek a different arrangement because of a buyer's handling or storage constraints. Explain the constraint without prescribing an unverified engineering solution. That gives the supplier context for responding and leaves feasibility, implications and alternatives available for discussion.
The custom project enquiry form provides fields for describing proposed requirements and reference information. Completing those fields starts a review; it does not confirm that every requested feature can be supplied. Carry the same revision reference into the form and its attachments so the request remains understandable when it reaches another reviewer.
Build a change list that accompanies the full brief
A change list explains what has moved since the previous enquiry. It should accompany a complete current brief rather than forcing the supplier to reconstruct the request from individual edits. Keep unchanged requirements in the current brief, and mark genuinely undecided fields as open. This preserves both the whole request and the reason an updated review is needed.
| Part of the enquiry | Useful revision information | Confusion to resolve |
|---|---|---|
| Reference product | Starting model and whether it remains the baseline | A new model reference appearing only in an email |
| Technical request | Changed field, previous request and current proposal | Two attachments showing different configurations |
| Quantity and destination | Current enquiry quantities and delivery destination | A commercial update omitted from the technical brief |
| Alternatives | Separately named options and their common requirements | Features from different options being combined |
| Attachments | Current file list and documents explicitly superseded | An older reference being used as the active request |
| Open questions | Issue, buyer contact and response needed | An unresolved proposal being treated as confirmed |
Keep alternatives separate enough to compare
Sometimes the buyer wants two proposals assessed. Give each option a stable label and say which requirements are common. Identify the fields that differ. If the team later prefers one option, state that choice in the next current brief instead of leaving both options active with a vague instruction to use the latest discussion.
Do not combine the dimensions from one alternative with the mechanism request from another unless that combination is itself a separately identified proposal. A clear option list reduces accidental combinations and makes supplier questions easier to answer. It also helps the buyer understand whether two quotations are responding to the same proposed scope.
Keep “preferred,” “required” and “subject to review” distinct. A preferred feature may permit alternatives; a requirement may need a defined acceptance basis; a proposal under review is unresolved. These labels explain the buyer's intent. They do not replace the supplier's assessment or turn an unconfirmed feature into an available product.
Control attachments without losing the review history
List current attachments by their actual file names and revision references. Identify which earlier files they supersede, including any photographs used only for context. Retain the history internally, but make the active reference set obvious to the supplier. A reference photograph should have a short note explaining the particular detail it illustrates and any features it does not define.
Where a drawing and written brief disagree, resolve the disagreement before asking the supplier to choose an interpretation. If the team cannot yet resolve it, identify the conflict as an open question. The same principle applies to mixed units or differing quantity statements: explain the intended basis instead of relying on the reviewer to infer priority.
After sending a revision, ask the supplier to identify the brief and option being reviewed. Review any response against that reference. If a quotation arrives without a clear connection to the current request, ask for clarification before circulating it as the answer to the revised enquiry. A shared reference helps locate misunderstandings while they are still questions.
Frequently asked questions
Does sending a revised cage enquiry mean the proposed design has been accepted?
No. A revised cage enquiry communicates the buyer's current request for review. It does not establish feasibility, availability, price or supplier acceptance of the proposed configuration. Ask the supplier to identify what has been reviewed, which questions remain open and what reference any resulting proposal uses. Keep requested features separate from the configuration that is eventually confirmed.
How can a buyer prevent two custom cage alternatives from being mixed together?
Give each alternative a stable label, identify its differences and list the requirements shared by both. Send one current brief that clearly separates the options, with matching attachment references. If the team proposes a combination of features, name that combination separately. When reviewing a supplier response, check that its option reference matches the proposal the buyer intended to assess.
What should a buyer send when changing an enquiry before quotation?
Send the complete current brief, its revision and date, a short change list and the active attachment list. Include the current quantity, destination and buyer contact as well as technical changes. Identify superseded files and unresolved questions. Explain whether the supplier should replace the earlier review or assess an additional option, then ask which reference the resulting quotation will use.
Prepare one coordinated enquiry
Before requesting an updated price, have the purchasing and technical reviewers agree on the current reference set. Use the quotation preparation page to submit the model or proposed scope, quantities, destination and revision reference. A coordinated request helps the next discussion focus on the proposal's substance and the questions that still need an answer.