Programme notes
Reading for the interval
Practical notes for people who run content operations.

Rights registers: the three dates that matter
Record the date a licence starts, the date it ends and the date you must act to renew or remove. That third date is usually weeks before expiry, and it is the one most registers forget. Pair each with an owner, not a team.
An editorial calendar is a view, not a spreadsheet
If the calendar is a separate document, it will drift from reality. Store each commissioned item once, with its date and status, and generate calendar views from those records. Editing the calendar should edit the item.
Matching contributor invoices to delivered work
Agree the fee at commission, record delivery and approval against the same item, then match the invoice to that item. Mismatches become visible questions rather than awkward surprises at month end.
Version naming that survives
Let the system hold versions; let people name files for meaning. A single record with version history beats a folder of files named final. If you must use files, agree a short pattern: item, channel, date, initials.
Approvals that hold up later
Record who approved, what exactly they approved and when. An approval of an earlier draft is not an approval of the published version. Good tools make this automatic.
When not to buy software
If no one owns the process, software will not fix it. Name an owner, write down the statuses and run the process for a month. Then decide.