Everyone knows how it should be done. Few can show it.
The rules, the steps and the to-do list usually sit in three different places.
The policy is a PDF nobody has opened
It was approved, filed and forgotten, so no one can say who has read the current version.
The process lives in one head
It works while that person is in. When they are away, the steps are rebuilt from memory.
The task list is three lists
One in a spreadsheet, one in a chat thread, one in a notebook, and none of them agree.
The rules, in a library people can search.
FinPera keeps policies and processes by company-wide scope and by function, with versions, owners and review dates in view.
Know who has accepted the current version
A policy is versioned and published. When a version needs acceptance, the people in scope are asked in the app to read and accept it, and reminded once a week later if they have not. A new version resets acceptance, and you see the count and the list of who has and who has not accepted it. Earlier versions stay on record.
3 of 4 accepted the current version
Start from the documents you already wrote
Import a document and it is read and given a proposed place: a title, a tab, an area and a type. You review each field before anything is saved, and import never publishes.
Proposed place
The report that tells you what to write next
Every search that finds nothing is recorded. Owners and admins open the Not found report from the page header. It groups them, so a question asked five times reads as a priority. It also shows whether nothing close exists or something near it needs improving.
Owners and admins see what the team searched for and did not find, grouped by how often it came up.
A written procedure becomes a checklist people run
Turn a process document into a checklist that can be applied to the work. The two are independent afterwards, so a running checklist never changes under the team. Edit the procedure and create a new checklist from it when you choose.
The same stages, every time
A workflow template holds stages and their tasks, with dependencies between stages and an approval where one is needed. Start one from the starter library or write your own, and each run becomes a job on a board by stage, so the work follows the same order each month and a step that needs approval waits for it.
One task list, three ways to see it
List, board and calendar views of the same tasks. Filter by priority, group by assignee or workflow, set a task to recur, and keep the discussion on the task itself.
Describe the goal, edit the checklist
Write what you want done in a sentence and get a checklist back, with a priority and a suggested role on each step. It is a draft: nothing is saved until you edit it and save it yourself.
Draft checklist. Edit before you save.
The people the work is assigned to.
A directory, an org chart and leave, so an owner is a person you can find.
Write it once. Run it the same way every time.
Put the policy, the workflow and the task list in one place.