Revit exports the sheet set to a folder. Twenty-two PDFs, each with a revision letter in the title block. That part is quick. Then comes the issue sheet: which drawings, which revision, who gets them, by what means, on what date. Someone types it into a spreadsheet, or into a Word table, and about one time in ten it is wrong.
The system watches the issue folder on Dropbox or Google Drive. When a new set lands, it reads the drawing number and revision from each file name or title block, compares it to the last issue, and lists what changed. A-101 goes from C to D and A-204 is new. The rest is unchanged.
You tick the recipients from the project's distribution list: contractor, structural engineer, client, the party wall surveyor if it matters this time. The issue sheet is generated in your format, numbered and dated, and goes out by email with the drawings attached or linked, from your own account. A copy of the sheet is filed with the drawings. The register in Google Sheets gets a row per drawing per recipient.
Four months later, when the steel is 50mm out and the fabricator says he worked from revision B, the register says revision D was issued to him on 3 June at 16.02 and opened on 4 June. This is the kind of thing we build. It runs in your own accounts. Which revision does your contractor think he has?