Buyer status-question governance is the operating discipline that decides which questions can receive an approved answer, which source supports that answer, and when a person must take over. It is not a script library. For preconstruction teams, each answer needs current buyer and unit context, an accountable source, and a policy for escalation when the question involves judgment, a commitment, a regulated topic, or conflicting records.
Key takeaways
- Classify questions by operational domain before writing or automating answers.
- Make the source and freshness of an answer visible to the person sending it.
- Use approved answer patterns for routine status, not for exceptions or commitments.
- Escalate uncertainty, conflicting records, legal/financial questions, and changes to contractual terms.
A practical question taxonomy
| Question type | Example | Safe operating response |
|---|---|---|
| Routine status | “Did you receive my document?” | Use the current documented receipt state and next step |
| Process guidance | “Where do I upload this?” | Send the approved instruction and record the request |
| Milestone context | “What happens after review?” | Explain the published process without promising a date |
| Financial status | “Has my wire cleared?” | Use finance-approved context or route to finance |
| Contractual, legal, or exception request | “Can you change this term?” | Escalate to the authorized owner; do not interpret or promise |
The taxonomy gives a team a common language for routing. It also makes clear that a fast answer is not helpful if it comes from a stale record or creates an unauthorized commitment.
The answer receipt
For routine questions, attach an internal answer receipt: the source used, its last-known update, the approved response pattern, the sender, and any next action. The buyer may not see the receipt, but the operating team needs it to explain how an answer was produced and to correct it if source context changes.
A governance checklist
- Identify the question category and buyer/unit context.
- Retrieve only the designated source for that category.
- Check whether the source is current enough for the project policy.
- Use an approved answer pattern that does not add a promise or interpretation.
- Record the communication and requested follow-up.
- Escalate if the source is missing, stale, contradictory, or outside the sender’s authority.
Human review and escalation
No workflow should decide a legal interpretation, underwriting outcome, finance adjustment, construction commitment, or contractual exception. Asterisko can route a question with its relevant records and preserve the history; the authorized team member makes the decision. This lets automation reduce searching and repetitive drafting while keeping responsibility with people.
Where Asterisko fits
See the buyer servicing workflow for the workflow model, and the guide to answering buyer questions for day-to-day practice. For questions that depend on payment state, use the ERP reconciliation guide.
