Production records need to identify the grower, plot, crop and handling activities they represent. Review changes through both practical traceability and the applicable scheme's scope rules.
Record location, previous use, crop, water source and management responsibility. Check the scheme's requirements for scope changes and assessment. Make clear when the plot entered the system and under which scope each harvest will be supplied.
Shared management documents are useful, but applications must remain traceable to each grower, plot and batch. Central records must reflect field practice. Assign responsibility for new-member approval, internal checks, corrective follow-up and movement of products through the group.
Examine their scopes, country-specific rules and customer acceptance separately. Compliance with one does not automatically establish another status. Identify the product, production method and destination, then review the relevant scheme's authorised bodies and current application conditions.
Distinguish irrigation, washing and other uses, product contact and source variability. Sampling location and date should represent the conditions of use. Link the analysis to risk assessment, control planning and the response to deviations instead of treating it as a stand-alone result.
Define responsibilities for tasks, hygiene information, equipment and working conditions. Keep product-contact risks and social compliance considerations distinct. The scope of an additional assessment such as GRASP must not be confused with the basic production certification scope.
Match dispatched and received batch identities, quantities and processing dates. Mixing, splitting, repacking and loss records should preserve batch links. Clarify how packing falls within the scheme and which records the external facility will make available.
Review differences in crops, weather, water sources, plant protection and harvest schedules. Previous nonconformities inform the new plan. Record dates must reflect actual operations; previous-season data must not imply that new-season activities have already been completed.
Check the product description, grower or group identity, covered activities and current status together. Similar names can conceal different production and handling scopes. Compare the buyer's requested scheme version and acceptance conditions with the official record and supply contract.
A fictional grower group adds a greenhouse and an external packing facility. It updates member and plot records, reviews water use and traces batches through packing. A shared policy file does not prove those checks occurred. The effects on internal controls and certification scope are assessed separately.
This is a fictional example, not an actual client case or conformity decision.
Share the subject, organisation or product, target market, current evidence and target date. The team can then separate consultancy, official fees, independent evaluation and realistic timing.
TRTürkçe
ENEnglish
AZAzərbaycanca
UZO‘zbekcha
ARالعربية
FRFrançais
DEDeutsch
RUРусский