Event Overview

A Company Event is a business plan for a group of Projects. It lets you shape how that group operates — which trades, sales and estimating processes, materials, suppliers, and subcontractors are in play — and lets those Projects present under a single corporate identity for a given area or campaign.

Events shine in multi-market and insurance-restoration work: stand up an Event for a storm response, a new region, or a branch office, and every Project created under it inherits that plan automatically — no re-configuring project by project.

An Event is required to create a Project. Only Active Events can be selected.

The key idea: guardrails, not gates

In Contractors Cloud, an Event restricts only what you tell it to restrict. Leave a section empty and everything is available — all of your trades, tax codes, estimate types, material lists, suppliers, and installers. You add items to a section only when you want to narrow the options for Projects on that Event.

So a brand-new “name-only” Event — just a name, state, and zip — is fully functional and wide open. Restrictions are an optional tool you reach for when a particular area or campaign should do less than everything you’re capable of.

Tip: Expanding into a market where only a couple of trades are profitable? Add just those trades to the Event. Everywhere else, leave the section empty and keep your full catalog available.

When to use an Event

• New region or branch office — limit trades, suppliers, and installers to what’s actually available there.
• Storm / catastrophe response — spin up a dated Event that stops accepting new Projects once the response window closes.
• Multiple offices, one brand — use a Corporate Alias so all customer-facing paperwork comes from one corporate name and address.
• Segmented sales — restrict estimate types so a segment only runs the sales activities you intend.

Details

The main details for the Event.

• Name (required) — a unique name for the Event. Best practice: include a location and date (e.g. “Dallas Hail — Spring 2026”).
• Description — an optional description for the Event.
• Status — only Active Events can be used within Projects.

Location details

• State, Zip (required) — where the Event occurs.
• Area comment — optional free text for additional detail, such as the cities or regions affected.

Corporate Alias

Optional, and one of the most useful features for multi-office operators. Enter a Corporate name, Address, and Contact details (Phone, Phone 2, Website/URL), and all printouts — invoices, estimates, and more — default to that identity instead of the individual office.

This lets several offices working the same area present under one corporate name and address, so your customer-facing paperwork stays consistent no matter which branch runs the job.

Duration

An optional active window for the Event.

• Start Date — the date the Event started.
• End Date — the date the Event is expected to end.
• Leave both dates blank to keep the Event available anytime.

If a duration is set, the Event can be selected only while a Project’s creation date falls within the window. Once the End Date passes, the Event expires and can no longer be added to new Projects — which is exactly what you want for seasonal and catastrophe work.

Tip: If you’re running all Projects under a single ongoing Event and don’t need expiration, leave the dates blank (or set the End Date a few years out) so it never expires. Use Clear Duration to remove the dates entirely.

Allowed Tax Codes

The jurisdictional tax codes available for Estimates and Invoicing on this Event. If your area combines several tax jurisdictions (state, county, city), you can create one code with a combined rate.

By default, all active Company Tax Codes are available. Add codes here only if you want to limit which ones may be used on this Event’s transactions.

Allowed Estimate Types

The estimate types (e.g. Installed, Retail, Insurance) available on this Event — useful when a certain area or segment should only run specific sales activities. Leave the section empty and all estimate types are available.

Click the three vertical dots (⋮) to import Estimate Type settings from another Event.

Allowed Trades & Parameters

The trades available to Projects on this Event. Even with many trades in your catalog, adding trades here limits what can be used in Estimates and Orders. If no trades are listed, all of your Tenant Trades are available.

Each Event trade can also carry parameters — lead times and general notes — that flow into scheduling and production.

Click the three vertical dots (⋮) to import Event Trade settings from another Event.

Allowed Material Lists

The Material Lists available to Projects on this Event — useful for limiting which systems or products you offer in a given area. Leave the section empty and all Material Lists are available.

Click the three vertical dots (⋮) to import Material List settings from another Event.

Allowed Suppliers

The Suppliers available to Orders on this Event — handy when a region has a limited set of suppliers. Leave the section empty and all Suppliers are available.

Click the three vertical dots (⋮) to import Supplier settings from another Event.

Allowed Installers

The Installers (crews / subcontractors) available to Orders on this Event — for when a region has a limited crew pool. Leave the section empty and all Installers are available.

Click the three vertical dots (⋮) to import Installer settings from another Event.

Projects

The Projects using this Event. Visit the Reports section for more detailed analysis of Event/Project relationships.