Projects, submittals & schedules

What are scopes and directives in Spectr?

Scopes and directives are how Spectr turns a contracted building into work the shop and field can execute — not a single work order named after the GC. They sit with phases so a date or a hold can move the right products.

See this on your jobs Phases, scopes, directives

Key facts

A contract is not a cutlist. Someone has to slice it into executable work.
Spectr uses phases, scopes, and directives as native project objects.
Directives should point at products, not at a paragraph in a meeting note.
This is operational project structure, not a company-wide task board.

How shops handle this

Map the contract to scopes
Systems, elevations, or bid packages — whatever purchasing and the shop already argue about.
Hang products on those scopes
Identity first, then dates.
Write directives people can finish
“Issue west podium BOM” beats “coordinate with GC.”
Close them from the same system
If closeout is a separate tracker, you have two truths again.

Common questions

Is this Microsoft Project?

No. It is the job structure under shop, ship, and install — not a generic Gantt.

Can we keep Monday for office tasks?

Yes. Status for panels should not live there.

Experience how Spectr could fit in your shop

From the jobs you're quoting now to the installs you're managing next month — we'll walk through your actual work, not a canned tour.

Start a conversation