The documents we ask for, and what each one is.
When you buy a review or a build, we ask you to send specific records. You only ever send the records for the specific review or build you buy — never all of these at once, and we send you the exact list when you order. Here is the plain-English version of each one: what it is, why we ask, what not to send in its place, and an example of what the record type looks like — not a model to copy.
Classification & market pathway
A description of a product or ingredient — what it is and what it is made of, how it will be used, and the claims and marketing it will carry.
Why we ask: it establishes how the product is classified — drug, supplement, cosmetic, conventional food, food additive, or new dietary ingredient — and whether a lawful market pathway is available.
Requested for: Classification & Viability
example
The evidence that a route to market is available and defensible — history or common use in food, presence in the food supply, published safety literature, and any prior FDA determinations or notifications — supporting a GRAS, NDI, food-additive, or novel-food (EU/UK) pathway.
Why we ask: to show whether the chosen pathway is actually supported by evidence — a defensible GRAS basis, or a genuine NDI versus a dead-end route — as distinct from whether the product is simply safe.
Don’t send: A marketing dossier or a supplier’s sales sheet in place of the evidence — we need the documented history, literature, and prior determinations behind the route.
Requested for: Classification & Viability
example
The claims and assurances you want on the label — structure/function, nutrient-content, health, or general marketing claims — as you intend to state them.
Why we ask: so the work can draft claim language written to be defensible under the labeling and claims rules that apply, and flag claims that look unsupported or high-risk.
example
Label & packaging
The finished product’s label and packaging artwork — the files as they will appear on the product.
Why we ask: it carries every claim and declaration the product makes to consumers and regulators.
Don’t send: A low-resolution photo or a rough mockup — send the final print-ready artwork or proof, with all panels legible.
Requested for: Product Labels
example
The product’s packaging configuration and container-closure construction — container and closure type and materials, any food-contact material or liner, the fill and net-contents basis, the seal specification, and the package dimensions.
Why we ask: it governs the net-quantity declaration and the panel-size-dependent type-size and placement rules on the label, and the container-closure integrity and food-contact suitability a packaging review depends on.
example
Specifications & lot records
The defining document for a product or ingredient: identity, composition, and the limits and acceptance criteria it must meet.
Why we ask: it is the statement of what the product is supposed to be — the baseline everything else is measured against.
Don’t send: A supplier marketing sheet or a certificate of analysis in place of the spec — we need the specification itself (the limits the product must meet), not one lot’s results.
Requested for: Specifications · Product Labels · Cosmetic Safety Substantiation
example
A document reporting the analytical results for a specific lot, measured against its specification.
Why we ask: it shows whether a given lot’s tested results met its specification.
Don’t send: A raw-material or ingredient COA, a supplier spec sheet, or a certificate with no measured values — we need the finished-lot results for the lot you’re releasing.
Requested for: Specifications
example
The completed, lot-specific record created by executing the master manufacturing record for one batch — what was actually made and done, recorded as it happened.
Why we ask: it shows whether a specific lot was actually made according to its master manufacturing record.
Don’t send: The blank master, a different lot’s record, or a draft — we need the signed, completed record for this exact lot.
Requested for: Specifications · Product Labels
example
The master, product-specific manufacturing instructions — the controlled recipe and steps every batch must follow, including the processing method and whether the product is made on dedicated or shared equipment.
Why we ask: it defines what every batch is required to contain and how it must be made.
Don’t send: Filled-in batch records, older revisions, or drafts — we want the current approved master.
Requested for: Specifications
example
Stability & shelf life
Study data showing how a product’s attributes hold up over time and under defined storage conditions.
Why we ask: to confirm whether claims and specifications still hold through the product’s shelf life.
Don’t send: A one-line shelf-life statement or a summary conclusion in place of the data — we need the actual pull-point results, the numbers behind the claim.
Requested for: Stability
example
A written summary of the stability program conducted for a product, including the testing laboratory, methodology basis, and the shelf-life claim it supports.
Why we ask: to confirm a documented stability program exists and the shelf-life or expiration date claim is grounded in it.
Don’t send: A single lot’s certificate of analysis, or a shelf-life date with no study behind it — we need the stability program summary, not one release test.
Requested for: Stability
example
The formal protocol for a stability study — storage conditions, study duration, pull-point schedule, and parameters tested.
Why we ask: to confirm the study was designed to actually prove the claimed shelf life.
Don’t send: The finished study summary or the raw results in place of the protocol — we need the study’s design, the plan set before the data came in.
Requested for: Stability
example
Documentation that the container-closure system has been qualified to maintain the required stability conditions — moisture, oxygen, and UV barrier — through the claimed shelf life.
Why we ask: to confirm the packaging was independently validated as fit for the stability claim, not merely specified.
Don’t send: A packaging spec sheet or a supplier brochure in place of qualification data — we need evidence the package was validated to hold the product stable, not just described.
Requested for: Stability
example
Analytical methods
A test method not drawn from a public compendial source (such as USP, AOAC, or APHA) — an in-house procedure, a contract lab’s proprietary method, or an adaptation of a published one.
Why we ask: when results were generated by a method that cannot be looked up, the method itself has to be reviewed for the analysis to be complete.
example
The report establishing that a test method was validated (USP <1225>, ICH Q2(R2)) — accuracy, precision, specificity, detection and quantitation limits, linearity, range, and robustness, with the protocol and acceptance criteria.
Why we ask: to confirm the method that generated your results was formally validated to an applicable standard and matches its own protocol.
Don’t send: A single test result or a certificate of analysis in place of the validation — we need the method validation report and its protocol, not one sample’s data.
Requested for: Method Validation
example
The underlying experimental data and statistical output behind a method validation — instrument raw data, analyst worksheets and calculations, and the statistics the reported performance was derived from.
Why we ask: to confirm the validation report’s claims actually reproduce from the raw numbers rather than being asserted in the summary.
Don’t send: The validation report or its summary tables in place of the source data — we need the raw data and statistics behind the numbers, so we can recalculate.
Requested for: Method Validation
example
The report establishing that a method performs acceptably under the actual conditions of use — transferred to a receiving lab (USP <1224>) or verified for the specific product matrix (USP <1226>).
Why we ask: to confirm a method that is sound in principle actually works in the lab and on the product where it is used.
Don’t send: The original validation report in place of the transfer or verification — we need the record that the method works in your lab and on your product.
Requested for: Method Validation
example
Cleaning validation
The document that defines how equipment or a process is cleaned and shows it was validated — the procedure, what is being removed, the acceptance criteria, the sampling plan, and the validation-run report.
Why we ask: to confirm a defined, approved cleaning process exists and has been formally validated to work.
Don’t send: A cleaning SOP alone, or a single cleaning log, in place of the validation — we need the validation protocol and its report, not just the procedure.
Requested for: Cleaning Validation
example
The actual results behind a cleaning validation — residue test results, recovery study data, and visual-inspection records from the validation runs.
Why we ask: to confirm the cleaning was actually tested and the measured results meet the acceptance criteria, not just that a protocol exists.
Don’t send: The protocol or the summary conclusion in place of the data — we need the actual residue, recovery, and visual results, the numbers behind the pass.
Requested for: Cleaning Validation
example
The scientific justification for the cleaning acceptance limit — the health-based exposure limit (HBEL/PDE), worst-case product selection, the maximum allowable carryover (MACO) calculation, and the recovery factors.
Why we ask: to confirm the cleaning pass/fail limit is derived from health-based science and worst-case reasoning, so a passing result supports that carryover to the next product stays within a health-based safe limit.
Don’t send: The acceptance limit as a bare number with no derivation — we need the health-based reasoning behind it, not just the pass/fail line.
Requested for: Cleaning Validation
example
The ongoing records that show cleaning stays effective after validation — routine verification results, periodic monitoring or re-qualification data, and production logs.
Why we ask: to confirm the validated cleaning state is maintained in day-to-day production, not just at the original validation.
Don’t send: The original validation package in place of routine records — we need what shows the cleaning is staying in control after validation.
Requested for: Cleaning Validation
example
Equipment qualification
The IQ/OQ/PQ protocols and reports showing a piece of equipment was installed correctly, operates within its specified ranges, and performs under real conditions.
Why we ask: to confirm the equipment was formally qualified as installed, operating, and performing as intended.
Don’t send: An OEM instrument certificate or a datasheet in place of the qualification — we need your IQ/OQ/PQ protocols and reports, not the vendor’s cert.
Requested for: Equipment Qualification
example
The recorded IQ/OQ/PQ test results, measurements, and challenge-test data captured when the qualification runs were performed.
Why we ask: to confirm the equipment was actually tested and the results meet the acceptance criteria, not just that a protocol exists.
Don’t send: The protocol or the summary conclusion in place of the data — we need the actual executed results and measurements.
Requested for: Equipment Qualification
example
The rationale behind the qualification’s pass/fail bar — how the OQ challenge ranges and PQ worst-case loads trace to the user requirement specification and risk assessment, and the calibration and traceability of the reference instruments.
Why we ask: to confirm the acceptance criteria are justified and the measurements were made with calibrated, traceable instruments.
Don’t send: The protocol or results alone — we need the rationale for the ranges and worst-case, and the calibration traceability behind the measurements.
Requested for: Equipment Qualification
example
The records that show equipment stays qualified after initial qualification — requalification after change or repair, periodic review, and change-control and maintenance records.
Why we ask: to confirm the validated state of the equipment is maintained over time.
Don’t send: The original qualification package in place of ongoing records — we need what shows the equipment stayed qualified as it was maintained and changed.
Requested for: Equipment Qualification
example
The paperwork that comes with the equipment — make and model, manuals and drawings, materials of construction, the utilities it needs, and any vendor or factory test paperwork.
Why we ask: it describes the actual machine, so the qualification can be built around it.
example
Process validation
The document that plans and records process validation — proof the commercial process runs under normal conditions and consistently makes in-spec output. Under drug GMP it is the PPQ protocol and report; under 111 / food / cosmetic GMP it is the process-verification or blend-uniformity study and report.
Why we ask: to confirm the commercial manufacturing process is validated to make in-spec output, at the depth the regime requires.
Don’t send: A single batch record, or a one-line ‘process validated’ statement — we need the validation protocol and its report, not one production batch.
Requested for: Process Validation
example
The actual executed results — run and batch records, in-process and release results, and sampling data captured when the validation was performed (PPQ batch data, or blend-uniformity sampling results and RSD).
Why we ask: to confirm the validation was actually run and the results meet the acceptance criteria, not just that a plan exists.
Don’t send: The protocol or the summary conclusion in place of the data — we need the actual executed results across the runs, the numbers behind the pass.
Requested for: Process Validation
example
The rationale behind the validation’s pass/fail bar and scope — how acceptance criteria trace to the real critical quality attributes, and the statistical and risk basis for the number of runs and the sampling plan.
Why we ask: to confirm the criteria and run count are scientifically justified — a pass means the process is proven, not an arbitrary three-batch exercise.
Don’t send: The protocol or the results alone — we need the rationale for the criteria and the run count, the ‘why this bar and this many batches.’
Requested for: Process Validation
example
The records that show a validated process stays in control after validation — ongoing verification trending of process parameters and quality attributes, plus revalidation triggers and change control.
Why we ask: to confirm the process stays in control during routine production, not only during the validation runs.
Don’t send: The original validation package in place of ongoing records — we need what shows the process stayed in control after validation, in routine production.
Requested for: Process Validation
example
The pre-PPQ evidence set — process design and characterization, critical process parameter and quality attribute definitions, the control strategy, and the status of prerequisites (equipment qualified, methods validated, governed MMR, data integrity).
Why we ask: to judge whether a process is actually ready to enter PPQ.
example
Your intended PPQ approach before any batch is run — the planned number of validation batches and its rationale, the sampling plan, and the acceptance-criteria approach.
Why we ask: to judge whether the PPQ you are about to run is well-designed before you commit the cost.
example
Safety & toxicology
The compiled file documenting that a product is safe for its intended use — the safety assessment, toxicological review, claims-substantiation data, preservative-efficacy or micro data, and supporting studies.
Why we ask: to show whether the evidence that the product’s safety and claims are substantiated has been assembled and can be produced for the formula as currently made.
Don’t send: An ingredient supplier’s safety sheet or a single COA in place of the file — we need your compiled safety substantiation for the finished product.
Requested for: Product Labels · Cosmetic Safety Substantiation
example
The toxicological dataset behind a cosmetic safety conclusion — per-ingredient hazard data and points of departure, exposure inputs (use level, frequency, retention, skin area), and the Margin of Safety calculation.
Why we ask: to confirm the safety conclusion is actually proven by the underlying toxicology and exposure math, not merely asserted.
Don’t send: The safety conclusion or the file’s summary in place of the data — we need the hazard data, exposure inputs, and the Margin-of-Safety math behind it.
Requested for: Cosmetic Safety Substantiation
example
The finished product’s microbiological safety evidence — preservative-efficacy (challenge) test results and microbial-limits data showing the product resists contamination in normal and foreseeable use.
Why we ask: to confirm the product-level safety evidence holds up — that the finished product resists microbial growth under normal and foreseeable use.
Don’t send: A raw-material micro spec or a finished-product release micro test in place of the challenge study — we need the preservative-efficacy (challenge) test.
Requested for: Cosmetic Safety Substantiation
example
Environmental monitoring
The written program for monitoring a production environment for pathogens and hygiene-indicator organisms — zones, sampling sites, frequency, target organisms, methods, and corrective-action and trending procedures.
Why we ask: to see what the facility intends to do to detect and control environmental contamination, and whether that plan is complete and compliant.
Don’t send: A single day’s swab results or a lab quote in place of the program — we need the EMP plan and zone map, not one set of results.
Requested for: Environmental Monitoring
example
The facility-specific risk assessment and zone and flow map that justify why the program samples the sites, frequencies, and organisms it does.
Why we ask: to confirm the monitoring design is defensibly tied to the facility’s layout, product, flow, and history.
Don’t send: The sampling plan alone with no rationale — we need the risk assessment and zone map that justify why you monitor the way you do.
Requested for: Environmental Monitoring
example
The facility’s executed monitoring results over time, including indicator and pathogen findings and the trending analysis.
Why we ask: to confirm the program is actually executed as written and that results are tracked, trended, and acted on.
Don’t send: The plan or a summary in place of the data — we need the actual monitoring results and trends, taken on schedule.
Requested for: Environmental Monitoring
example
The records of how the facility investigated environmental positives or excursions — expanded and vectoring sampling, root-cause analysis, corrective actions, and effectiveness checks.
Why we ask: to confirm the facility finds, eliminates, and prevents recurrence of environmental contamination.
Don’t send: A bare positive result with no investigation — we need the records of how you vectored, corrected, and verified it stayed fixed.
Requested for: Environmental Monitoring
example
The records of periodic program reassessment and the changes made over time in response to trends, changes, and events.
Why we ask: to confirm the program stays current and adapts — that its effectiveness is maintained over time.
Don’t send: The original plan in place of the reassessment history — we need what shows the program is kept current, not frozen at first write.
Requested for: Environmental Monitoring
example
Facility, process & quality systems
A drawing of the facility showing rooms, equipment placement, drains, and how people, product, and air move through the space.
Why we ask: it is the spatial basis for hygienic zoning and for where environmental samples should be taken.
example
The step-by-step flow of the production process from incoming materials to finished product, including any kill or lethality step and the points where product is exposed to the environment.
Why we ask: it is the basis for choosing target organisms and risk-ranking zones.
example
A written agreement between a brand or own-label distributor and a contract facility that allocates each party’s GMP responsibilities — manufacturing, testing, release, specifications, change control, deviations and CAPA, complaints, recall, and records.
Why we ask: to see who is responsible for each GMP activity in an outsourced relationship, and whether every responsibility is clearly and completely allocated.
Don’t send: A commercial supply or manufacturing-services agreement with no quality section, a blank template, or an unsigned draft — we need the executed quality agreement that governs this product.
Requested for: Quality Agreements
example
This page is general information about records used in regulated industries. It is not regulatory or legal advice for your specific product and creates no attorney-client relationship. Any Regulatory Options engagement is defined by its own written scope; you remain responsible for your product’s compliance.