An AI workflow can quote an approved source accurately and still produce the wrong business result if that source is out of date. A policy revised last quarter, an order status from the previous shift, and a customer address confirmed today do not have the same useful life. Each important field needs a rule for when it can be used, when it must be refreshed, and when the workflow must stop.

This guide helps United States small-business teams define source-freshness rules for one bounded workflow. It does not prescribe legal retention periods or claim that every system exposes reliable timestamps. Local AI Developer scopes workflows around approved sources, readable operating knowledge, connected tools, and human review. The Los Angeles County workflow page describes team handoffs in that broader national service context.

Define freshness for a decision

Freshness is not simply the age of a file. It is whether the available evidence is current enough for a particular output and decision. A two-day-old product specification may be current, while a two-hour-old shipment status may already be incomplete.

Start by naming the output. Then list the decisions a reviewer may make from it. A shift handoff, a draft customer reply, and a planning summary may require different evidence even when they reference the same order.

Write the consequence of stale information. If the wrong version could cause an unsupported commitment, record that the item must stop for review. If it would only omit a nonessential note, the output may continue while visibly marking the field unavailable.

Identify the event that makes data current

For each important field, name the business event that establishes its current value. Examples include an approved policy revision, a warehouse scan, an owner confirmation, a completed form, or a status change in an authoritative system.

Do not assume the newest file modification time represents the newest business fact. A copied file may have a recent timestamp but old contents. A record may be updated for an unrelated field without confirming the value the workflow needs.

Record which source and event together establish freshness. If the business cannot identify that event, classify the rule as unresolved before relying on the field for an external or consequential action.

Separate stable references from changing facts

Group inputs by how they change. Stable reference material may include approved terminology, a standard output format, or reviewed operating instructions. Changing facts may include inventory, shipment status, assigned owner, customer contact details, or a project decision.

Stable does not mean permanent. Give reference material an owner and a revision signal. A document can remain usable until the owner supersedes it, while a live status field may require a successful read during the current run.

Avoid one global freshness window for every source. A rule such as “anything under 30 days is current” is easy to automate but usually unrelated to the decisions the workflow supports.

Choose a usable freshness rule

A freshness rule may be based on elapsed time, a named business event, a version, or a combination. Write it so an operator can test it. Examples include “use the policy version marked current by the operations owner” or “retrieve order events during this run and display the latest event time.”

For a source that changes at a known handoff, tie the rule to that handoff. A receiving shift may need events recorded after the previous cutoff. A weekly planning brief may need owner confirmations made after the last meeting.

State the time zone when a calendar or cutoff time matters. Preserve the source timestamp as supplied and show any conversion used in the output. Ambiguous local times should cause review rather than a guessed sequence.

Record retrieval time separately from source time

The time a workflow fetched a record is not necessarily the time the business fact was observed or approved. Keep both values when they matter.

Source time answers when the event, revision, or confirmation occurred. Retrieval time answers when the workflow obtained it. A record fetched this morning may still contain a status last updated last week.

If a source supplies no reliable event time, say so in the brief. Do not manufacture precision from a file's local copy time or the moment a model read the text.

Resolve conflicting freshness signals

Two approved systems may disagree. A project tracker may show one owner while a later approved meeting note assigns another. A copied specification may have a newer filename while the controlled register still marks an earlier version as current.

Define precedence before launch. Name the authoritative source for each field and the owner who can resolve a conflict. Recency alone should not overrule an approved source hierarchy.

When the hierarchy does not resolve the case, put the item on hold. Show both values, their source references, relevant times, and the person responsible for selecting the current fact. Do not blend conflicting values into a confident summary.

Decide when to refresh, hold, or continue

Give each freshness check one of three outcomes. Continue when the source satisfies the rule. Refresh when the workflow can safely retrieve the current value from the same approved source. Hold when current evidence is unavailable, conflicting, or requires a person's confirmation.

Limit automated refresh attempts. Repeatedly querying a broken connection does not make the data newer and may create noise or tool limits. Record the attempt count, last error category, and owner for recovery without exposing credentials.

For optional fields, the workflow may continue with an explicit “not available” marker if the output remains useful and no commitment depends on the field. Required fields should produce a visible hold rather than disappear from the output.

Show freshness in the review packet

Give the reviewer enough evidence to assess important values. Include the field, current value, source reference, source time or version, retrieval time, and freshness result. Highlight unresolved or near-cutoff items.

Do not bury stale warnings in a general disclaimer. Place the warning next to the affected fact and explain the needed action. A reviewer should be able to distinguish a verified current value from a historical value included only for context.

Keep the display focused. Showing timestamps for every decorative field can obscure the few values that control the decision. The source-freshness map should identify which facts deserve prominent evidence.

Design a manual fallback

Write what operators do when the authoritative source is unavailable. They may check the source directly, contact the named owner, use a documented manual process, or defer the item until service returns.

Do not silently substitute an unapproved spreadsheet, old email, or remembered answer. If a temporary source is authorized for a specific situation, record who authorized it, which fields it may supply, and when that exception ends.

The fallback should preserve the workflow item and its source references. A person taking over should not need hidden chat history to understand what was checked and why processing stopped.

Test boundaries and clock problems

Create cases just inside and outside each time-based cutoff. Test a current version, a superseded version with a newer copy time, two sources that disagree, a missing timestamp, and a connection that returns cached data.

Test date boundaries in the business's operating time zone, including a handoff near midnight if that can occur. Confirm that displayed source times and retrieval times are labeled consistently.

For each case, verify the expected continue, refresh, or hold result. Inspect the source record independently and confirm that no external message or record change occurred from stale or unresolved information.

Review rules with operating evidence

After launch, inspect freshness holds and reviewer corrections. Frequent holds may mean a source owner is not updating the record, a cutoff is unrealistic, or the workflow is reading the wrong event. A lack of holds does not prove the rules are sound if test cases were too easy.

Adjust a rule only with an owner and reason. Making a window longer to reduce interruptions can hide genuinely stale facts. Making it shorter can create needless review without improving the decision.

When a source, handoff schedule, or business decision changes, update the map, acceptance cases, and readable operating instructions together.

Complete the source-freshness map

For one workflow, capture:

Bring this map when you request a scoped workflow conversation. A freshness rule tied to a real business decision helps a reviewer see when an AI-produced brief is ready to use and when the safest result is to wait for better evidence.