Skip to content

Main content

Food Frequency Recall Rate Crosswalk

Normalize an explicitly reported occurrence count over positive recall days without estimating serving size or nutrient intake.

Loading tool…

Description

Convert supplied recall occurrences to daily and seven-day rates.

Dietary arithmetic depends on as-purchased versus edible mass, per-serving versus per-100-gram bases, measured versus trace states and recall periods. A recorded allergen list is not a verified allergen-free declaration. Portion counts, label intervals and mass differences use supplied assumptions rather than establishing actual intake or nutritional suitability.

Convert supplied recall occurrences to daily and seven-day rates.

When to use this tool

Use Food Frequency Recall Rate Crosswalk when you already have reportedOccurrences, recallDays and need to convert supplied recall occurrences to daily and seven-day rates.

How to use the tool and how it works

  1. Enter reportedOccurrences, recallDays. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read occurrencesPerDay, occurrencesPerWeek. Use the output convention below.

Require reportedOccurrences>=0 and recallDays>0; return occurrences/days and 7*occurrences/days.1

Input fieldMeaning and unitsAccepted input
reportedOccurrencesReported OccurrencesRequired. Finite number; minimum 0.
recallDaysRecall DaysRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
occurrencesPerDayOccurrences Per DayRequired. Finite number.
occurrencesPerWeekSeven times the daily rate; a fixed seven-day reference, not imputed habitual frequency.Required. Finite number.
json
{
  "input": {
    "reportedOccurrences": 6,
    "recallDays": 14
  },
  "output": {
    "occurrencesPerDay": 0.42857142857142855,
    "occurrencesPerWeek": 3
  }
}

Limitations and assumptions

  • Occurrences may be fractional. A week is fixed at seven days; no recall accuracy, intake amount, habitual diet or nutritional adequacy is inferred.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Check original food labels, composition sources, ingredient/allergen information and dietary records before combining amounts. Use a complete appropriately interpreted dietary assessment when requirements or suitable intake matter; local scaling and source labels do not make those judgments.

References

  1. Calculation and input contract: dietetics/food-frequency-recall-rate-crosswalk — tool.io

Similar or alternative tools