Filling in the FSVP record forms
What each FSVP form asks for, how the sample answers work, and why a form will not sign with sample text left in it.
Aleph has five FSVP record forms: the supplier evaluation and approval, a completed verification activity, a corrective action, your hazard analysis, and your qualified individual's record. Each one becomes a signed, dated PDF filed as your record. FDA publishes no form for any of them, and the answers are yours: Aleph asks the questions the rule asks and prints what you write.
What FDA asks, box by box
On a wide screen a column beside the form — on a phone, below it — explains the box you are in, in plain words, with the paragraph of 21 CFR Part 1 it serves. Before you click into a box it describes the whole form. For example:
- The food's hazard analysis — 21 CFR 1.505(a)(1)(i): consider the hazard analysis of the food, "including the nature of the hazard requiring a control."
- Who controls the hazards — 1.505(a)(1)(ii): the company that significantly minimizes or prevents each hazard, or verifies that it has been — the supplier, its raw material supplier, or another company in your supply chain.
- The supplier's procedures, FDA compliance record and food safety history — 1.505(a)(1)(iii)(A)–(C).
- Your conclusion and decision — 1.505(a)(2) and (b): you must document the evaluation, and approve the supplier on its basis.
- A verification activity — 1.506(e)(1)(i)–(iv) list what each kind of activity's record must hold (for testing: the lot, the number of samples, the tests and methods, the dates, the results and the lab), and 1.506(e)(3) asks for your own review of the results.
- A corrective action — 1.508(a) asks you to document the actions you take; 1.508(b) adds an investigation of your FSVP when the problem was found some other way than your own verification or reevaluation.
- Signing — 1.510(a)(2): "You must sign and date records concerning your FSVP upon initial completion and upon any modification of the FSVP."
Sample answers
Each open text box shows a sample as its grey hint, and Use sample puts it in the box. A sample is a sentence pattern, never an answer: every fact in it — the supplier, the document, the date, the result, the lab — is a part in [square brackets] for you to replace. For example: We reviewed [supplier name]'s [document, e.g. food safety plan] dated [date]. It covers [what it covers]. We found [what you found]. If the box already has your words in it, the sample is added below them, never over them.
WARNING: A form will not sign while any box still holds sample text in [square brackets]. The box says so, and the line above Sign and file names each one; Aleph's server refuses it too. A signed FSVP record must describe the evaluation or activity you actually did — sample text signed as it is would be a false record. Because Aleph cannot tell a leftover placeholder from brackets you typed, do not use square brackets in a box that offers a sample; use round brackets instead.
Filling in from what is already in Aleph
- Foreign supplier — choose from the manufacturers and exporters on this product's supply chain, so the name is spelled exactly as the checklist spells it. You can still type a new one.
- Who controls the hazards — add a company from the product's supply chain. Aleph writes its name and role; how it controls which hazard stays in brackets for you.
- Verification activities and how often — starts from the activities you scheduled for this supplier, when there are any.
- The food and the hazard analysis start from the product and its hazards, and Signed by from your account. Each is a starting point you can edit, and none is written over something you typed.
- The qualified individual record prints what their roster entry holds — their education, training or experience, and the languages they read (21 CFR 1.503(a)). To change it, use Edit on the FSVP page, then sign.
Insert from your documents
The boxes where you describe what you reviewed, found or did — for example the supplier's procedures, its food safety history, how a problem was found, the results of a check — have Insert from your documents beside them. Choose one of your company's uploaded documents: this product's documents are listed first, then documents about this supplier, then the rest. Aleph adds one line where your cursor was (or under what you typed), built only from what is stored on that document — its type, its file name, who issued it, the date on it, and a test date and expiry date where the type has one. For example: Lab Report "SGS-0412.pdf", issued by SGS Shanghai, dated 2026-03-14, tested 2026-03-10, expires 2027-03-14.
- A value that is not stored goes in as a prompt in brackets, such as [issuer] or [date on the document]. Fill it in from the document.
- A value Aleph's AI read from the document that nobody has confirmed goes in inside brackets, such as [SGS Shanghai]. Check it against the document; if it is right, remove the brackets. To stop it being bracketed next time, confirm or correct it on the document's page.
The form will not sign while either kind of bracket remains, for the same reason as sample text: a signed record must say only what you checked. The line names the document; the box still needs your own words on what it shows.
Optional boxes that say why
Three places let you write down the reason behind a decision. Each is optional, and a record saved before they existed is unchanged.
- Why it does or does not need a control, on each hazard. A hazard analysis asks you to evaluate each hazard and decide whether it needs a control (21 CFR 1.504(a), (c)). The reason prints on your signed hazard analysis when you fill it in; adding or changing it means the signed record no longer matches, so sign the hazard analysis again.
- Why this activity and how often, on a verification schedule. You must determine and document which verification activities a supplier needs and how often (21 CFR 1.506(d)(1)(i)). The reason prints on your written verification procedures. It is left out of the extract a reader outside your company receives, like your notes.
- The supplier's corrective actions, on the supplier evaluation. A supplier's food safety history includes how responsive it is in correcting problems (21 CFR 1.505(a)(1)(iii)(C)).
The evaluation also asks, optionally, whether the supplier's food has been recalled. The rule's list of compliance actions names warning letters, import alerts and other FDA compliance actions (21 CFR 1.505(a)(1)(iii)(B)); a recall is part of the supplier's history. Left unanswered, the record prints "Not answered".
The reevaluation section
When it is turned on for your account, a reevaluation asks more than an initial evaluation:
- Why this reevaluation: Scheduled, the reevaluation due at least every 3 years (21 CFR 1.505(c)(2)), or For cause, because you learned something new about the supplier or the food (21 CFR 1.505(c)(1)). For cause asks what caused it.
- Previous evaluation date: filled in from the newest dated evaluation filed for this supplier, when there is one. Change it if it is wrong.
- What changed since the last evaluation: the supplier's procedures; new import alerts, recalls, warning letters or other compliance actions; the supplier's corrective actions; other new safety information; the hazards the supplier controls; and your verification activities and why. Each is optional; a blank one prints "Nothing entered".
- The outcome: Reapprove this supplier (or with conditions) with the reapproval date, or Stop using this supplier with the date you stopped. If the concerns have changed, the rule asks you to decide and document whether to keep importing from the supplier and whether your verification activities need to change (21 CFR 1.505(c)(1)).
Stopping is filed as a decision not to approve, so the supplier's approval row on the checklist no longer counts an earlier approval until you approve it again.
More detail