On-Site Execution

Once a workpack has been approved, the work moves to the field. The Execute view is where the crew progressively works through each inspection point — signing off rows, calling witnesses, raising defects, attaching photo evidence, and completing any linked forms — until every row is satisfied and the workpack is ready for closeout. This page is for the people doing and verifying the work on site: project engineers, site supervisors, and QA managers.

Opening the Execute View

1. Open the workpack from the Workpacks list.
2. On the workpack detail page, click Execute.

The Execute view shows the workpack's name and current status at the top, followed by a progress line ("X of Y passed") so you always know how much is left. Rows are grouped under their work-package heading and listed in sequence order.

If you have view access but not sign-off access, the Execute view opens in read-only mode with a notice at the top — you can review every row and its evidence, but the action buttons are hidden.

Filtering the List

A long workpack can run to dozens of rows. Use the Filters card at the top of the list to narrow what you see:

• Mine only — show only the rows you're responsible for (by name or by responsible role tag).
• Unblocked only — hide rows that are still waiting on an earlier hold point.
• Order — when the workpack is split across orders, show a single order, the rows with no order, or everything.

Understanding Row States

Every row carries a status badge that tells you where it is in its lifecycle:

• Pending — not started yet.
• In progress — work has begun on the row.
• Witness called — a witness has been notified for this point (see below).
• Failed — the row was marked failed and has an open defect to resolve.
• Passed — the row was signed off and met its acceptance criteria.
• Accepted as-is — a defect was closed with an "accept as-is" disposition.
• N/A — the row was marked Not Applicable.

A row counts as satisfied once it is Passed, Accepted as-is, or N/A. Satisfied rows stop showing a primary action and unblock any rows that were waiting on them.

Classification Points

Each row also shows its classification, which sets the expectation for how it's verified:

• Hold — a mandatory stop. Work downstream cannot proceed until this point is signed off.
• Witness — a nominated witness should be present or notified before the point is signed off.
• Monitor — checked and recorded, but it doesn't stop the work.

How Hold Points Gate Progress

Hold points enforce sequence. If a row depends on an earlier hold point that hasn't been satisfied yet, it shows a red Blocked by #N chip and its sign-off button is disabled, labelled Blocked. As soon as the blocking row is signed off (or marked N/A), the downstream row unblocks automatically — refresh or sign off the blocker and the dependent row becomes actionable.

Users with override authority can sign off a blocked row anyway. In that case the button reads Override and the sign-off panel asks for a written reason (at least a short justification) that is recorded against the sign-off.

Signing Off a Row

To sign off a row you have permission to action:

1. Click Sign off on the row.
2. The sign-off panel expands inline below the button.
3. Draw your signature in the signature pad. A signature is always required.
4. Add a photo if the row requires one (see Photo Evidence below). Required photos are marked with a red asterisk.
5. Capture any required records the row asks for (see Capturing Required Records below).
6. Optionally add notes about what you observed.
7. Click Sign off to confirm.

When the sign-off succeeds the row moves to Passed, the progress count updates, and the card shows who signed it off and when. Any rows that were blocked by this one unblock.

Capturing Required Records

If the template author set records required on a row (see Workpack Templates), the sign-off panel shows a Records required section with a capture field for each one — a number field with its unit for temperature/measurement/quantity, a photo or file upload, a signature pad, a text note, or a checkbox to attest. Required records are marked with an asterisk.

A row with unmet required records cannot be signed off — the Sign off button stays disabled until every required record has a value, and a short "Complete every required record before signing off." message explains what's outstanding. Optional records can be captured or left blank. What you enter is stored against the sign-off and carried through to the closeout PDF.

Rows with no records required behave exactly as before — the section simply doesn't appear.

Signing off on mobile. Capturing typed records at sign-off is a web feature today. Signing off a row that has required records from the mobile app will error until mobile parity ships — complete those sign-offs on the web app in the meantime. Rows without required records sign off on mobile as normal.

Photo Evidence

Hold and Witness rows require a photo at sign-off by default, and any row can be set to require one. In the sign-off panel:

1. Click Select photo (it opens your device camera or photo picker).
2. The selected file name appears next to the button — click Change photo to swap it.
3. Submit the sign-off; the photo is uploaded as evidence and attached to the row.

Signed-off photos appear as thumbnails on the row card afterward — tap a thumbnail to open it full size. These are separate from the reference drawings and specs attached to the row, which are also listed for you to open.

Marking a Row Not Applicable

When a row genuinely doesn't apply to this work, mark it N/A instead of signing it off. This requires manage access:

1. Click Mark N/A on the row.
2. Enter a reason explaining why the row doesn't apply.
3. Click to confirm.

An N/A row counts as satisfied and unblocks downstream rows, just like a sign-off — but it isn't recorded as a sign-off. If you marked a row N/A by mistake, use Reopen (in the same place) and supply a reason to return it to pending.

Calling a Witness

Witness-classified rows let you notify a witness before the point is verified. Click Notify witness on the row (it reads Notify again once a call already exists) and:

1. Choose Internal (a team member) or External (someone outside your organisation).
   • For an internal witness, pick the person from the picker.
   • For an external witness, enter their email address.
2. Choose how to reach them with Channel:
   • Internal witnesses can be notified in-app, by email, or both.
   • External witnesses are notified by email only.
3. Click to send the notification.

The row then shows a Witness called chip. When the witness acknowledges, the chip flips to Acknowledged with the time.

Acknowledging and Revoking

• If you are the internal witness who was notified, an Acknowledge button appears on the row so you can confirm in-app.
• A manager can Revoke an outstanding (not-yet-acknowledged) call — useful if an external link was mis-sent. Revoking invalidates the link so it can no longer be used.

Mandatory Witness Points

Most witness points are "notify and proceed" — the call is a courtesy and doesn't block sign-off. A point configured as a mandatory witness, though, behaves like a hold: its sign-off stays disabled (button reads Awaiting witness) until the witness acknowledges. Override holders can still sign off, providing a written reason.

Recording a Failure and Its Disposition

When a point doesn't meet its acceptance criteria, record the failure rather than skipping it:

1. Click Mark failed on an in-progress row. The row moves to Failed and opens a defect.
2. If the row has a linked defect form, complete it inline (see Completing Linked Forms).
3. When the defect is resolved, click Close out defect and choose a disposition:
   • Rework — the issue was corrected and the work redone.
   • Accept as-is — the deviation is accepted; this requires a signature.
   • Reject — the work is rejected.
4. Add comments describing the outcome (a brief explanation is required).
5. Confirm to close the defect.

An Accept as-is disposition moves the row to Accepted as-is, which counts as satisfied.

Completing Linked Forms

Rows can have one or more Field forms attached — for example an inspection checklist or a non-conformance report. Linked forms appear inline on the row card with a status chip (Not started, Draft, or Submitted) and a Required tag where applicable.

1. Click the form to expand it on the card.
2. Fill it out using the standard form renderer.
3. Click Complete to submit it. The status chip updates to Submitted.

A row with a required linked form that hasn't been submitted cannot be signed off — the sign-off button reads Form required and is disabled. Unlike a hold point, this cannot be overridden; the form must be completed first.

Delegating Work to a Subcontractor Organisation

Some workpacks are worked on by more than one company — for example, a principal contractor's ITP where a subcontractor actually performs and signs off a slice of the inspection points. Rather than adding each of the subcontractor's staff as individual approvers or witnesses, you can delegate whole activities (or the entire pack) to the subcontractor's organisation, and any of their internal team members can pick up and execute the assigned work.

This is a different relationship to External Reviewers: a reviewer only ever approves or rejects a plan from outside your team, while an organisation delegation lets the subcontractor's own people execute — sign off, call witnesses, raise defects — the specific rows assigned to them, using cross-tenant access rather than membership of your account.

Linking a subcontractor organisation

Before you can assign anything to a subcontractor, your organisations must be linked:

1. From the Workpacks landing page, open Linked organisations.
2. Click Invite organisation and enter the subcontractor's email address.
3. The invited organisation receives an email with a link to accept. Accepting binds one of their own team accounts to the link — it does not add them as a member of your account.
4. Once accepted, the link shows as Linked in your directory and the subcontractor becomes available to assign work to. You can Revoke a link at any time, which immediately removes the subcontractor's access to anything still assigned to them.

Note: A pending invitation can be revoked before it's accepted, and a revoked link doesn't automatically re-invite — send a fresh invitation if the partnership resumes later.

Assigning activities to a linked organisation

Once an organisation is linked, assign work to it from the workpack's row editor (while the workpack is still editable):

1. Open the row and set its Responsible party mode to Organisation.
2. Pick the linked subcontractor from the organisation picker.
3. Save the row. The row now shows an "Assigned to <organisation>" label, both in the editor and later on the Execute view.

To assign several rows (or the whole pack) at once, use the bulk assign bar above the row list: select the rows you want (or Select all), choose the target organisation, and click Assign selected to organisation.

A row can only have one responsible party at a time — assigning it to an organisation clears any person or user-tag it previously carried, and vice versa.

What the subcontractor sees and does

The subcontractor works entirely from their own account, not yours — they never become a member of your organisation.

1. Find the delegated work. From the subcontractor's own Workpacks landing page, they open Delegated to us. This lists every workpack a linked organisation has delegated one or more activities on to them, showing who delegated it and how many rows are theirs. (This mirrors the reviewer Assigned to us view, in the opposite direction.)
2. Open a delegated workpack. Opening one lands them on an Execute view scoped to the delegation. A banner explains that the workpack belongs to another organisation: rows badged "Yours to action" are theirs to execute, and everything else is read-only context so they can see how their work fits into the whole pack.
3. Execute the assigned rows. On a "Yours to action" row, the subcontractor's own internal team members can do everything the Execute view supports for that row — sign it off, capture the required records, attach the photo evidence a Hold or Witness point requires, and raise a defect. They don't need to be invited individually, and they can only act on rows assigned to their organisation.

If the organisation link is later revoked — or the last row assigned to them is unassigned — their access ends immediately, including the read-only context view.

Note: Two capabilities are intentionally deferred for delegated subcontractors for now: completing linked Field forms on a delegated row, and calling/acknowledging witnesses, remain with the workpack's own organisation. A row whose sign-off depends on one of these must be handled by the GC. Delegated execution otherwise covers sign-off, required records, photo evidence, and defects end to end.

Submitting for Review

Submitting a workpack happens before execution, when an authored draft is sent into its approval chain. From the workpack detail page (not the Execute view), a manager clicks Submit for approval and chooses how external reviewers can see it:

• Approval only — external reviewers see the workpack only while it's in approval.
• Ongoing — external reviewers keep visibility as the workpack progresses.

If the workpack has an approval chain configured, it routes to the approvers; if it has none, it self-approves straight to active and is ready to execute on site. Invited external (client or principal-contractor) reviewers access it through their Incoming view.

Related Pages

• Approvals & Sign-Off — route a workpack through its approval chain before work begins.
• Closeout & Reporting — finalise a fully-worked workpack and generate its closeout PDF.
• Forms — build and manage the Field forms you can link to workpack rows.
• External Reviewers — the approve-only counterpart to organisation delegation, for reviewers who sign off but don't execute.