The process card: one page that is both the instruction and the control

Most AI training teaches people to write prompts. That produces a drawer full of prompts nobody else can use and a result that changes every time. A finance team does not need prompts. It needs processes, and a process has a shape that has not changed in fifty years: something comes in, something is done to it, something goes out, and somebody checks.

The six lines

Input

What comes in, and from where. The file, the export, the report.

What I do to it

The steps, in order, in plain language. Where a rule applies, the rule.

Output

What goes out, in what layout, to whom.

Who checks

The named person who approves it, and what they look for.

How often

Monthly, weekly, on request, on a schedule.

How long

Hours per cycle today. This is the number the roadmap ranks on.

Written out, the card is the instruction the tool follows. It is also the document that tells an auditor, a new hire, or a colleague covering your vacation exactly what happens and who signs off. One page, two jobs.

A filled-in card

Input

AP open-item extract as of the last day of the month, by company. Trial balance report, PDF, same date.

What I do to it

Pivot open items by company and GL offset. Map each offset to its GL control account. Compare to the trial balance line. For each difference: if the GL date is after the activity date, mark timing; otherwise mark for investigation and write one line saying why.

Output

Reconciliation workbook: summary, TB totals, AP-versus-GL by account, difference and classification. Draft approval email listing accounts with zero difference and accounts with explained timing items.

Who checks

Accounting supervisor. Looks for zero differences, timing items explained, anything marked for investigation.

How often

Monthly, business day three.

How long

Four hours today.

The test

In the course, pairs swap cards. You run your neighbour's process on their data from their card alone. If you can, it is a process. If you cannot, the card is missing a line, and that is worth knowing before a tool runs it a hundred times. This is also why nobody in the room gets their prompt fixed for them. They get sent back to the card.

Why this beats a prompt library

• A card is owned by the process, not the person. It survives turnover.
• The 'who checks' line is a control. A prompt has no such line.
• The 'how long' line ranks the roadmap. Hours times frequency times how rule-bound it is tells you what to automate first.
• A card can be handed to a systems person to build into a scheduled agent without a single meeting to explain it.