Field notes, methodology updates, and answers to questions that come in by email. The guides are the reference; the blog is the conversation.
Shewhart and Western Electric rules applied to a fill-up log. The methodology OEM and Tier 1 supplier quality teams use, adapted to the messiness of vehicle data, with the practical adjustments (irregular fill-up intervals, weather, sensor noise) that vehicle fleets need.
What consumer OBD-II hardware can read from your car's computer, the limits of ECU-calculated fuel rate, and when telemetry is worth the setup.
What the three global test cycles actually measure, why a US MPG sticker and a European L/100km sticker for the same car can be different numbers without either being wrong, and where JC08 stands now.
The fill-up protocol expanded: how to record the odometer, what to do when you can't start with a full tank, the photo-validation habit, and the worked example in full.
When you need a number you can defend (warranty, tax, fleet reporting): the protocol changes, the sources of error, and the move from a fill-up average to a process control chart.
The factors that change your MPG result, ranked by how much each one moves the number. The point is to know which ones to control for in your use case.
What the popular apps (Fuelio, GasBuddy, Fuelly, Road Trip MPG, aCar) actually do, where they overlap with the calculator, and where the calculator does the same job without an account or a subscription.
The blog is where we publish opinion pieces, methodology deep-dives, and field notes that don't fit the long-form structure of the guide library. New posts appear roughly every two weeks, and older posts are updated as the underlying standards evolve. If you read only one article, start with the most recent; the front of the blog is always the freshest material.
Posts are tagged with one of three categories. Methodology posts explore a single technique in depth, for example, the trade-offs between weighted and unweighted averaging, or the difference between ISO 22514-2 and the older ISO 22514 process-capability framework. Industry posts cover regulatory changes, manufacturer announcements, and emerging automotive technologies. Tooling posts cover the calculator itself, new features, performance improvements, and the reasoning behind UX decisions.
The guides are reference material: long, structured, and designed to be read on demand when you have a specific question. The blog is conversation: shorter, more discursive, and designed to be browsed. We do not duplicate material between the two; if a blog post touches on a topic that is also covered in a guide, the blog links to the guide for the canonical version and uses the post to add context, opinion, or a recent example.
Posts are written by Sandeep Sitoke. We do not accept guest posts, sponsored content, or paid placements. If a manufacturer sends us a vehicle to test, we disclose that fact at the top of the relevant post; if a regulator cites our work, we note that too. We treat the byline as a real authorship signal, not a content-marketing slot.
Every blog post is reviewed by Sandeep before publication. The review checks for technical accuracy, attribution of sources, and clarity of argument. We do not publish AI-generated drafts without substantial human editing; we do not paraphrase press releases; we do not run sponsored segments. If we get something wrong, we issue a date-stamped correction at the top of the post and email readers who flagged the issue to let them know.
We do not maintain a comments section on the blog. The reason is simple: we would rather have a small number of high-quality conversations by email than a large number of low-quality conversations in a comment thread. If you would like to discuss a post, please use the contact form and reference the post title in your message.
The site does not maintain an email newsletter. The simplest way to follow new posts is to bookmark this page and revisit it every couple of weeks. If you want to be notified about major methodology changes that affect the published guides, the guides themselves are updated in place with a visible "Last Updated" date, and the affected guide is linked from the most recent post that announces the change.