Skip to main content
Product

From decision to delivery

Work in a list or kanban board, assign one person, due dates and dependencies, and send tasks to configured integrations.

List and kanban board Assignment and company permissions Task dependencies
Visualization for the page: From decision to delivery
Product view

List and kanban board

The list supports filtering and bulk actions, while the board groups the same recommendations by status. Switching views creates no copies.

The workspace currently has no 30/60/90-day timeline. Planning uses a horizon, status, and task due date.

In this area

Assignment and company permissions

A task can be assigned to one person. Access to operations is also controlled by company membership roles.

There are no separate task roles for executor, approver, and observer. We also do not claim task-detail filtering designed specifically for leadership.

In this area

Task dependencies

Some actions only make sense after others are done — content work after a technical blocker is removed, for example. Dependencies are recorded explicitly on tasks.

The team sees what blocks what and avoids spending time on work that cannot pay off in the current state.

In this area

Integrations with your tools

GeoFolks tasks can be pushed into the tools your teams already use, keeping a back-link to the assessment context and evidence.

We do not force your organization to change its processes — we bring the context to where the work actually happens.

In this area

Comments and operation trail

A recommendation stores status, assignment, dates, comments, and attachments. Changes made through controllers are recorded in the platform audit log.

Not every audit entry is currently shown to clients as a complete per-task timeline. Full reconstruction requires administrative audit access.

In this area

Implementation and verification status

Statuses distinguish implementation, verification, and confirmation. A user can store a review result on the recommendation.

Closing a task does not automatically launch a dedicated remeasurement or calculate task impact. Verification must use a later run and be recorded deliberately.

Next step

Organise the delivery workflow

Work in a list or kanban board, assign one person, due dates and dependencies, and send tasks to configured integrations.