In Beneficiari & Cazuri (Beneficiaries & Cases), each case has its own timeline. You can add events such as appointments, therapy, tasks or notes and optionally link each event to a relevant project and an existing document. The timeline supports organization and beneficiary/case reporting, but it is not an external calendar and does not send notifications by itself.
When to use a case timeline
Use a case when one beneficiary has a need that should be tracked separately: treatment, a therapy period, an education program, a social-support process or a cross-border case. The timeline is for operational steps inside that case: a consultation, session, trip, deadline, payment follow-up or note.
Do not create a new case for every appointment. The case is the broader context; events are the steps inside it.
1. Open the correct beneficiary and case
Go to Beneficiari & Cazuri, choose the Cazuri (Cases) tab and open the relevant case. The detail view shows the beneficiary, case status, objective, projects and related documents. + Eveniment adds a new step to that case's timeline.
2. Choose the event type and status
The current event types are Appointment, Therapy, Medical, School, Social support, Travel, Document, Payment, Task, Note and Other. These are organizational labels; they do not trigger an external integration.
Available statuses are Planned, Done, Info and Cancelled. A planned event shows a Finalizat (Done) action in the case timeline. You can also edit or delete an event.
3. Use event date/time and due date correctly
An event can have a main date/time, a due date, or both. For an appointment, the event date is usually primary. For a task, the deadline may matter more.
In the current implementation, lists and upcoming indicators use event date/time first and only fall back to the due date when no event date exists. When both are present, the timeline card does not display them as two separate dates.
4. Add provider, location and concise details
You can store Provider / person, Location and Details. Use these for short operational context: clinic, therapist, institution, city, confirmation number or the next practical step.
For detailed medical information, apply data minimization. A case timeline is not a medical record system and should not become a place where full diagnoses or sensitive documents are copied automatically.
5. Link a relevant project
Proiect asociat (Linked project) is optional. The selector is built from projects that TidyOne considers relevant to the beneficiary/case, including the primary project and projects linked through the multi-beneficiary project structure.
Linking a project adds operational context. It does not create a financial transaction or allocate money. If the event represents a real payment or expense, record that separately in Finance.
6. Link an existing document
Document asociat (Linked document) lets you select an existing document related to the case, beneficiary or relevant projects. The event stores the document reference and can show the file name in the timeline.
The case's Documente asociate (Related documents) section currently shows up to 10 matching documents. It is a short case view, not the complete archive.
7. Treat “next action” as an indicator, not a reminder system
In the cases list, TidyOne finds the first future Planned event and shows it as the next action. The beneficiary/case report uses the same principle for Următoarea acțiune (Next action).
This gives quick orientation, but it does not send email, SMS or push alerts and does not automatically sync the timeline to Google Calendar, Outlook Calendar or another external calendar.
8. How the timeline appears in beneficiary / case reports
In Reports → Beneficiary / case report, TidyOne can show the selected case context and events within the report period. The summary counts planned, done and cancelled events, while the timeline table renders the first 20 events in that period.
When you generate an AI draft for a case report, the backend includes up to 30 events from the selected period with type, title, status, dates and provider. Sensitive case health fields are intentionally excluded from this AI reporting flow.
For a report filtered to a beneficiary or case, the Accounting package ZIP can include `timeline-caz.csv`. Full PDF/CSV/ZIP exports currently require the Association PRO plan.
Example: treatment in another city
| Step | Event | Useful link |
|---|---|---|
| 1 | Initial assessment appointment | Provider + location + project |
| 2 | Clinic document received | Existing document |
| 3 | Task: confirm transport | Due date |
| 4 | Travel | Date/time + location |
| 5 | Consultation completed | Done status |
These events describe the case workflow. Travel, accommodation or treatment costs still belong in financial transactions and, when shared across beneficiaries, require explicit allocations.
Current limitations to know
Frequently asked questions
Can I create an event without a date?
Yes. The data model allows events without an event date or due date. They remain in the timeline, but cannot become the upcoming action until they have a relevant future date.
Can the same document be linked to several events?
Each event stores one document reference. A relevant document can be selected in more than one event context without duplicating the underlying file.
Does marking an event Done close the case?
No. Event status and case status are separate. The case remains Active, Paused, Completed or Archived until it is edited.
Does a Payment event create an expense?
No. “Payment” is only an event type. The financial transaction must still be recorded through the Finance workflow.
Does the annual nonprofit report include the full case timeline?
Detailed timeline context is mainly used in beneficiary/case reporting. The annual organization report stays focused on finances, projects, funds, documents and data quality.
Continue with related guides
A useful timeline shows what happens next without turning every appointment into a separate project or case.
Open Beneficiaries & CasesThis tutorial documents functions present in the TidyOne V13.5.30 package inspected on 24 September 2026. It does not assume external calendar sync, automatic timeline notifications or file uploads directly from the Event form.