Work Orders

Work orders are execution units for confirmed scope. They can stand alone or sit under a project, and they can optionally stay linked to the quote they came from. When a work order has a project, it behaves like a subproject or work package inside that project.

How work orders fit into a project

• A project can contain multiple work orders, but the project link is optional.
• A work order collects its own positions, work times, reports, planner phases, and milestones.
• In the planner, project-linked work follows project -> work order -> phase or milestone. Work orders without a project can still be planned directly with their phases and milestones.

Create and structure work orders

• Create a work order directly inside a project when you want to split scope into a separate package.
• Create a work order from Work Orders without a project when the execution package should not sit under a project yet.
• Create a work order from a quote to carry accepted scope and positions into execution. If the quote has no project, the new work order can remain projectless.
• Use separate work orders when different parts of a project need different timelines, documentation, or billing context.

What you manage on a work order

• On the general tab, maintain title, status, issuer organization, optional parent project, optional quote, and description.
• When a work order is created from a quote, accepted positions can be copied over and reviewed on the detail page.
• Use Create invoice from a work order to create a draft invoice with copied work-order positions and preserved quote/project/source links where available.
• In Work Times, track labor against the work order.
• In Reports, collect reports linked to that work order.
• In Planner, manage the phases and milestones that define the work-order timeline.

Merge duplicate work orders

• Select at least two work order rows and choose Merge work orders from the selected actions.
• Pick the work order to keep; the comparison dialog shows linked data before you confirm.
• Positions, phases, reports, inquiries, invoices, work times, transports, resources, discussions, calendar sync entries, shares, activity and automation history, page and email links, and assistant executions move to the kept work order. Duplicate calendar sync entries for the same connected account or mobile device collapse into one entry with the newest sync state. Linked inquiries, invoices, work times, report time entries, and GitHub links align to the kept work order's project when it has one, and the other work order records are deleted.

Best practices

• Treat work orders as execution packages; add a project when that package belongs to a larger delivery container.
• Keep work times, reports, phases, and milestones attached to the correct work order so project data stays cleanly separated.
• Split work into multiple work orders when teams, schedules, or deliverables need to be tracked independently.