Event Mappings

The Event Mappings page is an administrator tool for reviewing how builder schedule events are matched to ConstructEase requirements when project data is imported. You reach it from a builder's actions on the Builders tab in Settings.

Each row shows one builder event and how it maps into ConstructEase:

• Builder and Division the event belongs to.

• Event Description, the name that comes in from the builder.

• Mapped Requirement and Stage Name, the ConstructEase requirement it maps to. Events with no match show an Unmapped badge.

• Trade and Inspection, showing which trade the requirement belongs to and whether it is treated as an inspection.

• Source, showing where the current mapping comes from: Import when it was set automatically during import, Manual when someone set an override by hand, or Ignored when someone marked the event as one that should not import.

• Last Mapped, the date the mapping was last updated.

Filter the list by builder, division, or trade, turn on Unmapped Only to find events that still need a decision, and search by event description. Events that were manually mapped or ignored no longer appear under Unmapped Only, so the filter always shows just the new event names waiting on a decision.

If an imported event maps to the wrong requirement or comes in unmapped, you can correct it by hand:

1. Click Map on an unmapped event, or Edit on one that already has a mapping.

2. In the Map Event dialog, choose the Mapped Requirement the event should point to.

3. Optionally set the Trade and check Map as inspection if the requirement should be treated as an inspection.

4. Click Save.

The row's Source changes to Manual, and your override is used in place of the imported value. To undo an override and go back to the automatic import value, open the event again and click Revert to import.

Some builder events are noise that should never import - internal milestones, punch items, or tasks that have no matching requirement on purpose. Instead of mapping them, mark them as ignored:

1. Click Map (or Edit) on the event.

2. Click Ignore in the dialog.

The row's Source changes to Ignored and, from the next import on, the event is skipped quietly: it stops appearing under Unmapped Only and no longer raises dropped-task notifications. Any open dropped-task notifications for the event are cleared right away.

You can also ignore a task directly from a dropped-task notification in the notification bell - press Ignore on the notification card and ConstructEase marks the task name as ignored here for you.

To start importing the event again, open it and click Restore. The event returns to the automatic import mapping.

Event Mappings and manual overrides are available to administrators.