Back to all articlesMobile team operations

Use Not Applicable and Blocked Without Hiding Incomplete Field Work

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A field worker reaches a locked equipment room. The inspection checklist offers only a checkbox. Ticking it implies the inspection happened; leaving it blank gives the next reader no way to distinguish denied access from a forgotten step. Neither choice records the work accurately.

Use four distinct checklist states: completed, not applicable, blocked, and not yet checked. Completed means the required result has been verified. Not applicable means a defined condition makes the step unnecessary. Blocked means the step applies but cannot currently be finished. Not yet checked means there is no supported outcome yet.

The overall task should count as complete only when every required item is either completed with sufficient evidence or validly not applicable. A blocked or not-yet-checked required item prevents completion. So does a completion claim that lacks its required evidence. The operating rules below are a recommended design, not a claim that particular controls exist in an application.

1. Define the result before assigning a state

A state is meaningful only when the checklist item says what must be established. “Equipment room” is a location, not a test. “Check equipment room” leaves room for disagreement about whether opening the door is enough.

Write each item with an action, an acceptance condition, and the evidence needed to support the answer. Keep the evidence proportionate: some steps need a reading or reference, while others need only an explicit confirmation.

Hypothetical item: “Verify that the replacement unit’s identifier matches the work order. Record the identifier observed.” This makes it possible to distinguish seeing the unit from verifying the match.

  • Applicability rule: Under what circumstances is this step required?
  • Acceptance condition: What result permits the item to be marked completed?
  • Evidence requirement: What must the reader be able to inspect afterward?
  • Resolution responsibility: Who can resolve a blocker or decide a disputed applicability question?

Make those decisions before the visit where possible. Otherwise, staff must invent the rules while dealing with access problems, time pressure, or incomplete instructions.

2. Give each state a narrow meaning

Completed: the specified result was achieved

Use completed only when the acceptance condition has been met and the required evidence has been recorded. An attempt is not completion. Neither is a plan to return later.

For an item that says “record the observed identifier,” an empty evidence field makes the completion claim unsupported. For a step that asks for a satisfactory condition, recording an unsatisfactory condition documents an inspection but does not establish the required result.

Watch the wording here. “Inspect and record the condition” can be completed even when a defect is found, provided any required follow-up is separately captured. “Verify the unit is ready for handover” cannot be completed merely because the defect has been documented.

Not applicable: the step is not required in this case

Use not applicable only when the item’s applicability rule excludes it. Record the relevant condition, rather than a vague explanation such as “not needed.”

Not applicable does not mean inconvenient, inaccessible, out of time, or missing equipment. Those circumstances do not remove the requirement. They explain why an applicable requirement remains unfinished.

Blocked: the requirement remains, but progress is prevented

A blocked item needs a specific obstacle, the remaining work, a resolution owner, and a next action or review trigger. “Waiting” does not tell another person what to do.

Do not use blocked merely because a step has not been attempted. There should be a known obstacle. If an inspection reveals a failure that cannot be resolved during the visit, record the observed failure alongside the blocker so that blocked does not conceal what was found.

Not yet checked: no supported determination exists

This is the honest starting state. It covers untouched steps and items whose outcome has not yet been verified. It should not silently become completed when a visit ends or a record is submitted.

If an item was missed, say so. Recording “not checked before departure” is more useful than inventing a blocker after the fact.

3. Set an evidence rule for every outcome

Requiring a long note on every item can create rushed, repetitive text. Requiring nothing creates unsupported claims. A practical middle ground is to define a small evidence requirement for each item and state.

  • Completed: Record the item-specific result, who verified it, and when. Include a reading, identifier, reference, or other supporting detail only where the item requires it.
  • Not applicable: Record the exclusion rule and the fact that satisfies it. Include confirmation by a designated reviewer if applicability requires judgment.
  • Blocked: Record what prevents completion, what remains undone, who owns resolution, and what event or agreed review point should prompt action.
  • Not yet checked: Preserve the absence of a result. When handing over unfinished work, identify who should check it next and any relevant limitation.

Keep evidence attached to the relevant item. A general visit note saying “some checks unavailable” makes readers reconstruct which checks were affected.

Use only the evidence necessary to establish the outcome. Do not collect unrelated personal information or broad photographs when a short observation will answer the operational question.

4. Use this filled checklist-state decision table

Fictional worked example: The following hypothetical visit concerns a replacement display unit at a business site. Every item is required unless its stated applicability rule excludes it. The people, references, observations, and times are fictional. The stacked rows below form a decision table that can be copied into a working document without needing a wide mobile screen.

Row A — Verify the replacement unit identifier

  • Applicability: Required whenever a replacement unit is installed.
  • Acceptance condition: Observed identifier matches the work order.
  • State: Completed.
  • Recorded evidence: “Mira observed unit D-418; work order WO-207 specifies D-418. Verified at 10:10.”
  • Next action: None for this item.
  • Completion decision: Passes the completion gate.

Row B — Check the wall-mount fittings

  • Applicability: Required only for a wall-mounted installation.
  • Acceptance condition: If applicable, verify the specified fittings are present.
  • State: Not applicable.
  • Recorded evidence: “Work order specifies a freestanding installation. Mira confirmed the unit stands on its floor base; no wall mount is used.”
  • Next action: Reassess if the installation changes to wall-mounted.
  • Completion decision: Passes because the documented exclusion rule is satisfied. It does not claim that fittings were inspected.

Row C — Verify the power connection in the equipment room

  • Applicability: Required for this installation.
  • Acceptance condition: Verify the designated connection against the work instructions and record the result.
  • State: Blocked.
  • Recorded evidence: “At 10:20, equipment room was locked. Site contact Arun confirmed the key holder was unavailable. Connection has not been inspected.”
  • Next action: “Visit coordinator Lena to arrange access with Arun. Review access arrangements at 15:00; assign the return check once access is confirmed.”
  • Completion decision: Prevents overall completion. Naming an owner does not resolve the missing inspection.

Row D — Demonstrate the controls to the site contact

  • Applicability: Required for this handover.
  • Acceptance condition: Demonstration delivered and recipient recorded.
  • State: Not yet checked.
  • Recorded evidence: “No demonstration recorded. Mira left before this step was attempted.”
  • Next action: “Lena to assign the demonstration during the return visit and record who receives it.”
  • Completion decision: Prevents overall completion. There is no established blocker and no verified outcome.

Overall completion decision: not complete. Row A is supported as completed, and Row B has a valid not-applicable rationale. Rows C and D remain unresolved. The visit can be recorded as ended and the checklist can be submitted for handover, but neither event means the required work is complete.

5. Make the overall completion gate explicit

Use a rule that a worker and reviewer can apply to the same record and reach the same answer:

A task is complete only when every required checklist item has a supported completed outcome or a supported not-applicable outcome, with any required review finished.

That rule produces these decisions:

  • All items completed with sufficient evidence: Complete.
  • A mix of completed and valid not-applicable items: Complete.
  • Any required item blocked: Not complete, even if someone accepts responsibility for resolving it.
  • Any required item not yet checked: Not complete.
  • A completed item missing required evidence: Not complete until the evidence gap is resolved.
  • A not-applicable item with an unsupported or disputed reason: Not complete until applicability is resolved.

An entirely not-applicable checklist deserves a separate review. It may legitimately mean no work was required, but it can also indicate that the wrong checklist was assigned. Confirm the scope before accepting that outcome.

If someone authorises closure with outstanding work, describe that as an exception rather than ordinary completion. Preserve the unresolved items and the decision maker’s rationale. Ending responsibility for a visit must not rewrite its factual outcome.

6. Make honest answers practical on mobile

Put the four state meanings close to the point of entry. Staff should not need to remember whether “not applicable” includes access problems; it should clearly exclude them.

Keep prompts short and specific. For blocked, ask “What prevents this step?” and “Who owns the next action?” For not applicable, ask “Which condition makes this step unnecessary?” Avoid one generic comments box serving every purpose.

Where a form is being designed, controls need clear labels associated with their inputs, as described in the W3C guidance on labeling form controls. Do not rely on colour alone to distinguish an unresolved item from a completed one.

If the available application provides only binary checkboxes, do not tick unfinished work to satisfy the interface. Use an agreed accompanying record with item names, explicit states, and evidence, and make clear that the checkbox alone is not the completion authority. Check the workspace and current plan before assuming richer state controls are available.

7. Recover from wrong states without erasing the problem

The most damaging mistake is converting uncertainty into apparent completion. Correcting it should restore visibility, not merely tidy the record.

  1. Identify the affected item. State what the earlier selection incorrectly implied.
  2. Restore the supported state. Use blocked for a known obstacle or not yet checked where the outcome remains unverified.
  3. Preserve the correction context. Record who corrected it, when, and why, using the available recordkeeping method.
  4. Reassess overall completion. An unresolved required item means the task is no longer supported as complete.
  5. Inform the person relying on the result. Give them the remaining work and next action, not just a notice that a field changed.

A blocker being removed does not itself complete the item. Access to the equipment room permits the inspection; it does not prove the inspection occurred. Likewise, newly supplied evidence must establish the result rather than merely fill an empty field.

Revisit applicability when conditions change. In the fictional example, switching to a wall-mounted installation would invalidate Row B’s exclusion and make that check necessary.

8. Test the rules on the next checklist

Start with one checklist rather than rewriting every field process. Before its next use, define the applicability rule, acceptance condition, and minimum evidence for each item. Assign responsibility for unresolved items and agree on the overall completion gate.

For a hypothetical pilot of five completed visits, have a reviewer independently assess the submitted records. Count unsupported completion claims, not-applicable entries without a valid rationale, blocked entries without an owner or next action, and disagreements about overall completion.

Use those observations to revise the wording. If reviewers disagree about the same item, clarify its acceptance condition. If workers repeatedly choose not applicable for access problems, tighten that distinction. If evidence is consistently missing, check whether the requirement is unclear, excessive, or difficult to capture.

The immediate test is simple: can the next person tell what was verified, what genuinely did not apply, what remains prevented, and what nobody has checked yet—without calling the worker to reconstruct the visit?

Mobile operationsChecklistsField workTask completion

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications