Month-End Close Calendar and Roles
Assign owners and deadlines.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Create a close calendar. Team members and their availability: [TEAM_AVAILABILITY]. Month-end date and reporting deadline: [DEADLINES]. Systems and dependencies (payroll provider, bank feeds, inventory counts): [DEPENDENCIES]. Produce a day-by-day table counting working days from month end: Day | Task | Owner | Backup | Depends on | Output | Deadline time. Include cut-off times for expense claims, invoices, and timesheets in the days before month end. Add a RACI-style table (responsible, accountable, consulted, informed) for the main tasks. Include a risk list (staff absence, late bank data) with a mitigation for each and an escalation rule if the close is more than one day late. Provide a message to the team announcing the calendar (90 words) and a short review template for after each close: what went well, what delayed us, one improvement. Use only the information given. Include a contingency rule for a missing person on close day (who covers which task) and a late-document rule: anything arriving after the cut-off date is recorded in the next month and listed in the close notes with its amount. Keep every conclusion tentative: it should rest only on the inputs I have given and nothing else. It is planning support only, and not accounting, tax, legal or investment advice. Do not act on this until an accountant or financial adviser experienced in [JURISDICTION] has reviewed it.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.