Work Order (WO)

A Work Order is the formal, legally binding agreement issued to a subcontractor for executing defined work packages on a project. It is the subcontractor equivalent of the Purchase Order — while a PO procures materials from a vendor, a WO procures labor and services from a subcontractor. Work Orders specify the work items (linked to the project’s BOQ/scope), agreed rates, quantities, payment terms, recovery provisions, and completion timelines.

Work Orders are created after evaluating proposals received through the RFP process. They serve as the contractual document governing the subcontractor relationship, linking scope execution to progress measurements, running bills, and payment.

Subcontractor Procurement Workflow

The Work Order sits at the center of the subcontractor management lifecycle. The complete flow is:

WO List Grid

The Work Order list displays all work orders created within the selected date range. The default filter period is the last 30 days.

Row Actions

Each WO row has a dropdown action menu:

WO Header Fields

The WO header captures the overall order details. All header fields are stored in the omni_work_order_header table (41 columns).

Order-Level Amount Fields

These fields summarize the WO’s financial totals and are computed from line items and recoveries:

WO Line Items (Detail)

Each WO contains one or more line items representing individual work items being subcontracted. Unlike PO line items that reference materials, WO line items reference work items from the project’s BOQ/scope. Line items are stored in the omni_work_order_detail table (13 columns).

Creating a Work Order

Work Orders are created from the RFP module after evaluating subcontractor proposals. The standard process follows the WR → RFP → Offer → WO path:

1. Raise a Work Requisition (WR) — The site team identifies scope items that need to be subcontracted and creates a Work Requisition specifying the work items, quantities, and required timelines. The WR is approved through the configured workflow.
2. Create an RFP from the WR — Navigate to Procurement → RFP and create a new Request for Proposal from the approved WR. The RFP inherits the work items and quantities from the WR.
3. Invite subcontractors — Select subcontractors from the Vendor Directory to receive the RFP. Each invited subcontractor can submit their proposal with unit rates, terms, and conditions.
4. Evaluate vendor offers — Once proposals are received, review and compare them using the comparative evaluation view. Assess based on total cost, unit rates per item, vendor capability, past performance, and compliance with technical specifications.
5. Select the winning offer and create WO — From the selected vendor offer, click Create Work Order. The system auto-populates the WO with all data from the offer: subcontractor details, work items with quantities and rates, and the offer reference for traceability.
6. Review WO header — Verify the auto-populated header: WO description, subcontractor, WO date, currency, exchange rate, expected start and completion dates, and billing address.
7. Review work items — Check each line item for work item description, UOM, quantity, basic rate, and base amount. Adjust as needed. Ensure each item correctly maps to the project BOQ/scope.
8. Configure recovery items — Add any material recoveries, retention amounts, or other deductions that will be applied. See Recovery Items.
9. Add resources provisioned — If the company will provide resources (equipment, accommodation, transport) to the subcontractor, define them here. See Resources Provisioned.
10. Set payment terms and T&C — Define payment milestones, add terms & conditions, and configure tax items. See Payment Terms.
11. Attach documents — Optionally attach supporting documents (scope drawings, specifications, method statements, safety plans) to the WO.
12. Submit for approval — Save the WO (status: Draft), then click Approve to send it through the configured approval workflow.

Recovery Items

Recovery items represent deductions that the company will make from the subcontractor’s payments. These are contractual provisions defined at the WO level and applied proportionally during each running bill. Recovery items are stored in the omni_work_order_recovery_items table.

Types of Recoveries

Before-Tax vs. After-Tax Recoveries

Recoveries are categorized into two groups based on when they are applied in the payment calculation:

Resources Provisioned

The company may provide certain resources to the subcontractor as part of the work order agreement. These are tracked in the omni_work_order_resources_provisioned table and represent the company’s in-kind contribution to the subcontract scope.

Measurement System

The measurement system is the mechanism for recording and certifying actual work progress against the WO line items. JobNext uses a 3-tier measurement structure that mirrors the industry-standard approach for construction measurement:

Tier 1: Measurement Header

Stored in omni_work_order_item_measurement_header, the measurement header represents a single measurement session or certification event.

Tier 2: Measurement Detail

Stored in omni_work_order_item_measurement_detail, each detail record corresponds to a specific WO work item being measured.

Tier 3: Measurement Dimensions

Stored in omni_work_order_item_measurement_detail_dimensions, dimensions provide the granular breakdown of how the measured quantity was computed.

Measurement Workflow

1. Record measurements on site — The site engineer or quantity surveyor visits the work location and records physical measurements (dimensions) for each WO work item. Measurements are entered directly in JobNext or via a field device.
2. Enter dimensions — For each work item, enter the detailed dimensions (Tier 3) that make up the measured quantity. The system automatically calculates the quantity from the dimensions.
3. Review totals — Verify that the computed measurement quantities are accurate. The system shows the current period quantity (measured minus previous) for each item.
4. Submit for certification — The measurement is submitted for review by a senior engineer or project manager.
5. Certify or reject — The certifier reviews the measurements, verifies against site conditions, and either certifies (approves) or rejects with comments.
6. Generate running bill — Once certified, the measurement forms the basis for the subcontractor’s running bill. See Running Bills.

Running Bills

A running bill (also called an Interim Payment Certificate or IPC) is a periodic payment document generated from certified measurements. Each running bill calculates the amount payable to the subcontractor for work completed in the current period, less any recoveries and previous payments.

Running Bill Calculation

Running Bill Workflow

1. Measurements are certified — The certified measurement quantities form the basis for billing.
2. Generate the running bill — The system creates a vendor bill (in Finance) from the certified measurements, applying all recovery items and deductions as defined in the WO.
3. Review and approve the bill — The project QS or finance team reviews the bill calculations, verifies recoveries, and approves for payment.
4. Process payment — A payment voucher is created from the approved bill, generating accounting entries in the ledger (omni_account_voucher_entry).

Payment Terms

Payment terms define when and how the subcontractor will be paid. Each WO can have one or more payment milestones stored in the omni_work_order_paymentterms table.

Terms & Conditions

WOs include standard and custom terms & conditions that define the contractual obligations between the company and the subcontractor. Terms are stored in the omni_work_order_termsandconditions table.

• Template-based — Select from pre-configured T&C templates defined in the master settings. Each template has a term ID and default text.
• Customizable — The terms text can be edited per WO to add special conditions, modify default clauses, or remove inapplicable terms.
• Printed on WO document — All T&Cs are included in the SSRS WO report document sent to the subcontractor.

Common subcontractor T&C categories include:

• Scope of work and exclusions
• Mobilization and demobilization requirements
• Work schedule and completion milestones
• Liquidated damages for delay
• Safety, health, and environmental compliance
• Quality standards and inspection procedures
• Insurance requirements (third-party, workmen’s compensation)
• Retention and defects liability period
• Variation and change order procedures
• Termination and dispute resolution clauses
• Company-provided resources and material recovery terms
• Compliance with labor laws and worker welfare standards

Tax Items

Tax handling on Work Orders is managed through the omni_work_order_tax_items table. Taxes can be applied at the order level:

• Tax Component — Selected from the tax master (e.g., VAT @ 5%, CGST @ 9%, SGST @ 9%, IGST @ 18%, TDS — Tax Deducted at Source).
• Tax Rate — Percentage applied to the taxable base (net item amount less before-tax recoveries).
• Tax Amount — Computed amount: Taxable Base × Tax Rate. Stored in the order_tax_amount header field.
• Multiple Tax Components — Multiple tax entries can be added for dual or multi-component tax regimes (e.g., CGST + SGST, or VAT + WHT).

WO Statuses

Approval Workflow

WOs follow the organization’s configured approval workflow, similar to POs:

• Value-Based — Different approvers based on WO amount thresholds (e.g., up to 50,000 = Project Manager, above 50,000 = Director).
• Multi-Level Sequential — WO passes through multiple approval levels (e.g., Site Engineer → QS Manager → Contracts Manager → Management).

What Happens on Approval

1. WO status changes from Draft to Approved.
2. Approved-by user (approved_by) and timestamp (approved_on) are recorded.
3. Approver comments are stored in approved_comments for audit trail.
4. The WO becomes available for measurements and billing.
5. The WO value is committed against the job’s subcontractor budget.

WO Amendments

After a WO is approved, it may need modifications due to scope changes, rate renegotiations, additional work items, or revised timelines. JobNext handles this through the Amendment process rather than editing the original WO — the same pattern used for PO amendments:

1. Initiate Amendment — On an Approved WO, click Amend from the row actions. The system creates a new Draft WO linked to the original via the original_wo_id field. Detail line items are linked via orginal_wo_detail_id.
2. Make changes — The amended WO is a full copy of the original. You can:
   • Modify quantities (increase or decrease scope)
   • Add new work items
   • Remove work items not yet measured
   • Change unit rates (renegotiated rates)
   • Update expected completion dates
   • Revise recovery items, resources, or terms & conditions
3. Submit for approval — The amended WO goes through the standard approval workflow. Approvers can see what changed from the original.
4. Approved amendment replaces original — Once approved, the amended WO becomes the active version. The original WO’s budget commitment is adjusted to reflect the new values. All future measurements and bills reference the amended WO.

Monthly Recurring Work Orders

The is_monthly_recurring flag enables a special Work Order mode designed for ongoing, repetitive subcontractor engagements such as:

• Facility maintenance contracts — Monthly housekeeping, landscaping, pest control
• Security services — Ongoing guard services billed monthly
• Equipment rental — Monthly crane or generator hire
• Recurring labor supply — Monthly provision of general labor at fixed rates
• AMC contracts — Annual maintenance contracts with monthly billing cycles

When a WO is marked as monthly recurring:

• The system expects monthly measurement and billing cycles aligned with calendar months.
• Each month’s measurement represents the work done in that specific month (not cumulative).
• Running bills are generated monthly based on the fixed recurring rates.
• The WO remains active until explicitly closed or cancelled, rather than auto-completing when quantities are fully measured.

Multi-Currency Support

JobNext Work Orders support multi-currency contracting, which is critical for projects with international subcontractors:

• WO Currency (wo_currency) — The currency in which the subcontractor is paid. Set at the WO header level (e.g., a subcontractor from India is paid in INR, a local subcontractor in OMR or AED).
• Job Currency (job_currency) — The base currency of the job/project. Used for budget tracking and cost reporting.
• Exchange Rate (job_ccy_exchange_rate) — The conversion rate from WO currency to job currency. This rate is set at the time of WO creation and used to convert WO values for budget comparison.

Full Traceability

Every Work Order maintains a complete audit trail in both directions through the subcontractor management lifecycle:

WO Document (SSRS Report)

The printable WO document is generated as an SSRS report and serves as the formal subcontract document sent to the subcontractor. It contains:

Budget Control

WO values are tracked against the approved subcontractor budget for the job:

• Budget Availability Check — At WO creation, the system checks if sufficient subcontractor budget exists for the work items being ordered. If the WO value exceeds the available budget, the system can either warn or block depending on configuration.
• Budget Commitment — On WO approval, the WO value is committed against the subcontractor budget. This reduces the “available” budget even before work is executed or paid for.
• Scope Tracking — Because WO line items link to BOQ/scope work items via job_work_item_id, the system tracks what percentage of each scope item has been subcontracted, preventing over-commitment.
• Budget Burn Tracking — The Subcontractor Budget Burn report shows estimated vs. ordered (WO) vs. measured vs. billed vs. paid amounts, giving real-time visibility into subcontractor spending.
• Rate Variance — Comparing WO rates against estimate/budget rates reveals contracting efficiency. The system tracks awarded rates vs. budget rates at the work item level.

Available Reports

Related Database Tables

The Work Order module uses 11 database tables that together form the complete subcontract management data model:

Best Practices

1. Always follow the standard procurement path for subcontract work — WR → RFP → Comparative Evaluation → WO. This ensures competitive pricing, a complete audit trail, and proper budget authorization. Avoid creating WOs directly without an RFP evaluation for any significant value.
2. Link every work item to the BOQ/scope using job_work_item_id. This is essential for scope tracking, budget burn analysis, and preventing over-commitment of scope items to multiple subcontractors.
3. Define recovery items upfront before approving the WO. Clearly specify material recovery rates, retention percentages, advance recovery schedules, and LD provisions. Changing recovery terms after bills have been raised creates reconciliation issues.
4. Record measurements promptly and accurately. Use the 3-tier dimension system for all items measured by area or volume. Attach photographs as supporting documentation for measurements. Late or inaccurate measurements delay subcontractor payments and damage the working relationship.
5. Use the before-tax / after-tax recovery distinction correctly. Material recoveries (company-supplied materials) should be before tax. Retention, penalties, and advance recovery should be after tax. Incorrect classification affects tax computation and may cause compliance issues.
6. Document resources provisioned even when they are provided at no cost. This creates a record of the company’s in-kind contribution and supports dispute resolution if the subcontractor claims they were not provided agreed resources.
7. Use amendments, not cancellations, when an approved WO needs changes. Amendments preserve the history, maintain the measurement trail, and provide a clear audit trail of scope changes. Only cancel a WO when the entire subcontract is no longer needed.
8. Review budget impact before approving a WO. Use the Subcontractor Budget Burn report to ensure the WO value fits within the allocated subcontractor budget for the job.
9. Set expected start and completion dates on every WO. These dates are essential for project scheduling, resource planning, and enforcing liquidated damages in case of delay.
10. Use monthly recurring WOs for ongoing service contracts instead of creating separate WOs each month. This consolidates the billing history and provides a single view of the contract’s lifetime value and payments.
11. Attach all supporting documents to the WO — scope drawings, method statements, safety plans, insurance certificates, vendor correspondence, and negotiation records. This creates a complete subcontract file for audits and dispute resolution.
12. Process running bills regularly (monthly for construction subcontracts). Delayed billing frustrates subcontractors and can impact site productivity. Establish a fixed billing cycle (e.g., measurements by the 25th, bills by the 5th, payment by the 30th).