In any organisation, work happens in many different ways. Some work is planned in advance. Some work happens because someone is responsible for it. Some work happens suddenly when a customer or vendor contacts you. Tuhund is designed to handle all of this clearly and consistently.
To do this, Tuhund uses three distinct but connected concepts: assignments, reminders and events. Each one represents a different aspect of work. Together, they form a complete and accurate picture of responsibility, planning and execution.
Assignments
Assignments define responsibility.
An assignment in Tuhund means that a person or a team is responsible for something. It does not matter whether the work is planned or unplanned. It does not matter whether it involves a customer or not. The assignment simply establishes ownership.
What an assignment represents
-
A person or role is accountable
-
The work can be internal or external
-
The work can be linked to a business record or be completely standalone
-
Progress and completion can be tracked
Assignments can be created by users or automatically by the system.
Common examples
-
A service request assigned to an engineer or a team
-
An approval task assigned to a manager
-
A system generated task from a workflow
-
A personal operational task created by a user
A service request itself is an assignment. Even though many interactions may happen during its life, responsibility always stays with the assigned person or team.
Assignments run in parallel with reminders and events. They do not replace them.
Reminders
Reminders define planned interactions.
Reminders in Tuhund represent work that is planned to happen in the future. They are not simple alerts. They are structured plans that are visible across the system.
What a reminder represents
-
A future interaction is planned
-
The interaction involves a customer, vendor or agent
-
The interaction is linked to a clear business context
Key characteristics
-
Always linked to a customer, vendor or agent
-
Associated with business records such as
-
Meetings and enquiries
-
Quotations, proforma invoices and sales orders
-
Commercial invoices and collections
-
Service requests, installations and CRM activities
-
-
Visible on calendars, home pages and dashboards
-
Triggers alerts and notifications
-
Represents intent and preparation
Reminders help users organise their future work and ensure that important interactions are not forgotten.
Events
Events define what was actually done.
Events in Tuhund are records of completed work. This includes both digital and physical activities.
What an event represents
-
A completed interaction with a customer, vendor or agent
-
Physical activities such as
-
Visiting a customer site or factory
-
Performing inspections or installations
-
Handing over documents, samples or materials
-
Collecting items, signatures or payments
-
-
Meetings, calls and detailed discussions
Events capture reality, not intention.
Key characteristics
-
Can be created from a reminder after execution
-
Can also be created directly without any reminder
-
Always linked to a customer, vendor or agent
-
Stores detailed notes, outcomes and observations
-
Supports metadata, attachments, images and documents
-
Fully integrated with Tuhund’s expense claims management
-
Allows travel, accommodation, meals and other expenses to be recorded
-
Does not trigger alerts
Events form the permanent and auditable record of work done.
Expense claims and events
A critical design principle in Tuhund is that expense claims are always linked to events.
When work involves travel or out of pocket spending, those costs are recorded against the exact event where the work happened. This ensures that:
-
Expenses are tied to real activity
-
Claims are linked to the correct customer or job
-
Approvals are clear and contextual
-
Reporting is accurate and auditable
This makes Tuhund’s expense management both strong and trustworthy.
Planned and unplanned work
Tuhund supports both planned and reactive work.
Planned work
A reminder is created for a customer visit.
The visit happens as planned.
The reminder is executed and becomes an event.
Expenses and documentation are recorded.
The event may create the next reminder.
Unplanned work
A customer calls without notice.
A visit or detailed discussion follows.
No reminder existed beforehand.
An event is created directly.
Expenses and records are still captured.
Unplanned work is common and is treated as first class activity in Tuhund.
A continuous and cyclic workflow
In many sales and service scenarios, work repeats until a larger objective is completed.
In Tuhund:
-
Reminders represent planned interactions
-
Events represent completed interactions
-
Events can create new reminders
-
This cycle continues until the parent work is finished
This is common in sales follow ups, negotiations, installations and service delivery.
How everything fits together
Assignments define who is responsible.
Reminders define what is planned.
Events define what was actually done and what it cost.
Each concept has a clear meaning and a clear boundary.
Why this matters
With this design, Tuhund provides absolute clarity to both humans and the system itself.
People clearly understand responsibility, plans and execution.
The system clearly understands intent, action and outcome.
This clarity enables reliable automation, predictable workflows and accurate reporting. It forms a strong foundation for system driven intelligence and AI.
Very few ERP systems in the world have achieved this level of conceptual clarity. Tuhund is one of them.
This is what allows Tuhund to move beyond recording transactions and into understanding, guiding and improving real business operations.
