Separated burnt-orange terracotta arches and a pale oval stone on an icy blue surface.
Original AI-generated editorial illustration; not a real account, product sale or completed job. View full-size image.

A service enquiry is ready for a useful next decision when the provider can distinguish the requested result, confirmed requirements and unanswered questions. Ask what would change the decision to continue. Record the answer and its source, then leave unresolved conditions open. An interested message alone doesn't establish a suitable job or a promise to buy.

This guide proposes an enquiry-review exercise, not a scoring model or a sales service that Fovza has tested. The examples use an invented request for a community exhibition's printed visitor cards. There is no real buyer, supplier, budget, conversation or sale. The method doesn't authorize unsolicited contact, data collection or an offer on someone else's behalf.

Begin with the decision the enquiry can support

The fictional message says, “We're considering visitor cards for our exhibition. Can you help?” It identifies a possible need, but leaves the deliverable unclear. The sender might want writing, design, printing, or a referral. A provider who treats every interpretation as agreed can promise work that neither person requested.

Write the next decision in ordinary language: can this provider prepare a relevant scope discussion, or is a different service needed? Keep that decision smaller than accepting the job. You can decide that a writing conversation is relevant while still having no basis to confirm a printer's deadline, stock or production capacity.

For this example, the provider's hypothetical service is editing supplied visitor-card wording. Designing the cards and manufacturing them sit outside that draft offer. State that boundary before asking a long list of questions. The prospective buyer can then correct the basic interpretation instead of spending time answering questions for an unsuitable service.

The client onboarding guide begins when a defined assignment needs people, assets and access. Qualification comes earlier. Its useful output may be a short clarification request or an honest explanation that the requested work falls outside the provider's scope.

Ask questions that can change the next action

“Tell me about your business” can produce plenty of detail without resolving the visitor-card request. A sharper question asks which wording already exists and what the sender wants changed. The answer could distinguish proofreading supplied text from researching and writing new exhibition descriptions.

For each question, write the decision it affects. “Who can confirm the final text?” identifies the person needed for a wording decision. “Is the event date fixed?” identifies a timing dependency. Neither answer establishes that the provider is available or that another supplier can deliver the printed cards.

Keep a requirement separate from a preference. The fictional organizer may prefer a folded card but only require a readable visitor handout. If the provider doesn't design printed materials, the fold question belongs with the relevant supplier. It shouldn't silently expand the writing task into production advice.

Don't invent a budget range, purchase deadline or decision-maker's name to complete the sheet. Mark the unanswered question and explain why it matters. Avoid requesting credentials, payment details or unrelated personal information in this preliminary exercise. A small enquiry brief doesn't need a copy of an organization's entire internal planning folder.

Preserve the answer before proposing its interpretation

The sender's wording and the provider's conclusion deserve separate places. “We have a draft list of exhibits” is an answer. “All card copy is ready for proofreading” is an interpretation that may be wrong. The draft could contain only exhibit names, with the descriptions still unwritten.

Google Docs' guidance on suggesting edits describes proposed changes that can be accepted or rejected. That supports a limited document-review choice: present an interpretation as a proposed change instead of replacing the recorded answer without review. It doesn't verify the sender's identity, buying intent or authority to commission work.

In the invented sheet, keep the supplied answer beside a proposed reading: “A draft list exists; completeness of the visitor-card wording is unconfirmed.” The next question asks for an agreed sample or a description of the missing material. Don't describe that sample as received until it actually arrives through an authorized channel.

If someone corrects an earlier answer, retain enough context to understand the change. “The date is provisional” and “the event date is confirmed” lead to different conversations. A newer statement can replace the current working assumption without making the earlier uncertainty disappear from the review record.

Try the brief against conflicting answers

Suppose the hypothetical organizer says the card wording is final, then asks the provider to write descriptions from exhibit names. The sheet should expose that conflict. It can say that the supplied description of the task and the requested work don't yet match. Calling the enquiry “qualified” doesn't resolve the contradiction.

A useful clarification is specific: does the organizer want a language pass on complete text, or newly drafted descriptions? Ask who can answer and what material would distinguish the tasks. Keep a proposed next conversation conditional on that answer. Don't promise a delivery schedule while the size of the assignment remains undefined.

Another invented answer says that a colleague will approve the wording, but the colleague hasn't seen the proposed scope. Record the approval dependency. The person sending the enquiry may be helping collect information rather than placing an order. Neither their enthusiasm nor their email address establishes commissioning authority.

Use an explicit reason for each current outcome: relevant enough for clarification, outside the offered service, or waiting on a named unanswered condition. A numerical score would add an appearance of precision without validated inputs. This exercise supplies no evidence that a particular score predicts a sale or a satisfactory client relationship.

Identify the version behind the recommendation

Google Docs' version-history guidance describes named versions and the access needed to inspect earlier changes. A named stage can identify the enquiry copy used for a recommendation. It cannot prove that an answer was accurate or that the recipient accepted a commercial proposal.

Give the review a plain stage name such as “visitor-card scope questions, awaiting clarification.” Attach its conclusion to the answers present in that copy. If the organizer later changes the requested task, review that change before reusing the previous conclusion. The old brief may still be a useful record, but its recommendation may no longer fit.

Limit the recipient copy to the information needed for the next discussion. A colleague preparing an estimate may need the wording scope and unresolved timing, while unrelated private correspondence adds no useful evidence. Agree who may receive the brief rather than treating a shared document link as permission for wider circulation.

The project change guide covers changes within an assignment. This enquiry brief has a different stopping point: it records whether a defined scope discussion can proceed. It should not quietly become a project plan for work the provider has never accepted.

End with a question or a bounded handoff

The invented example can end with a short response: the request may fit a wording-editing discussion, but the organizer needs to confirm whether complete text exists and who can approve the scope. That is enough to make the next exchange useful. It doesn't claim that the work, budget or timetable has been accepted.

Check the handoff by asking whether another reviewer can locate the requested result, see which answers are direct statements, and find the unresolved condition behind the next action. If the conclusion depends on an assumption that isn't written down, return that assumption to the question list.

If the answer shows that the provider's service doesn't fit, state that narrow reason without inventing an alternative supplier's availability. If the sender wants no further discussion, the brief gives no basis to continue contacting them. Any real contact process needs its own authorization and applicable rules; this document doesn't supply them.

Retain the current decision and the information that could change it. A useful qualification brief can finish with an unanswered question. Its value is that the question is visible before anyone mistakes a possible assignment for a confirmed commitment.