01
Define the buyer question
Share the product direction, intended application, destination, and review priorities.
Guilin Coordination
A factual handoff from buyer brief to project follow-up
Guilin is the named coordination reference for project follow-up. This statement describes only how the buyer conversation is organized.
Current Boundary
Coordination can be described before proof is published
No visual or record is presented as proof on this page.
The page explains the handoff only. Questions about a selected product, order context, or requested material move to manual review.
Coordination Path
Four steps keep the project scope clear
02
Confirm the product scope
Keep the discussion tied to one of the four current products before packaging or record requests are considered.
03
Coordinate the Guilin handoff
Use Guilin only as the named coordination reference for questions, responses, and follow-up.
04
Record open requests
List the questions that still require manual review. A request does not establish that a supporting file exists.
Next Review
Move from coordination to a scoped request
Use the quality and export review to separate requested information from material that has actually been checked for a defined project.