A long timesheet at month end is not a management decision. The monthly operating rhythm on the partner side is a short note: what closed, what is waiting, why enquiry volume moved, and which access still sits with the company.
Four lines, not a timesheet
Line one: queue items that closed, with the condition that made them done. Line two: what is waiting, and why. Line three: measurement, and whether the form, search and ads count the same enquiry once. Line four: risk, such as a certificate, a broken redirect, or an account whose access disappeared. Hours may sit in an annex. They do not replace the four lines.
The meeting does not stretch the decision
A short look every two weeks and one written note a month is enough. The meeting is not used to open new written scope by conversation. A new request joins the queue. If it replaces an item, that replacement is visible in the note. A spoken addition does not become a surprise on the next invoice.
The report does not hide ownership
Code ownership stays with the company. The report does not resell that sentence every month. It shows drift. If the repository is still a personal account, that is a finding. If the ads account ownership changed, it is on the note. If the handover list quietly lost a row, the rhythm says so in that week.
One note, not three PDFs
HED Creative is the accountable partner in Berlin and Ankara and keeps a single note. Website, software and ads do not arrive as separate PDFs. One counterpart reconciles conflicting numbers in the same table. The managing director approves the sequence instead of mediating it.
The written scope the note belongs to starts at IT partner. How the queue is written: retainer scope.