Does 03/04 Mean March 4 or April 3? Check Spreadsheet Dates Before AI Uses Them

A supplier’s spreadsheet lists a delivery date as 03/04/2026. Your AI-generated follow-up plan confidently places it in March. The problem may not be the wording of the prompt: the source date itself needs clarification.

Do not turn a familiar-looking date into an operational deadline until you know what it means. Separate the original text, the intended calendar date, and the value passed into the next workflow. Changing how a cell looks is not evidence that all three agree.

Preserve the original date and ask what it means

Keep the original export or supplied file unchanged. Record the relevant sheet, row and source reference so another reviewer can find the same value. Work on a clearly named review copy when you need to explore a correction.

Look for an explicit date convention in the source documentation. If it is absent, ask the authorized source owner to confirm the intended date. Do not infer the convention solely from the sender’s name, country or your computer’s settings.

A date such as 03/04/2026 can be read as March 4 or April 3. That illustrates the ambiguity; it does not establish which reading the supplier intended. Other entries may provide clues, but a plausible pattern is not a substitute for confirmation when the date controls real work.

If the year is missing, keep that unresolved too. Do not let an AI summary silently fill it from today’s year or from another row.

Inspect spreadsheet settings without changing the shared file

Google’s spreadsheet-settings documentation explains that a sheet’s locale and time-zone settings affect its default currency, date and number formatting. On a computer, the documented settings are under File → Settings, in General.

Inspect the existing values as context. They do not prove how an earlier import was interpreted or what the original author meant. A source can contain mixed conventions or text that has not been treated as a date at all.

Google also states that settings changes apply to the entire spreadsheet and are visible to everyone working on it. Do not change a shared sheet’s locale just to make one column resemble the expected dates. Ask its authorized owner to evaluate any proposed change and its wider effects.

This is a Google Sheets example, not a guarantee that another spreadsheet tool or your account exposes the same controls. Preparation can continue with the raw value and a clarification note if the relevant setting cannot be inspected.

Prepare an explicit date with its source evidence

Once the source owner confirms the date, preserve the original value alongside the clarified one in the review artifact. Use a written month and year when presenting the decision to a person. For a system import, follow that destination’s documented date requirements rather than assuming it accepts your preferred format.

Here is a fictional review record, not an import or customer test we performed:

In a real record, replace the illustrative confirmation with its actual source and date. If no confirmation exists, label the intended date unknown. Do not copy the example into a live row as if it were evidence.

An AI assistant can draft a list of ambiguous entries and the questions to ask. Keep its role bounded: flag uncertainty, do not decide the missing convention or create reminders automatically.

Check the value the next workflow actually receives

Before an approved import or automation run, inspect the prepared input using a synthetic example with a known intended date. Compare what was supplied with the date shown in the destination’s draft or preview. A successful file upload does not establish that the day and month were interpreted correctly.

If the workflow adds a specific time, review its time-zone handling separately. Resolving April 3 versus March 4 does not establish what “9 AM” means. Conversely, fixing a time-zone display does not resolve an ambiguous source date.

Keep real deadlines and customer messages paused if the interpretation is still uncertain. Do not send a reminder to discover whether the date was correct. Preserve the discrepancy and have the appropriate owner decide the smallest approved correction.

The useful handoff is specific: original row, confirmed intended date, tested destination value and any remaining uncertainty. “Dates cleaned” is not enough for someone relying on the schedule.

For bounded preparation prompts, see our AI operator prompt pack. If your team needs help tracing spreadsheet inputs into reviewed follow-up plans, contact Business Boomer about a scoped workflow review. Start with a synthetic row whose intended date is known before any real deadline is changed.