1 Purpose
This document defines the controlled records and field requirements for Organization and Product Submission Form Pack within the controlled Good Taste Awards standards system.
2 Scope
This document applies to the requirements, decisions, records, controls, and outputs expressly identified under Organization and Product Submission Form Pack. Award scope and exclusions are controlled by GTA-STD-100; this document shall not create an additional award dimension. Operational prerequisites identified here affect assessment validity and never constitute product certification.
3 Authority and interpretation
The Data and Publication Custodian owns GTA-FRM-101; the Standards Authority approves it. Normative verbs, controlled terms, stable requirement identities, policy constants, and generated representations shall be interpreted under GTA-GOV-002, GTA-GOV-005, and the controlled registers.
3.1 Registered relationships
| Relationship | Direction | Related document |
|---|---|---|
collects_records_for | outbound | GTA-OPS-101 |
defines_fields_for | inbound | GTA-DATA-002 |
governed_by | outbound | GTA-GOV-001 |
drafted_under | outbound | GTA-GOV-002 |
4 Requirements
GTA-FRM-101-R001 — Organization record
The Assessment Operations Lead shall capture legal or operating identity, authorized contacts, communication route, and declaration authority.
GTA-FRM-101-R002 — Product identity
The Assessment Operations Lead shall capture public name, internal identifier, flavour, variant, formulation scope, and package format.
GTA-FRM-101-R003 — Category and use
The Assessment Operations Lead shall capture product type, intended consumption, preparation, carrier, and target-population information.
GTA-FRM-101-R004 — Restrictions
The Assessment Operations Lead shall capture ingredient, allergen, alcohol, dietary, storage, and handling declarations for authorized operations.
GTA-FRM-101-R005 — Quantity inputs
The Assessment Operations Lead shall capture unit size, usable yield, preparation loss, and available units.
GTA-FRM-101-R006 — Claim permissions
The Assessment Operations Lead shall capture proposed public identity and mark-use contacts.
GTA-FRM-101-R007 — Entrant declaration
The Assessment Operations Lead shall confirm representativeness, accuracy, authority, and controlled communication.
GTA-FRM-101-R008 — Internal decision
The Assessment Operations Lead shall record eligibility, module, quantity, target population, scope, and acceptance state.
5 Form field specification
| Field ID | Label | Type | Required when | Allowed value or validation source | Visibility | ||
|---|---|---|---|---|---|---|---|
form_instance_id | Form instance | stable identifier | required | system assigned and unique | controlled | ||
subject_id | Controlled subject | stable identifier | required | registered object reference | controlled | ||
form_state | Form state | controlled enumeration | required | open, held, verified, authorized, or closed | controlled | ||
event_sequence | Event sequence | positive integer | required | immutable and increasing within the subject stream | controlled | ||
event_timestamp | Machine event timestamp | machine timestamp | required | system recorded | controlled | ||
entered_by_role | Entering role | controlled role | required | authorized for the field group | controlled | ||
verified_by_role | Verifying role | controlled role | conditional | required before closure | controlled | ||
correction_parent | Correction parent | stable identifier | conditional | required for an append-only correction | controlled | ||
gta-frm-101.product_id | Product identifier | stable_identifier | always | system_assigned | controlled | ||
gta-frm-101.public_product_name | Public product name | text | always | entrant_supplied | public_after_authorization | ||
gta-frm-101.flavour_variant | Flavour and variant | text | always | exact_identity | controlled | ||
gta-frm-101.package_format | Package and product format | structured_text | always | size_container_form | controlled | ||
gta-frm-101.public_primary_category_id | Public Primary Category | controlled_code | always | active_category_taxonomy | controlled | ||
gta-frm-101.product_type_id | Product Type | controlled_code | always | selected_category_product_type | controlled | ||
gta-frm-101.target_population_id | Target Population identifier | stable_identifier | internal_completion | registered_target_population | controlled | ||
gta-frm-101.intended_consumption | Intended consumption | structured_text | always | ordinary_use_context | controlled | ||
gta-frm-101.preparation_instruction | Preparation instruction | structured_instruction | when_preparation_applies | inputs_equipment_sequence_endpoint_service | controlled | ||
gta-frm-101.target_population_description | Target population description | structured_text | always | consumption_possibility_and_relevance | controlled | ||
gta-frm-101.storage_condition | Required storage condition | structured_value | always | condition_and_tolerance | controlled | ||
gta-frm-101.unit_net_quantity | Net quantity per unit | measurement | always | positive_value_and_unit | controlled | ||
gta-frm-101.usable_yield_per_unit | Verified usable yield per unit | measurement | always | positive_value_and_unit | controlled | ||
gta-frm-101.preparation_loss_basis | Preparation loss basis | measurement_with_method | when_preparation_applies | value_unit_method | controlled | ||
gta-frm-101.initial_supply_units | Initial supply units | positive_integer | always | calculated_and_rounded_up | controlled | ||
gta-frm-101.advancement_supply_method | Advancement supply method | enumeration | always | sealed_reserve\ | staged_supply\ | complete_supply | controlled |
6 Completion and interface rules
The Assessment Operations Lead owns completion control. A digital or printable implementation shall preserve field IDs, labels, applicability, allowed values, instructions, and verification states. Conditional fields shall become visible before the user can create a contradictory state. A validation message shall identify the failed rule and the correction required without deleting the original entry.
The final view shall separate supplied facts, calculated values, professional judgments, authorization, and declarations. Restricted identity shall not appear in a blind operational view. Closure shall generate an immutable form-state event and a content integrity value.
7 Conformity and records
Conformity with Organization and Product Submission Form Pack requires evidence comprising the field values, source references, validation results, authorization, and correction lineage. The record for each applicable GTA-FRM-101 requirement shall permit reconstruction without relying on an unrecorded explanation.
Evidence created under GTA-FRM-101 shall use stable identifiers, immutable event sequence numbers, and machine event timestamps. A correction shall be append-only. A nonconformity shall place the affected object in a non-releasable state until its consequence and authorized disposition are recorded. Role combination remains subject to the mandatory separation rules.