Tracking plans
Use cleaning and control plans to set how many logs each shift expects, handle public holidays, and measure plan compliance as a percentage.
A tracking plan is a schedule that defines how many cleaning or control logs a location should receive in each time slot of the day. It is the digital version of a paper restroom cleaning schedule: you set the shifts, staff log their work, and EnaFeedback compares what happened with the plan and calculates compliance.
Required role and prerequisites
- Owner, Administrator or Hygiene manager can manage cleaning and control plans.
- Your field staff need the Cleaning or Control role, so there are logs for the plan to measure.
- For holidays to be evaluated correctly, define them under System → System settings → Hours and holidays.
How plans are structured
There are two separate domains: Cleaning plans and Control plans. Each domain has:
- One global plan, with the day start (default 08:00), the shifts, and locations opted out of the plan.
- Optional custom plans, for example tighter shifts for a busy polyclinic waiting area. A location can belong to at most one custom plan per domain.
- Two day profiles: routine and public holiday. In the English interface they appear with their Turkish labels, Rutin and Resmi tatil. You can use a different shift pattern on holidays.
Creating a plan
Open the plan screen
For cleaning, go to Cleaning logs → Cleaning plans. For control, go to Control logs → Control plans.
Edit the global plan
Check the day start time and opt out any locations that should not be tracked.
Define the shifts
For each shift, enter a start, an end and the required number of logs (1–3). Arrange shifts by dragging on the timeline or edit them in the table view. Do this for both the Rutin and Resmi tatil profiles.
Add custom plans if needed
Create a custom plan for locations that run at a different pace and assign those locations to it.
Choose the effective date
When you save, set the date from which the plan applies.
Shift rules
| Rule | Value |
|---|---|
| Required logs per shift | 1–3 |
| Shortest shift | 30 minutes |
| Time grid | 5-minute steps |
| Default day start | 08:00 |
Versions
Plans are versioned. Each change is saved with an effective date, and past days stay evaluated against the plan that was in force at the time. The interface notes this as Past days are preserved. Changing a plan does not rewrite your past reports.
Plan compliance
The Plan compliance view shows two measures:
- Completion % = the sum of min(actual, required) per shift ÷ the sum of required. Extra logs in one shift do not make up for a shortfall in another.
- Success % = shifts that met their requirement ÷ all shifts.
You also see each location's operational status for today. Cleaning and control compliance are reported separately.
Example
If a shift requires 2 logs and 3 were made, 2 count toward completion. If 2 of 3 shifts are met, success is 67%.
Hours and holidays
Working hours and holidays live under System → System settings → Hours and holidays and are used only by tracking plans. Enter holidays by hand or import your country's public holidays from Nager.Date. Days marked as holidays use the Resmi tatil profile.
Tips and common mistakes
- Holidays not entered: without them, public holidays are judged against the routine plan and compliance looks low.
- One location in two custom plans: a location can belong to only one custom plan per domain.
- Unrealistic targets: set the required count to match your staffing. Because of the 30-minute cooldown, one person may not be able to log twice in a short shift.
Related articles
Can't find what you need?
Our support team can help with anything from setup to reporting.
Cleaning and control logs
How field staff log cleaning and control rounds at a location, how control parameters and quality % work, and how proof of presence is enforced.
Attendance
How field staff check in and out at a location, use I forgot to check out, and how admins review verified attendance with Excel and PDF exports.