Step-by-step instructions: how to turn a process description into a clear checklist
The Step-by-step instructions tool helps you turn a free-form process description into a structured checklist. You enter text describing a sequence of actions, specify available time and goal, and receive an ordered list of steps with prerequisites and checkpoints. This is convenient for everyday work tasks: meeting prep, onboarding, reporting, event organization. In this article we’ll walk through how to formulate your input correctly, provide a concrete example, and show how to verify the result and what limitations to keep in mind.
Open tool: Step-by-step instructions ↗What the tool actually does
The tool accepts a textual description of a process — up to 8000 characters in the first field and up to 1000 characters in the details field. You also specify available time (e.g. "30 minutes") and goal (e.g. "hold a meeting and record decisions"). Based on this an ordered checklist is generated: steps follow a logical order, prerequisites (what must be ready before starting) and checks (how to verify a step is completed) are added.
Important to understand: the tool does not perform actions for you and does not guarantee results. It only structures your text. If the input contains contradictions or missing key details, the checklist may end up incomplete. The more specific the description, the more useful the result.
The interface is a web form with text fields. There are no sliders, style presets or change levels. You select output language, press Generate and get one result in a separate panel. You can copy it or download it as plain text TXT. Other formats (DOCX, PDF) are not supported.
Input: "Need to prepare and conduct a weekly team meeting of 5 people. Goal — agree on tasks for the week. Time — 30 minutes". Output: a checklist with steps: identify participants, collect topics, send invitation, prepare agenda, conduct meeting, record decisions, send follow-ups.
How to prepare your input data
The first step is to describe the process in your own words, without unnecessary digressions. State what is being done, in what order and what resources are needed. For example: "First I collect requests from colleagues, then check them against budget, then approve with the manager and only then pass to work". The clearer the sequence, the more accurate the checklist.
In the Details field you can add constraints: who participates, what deadlines, what tools are used. For example: "Participants — 5 people, meeting online, agenda document needed". This helps the tool take the context into account. Do not enter more than 1000 characters in this field.
The Available time field sets boundaries. If you write "15 minutes", the tool may suggest a more concise checklist. If "2 hours" — a more detailed one. Formulate the Goal field as a result: "get manager approval", "record agreements", "pass task to work".
Example filling: input — "Every Monday I collect statuses from three departments, merge them into a table, check discrepancies and send report to director". time — "1 hour". goal — "send report without errors".
Step-by-step breakdown on the example of meeting preparation
Consider the example: preparing and conducting a weekly team meeting. Suppose you have 30 minutes for the meeting itself and 20 minutes for preparation. Goal — agree on tasks for the week. You enter the description: "Need to collect topics from participants, prepare agenda, send invitation, conduct meeting, record decisions and send follow-ups". The tool can output a checklist of 7–9 steps.
A typical result will include prerequisites: "Participants defined", "Topics collected", "Agenda ready". Then steps: "Send invitation with agenda", "Conduct meeting by agenda points", "Record decisions and responsible persons", "Send follow-ups within an hour after meeting". And checks: "Did all participants confirm participation?", "Is there a record of decisions?, "Did participants receive follow-ups?".
Such a checklist can serve as a basis for real planning. But remember: this is just structure, not a guarantee that the meeting will go perfectly. You decide which steps to add or remove.
Generated checklist (excerpt): 1. Check that all participants are available. 2. Collect topics by Friday. 3. Prepare agenda and allocate time. 4. Send invitation a day in advance. 5. Start meeting on time. 6. Record decisions. 7. Send follow-ups.
How to verify the result
After generation carefully read the checklist. Make sure steps are in logical order and no key actions are missed. Check that prerequisites are present — they should be executable before the process starts. If a prerequisite sounds vague ("everything ready"), replace it with a specific one ("agenda approved").
Pay attention to checks. A good check answers the question "how do I know a step is completed?". For example, "decisions recorded and sent" is a check. If there are no checks, add them manually. The tool may not account for your specific domain, so final responsibility rests with you.
Compare the result with your goal. If the goal is "agree tasks" and the checklist has no step "record responsible persons", that is a gap. Supplement the list. Remember: the model may make errors, and queue and availability may change.
Verification: the step "Send invitation" has prerequisite "agenda ready" and check "all confirmed". If no check exists, add: "Make sure all replied to the invitation".
Limitations and common errors
The tool does not support document upload, does not perform OCR, has no comparison modes and does not automatically save results. You can only copy or download TXT. No batch processing, integrations or email delivery. Everything you input is processed in a single request.
Do not use the tool for legal, medical or financial processes where personalized consultation is needed. It does not give guarantees and does not replace an expert. Also do not try to generate images or audio — this is a text tool. Audio is not sent to AI: speech is processed locally via eSpeak if you use that function separately.
A typical error — too general description. The phrase "make a report" will not give a useful checklist. Better: "collect data from three sources, check totals, consolidate into a table, send to manager". Another mistake — ignoring the Time field: without it steps may be unrealistic.
Poor input: "Conduct a meeting". Good input: "Conduct a meeting with a team of 5 people, discuss project statuses, record blockers, assign responsible persons, send follow-ups".
Practical tips for using the tool
Break complex processes into parts. If the description exceeds 8000 characters, shorten it or split into multiple requests. For example, describe preparation separately, then conduct, then wrap-up. Checklists will be more accurate.
Use the Details field to specify roles and tools. For example: "Responsible — manager, tool — Google Meet, document — Google Docs". This helps the tool include relevant steps, e.g. "create agenda document in Google Docs".
After generation save the result as TXT and edit it to suit you. Add deadlines, names, links. The tool gives a skeleton, filling is your task. Do not rely on it as the sole source of truth.
Tip: if the checklist is missing a step "assign responsible person", add it manually. The tool does not know your team.
The Step-by-step instructions tool is a practical helper for transforming a process description into a structured checklist. It suits everyday tasks: meeting prep, reporting, onboarding, planning. The key is to give specific input data, specify time and goal, then verify the result and supplement it. Remember the limitations: no document upload, no automatic saving, no guarantees. This is just a structure, not a ready-made solution. Use it as a starting point for your own workflows.
Open tool: Step-by-step instructions ↗Interface translations are machine-assisted and may need refinement.