Track progress without guessing.

The correspondence workflow in practice.

For an individual, that might mean remembering whether a complaint was sent before a deadline. For a company, it might mean identifying letters awaiting approval or postal orders awaiting dispatch. The timeline must distinguish actions performed inside the platform from events confirmed by outside providers.

A tracking badge must never turn an assumption into a fact. If no carrier tracking information exists, the interface should say so. Clear states can be more useful than a vague “delivered” label that hides uncertainty.

Consider a letter that is prepared on Monday, approved on Tuesday and handed to a postal operator on Wednesday. Showing one date labelled “sent” would erase useful detail. A correspondence timeline should identify each confirmed step and, where available, distinguish the time an event occurred from the time Epistles received the update. This is especially valuable when an external provider reports information late or out of order. Users should also be able to recognise when the system simply has no newer tracking information.

Tracking is also about the next human action. After a formal request is posted, a sender might want to keep a reminder to review the response in two weeks. Another person may upload the reply when it arrives by ordinary post. The value comes from viewing the original request, the sending history and the subsequent response as part of one matter, rather than treating tracking as a single parcel-style badge.