Skip to main content

Resource Conflicts

Find, review, and resolve double-booked people, tools, and locations on a project schedule.

Overview

Resource Conflicts checks the people, tools, and locations booked on a project schedule and flags any booking that can’t realistically happen. For example, a technician booked on two full-day events on the same day, a tool that is due for maintenance during the job, or a walkdown scheduled on a Saturday when nobody is working.

Conflicts are warnings, not blocks. Epsilon3 always saves your change first, then tells you about any new conflict so you can fix the booking or accept it with a written reason. Nothing on the schedule moves on its own.

Why use Resource Conflicts

  • Catch double-bookings while you are still planning, not on the day of the operation.

  • Keep tool and facility schedules realistic by flagging bookings that land on maintenance or outside working hours.

  • Check that the people you book actually hold the skills, roles, or group membership the work requires.

  • Leave a clear record when a conflict is intentional, such as approved overtime or a weekend shift.

Where conflicts appear

  • Project Schedule tab: open a project from Planning > Projects. The left sidebar has a Conflicts tab with a count of flagged conflicts.

  • Gantt view: an amber warning triangle next to the event name and a dashed amber outline around the bar.

  • Event popup: the Resources section shows a warning count and the conflict next to each affected resource.

  • After you save: a message tells you when a change creates a new resource conflict.

Note: Conflict markers only appear in the Gantt view of the schedule. The Calendar and List views do not show triangles or outlines.

What gets checked

Epsilon3 checks three kinds of resources: people, tools (each individual tool instance), and locations.

Each resource is checked against everything it is booked on across the whole workspace, so a double-booking caused by another project still shows up.

A booking counts toward conflicts when it is:

  • A user, tool, or location added to an event, either directly with Add Resource or by filling a requirement. Each booking has an allocation percentage, which defaults to 100%.

  • An assignee on an open work order (Planned or Running) with planned dates. Work order assignees count at 100% across the planned dates, with no event needed.

Conflict types

Every conflict is labeled with an amber tag that tells you what is wrong:

  • Over-allocated: a person, tool, or location is booked for more than 100% of their available working time on a day. Exactly 100% is fine.

  • Outside Working Hours: the event has no working time at all for that resource, such as an event that falls entirely on a weekend or holiday. An event that is only partly outside working hours is not flagged.

  • Tool Unavailable: the booked tool is archived or marked as scrap. A tool that is simply checked out is not flagged.

  • Maintenance Due: a maintenance routine set to block use comes due on a booked tool or location before the booking ends.

  • Missing Skill: a person booked against a requirement doesn’t hold a required skill, or the skill expires before the event ends.

  • Missing Role: a person booked against a requirement doesn’t hold the required role.

  • Not in Group: a person booked against a requirement isn’t a member of the required group.

How over-allocation is calculated

Epsilon3 looks at each day on its own, in the resource’s time zone. For every booking that day, it takes the working time the booking covers and multiplies it by the booking’s allocation. If the total for the day is more than the resource’s working time, the day is flagged.

For example, with working hours of 9:00 AM to 5:00 PM, a person booked at 100% on a 9:00 AM to 5:00 PM event uses the full 8 hours. If they are also booked at 100% on an event from 2:00 PM to 6:00 PM, that event covers 3 working hours (2:00 to 5:00 PM), or 37.5% of the day. The total is about 138%, so the day is flagged as Over-allocated.

  • Bookings aren’t compared by clock time. Two 4-hour events at the same time total 100% of an 8-hour day and are not flagged.

  • Milestones and bookings at 0% add no time, so they never cause over-allocation.

  • Consecutive days with the same bookings are grouped into one conflict, such as “Dec 1 – Dec 3 (3 days)”.

  • Only today and future days are checked. By default the Conflicts tab looks at the next 90 days, or at the date range set on the schedule.

Set working hours

Conflict checks are only as accurate as your working hours. Tools and locations use the workspace hours in Settings > General > Working Hours, plus any holidays or special days added under Schedule Exceptions. New workspaces start with Monday to Friday, 9:00 AM to 5:00 PM.

17-working-hours

People use their own Work Schedule from their User Profile when one is set. Workspace holidays still apply to them. A person’s time zone comes from their profile, and the workspace time zone is used when the profile is set to UTC.

Find conflicts

See new conflicts as soon as you save

When a save creates a new conflict, a message appears at the top of the page, for example 1 new resource conflict. Click Review to jump straight to it in the Conflicts tab. The Conflicts tab also shows the total count and a blue New badge until you open it.

04-toast

Note: If the Conflicts tab is already open when you save, the message is skipped and the new conflict is simply tagged New in the list.

Spot conflicts on the Gantt

In the Gantt view, events with a conflict show an amber triangle next to the event name and a dashed amber outline around the bar.

01-overview

Hover over a triangle to see who is affected and why.

02-tooltip

Click an event to open its popup. The Resources header shows the number of conflicts, and each affected resource shows the problem in amber text, such as 200% in window for over-allocation.

03-popup

Review the Conflicts tab

  • Go to Planning > Projects and open the project.

  • On the Schedule tab, click Conflicts in the left sidebar.

  • The summary line shows how many conflicts are flagged and accepted, and the date range checked, for example “3 flagged · 0 accepted · Next 90 days”.

  • Conflicts are grouped by person, tool, or location. Each card shows the conflict type, the date, and a short description.

05-list

Open a conflict

Click a conflict card to open its details. From here you can see every event involved and its allocation, the Peak Allocation for over-allocated resources, and the ways to resolve it. Use the arrows at the top to step through each conflict, or All Conflicts to go back to the list.

06-detail

Click Show on Gantt to focus the schedule on the conflict. The events involved are highlighted, everything else is dimmed, and the affected days are shaded. A banner shows the resource and conflict type. Click Done or Exit Gantt Focus to return to the normal view.

07-focus

Resolve a conflict

The Resolve section offers the options that make sense for the type of conflict. You need the Edit Events permission to see it.

  • Over-allocated: Reduce Allocation, Move Event, Reassign, or Accept With a Reason.

  • Outside Working Hours: Move Event, Reassign, or Accept With a Reason.

  • Missing Skill, Missing Role, Not in Group, Maintenance Due, and Tool Unavailable: Reassign or Accept With a Reason.

When a conflict is cleared or accepted, Epsilon3 confirms it and moves you on to the next conflict in the list.

Reduce Allocation

Use this when the resource can split their time, for example a lead who only needs to be on part of an event.

  • Select Reduce Allocation.

  • Choose the Event to change.

  • Drag the New allocation slider. Epsilon3 suggests a value and the helper text tells you whether it will work, such as Should clear this conflict.

  • Click Lower to N%.

08-reduce

Move Event

Use this to reschedule the event to a time when the resource is free.

  • Select Move Event. The panel reads Drag a highlighted bar to new dates.

  • On the Gantt, drag the highlighted event bar to its new dates.

  • For a repeating event, choose whether to move only that date or the whole series.

09-move

Moving an event can create a different conflict. For example, dragging an event onto a Saturday clears an over-allocation but creates an Outside Working Hours conflict. Check the Conflicts tab after you move it.

Reassign

Use this to hand the booking to someone or something else that is available.

  • Select Reassign.

  • Choose the Event booking to reassign, then click Find Replacement.

10-reassign

The Reassign window lists candidates that match the booking. Each row shows how well the candidate matches the requirement (Strong match or Partial match) and how much of their time is free. Partial matches include a short warning, such as only having 50% free on the busiest day.

  • Use Hide fully allocated and Hide ineligible to narrow the list, or search by name.

  • Select the replacement and set the Allocate slider.

  • Click Assign.

11-reassign-modal

A confirmation appears, such as Conflict cleared for kyle@epsilon3.io, and the next conflict opens.

12-cleared

Accept With a Reason

Some conflicts are intentional, like an approved weekend shift or planned overtime. Accepting a conflict records why it is acceptable and removes it from the flagged list. Nothing on the schedule changes.

13-owh

  • Select Accept With a Reason.

  • Enter a Reason (required), up to 2,000 characters.

  • Click Accept Conflict. For a repeating event, the button reads Accept N Occurrences.

14-accept

The conflict moves to the collapsed Accepted section at the bottom of the Conflicts tab, along with its reason. Its triangle and outline are removed from the Gantt.

Important: A reason is always required. There is no way to dismiss a conflict without one, so the schedule keeps a record of every accepted conflict.

Revoke an accepted conflict

  • On the Conflicts tab, expand Accepted.

  • Find the conflict and click Revoke.

  • In Revoke Exception, click Revoke to confirm.

15-accepted-list

16-revoke

The conflict is flagged again, and the exception stays in the log as revoked.

When an accepted conflict comes back

An acceptance covers the bookings and dates involved when it was accepted. The conflict is flagged again if:

  • A new booking is added on one of the accepted days.

  • The over-booking spreads to days outside the accepted dates.

  • For conflict types other than Over-allocated, the bookings involved change.

Repeating events

Each occurrence of a repeating event is checked on its own. Conflicts from the same series are rolled up into one card labeled N Occurrences. From the details you can accept the whole series with one reason, or resolve individual dates under Or Resolve One Date.

Plan with requirements to avoid conflicts

Instead of picking a specific person or tool up front, you can describe what the event needs and fill it with whoever is available. Requirements also let Epsilon3 check that the people you book hold the right skills, roles, and groups.

Add a requirement to an event

  • Click Create Event, or edit an existing event.

  • Under Resources, click Add Requirement. To book a specific user, tool, or location instead, click Add Resource.

  • Choose the Type (User, Tool, or Location).

19-create

  • For users, open Role, Group or Skills and choose from the Roles, Groups, and Skills tabs.

  • Set the Qty (how many are needed) and the Allocation for each.

  • Click Create Event or save your changes.

20-requirement-picker

Fill a requirement

  • Click the event to open its popup. The requirement shows what is needed, such as 2 × Operator at 100%, with an Open tag and an Unfilled slot for each person still needed.

  • Click Find next to an unfilled slot.

22-req-popup

  • The Staff window lists candidates with their match and free time. Use Hide fully allocated and Hide ineligible to narrow the list.

  • Select a person, set the Allocate slider, and click Assign.

23-staff

The slot fills and the requirement shows its progress, such as 1 of 2 filled. Once every slot is filled, the tag changes to Filled.

24-req-filled

Note: People booked against a requirement are checked for Missing Skill, Missing Role, and Not in Group. If you assign someone who doesn’t meet the requirement, they still count toward it, and the conflict is flagged so it can be reviewed.

Notifications

Booked people can be notified when a schedule change creates a conflict for them. Go to Settings > Notifications, expand Other, and find Schedule Conflict. In-app notifications are on by default and email is off.

18-notifications

  • Notifications go to the booked people in a newly created conflict, not to the person who made the change.

  • Conflicts on tools and locations don’t send notifications. They are left for planners to review in the Conflicts tab.

  • Changes saved through an API key don’t send notifications.

Permissions

  • See conflicts: the Planning module must be on for the workspace, and the user needs the View Schedules permission on the project.

  • See conflicts on Planning > Programs: the Programs module must also be on, and the user must be able to view every selected project.

  • Resolve, accept, or revoke: the user needs the Edit Events permission. The Resolve section is hidden for users without it.

  • Events in projects a user can’t open still count toward conflicts, but appear as Busy with no link or details.

See Role Based Permissions for how workspace and project roles work together.

Things to know

  • Conflicts never block a save, and Epsilon3 never reschedules or resolves conflicts automatically.

  • There is no setting to turn conflict checks on or off for a workspace or project.

  • Each person, tool instance, and location counts as one. Pools such as “5 units of this tool” aren’t supported.

  • Parts, inventory, teams, and groups aren’t checked as resources.

  • Completed and canceled work orders, unscheduled events, milestones, and draft plan events are not checked.

  • The Conflicts list refreshes after you save, drag, or resolve something, and when you reload the page. It doesn’t update on its own while the page sits open.

Related articles

Did this answer your question?