Reports

What Are Reports in Enlivy?

Reports are structured forms that users fill out based on Report Schemas.

• Schemas are the blueprint (they define the structure, fields, frequency, and who should fill them).
• Reports are the actual instances users see and complete.

Think of it like this:

• Schema → Template (e.g., “Daily Work Report”)
• Report → Filled version of that template for a specific user, on a specific date.

Why Are Reports Useful?

Reports make it easy to:

• Collect consistent updates from your team without endless chats or meetings.
• Keep track of progress, challenges, and time worked in one place.
• Build a history of data that can be reviewed, exported, or analyzed later.

For example:

• Employees complete a Daily Standup Report with questions like “What did you work on today?”.
• Managers complete a Weekly Performance Report summarizing team results.
• Contractors submit a Timesheet Report to log their hours.

How Reports Work

1. An Admin Creates a Report Schema
   • Defines the fields/questions
   • Chooses who should complete it (user roles)
   • Sets how often it should appear (daily, weekly, on-demand)
2. Reports Are Generated for the Assigned Users
   • If the schema is daily, a new report appears for each day.
3. Users Fill Out the Report
   • They answer all required fields.
   • Conditional fields appear dynamically if logic is set.
4. Reports Can Be Reviewed & Exported
   • Managers or admins can see completed reports.
   • Data can be filtered or exported for further analysis.

Creating vs Filling Reports

• Admins & Managers → Create Schemas that define what reports should exist.
• Users (Employees, Contractors, Clients) → Simply fill out reports generated from schemas.

Key Elements of a Report

A single Report contains:

• Title – Taken from the schema (e.g., Daily Report – July 17, 2025).
• Fields – All the questions or inputs defined in the schema.
• Completion Status – Pending or Completed.
• Submit Button – Once filled, the report is locked and saved.

Filling Out a Report

When a user opens a report, they will see:

1. The Title & Instructions
2. All fields/questions in the order defined by the schema.
3. Conditional fields (if any) that appear based on previous answers.
4. Submit button to finalize the report.

Once submitted, the report cannot be edited unless allowed by an admin.

Example of a Completed Report

To better understand how a Report Schema translates into a real user experience, let’s look at an example of a completed report before it is submitted.

When a user opens a report generated from a schema, they will see all the fields you defined—text fields, radio buttons, checkboxes, timesheets, etc., organized exactly as you configured.