{"id":115,"date":"2026-09-24T09:00:00","date_gmt":"2026-09-24T07:00:00","guid":{"rendered":"https:\/\/yindle.com\/?p=115"},"modified":"2026-09-24T09:00:00","modified_gmt":"2026-09-24T07:00:00","slug":"processtappen-opvolgbare-acties","status":"publish","type":"post","link":"https:\/\/yindle.com\/en\/from-process-explanations-to-actions-that-can-actually-be-followed-up\/","title":{"rendered":"From process explanations to actions that can actually be followed up"},"content":{"rendered":"

Only turn a process step into an action when someone can actually complete something and the outcome can be checked.<\/strong> \u2018Documents\u2019 is a subject; \u2018upload the signed intake form\u2019 is an action. Name the owner, desired outcome and any date, and track the status for each file.<\/p>\n

Process descriptions explain how a journey works. Actions direct today\u2019s work. When the two are mixed, clients may think an explanation is mandatory or miss a task among informational text. Good customer portal design<\/a> uses them alongside each other with different visual emphasis.<\/p>\n

Write an action as a verifiable sentence<\/h2>\n

Use the formula: verb + object + criterion. \u2018Review\u2019 is too vague. \u2018Check proposal v2 and choose approve or amend\u2019 explains the endpoint. Add a date only if it comes from the actual process and someone is responsible for maintaining it.<\/p>\n

Yindle Portal separates ordered process steps from action items. For each file, an action can be open, completed or confirmed, with a note and the person confirming it. \u2018Step 3\u2019 therefore does not have to be complete for every file at the same time.<\/p>\n

Choose who may change the status<\/h2>\n

Not every task can be ticked off by the client. Distinguish in advance between:<\/p>\n