Data

Operational knowledge that compounds

Every event creates knowledge.

The schedule gives the data its shape

Most software organises information around its own category.

Task tools organise around tasks.
Ticketing systems organise around tickets.
Chat tools organise around conversations.

Cothena organises the operation around the event itself.

The schedule provides natural context: time, place, sequence and relationship.

The same activity can appear in a guest programme, a staff schedule, a runsheet, a task list and a conversation without becoming five unrelated pieces of information.

That shared structure is what makes the operational history reusable.

One event's activities at the centre, linked by dotted lines to the schedules, tasks, roles, notes, statuses, locations and chats that belong to them — a task board, a setup-briefing note, a venue address and a message from a speaker among them.

Captured as a byproduct of doing the work

There is no separate knowledge-management exercise.

Cothena structures the information your team already creates while using the platform:

Schedules, activities and runsheets
Venues, spaces and capacities
Tasks, dependencies and workflows
Conversations, notes and notifications
Products, packages, bookings and payments
Roles, people and permissions
Content and translations
Change history and audit trails
Planning context such as calendars, holidays and external information

The important part is not simply that this information exists.

It stays linked to the event, activity, person or decision it belongs to.

That is what makes it useful later.

What connected operational knowledge gives you

Faster onboarding

Give new team members the context of previous editions from day one.

Instead of waiting for one experienced person to explain how things were done, they can review the schedules, tasks, notes, conversations and decisions that shaped the event.

Better reuse

Turn previous events into working playbooks.

Clone schedules, activities, tasks and operational structures, then adapt them for the next edition rather than rebuilding from scratch.

Cothena preserves the relationship between editions, so reused activities can remain traceable back to where they came from.

Clearer root causes

Understand what happened before the final symptom appeared.

Tasks, dependencies, changes, timestamps and conversations provide context around blockers and delays, making it easier to trace how an issue developed and what else it affected.

Better comparison over time

Compare like with like across editions.

Because events share a consistent underlying structure, you can more easily spot recurring issues, understand what changed and identify patterns across events, seasons or locations.

Less key-person dependency

Important context stays with the organisation instead of leaving with the person who happened to remember it.

Decisions, notes, conversations and operational history remain available to the people who need them, subject to their permissions.

Review the event with Assist

Once the context is connected, Assist can help you work with it.

Ask questions such as:

What caused this activity to run late?
Which blockers appeared more than once?
What changed between this edition and the previous one?
Which tasks created downstream delays?
How did we handle this last time?

Assist can use the operational context already inside Cothena to help surface patterns, compare events and trace issues back through the work that produced them.

Instead of beginning with a blank prompt, it begins with the structure of the actual event.

Discover Cothena Assist

From individual know-how to shared operational memory

When information stays connected, the organisation becomes less dependent on whoever happens to remember how things were done last time.

Each person contributes to the system.

Each event adds to it.

And the next team can start with more of what the organisation already knows.

That is the idea behind Cothena:

coordination guided by wisdom and purpose.

See the structure behind an event

A single event can contain hundreds of relationships between schedules, activities, tasks, venues, products, conversations, notifications and people.

Explore an example event graph to see how those relationships form a connected operational model.

Explore the event graph

One event's data model drawn as a graph: several hundred nodes for schedules, activities, tasks, bookings and people, grouped in colour by type and linked by the dependencies between them.

See it against your own event

Bring a real edition — cities, dates, crews — and we will walk through what Cothena would be holding for you by the end of it.

Book a meeting Email us