How we test, develop and verify food.fast recipes

The non-negotiable rule

A page does not say that a recipe was cooked, tasted, compared with the original or independently tested unless a dated record identifies who did it, what version they used and what changed. A plausible story is not evidence.

The same rule applies to authorship. Until a contributor supplies verifiable details and a real photograph they have approved, the page uses the food.fast editors organisational byline. It does not invent a chef, nutritionist or barista to make the page look authoritative.

What the automated checks prove

The publication gate can verify structural facts about every recipe:

• every ingredient has a numeric quantity or an explicit count unit;
• every quantity survives the 1×, 2×, 4× and 8× controls in cups and metric;
• solid ingredients are converted with an ingredient-specific density rather than a single cups-to-grams number;
• every method step has a title, an instruction and enough detail to act on;
• nutrition arithmetic is internally consistent within a stated tolerance;
• costs, images, internal links, headings and structured data resolve;
• openings and discussion headings are not duplicated across the corpus;
• safety language is present where a recipe uses a substantial volume of hot oil.

These checks establish usability and internal consistency. They do not prove that a recipe tastes like a restaurant product, and the page must not pretend they do.

What must be shown on the page

Every recipe leads with the outcome it is designed to produce, followed by the method and quantities. Troubleshooting entries name a likely cause and a correction. Ingredient notes explain choices that materially change texture, flavour or handling. Equipment limits and commercial processes that cannot be reproduced safely at home belong before the method, not in a disclaimer after it.

Cost and nutrition figures link to their methodology. External factual claims that affect safety, health or legal decisions require an authoritative source. AI-generated food imagery is labelled as illustration and is never offered as proof of a cooked batch.

What a documented cook record must contain

When first-hand testing is carried out, its record must contain:

1. the recipe slug and version or commit being followed;
2. the date and the tester's verified identity;
3. ingredient brands or substitutions that could affect the result;
4. equipment, batch size and measurement system;
5. observations and photographs from that cook;
6. every change made to the published page as a result.

Only then may the page make a first-person testing or comparison claim. A second cook is valuable, but the site will not claim one merely because that would sound reassuring.

Corrections and reader reports

If a quantity, temperature or technique changes materially, the page's review date changes as well. Reader reports are leads to investigate, not testimonials to publish as fact. If something fails, send the exact recipe, equipment and result so the report can be reproduced and corrected.