Connect enquiry fields to review decisions
Route the translation request through project type, language pair, approximate scope, desired date and reply details. Explain what the form records and avoid soliciting confidential source files by default. A useful confirmation gives a supported next step without accepting the engagement or promising an unverified response time.
Worked example — illustrative data.
| Field | Receiver/use | Acceptance |
|---|---|---|
| Project type | Sales routing | Supported request category |
| Language pair | Qualified service review | Clear input without implied availability |
| Approximate length and date | Scope/feasibility review | Request, not promised delivery |
| Contact email | Reply route | Valid receipt and approved handling |
| Optional context | Reviewer | Do not request confidential files by default |
Write the reviewer’s next action beside each field before deciding whether it is required. Explain supported project scope on the page so a buyer can assess fit before submitting. Keep the confirmation accurate: receipt can be confirmed only when the receiver records it. Provide an appropriate route for existing customers and requests outside the standard form. Test routing with synthetic enquiries and preserve the request reference for follow-up.
Remove a field unless it changes the next review action
For the translation-studio example, map language pair, approximate length and requested date to an actual review decision. If no team uses a field, remove it or explain its optional purpose. Keep confidential source documents outside the initial form unless a reviewed route is necessary. Rehearse a valid request and an unsupported project type with synthetic data.
An unrestricted message field can collect confidential material
A buyer may paste confidential material into an unrestricted message field. Give clear, approved instructions about what to send and use a reviewed secure route if later documents are necessary.
Accept the form when the responsible team receives the required context and the buyer understands the next action. Avoid a response-time or acceptance promise until it is supported.
Continue with Guides for stores, software teams and local businesses, Website design for local businesses and Design a B2B request-for-quote flow.