← All job outcomes

Illustrated workflow

Turn an accepted milestone into an invoice draft.

Bring the accepted work and fee information together so the director can review the invoice.

Illustrated engineering workflows, with current product capabilities and the decisions for your people shown on each page.

The example

A client accepts a completed milestone. This example follows the recorded acceptance to an invoice draft for review.

Read the current scope ↓

Illustration of delivered drawings, an invoice draft, an approval screen and intended commercial follow-up on a desk.
Illustration, not a product screenshot or customer recording. From delivery to invoice. The image includes intended steps; the current limits below apply.

The illustrated steps

  1. Confirm the milestone

    Identify the completed work and the milestone it belongs to.

  2. Record client acceptance

    The managing director records the client's acceptance before the invoice draft is prepared.

  3. Gather the supporting information

    Keep the accepted work and fee information together for review.

  4. Prepare the draft

    Prepare the invoice draft for that accepted milestone.

  5. Review and approve

    The director or finance lead checks the amount, customer and supporting record.

  6. Issue outside OpsWork

    The authorised person issues the invoice and handles payment through the existing finance process.

What is built, and where it stops

The current scope ends at the invoice draft. The illustration does not promise same-day issue, automatic delivery, payment collection or an accounting connection.

Current product scope recorded 28 October 2026. Built, switched off means it is not switched on for customers yet. Coming means it is planned and not yet available.

Michael: Invoice drafts from an accepted milestone
Built, switched off

Prepares an invoice draft for a milestone once the managing director records the client's acceptance.

Draft only; issuing the invoice and payment happen outside OpsWork.

These scope statements use the same source as the Feature List in the procurement pack. Read the OpsWork specification →