Policy · Specification
Trust Score Methodology
This document defines how the Food O Live Trust Score is calculated, how often it updates, and how a restaurant can request a correction. Because the score can affect a restaurant's income, the method is documented, dated and open to appeal.
1 · Scope
What the Trust Score measures
The Trust Score is a single integer from 0 to 100 that summarises the verifiable trust signals available for a restaurant. It is designed to be reproducible: given the same inputs, the same score is produced, and every input traces to a documented source.
The score is not a measure of taste, popularity or price. It reflects only the signals defined in Section 2. Where a required input is unavailable for a restaurant, the handling of the missing input is defined in Section 2 and does not default to a favourable value.
- Range
- 0 – 100
- Type
- Integer
- Rounding
[ROUNDING RULE] (placeholder — value not yet supplied)
2 · Components
Components, weights and data sources
The score is the weighted sum of the components below. Weights sum to 100%. Each component names the data source it draws from, the measurement window over which it is evaluated, and the threshold at which it contributes.
C1
[COMPONENT NAME] (placeholder — value not yet supplied) [WEIGHT] (placeholder — value not yet supplied) - Data source
[DATA SOURCE] (placeholder — value not yet supplied) - Measurement window
[MEASUREMENT WINDOW] (placeholder — value not yet supplied) - Threshold
[THRESHOLD] (placeholder — value not yet supplied)
C2
[COMPONENT NAME] (placeholder — value not yet supplied) [WEIGHT] (placeholder — value not yet supplied) - Data source
[DATA SOURCE] (placeholder — value not yet supplied) - Measurement window
[MEASUREMENT WINDOW] (placeholder — value not yet supplied) - Threshold
[THRESHOLD] (placeholder — value not yet supplied)
C3
[COMPONENT NAME] (placeholder — value not yet supplied) [WEIGHT] (placeholder — value not yet supplied) - Data source
[DATA SOURCE] (placeholder — value not yet supplied) - Measurement window
[MEASUREMENT WINDOW] (placeholder — value not yet supplied) - Threshold
[THRESHOLD] (placeholder — value not yet supplied)
C4
[COMPONENT NAME] (placeholder — value not yet supplied) [WEIGHT] (placeholder — value not yet supplied) - Data source
[DATA SOURCE] (placeholder — value not yet supplied) - Measurement window
[MEASUREMENT WINDOW] (placeholder — value not yet supplied) - Threshold
[THRESHOLD] (placeholder — value not yet supplied)
Total weight
Missing-input handling:
3 · Cadence
Refresh cadence
Each component refreshes on its own schedule as new source data arrives. The published score is recomputed on the cadence below; the timestamp of the last recomputation is shown next to the score in the app.
- Published score recomputed
[RECOMPUTE CADENCE] (placeholder — value not yet supplied) - Inspection-record inputs
[SOURCE REFRESH] (placeholder — value not yet supplied) - Live-feed / operational inputs
[SOURCE REFRESH] (placeholder — value not yet supplied)
4 · Corrections & appeals
How a restaurant corrects or appeals its score
A restaurant that believes an input or the resulting score is wrong can raise a correction. Corrections are handled on a defined timeline, and the score is annotated as "under review" while an appeal is open.
- 1
Raise a correction
The restaurant submits a correction from the partner dashboard or the appeal email, identifying the disputed input or score.
- 2
Score marked under review
While the appeal is open, the score is annotated as under review and the disputed input is flagged.
- 3
Review against sources
The disputed input is checked against its documented source within the response window.
- 4
Outcome recorded
The correction is applied or declined with a reason, and the outcome is logged against the score.
- Response window
[RESPONSE WINDOW] (placeholder — value not yet supplied) - Raise a correction
[GRIEVANCE / APPEAL EMAIL] (placeholder — value not yet supplied)
5 · Version history
Version history
Every change to this methodology is versioned with an effective date. A score computed under a previous version is labelled with the version that produced it.
| Version | Effective date | Summary of change | Approved by |
|---|---|---|---|
No version is live. The first row becomes effective only once the draft notice at the top of this page is removed and an effective date is recorded here.