[No QA] Add Save for later odometer details to Distance Expenses help docs by Julesssss · Pull Request #89960 · Expensify/App

Julesssss · 2026-05-07T18:48:44Z

Explanation of Change

With the launch of Odometer project phase 2, we need to add updates the Distance Expenses help site page with information about the Save for later feature for odometer expenses:

Adds a Save for later step to the Odometer creation flow
Adds two new FAQs covering saving an odometer expense for later and the single-in-progress limit
Design Doc plan

Follow up to #86366.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/571644

Tests

N/A — documentation-only change

Offline tests

N/A

QA Steps

N/A

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

github-actions · 2026-05-07T18:50:42Z

HelpDot Documentation Review

Overall Assessment

This PR adds a "Save for later" feature to the odometer-based Distance expense workflow. The changes are small and focused: one new optional step in the procedure, three new keywords, and two new FAQ entries. The additions are well-scoped and consistent with the existing article's structure and tone.

Scores Summary

Readability: 8/10 - The new step is clearly written and correctly marked as optional. The FAQ answers are concise and direct. Minor issue: the first FAQ answer uses an exclamation mark ("Yes!") which introduces an informal tone inconsistent with the rest of the article, and the phrasing "Enter a reading at the beginning of your trip and you can save the expense until the end" could be slightly clearer about the specific action (selecting Save for later).
AI Readiness: 9/10 - New keywords ("save for later", "in-progress odometer", "incomplete odometer") are well-chosen and match realistic search queries. The FAQ headings are question-based and feature-specific, aligning with retrieval optimization rules.
Style Compliance: 9/10 - Save for later is correctly bolded as a UI element. Step formatting follows the established pattern. FAQ headings use proper question-word format. One minor note: the second FAQ answer ("Only one in-progress odometer expense can be saved to your device at a time.") does not bold "in-progress" as a UI concept, but this is acceptable since it reads as a descriptive phrase rather than a UI label.

Key Findings

The new step 6 is properly integrated into the numbered sequence with correct renumbering of subsequent steps.
Keywords additions are relevant and support discoverability for the new save-for-later functionality.
Both FAQ entries follow the question-based heading convention required by governance rules.
The first FAQ answer ("Yes! Enter a reading at the beginning of your trip and you can save the expense until the end. Or simply take a photo and attach them both once the trip is complete.") would benefit from referencing the exact UI action (Save for later) for consistency with the procedural step and to reinforce UI-exact terminology per naming conventions.
The exclamation mark in "Yes!" should be removed to maintain the neutral, deterministic tone required by the authoring guidelines.

Recommendations

Remove the exclamation mark from "Yes!" in the first FAQ answer -- use "Yes." to match the tone of other FAQ answers in the article.
Consider referencing Save for later by name in the first FAQ answer body to reinforce UI-exact terminology (e.g., "Yes. Enter your start reading before the trip, then select Save for later. After the trip, reopen the expense to enter the end reading.").
No structural or metadata issues found -- the changes are ready to merge after addressing the minor tone and terminology items above.

Files Reviewed

docs/articles/new-expensify/reports-and-expenses/Distance-Expenses.md — New optional step for saving odometer expenses, two new FAQ entries, and updated keywords. Changes are well-structured with minor tone refinements recommended.

OSBotify · 2026-05-07T18:56:00Z

A preview of your ExpensifyHelp changes have been deployed to https://d0b488d6.helpdot.pages.dev ⚡️

Updated articles:

articles/new-expensify/reports-and-expenses/Distance-Expenses

melvin-bot · 2026-05-07T19:04:47Z

melvin-bot · 2026-05-07T19:04:50Z

@arosiclair @jliexpensify One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Julesssss · 2026-05-07T19:11:16Z

@jliexpensify @stephanieelliott I applied some feedback from the AI reviewer. Please let me know how it looks.

jliexpensify

LGTM!

github-actions · 2026-05-09T01:40:28Z

 5. (Optional) Select the image icon next to each reading to attach a photo of your odometer.
-6. Select **Next**.
-7. On the confirmation screen, review and confirm:
+6. (Optional) To finish creating the expense later, select **Save for later** to keep the expense in progress on your device. After your trip, return to **➕ Create** > **Track distance** > **Odometer** to resume the saved expense and enter the end reading.


Step clarity / sequential flow: This step combines two distinct actions — saving the expense now and resuming it later after the trip. Per the step formatting standard (Section 5), steps must be sequential and aligned with the actual UI flow. The "After your trip, return to..." portion describes a separate future action that breaks the sequential flow of the current procedure.

Consider trimming this step to the immediate action only:

Suggested change

6. (Optional) To finish creating the expense later, select **Save for later** to keep the expense in progress on your device. After your trip, return to **➕ Create** > **Track distance** > **Odometer** to resume the saved expense and enter the end reading.

6. (Optional) To finish creating the expense later, select **Save for later** to keep the expense in progress on your device.

The resumption instructions are already covered in the FAQ ("Can I save an odometer expense for later?"), so they don't need to be duplicated here.

github-actions · 2026-05-09T01:40:42Z

HelpDot Documentation Review Summary

Overall Score: 9/10

Category Scores

Category	Score	Notes
Metadata & Keywords	10/10	Three relevant keywords added (`save for later`, `in-progress odometer`, `incomplete odometer`) that reflect realistic search queries. No issues with existing YAML fields.
Heading Compliance	10/10	Both new FAQ headings start with question words ("Can I..."), which satisfies the task-based heading requirement. `# FAQ` exemption is respected.
Step Formatting	9/10	New step 6 is clear, action-oriented, and fits logically into the existing sequence. Step renumbering is correct. One minor note: step 6 packs two actions (selecting Save for later and the return path) into a single step, which is dense but acceptable since it is marked optional.
UI Terminology & Naming	9/10	Save for later is bolded correctly. Navigation path uses the established `>` convention consistent with the rest of the article. Minor observation: confirm that "Save for later" matches the exact UI button text (including capitalization).
Cross-linking	10/10	No new cross-links introduced. Existing cross-link structure is unaffected. No links placed inside numbered steps.
AI Retrieval Optimization	9/10	New FAQ entries use full feature names and are phrased as natural questions users would ask. The `internalScope` field was not updated to mention the save-for-later capability, which would marginally improve retrieval scoping.

Strengths

Clean, minimal change that adds a single new capability to an existing well-structured article.
The new optional step is placed at the correct point in the procedural flow (after entering readings, before finalizing).
FAQ entries are concise and directly answer the questions posed.
Keywords added are realistic search terms that users would actually type.
Step renumbering is handled correctly throughout.

Issues Found

The internalScope field could be updated to mention the save-for-later / in-progress odometer workflow, since it now covers this capability. This is a minor gap -- the current scope statement ("Covers creating Distance expenses using GPS tracking, map-based routes, manual entry, and odometer readings") is broadly accurate but does not explicitly call out the new save-for-later behavior.

Step 6 contains both the action ("select Save for later") and the resumption path ("return to ... to resume"), making it information-dense for a single step. Consider splitting the resumption instructions into a separate sub-bullet for scannability, e.g.:

6. (Optional) To finish creating the expense later, select **Save for later** to keep the expense in progress on your device.
   - After your trip, return to **+ Create** > **Track distance** > **Odometer** to resume the saved expense and enter the end reading.

The FAQ answer for "Can I have multiple incomplete odometer expenses at the same time?" does not begin with "Yes" or "No", which breaks the pattern established by every other FAQ answer in this article. Starting with "No." before the explanation would improve consistency.

Recommendations

Add "No." prefix to the last FAQ answer: "No. Only one in-progress odometer expense can be saved to your device at a time."
Consider splitting step 6 into action + sub-bullet for the resumption path, improving scannability.
Optionally update internalScope to mention save-for-later capability for better AI retrieval precision.

Files Reviewed

docs/articles/new-expensify/reports-and-expenses/Distance-Expenses.md -- 13 lines added, 4 removed. Adds save-for-later odometer functionality documentation (new step, new keywords, two new FAQ entries).

Generated with Claude Code

github-actions · 2026-05-09T02:30:09Z

 5. (Optional) Select the image icon next to each reading to attach a photo of your odometer.
-6. Select **Next**.
-7. On the confirmation screen, review and confirm:
+6. (Optional) To finish creating the expense later, select **Save for later** to keep the expense in progress on your device. After your trip, return to **➕ Create** > **Track distance** > **Odometer** to resume the saved expense and enter the end reading.


Readability / step formatting: This step combines two distinct actions across different timeframes (saving now, resuming later) into a single numbered step. Per the authoring guidelines, steps must be "sequential, clear, action-oriented, aligned with actual UI flow." Consider splitting this into a focused instruction for the current action only:

Suggested change

6. (Optional) To finish creating the expense later, select **Save for later** to keep the expense in progress on your device. After your trip, return to **➕ Create** > **Track distance** > **Odometer** to resume the saved expense and enter the end reading.

6. (Optional) To finish creating the expense later, select **Save for later** to keep the expense in progress on your device.

The resumption instructions ("After your trip, return to...") are already covered in the FAQ entry below and don't belong in the procedural step sequence, which should describe the current UI flow in order.

github-actions · 2026-05-09T02:30:11Z

+
+## Can I have multiple incomplete odometer expenses at the same time?
+
+Only one in-progress odometer expense can be saved to your device at a time.


Readability: The question asks "Can I have multiple incomplete odometer expenses at the same time?" but the answer does not begin with a direct "Yes" or "No." Other FAQ answers in this article consistently lead with "Yes" or "No" before elaborating. Consider starting with "No." for consistency and clarity:

Suggested change

Only one in-progress odometer expense can be saved to your device at a time.

No. Only one in-progress odometer expense can be saved to your device at a time.

github-actions · 2026-05-09T02:30:23Z

HelpDot Documentation Review

Overall Assessment

This PR adds "Save for later" functionality documentation to the Distance Expenses article. The changes are well-scoped: three new keywords in the YAML frontmatter, a new optional step in the odometer workflow, and two new FAQ entries. The additions are clean, consistent with the existing article style, and align well with governance standards.

Scores Summary

Readability: 9/10 - The new step and FAQ entries are clear, concise, and scannable. Step 6 is well-structured as an optional action with a follow-up instruction. The FAQ answers are direct and to the point.
AI Readiness: 9/10 - New keywords ("save for later", "in-progress odometer", "incomplete odometer") match realistic search queries. The FAQ headings use question-word format, which supports retrieval. The internalScope field was not updated to mention the new "save for later" workflow, which is a minor gap.
Style Compliance: 9/10 - Save for later is correctly bolded as a UI element. Navigation path formatting (using > separators with bolded create button) is consistent with the rest of the article. FAQ structure follows the governance pattern correctly.

Key Findings

The new step 6 correctly uses "(Optional)" prefix and Save for later bold formatting, matching button naming standards.
The navigation path in step 6 and the FAQ answer are identical, which provides good consistency but also means any future path change must be updated in two places.
The two new FAQ entries follow the established pattern: question-word headings at ## level, concise direct answers.
The keywords added are realistic search phrases that users would actually type, satisfying the metadata requirements.
Minor observation: The internalScope metadata was not updated to mention the "save for later" or "in-progress odometer" capability. Consider appending something like "including saving odometer expenses for later" to the internalScope value for completeness.

Recommendations

Consider updating internalScope - The internalScope field could be expanded to mention the "save for later" workflow, since it now covers more than just creating odometer expenses. This helps AI retrieval systems understand the full scope of the article.
No structural, formatting, or compliance issues were found. The changes are ready to merge from a documentation quality perspective.

Files Reviewed

docs/articles/new-expensify/reports-and-expenses/Distance-Expenses.md - Keywords, step insertion, and FAQ additions all comply with governance standards. Clean, well-integrated changes.

Review performed against docs/HELPSITE_NAMING_CONVENTIONS.md, docs/HELP_AUTHORING_GUIDELINES.md, and docs/TEMPLATE.md governance files.

OSBotify · 2026-05-12T00:05:15Z

🚀 Deployed to staging by https://github.com/Julesssss in version: 9.3.70-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	failure ❌
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

iOS

OSBotify · 2026-05-13T01:19:17Z

🚀 Deployed to staging by https://github.com/Julesssss in version: 9.3.72-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android
iOS

OSBotify · 2026-05-13T07:01:08Z

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.72-1 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Add Save for later odometer details to Distance Expenses help docs

2b186ea

Julesssss requested a review from stephanieelliott as a code owner May 7, 2026 18:48

melvin-bot Bot assigned Julesssss May 7, 2026

github-actions Bot reviewed May 7, 2026

View reviewed changes

Comment thread docs/articles/new-expensify/reports-and-expenses/Distance-Expenses.md Outdated

github-actions Bot reviewed May 7, 2026

View reviewed changes

Comment thread docs/articles/new-expensify/reports-and-expenses/Distance-Expenses.md Outdated

Julesssss requested a review from a team as a code owner May 7, 2026 19:04

melvin-bot Bot requested review from arosiclair and jliexpensify and removed request for a team May 7, 2026 19:04

alter copy

1f6b4bc

Julesssss force-pushed the jules-odometerSaveForLaterDocs branch from d99d927 to 1f6b4bc Compare May 7, 2026 19:05

Julesssss added 3 commits May 7, 2026 12:06

Reference Save for later button and drop photo sentence

210532c

Tone and tighten Save for later FAQ

7c4b53d

Spell out reopen path for saved odometer expense

0f2ccbb

arosiclair approved these changes May 8, 2026

View reviewed changes

Julesssss mentioned this pull request May 8, 2026

[Odometer] [Tracking] Add Odometer mileage to NewDot #71841

Open

20 tasks

jliexpensify approved these changes May 9, 2026

View reviewed changes

github-actions Bot reviewed May 9, 2026

View reviewed changes

stephanieelliott approved these changes May 9, 2026

View reviewed changes

github-actions Bot reviewed May 9, 2026

View reviewed changes

Julesssss merged commit 0ff9a3f into main May 11, 2026
29 checks passed

Julesssss deleted the jules-odometerSaveForLaterDocs branch May 11, 2026 17:30

This was referenced May 11, 2026

[No QA] Docs updates for E/A#89858 Add Map and Manual tabs for editing distance expenses #90022

Closed

[No QA] Docs updates for E/A#85493 Add distance editing to Distance Expenses help article #89825

Closed

OSBotify mentioned this pull request May 11, 2026

Deploy Checklist: New Expensify 2026-05-11 #90263

Closed

	6. (Optional) To finish creating the expense later, select Save for later to keep the expense in progress on your device. After your trip, return to ➕ Create > Track distance > Odometer to resume the saved expense and enter the end reading.
	6. (Optional) To finish creating the expense later, select Save for later to keep the expense in progress on your device.


		## Can I have multiple incomplete odometer expenses at the same time?

		Only one in-progress odometer expense can be saved to your device at a time.

	Only one in-progress odometer expense can be saved to your device at a time.
	No. Only one in-progress odometer expense can be saved to your device at a time.

Conversation

Julesssss commented May 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

github-actions Bot commented May 7, 2026

HelpDot Documentation Review

Overall Assessment

Scores Summary

Key Findings

Recommendations

Files Reviewed

Uh oh!

Uh oh!

Uh oh!

OSBotify commented May 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

melvin-bot Bot commented May 7, 2026 • edited by jliexpensify Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Concierge reviewer checklist:

Uh oh!

melvin-bot Bot commented May 7, 2026

Uh oh!

Julesssss commented May 7, 2026

Uh oh!

jliexpensify left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 9, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented May 9, 2026

HelpDot Documentation Review Summary

Overall Score: 9/10

Category Scores

Strengths

Issues Found

Recommendations

Files Reviewed

Uh oh!

github-actions Bot May 9, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot May 9, 2026

Choose a reason for hiding this comment

Uh oh!

github-actions Bot commented May 9, 2026

HelpDot Documentation Review

Overall Assessment

Scores Summary

Key Findings

Recommendations

Files Reviewed

Uh oh!

Uh oh!

OSBotify commented May 12, 2026

Uh oh!

OSBotify commented May 13, 2026

Uh oh!

OSBotify commented May 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Julesssss commented May 7, 2026 •

edited

Loading

OSBotify commented May 7, 2026 •

edited

Loading

melvin-bot Bot commented May 7, 2026 •

edited by jliexpensify

Loading