Use order per object

Generate separate contract work orders per linked object when your service flow needs object-level work.

Order per object changes how contract work is generated for linked objects.

Use it when each object should get its own work order.

What order per object does

When a contract is linked to multiple objects, order per object can generate separate work orders per object.

This is useful when each installation or asset needs its own job record.

When to use it

Use order per object when you want:

• one work order per asset
• clearer object history
• separate follow-up per installation

Do not use it when all linked objects should be handled on one shared work order.

What to check first

Before you use this setting, check:

• which objects are linked to the contract
• whether your planners expect separate jobs
• whether your technicians need object-specific work orders

Frequently asked questions

Can one contract generate several work orders on the same cycle?

Yes.

That can happen when order per object is used with multiple linked objects.

Why would I use separate work orders per object?

It keeps planning, execution, and history clearer per asset.

Does this setting matter if no objects are linked?

No.

It only matters when the contract uses linked objects.

Related topics

• Link contracts to objects
• Understand contract work order generation
• Configure contract parameters
• Contracts