EntriesEntries are not open at the moment.
Standards
Begin with authority, not file length
The Good Taste Awards system contains several document families because one document should not own every rule and every operating detail. The document title, identifier, formal status, version, visibility, owner and approval authority tell you how to use it.
A formal document contains requirements that govern the system. Standards, schedules and applicable preparation requirements are formal according to their registered status.
A category or tasting guide is official but explanatory. It can explain how a product is placed, prepared, experienced and described. It cannot change panel size, candidate thresholds, star meanings, result states or claims permissions.
If a guide and a defined formal source appear to differ, the formal source governs.
Shall identifies a mandatory requirement in defined formal text. May identifies permission. Should appears only where the drafting rules permit a recommendation rather than an obligation.
Public website explanations use ordinary language and do not reproduce every shall. This does not weaken the underlying requirement.
A standards document has an identifier such as GTA-METHOD-001 or GTA-STD-400. The descriptive title helps a human reader; the identifier keeps relationships and citations stable.
Each requirement has a stable anchor such as GTA-STD-400-R007. Link to the requirement when a precise statement matters.
The main document address leads to the active public version. A fixed-version link includes the version identity and preserves that representation for citation.
Use the main document address for the text that applies now. Use a fixed-version link when recording which text supported a decision, analysis or publication.
A standard may be supported by a schedule, module or procedure. A form may collect the evidence required by several standards. Related-document links allow a reader to move from a principle to the detailed requirement that applies it.
A related link is not an authority transfer. A form that records a star does not own the rule that defines the star.
Some source documents contain both public and restricted information. The public library may display an confirmed extract that omits confidential roles, personal data or protected records while preserving the public meaning.
The extract identifies its source and status. The absence of confidential material from the public text does not mean that the material does not exist or that its protections have been removed.
Category guides provide a fluent public account of the product experience. Supporting method documents connect the public category to repeatable preparation and serving requirements.
Do not read a sensory lens as a scoring criterion. Overall Liking remains the sole primary candidate input across categories.
A precise citation includes the document identifier, requirement identifier where applicable, version when fixed meaning matters, and the link to the text consulted.
Example form:
Good Taste Awards,
GTA-STD-400, requirementGTA-STD-400-R007, fixed version as linked.
Do not cite a search-result snippet as the defined text.
defined terms have one registered meaning. The glossary provides the definition, plain explanation and related sources. A page may explain a term in context but shall not silently redefine it.
You do not need to read all standards documents to enter a product or understand a star. The task pages assemble the relevant public guidance in sequence and link to the source when the exact rule matters.
