Evidence and scope
FFEPlaybook separates enforceable requirements, voluntary standards, historical benchmarks, and operating assumptions. Legal or safety claims should link to the agency or standards body that establishes them. Planning ranges are not codes and should be checked against the project's location, contract, brand standard, authority having jurisdiction, and current vendor proposals.
Costs and dates
Hotel development and renovation costs change with time, location, scope, and sample mix. Every published cost table should identify its source year. Historical data can explain the shape of a budget but must not be copied into a current capital plan without rebasing and current market pricing.
Product and material claims
Abrasion, flammability, structural performance, emissions, and accessibility are separate questions. We name the test method and application instead of treating “contract grade” as proof. Product compliance must be supported by documentation for the exact model, construction, and jurisdiction.
Corrections
When a claim is wrong or too broad, we replace it with the directly supported fact or label it as a planning assumption. We do not invent authors, review dates, or credentials for legacy pages. The source list on each guide is visible so readers can inspect the references used.