◆ Asana

Manage month-end close processes

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskFor the month-end close, create tasks for Sarah to reconcile bank statements by the 28th, for…+
For the month-end close, create tasks for Sarah to reconcile bank statements by the 28th, for David to finalize payroll by the 29th, and for Maria to prepare financial reports by the 30th. Mark all as high priority and assign them to the 'Finance Team' project.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore the next month-end close, review the current process. Highlight any bottlenecks from the…+
Before the next month-end close, review the current process. Highlight any bottlenecks from the last three closes, suggest ways to automate repetitive data entry, and propose a new sequence for tasks that could shave a day off the overall timeline.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentDavid just told me the payroll software crashed and he can't access the data, and it's already…+
David just told me the payroll software crashed and he can't access the data.
David just told me the payroll software crashed and he can't access the data, and it's already the 29th. The finance director is expecting preliminary numbers this afternoon, and I'm worried about missing the deadline. What's the immediate impact on the month-end close, and what's the best first step to keep us on track?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing hours every month chasing people for their month-end close updates, often because…+
I keep chasing people for their month-end close updates, losing hours every time.
I keep losing hours every month chasing people for their month-end close updates, often because they don't see the urgency until the last minute. It feels like I'm always pulling teeth to get progress reports. What habit should I change to get everyone to proactively update their task status without me constantly nagging?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Asana's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.