Engagement data request register
Every engagement asks for dozens of files from several client teams, and within a fortnight nobody can say which were requested, promised, received or rejected. A single register, one row per request with owner, date asked, date due and status, becomes the document you send to the client, quote in escalations and use to explain why an analysis is late.
First tasks
- Create the register with ID, owner, asked, due, status and notes columns
- Enter every request already sent by email or mentioned in meetings
- Agree the six status values with the engagement manager
- Add the request ID to the subject line of each open request email