Company data keeps accumulating. New tickets are opened and new documents written every day. A buyer that licensed a historical archive often wants the records created afterward, both to keep models current and to study how work changes. A refresh clause turns a one-time deal into a continuing supply without negotiating a new license each time.
The clause should define the increment clearly: records created or closed since the last cut-off date, from the same systems, in the same schema, de-identified by the same method. It should set the schedule and the price, which may be a fixed fee per delivery or tied to volume. Each refresh needs its own manifest and should pass the same acceptance checks as the first delivery. Rights do not stand still either. A customer contract signed last month or a revised privacy notice can change what may be included, so the rights position should be confirmed for each period. The clause should also say how exclusivity and term apply to refreshed records and how either party can end the schedule.
A refresh schedule should be realistic for the seller's team, since each delivery repeats the export, de-identification and checking work.