RecipeWanted Quality & Safety Standard

How we approach reliable cooking information.

This standard explains how RecipeWanted approaches editorial quality, practical cooking accuracy, responsible claims, AI-assisted workflows, corrections and the boundaries around food and cooking guidance.

It applies across RecipeWanted recipes, Cooking Education, editorial content and other published cooking resources, while allowing the level of review to reflect the subject and the potential consequence of getting it wrong.

Found something that may need reviewing? Contact RecipeWanted.

Scope of this standard: RecipeWanted provides general cooking, recipe and food-education information. It does not represent personalised medical or dietetic advice, allergy diagnosis, legal advice, formal catering compliance certification, or approval by a government or regulatory body.

Why This Standard Exists

Clear standards make growth easier to trust.

RecipeWanted publishes across different types of cooking content, from recipes and practical education to editorial articles. A shared standard creates a consistent basis for deciding what good information looks like, where extra care is needed and how published material should be reviewed over time.

01
Consistency

Different content should follow the same core expectations.

Recipes, Education guides and editorial content may serve different purposes, but clarity, practical usefulness, responsible wording and editorial accountability should remain consistent across RecipeWanted.

02
Proportionate Review

The consequence of an error should affect the level of scrutiny.

A minor wording issue does not carry the same consequence as incorrect information involving allergens, storage, reheating or another safety-sensitive subject. The standard allows review depth to reflect that difference.

03
Transparency

Readers should be able to understand the boundaries of the platform.

Publishing the standard makes RecipeWanted's approach easier to assess without requiring users, educators, organisations or partners to infer how content, claims and corrections are handled behind the scenes.

04
Improvement

Published content should remain reviewable rather than treated as finished forever.

Cooking information, references, links and platform practices can change. A visible standard creates a basis for correcting, clarifying and improving content when better information or a material issue is identified.

How We Handle Cooking Information

Practical guidance with clear limits on certainty.

RecipeWanted aims to explain what a cook needs to know without pretending that every kitchen, ingredient, appliance or personal circumstance will produce an identical result. Guidance should be useful enough to act on and careful enough to show where conditions can change the answer.

01
Recipe Coherence

Ingredients, method, timing and equipment should agree.

A recipe should not require an ingredient that is missing from the list, introduce an unexplained step, contradict its own timing, or describe a result that does not make practical sense for the method being used.

02
Technique

Explain the reason behind a step when it improves the result.

Useful guidance can explain why browning develops flavour, why dough rests, why a sauce needs gentler heat or why weighing matters in some baking. The explanation should help a cook make a better decision rather than add technical detail for its own sake.

03
Substitutions

Ingredient swaps are treated as conditional, not automatic.

Replacing an ingredient can affect flavour, moisture, structure, rise, browning, cooking time or storage behaviour. Where a swap is suggested, RecipeWanted should explain meaningful trade-offs rather than imply that every substitute is an identical replacement.

04
Safety-Sensitive Information

Greater consequence means greater caution.

Storage, reheating, allergens, hygiene and other safety-sensitive subjects require more careful wording than ordinary technique advice. Guidance should identify important limitations and direct users toward appropriate labels or current local guidance when needed.

05
Dietary & Health Context

Food information should not be turned into medical certainty.

RecipeWanted may discuss ingredients, dietary characteristics and general food context, but should not present recipes as diagnosis, treatment, disease prevention or personalised nutrition advice, or guarantee suitability for a particular allergy.

Editorial Boundary

What RecipeWanted can explain — and where the claim should stop.

These examples show the difference between useful cooking education and a level of certainty the platform should not imply.

Area RecipeWanted Can Explain RecipeWanted Should Not Claim
Cooking methods How heat, timing and technique commonly affect texture, flavour, browning and doneness. That one instruction will produce an identical result across every appliance, ingredient and kitchen.
Substitutions Why a replacement may work, what may change and when the result needs additional adjustment. That a substitute is automatically equivalent, allergen-safe or suitable for every dietary requirement.
Storage & reheating General handling principles, practical risk awareness and important points that warrant extra care. That RecipeWanted replaces current local food-safety rules, professional procedures or required training.
Nutrition & allergens General ingredient context, dietary characteristics and reminders to check labels and individual requirements. Diagnosis, treatment, medical suitability or guaranteed allergen safety for an individual user.
Education & professional use Practical explanations that may support cooking education, training discussion and general learning. Formal approval for a curriculum, school, healthcare setting, professional kitchen, regulator or other controlled environment.

Source & Reference Policy

Match the evidence to the claim being made.

Not every ordinary cooking instruction requires an external citation. External verification becomes more important when information is safety-sensitive, product-specific, time-sensitive, commercially material or capable of changing a meaningful user decision.

01
Relevance

Use evidence that actually supports the point being made.

A source should be relevant to the specific ingredient, product, safety question, cooking principle or factual claim. A reputable source on a broad subject does not automatically support every narrower conclusion drawn from it.

02
Authority

Higher-consequence claims need stronger evidence.

Where food safety, allergens, regulation or another consequential subject is involved, current official or otherwise authoritative information should carry more weight than general articles, promotional material or informal advice.

03
Product Specificity

Check the product when the answer depends on the product.

Ingredients, allergen statements, preparation directions, serving information and formulations can vary between brands and markets. Product packaging or current manufacturer information is more appropriate than assuming every version of a food behaves or contains the same things.

04
Freshness

Information that can change should be treated as changeable.

Guidance, labels, policies, product formulations and other time-sensitive information may become outdated. Where the current position matters, RecipeWanted should check the relevant information again rather than rely on an old reference.

05
Interpretation

A reference supports context; it does not create authority by association.

Linking to a government body, manufacturer, university, organisation or other external source does not mean that organisation has reviewed, approved or endorsed RecipeWanted. The wording around a reference should not imply otherwise.

06
Correction

Sources and references remain open to review.

If a reference becomes outdated, a destination disappears or stronger evidence changes the understanding of a material point, the affected content can be reviewed and the reference, wording or guidance updated.

Source Selection

Different questions need different kinds of evidence.

Source choice should follow the decision being supported rather than using one type of reference for every page.

Information Type Useful Evidence Review Expectation
Everyday cooking technique Established culinary knowledge, practical testing, appropriate culinary references and internally consistent cooking logic. Check that the explanation matches the ingredients, method and expected result. Avoid unnecessary certainty where kitchens or ingredients vary.
Food safety & storage Current official or otherwise authoritative food-safety guidance appropriate to the subject and audience. Check freshness carefully and distinguish general education from local rules, professional procedures or individual risk requirements.
Ingredients & allergens Current product labels, manufacturer information and reliable ingredient-specific references where needed. Do not infer allergen status or formulation across brands. Users with sensitive requirements should verify the product they actually intend to use.
Substitutions & measurements Ingredient properties, practical culinary references, conversion logic and appropriate testing or comparison. Explain material changes in texture, structure, moisture, flavour or cooking behaviour instead of treating every conversion or replacement as exact.
Changing or current information Recent primary, official or directly responsible sources where available. Confirm that the information is still current before presenting it as the present position.
Commercial or partner claims Evidence appropriate to the specific claim, together with clear information about the commercial relationship. Commercial involvement should not lower the evidential threshold or turn supplied marketing language into an unsupported editorial statement.

User Verification

Sometimes the most reliable answer depends on information RecipeWanted cannot know for the user.

Product labels, local food-safety guidance, appliance instructions, organisation policies and individual dietary requirements can all differ. Where one of those details materially affects the decision, RecipeWanted should make that limitation visible rather than pretending a general page can resolve it universally.

Found an outdated reference, broken source or material factual issue? Report it to RecipeWanted.

AI-Assisted Content

AI can assist the workflow. It does not replace accountability.

RecipeWanted may use AI to support drafting, structuring, classification, formatting and quality checks. The use of AI does not change the standards applied to published content: cooking information should still be coherent, appropriately supported, responsibly worded and open to correction.

01
Assistance

AI is used as a production tool, not as an independent authority.

It may help organise information, draft or transform copy, classify content, prepare structured fields or identify potential inconsistencies. Its output is not considered reliable merely because it was generated confidently or in the correct format.

02
Validation

Outputs should pass the checks relevant to what they contain.

Automated and editorial controls can check structure, required fields, ingredient and method consistency, duplication, claim wording, classification and other predictable failure points before content is treated as ready for publication.

03
Escalation

Higher-risk or uncertain material needs stronger scrutiny.

Food safety, allergens, health-sensitive wording, changing factual information and ambiguous claims should not rely on AI confidence alone. The level of verification or human judgment should increase when the consequence of an error increases.

04
Accountability

RecipeWanted remains responsible for its publishing standard.

AI use does not transfer responsibility to a model or software provider. If published content is unclear, unsupported, misleading or materially incorrect, it remains subject to RecipeWanted's review and correction processes.

Controlled Workflow

The controls matter more than whether AI touched the first draft.

RecipeWanted can combine automated validation, editorial rules, source checks and human judgment according to the type of content and the risk involved.

01
Define Set the purpose and boundaries.

Establish what the content needs to do, the structure it requires and any claims or topics needing additional care.

02
Produce Use AI only within that defined role.

AI may draft, organise, classify or transform material rather than being given unrestricted authority over the final page.

03
Validate Check the failures that can be checked.

Structure, internal consistency, required fields, claims and other known failure modes can be tested before publication.

04
Escalate Apply stronger review where judgment matters.

Sensitive, uncertain or consequential information should receive the additional verification appropriate to the decision it may influence.

Important Boundary

AI output is not evidence simply because it sounds authoritative.

When a statement requires external support, the evidence should come from an appropriate source rather than from the AI system that generated or reviewed the wording.
Not a food-safety authority Safety-sensitive information should follow the sourcing and verification standards appropriate to that subject.
Not an allergy guarantee AI cannot establish that a recipe or product is safe for every individual, brand, production environment or cross-contact risk.
Not a medical or legal authority Generated wording does not turn general cooking information into personalised professional advice or formal compliance guidance.
Not a substitute for current evidence Information that may have changed should be checked against an appropriate current source rather than assumed from model output.

Concerned about something published on RecipeWanted? Report it for review.

Health, Safety & Nutrition Boundaries

Useful food guidance needs clear limits around higher-risk decisions.

RecipeWanted provides general cooking, recipe and food-education information. When a subject moves into medical needs, allergies, food-safety risk or controlled organisational use, the platform should make that boundary visible rather than implying that general cooking guidance can resolve the decision for every user or setting.

01
Medical & Nutrition

General food information should not become personalised treatment advice.

RecipeWanted may explain ingredients, cooking choices, portions and general dietary context. It should not diagnose a condition, prescribe a diet, claim that food will treat or prevent disease, or replace individual medical or dietetic advice.

02
Allergens

A recipe or substitution should not be presented as universally allergen-safe.

Formulations, labels, manufacturing environments and cross-contact risks can differ between products and markets. RecipeWanted can explain substitution principles and label awareness, but users with allergy-related requirements need to verify the ingredients and products they actually use.

03
Food Safety

Storage, cooling, reheating and hygiene require proportionate caution.

Safety-sensitive advice can depend on the food, handling conditions, temperature, timing and the people being served. RecipeWanted should distinguish general education from situations where current official guidance or professional procedures matter.

04
Organisational Use

Public cooking information is not automatic approval for a controlled setting.

Schools, care environments, workplaces, professional kitchens and other organisations can have their own policies, duties and risk controls. RecipeWanted content may support learning or discussion, but those organisations remain responsible for checking suitability against their own requirements.

Heightened Review

Some subjects warrant more caution than an ordinary cooking technique.

The objective is not to make every food page defensive. It is to recognise when the consequence of an incorrect assumption is high enough to justify stronger verification, narrower wording or a clearer direction for the user to check elsewhere.

01
Allergen-sensitive substitutions

Ingredient similarity does not establish allergen safety. Product labels and cross-contact information may still need direct verification.

02
Storage, cooling and reheating

Avoid false precision or universal assumptions where actual handling conditions and current food-safety guidance matter.

03
Pregnancy or other health-sensitive circumstances

Keep guidance general and avoid turning cooking information into personalised medical or dietary recommendations.

04
People at greater food-safety risk

General cooking guidance should not override advice or precautions appropriate to the individual's circumstances.

05
Clinical diets or condition-specific eating

RecipeWanted should not convert general ingredient information into a personalised plan for managing a medical condition.

06
Schools, care settings and professional food service

Recipes and education content should be checked against the organisation's own procedures, policies and applicable requirements before operational use.

Decision Rule

The more personal or consequential the decision, the less RecipeWanted should imply certainty.

General Explain Give clear cooking information and practical context.
Variable Qualify Make meaningful differences and uncertainty visible.
Safety-Sensitive Verify Use stronger evidence and current guidance where appropriate.
Personal / Regulated Refer Do not replace qualified advice or organisation-specific controls.

Found wording that may cross one of these boundaries? Report it for review.

Correction & Update Policy

Publishing is not the end of editorial responsibility.

Recipes, guidance, references and page information can need correction as new information appears or a problem becomes visible. RecipeWanted treats meaningful corrections as part of normal publishing responsibility rather than assuming published content should remain unchanged indefinitely.

Correction Lifecycle

Identify the problem, understand its consequence, fix the right thing and reduce the chance of repetition.

A reported concern is not automatically assumed to be correct, but it should be assessable. The response should reflect both the evidence available and the potential consequence for users.

01
Report

Identify the affected content and the concern.

A report may involve a recipe inconsistency, factual issue, outdated reference, safety-sensitive statement, broken route, accessibility problem, misleading claim or another material problem with the published page.

02
Assess

Establish whether the issue is valid and how much it matters.

The surrounding content, supporting evidence and likely user consequence should be considered before deciding whether the issue needs immediate intervention, a substantive correction or routine maintenance.

03
Correct

Change what is necessary rather than rewriting for appearance.

A correction may alter a sentence, ingredient, method step, source, safety boundary, link, structured field or larger section. The scale of the edit should follow the problem being corrected.

04
Learn

Repeated failures should improve more than one page.

Where an issue reveals a wider pattern, related content, templates, automated checks, editorial rules or publishing workflows can also be reviewed so the same failure is less likely to recur.

Correction Priority

Priority follows potential consequence, not simply how noticeable the error is.

A visually obvious formatting error may be less consequential than a small sentence that changes an allergen, storage or health-related decision.
Higher Consequence Safety, allergens and materially misleading claims

Examples include unsafe handling guidance, allergy-sensitive errors, serious ingredient contradictions or wording that improperly implies medical, regulatory or professional authority.

Material Problems that could materially affect the cooking decision

Examples include missing steps, incorrect timings, significant substitution errors, misleading references or content that could produce a substantially different outcome.

Routine Maintenance Problems that reduce quality without materially changing the decision

Broken non-critical links, unclear headings, formatting defects, duplicated wording and other lower-consequence issues can be handled through normal maintenance and improvement.

Correction Scope

A useful correction fixes the affected decision, not just the visible sentence.

Where necessary, review can extend beyond the exact line that first revealed the problem.

Content

Ingredients, method steps, timings, explanations, substitutions, serving guidance and other practical information.

Evidence

References, factual context, source links and information that has become outdated or is no longer sufficiently supported.

Boundaries

Health, allergy, food-safety, commercial or other wording that needs clearer limits or less certainty.

Presentation

Broken links, accessibility problems, navigation, labels, layout or other technical issues that materially affect use.

Found something that may need correcting? Include the page or recipe, the specific issue and any supporting information that may help RecipeWanted review it.
Report a Content Issue

Accessibility & User Experience

Cooking information should be easy to find, read and use.

Useful information loses value when the page around it creates unnecessary friction. RecipeWanted aims to make recipes, education and supporting content understandable across common devices, navigable with clear structure and usable without relying on decorative presentation alone.

01
Readability

Information should be understandable without fighting the layout.

Headings, paragraphs, labels and important notes should use readable sizing, sensible spacing and sufficient contrast. Long or complex subjects should be broken into a structure that helps users locate the part they actually need.

02
Structure

Visual hierarchy should also make sense in the underlying page.

RecipeWanted aims to use meaningful headings, appropriate lists, properly structured tables, descriptive links and labelled regions so page relationships are clearer for both visual browsing and assistive technologies.

03
Interaction

Important actions should be identifiable and operable.

Links and controls should use understandable labels, visible states and usable focus treatment. Core information should not depend on hover behaviour, colour alone or an unnecessarily difficult interaction.

04
Responsive Use

A cooking page should remain practical on a smaller screen.

Content should reflow cleanly, controls should remain usable by touch and important information should not disappear because the user is on a phone or tablet. Wide data such as comparison tables should have a usable narrow-screen treatment.

05
Performance & Stability

Loading behaviour is part of the user experience.

Pages should avoid unnecessary weight, disruptive movement and avoidable delays that make recipes or guidance harder to use. Images, embeds and other media should be handled with the wider reading experience in mind.

06
Commercial Clarity

Monetisation should not obscure the user's task.

Advertising, affiliate links, sponsorships and commercial actions should remain distinguishable from core cooking guidance and should not hide important instructions, safety information or the route a user needs to complete their task.

Practical Test

The page should support the task the user came to complete.

Accessibility and usability are considered together because technically available content can still be difficult to use when hierarchy, interaction or presentation creates unnecessary friction.
Can the user find it? Important information should have a clear place in the page hierarchy.
Can the user understand it? Language, labels and presentation should support comprehension.
Can the user operate it? Links, controls and interactive elements should remain usable.
Can the user act on it? The design should not interfere with the cooking or learning decision.
Found an accessibility or usability problem? Tell us which page is affected and what made it difficult to read, navigate or use.
Report a UX Issue

Commercial Independence & Disclosure

Commercial support should be visible. Editorial standards should stay independent.

RecipeWanted may use advertising, affiliate relationships, sponsorships and other commercial collaborations to support the platform. Those relationships should be identifiable to users and should not lower the standards applied to cooking information, evidence, safety boundaries or corrections.

01
Transparency

Users should be able to recognise commercial involvement.

Sponsored, affiliate or otherwise commercial content should be presented with enough context for the user to understand that a commercial relationship exists. Promotion should not be disguised as independent safety or educational authority.

02
Editorial Independence

Payment does not purchase the editorial conclusion.

Commercial involvement should not determine RecipeWanted's food-safety wording, allergen boundaries, correction decisions, evidence standards or conclusions about what users should understand from a piece of cooking information.

03
Claim Control

Commercial claims should still be supportable.

Marketing language supplied by a brand or partner does not automatically become an editorial fact. Material claims should be handled according to the same relevance, evidence and certainty standards applied elsewhere on RecipeWanted.

04
User Experience

Monetisation should not obstruct the reason the user came to the page.

Commercial placements should not hide recipe instructions, interrupt important safety information, create misleading navigation or add unnecessary friction to the user's cooking or learning task.

Commercial Context

Different commercial relationships need clear context, not identical presentation.

The exact disclosure can depend on the relationship, but the underlying principle is consistent: users should not have to guess when commercial interests are relevant to what they are seeing.

Advertising

Advertising should remain distinguishable from RecipeWanted's core editorial and educational information.

Affiliate Relationships

Product or retailer links that form part of an affiliate relationship should not be presented as independent certification, medical necessity or universal product suitability.

Sponsored Content

Where commercial support contributes to a resource or campaign, that support should be made clear without allowing sponsorship to create false safety, approval or compliance authority.

Partnerships

Collaborative work should still follow the relevant RecipeWanted standards for claims, sources, accessibility, corrections and practical user value.

Commercial Boundary

Commercial involvement does not create additional authority.

A paid relationship may support distribution, production or access to a relevant resource. It does not by itself establish that the promoted product, partner or content has been independently certified for every user or setting.
No purchased safety conclusion Sponsors do not determine food-safety or allergen guidance.
No exemption from evidence standards Commercial claims do not receive a lower verification threshold.
No implied certification Payment or partnership does not establish medical, government, school, regulatory or professional approval.
No hidden commercial influence Material commercial relationships should not be deliberately concealed from users.

Next Steps

Standards matter when they change how the platform behaves.

RecipeWanted uses this standard as a public framework for practical cooking information, evidence, AI-assisted workflows, higher-risk topics, corrections, accessibility and commercial independence. The aim is straightforward: useful cooking information with clearer limits, stronger accountability and room to improve.