Paste a procedure and get back a concise, one-page job aid a worker can follow while the task is in front of them: numbered steps, the cautions that trip people up, and a quick-reference block for the calls that come up most.
Turn this [expense-approval procedure] into a one-page job aid.
An illustrative example. Your output will reflect your own sources, data, and prompts.
This pulls from the expense-approval procedure and the travel policy in your Knowledge Center, and keeps only what an approver needs while the report is open. Here is the one-pager, ready for your template.
Here is the procedure rewritten as a one-page job aid an approver can follow while the report is open in front of them. Six steps, each with the thing that most often goes wrong right beside it.
| Step | Do this | Watch out for |
|---|---|---|
| 1. Open the report | Open the submitted report and check the submitter, the date range, and the total. | Expenses dated more than 60 days ago. Flag the report for review before you go further. |
| 2. Check receipts over $25 | Confirm an itemized receipt is attached for every line above $25. | A card summary pasted in place of an itemized receipt. It shows the charge, not what was bought, so it does not count. |
| 3. Verify policy limits | Compare each line against the per-category limits in the travel policy. | Meals over the daily cap, and alcohol, which is never reimbursable. |
| 4. Check the budget code | Confirm the cost center and project code match the submitter’s team and an active budget. | A closed or wrong project code. Return the report rather than guessing which budget it belongs to. |
| 5. Approve or return with a reason | Approve if everything checks out. Otherwise return the report with a specific reason the submitter can act on. | A return with no reason. A vague bounce comes straight back unchanged. |
| 6. Confirm it routed to finance | After approving, confirm the report shows a “Sent to finance” status. | Reports that stall in “Pending sync.” If it has not moved within a day, contact finance. |
Quick reference — the calls that come up most:
Key contacts — Approvals and exceptions: Priya Nathan, finance-ops@company.com · Policy questions: the Travel & Expense Policy in your Knowledge Center · System issues: the IT help desk.
It is written to fit on a single page. Tighten any wording that runs long before you drop it into your template.
Want me to draft a wallet-size version that fits on a badge card, or a submitter's-side version so people file it right the first time?
A job aid is the short version people actually use: the steps in order, the two or three things that go wrong, and who to call when they do. The problem is that writing one means reading the full procedure, deciding what to cut, and formatting it so it fits on a page. That work is why most job aids never get made.
Paste the SOP, policy section, or your notes, or point Joy at the document in your Knowledge Center. Rough is fine; it does not need to be cleaned up first.
Ask for a job aid and name who follows it and when they use it. Joy keeps the steps a person needs in the moment and drops the background a full SOP carries.
Check the steps and the caution beside each one, tighten anything that runs long, and ask for changes in plain language ("add a step for mileage," "make the quick reference shorter").
Copy the finished job aid into your one-page template, wiki, or design tool. Joy drafts the content; you place it in the format your team prints or pins up.
Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.
Joy keeps the do-this steps and the common mistakes, and leaves out the policy background a worker doesn't need while the task is open.
Each step carries the thing that most often goes wrong next to it, so the aid prevents errors instead of just listing actions.
The if-this-then-that calls that come up most get their own short block, so people find the answer without rereading the whole aid.
A key-contacts line names who owns exceptions and where policy questions go, so a stuck worker knows the next move.
Ask for a badge-card version: the steps trimmed to a handful of words each, for a card people carry.
Flip the same procedure to the person filing the report, so they get it right before it reaches an approver.
Turn a branchy procedure into an if-this-then-that flow instead of straight numbered steps.
Add a short why-it-matters line to each step for someone doing the task for the first time.
A job aid is a short reference a worker follows at the moment of need, rather than a full procedure they study in advance. It gives the steps in order, the cautions that prevent common mistakes, and who to contact, all sized to fit on a single page.
No. Joy drafts the job-aid content as text in the chat: the steps, the cautions, the quick reference, and the contacts. You paste that into your own one-page template or design tool to produce the printed or PDF card. Joy writes the content; you handle the layout and printing.
It aims for one page: a numbered steps table, a short quick-reference block, and a key-contacts line. If your procedure is large, Joy keeps the steps a person needs in the moment and leaves out the background a full SOP carries, and you can ask it to tighten further.
Yes. Review what Joy drafted and ask for changes in plain language, such as adding a step, rewording a caution, or shortening the quick reference. Joy redrafts, and you copy the version you are happy with into your template.
The procedure or SOP itself, plus any policy that sets the limits the steps enforce and the approval matrix if there is one. The more of the real procedure Joy can see, the more accurate the steps and the cautions beside them.
Join the waitlist and be first to try this workflow when JoySuite launches.