See How Checklists Appear on a Job

The checklist shown on a job comes from the job type, subtype, unit, and checklist configuration. Use this guide to understand what a field worker sees and why an item may be required.

What you will accomplish

By the end of this guide, you will be able to complete a job checklist from the correct CleanOver screen, understand the important checks before saving, and verify that the result is visible to the people who use it next.

Before you begin

• Know the unit and job subtype you want to inspect.
• Use a test or pending job when you only need to review the checklist.
• Sign in to the Admin workspace and confirm you are in the correct business context.
• Use real operational dates and the property’s local timezone when the workflow includes time.

Step 1: Open the correct job

From Jobs, select the unit and confirm the card’s job type and subtype. Different subtypes can load different checklist content.

Expected result: The correct job detail is open.

Step 2: Locate the checklist section

Scroll to the checklist area and review the categories in the order presented. The worker should follow this order unless operations instructed otherwise.

Expected result: Checklist categories and tasks are visible.

Step 3: Understand required items

Required tasks must be answered before completion. Text, yes/no, photo, and other answer types request different evidence.

Expected result: You can identify which items block completion.

Step 4: Check unit-specific wording

Compare the task with the unit’s operational notes. A checklist cell can be customized for one unit even when the category is shared.

Expected result: The instruction applies to this exact property.

Step 5: Record answers and evidence

Enter clear answers and attach photos that show the requested result. Do not upload unrelated images simply to satisfy a required field.

Expected result: Each answer provides useful evidence.

Step 6: Review linked tasks

If a checklist item reveals damage or missing supplies, create or open the related Cleaning Task or Maintenance Ticket instead of hiding the issue in a checklist answer.

Expected result: Follow-up work has a trackable owner.

Step 7: Complete the job

When every required item is finished, use Complete and follow the confirmation prompts.

Expected result: The job completes without a checklist blocker.

Step 8: Correct the source when needed

If the checklist is wrong for many jobs, update Checklists V2 rather than editing each live job independently.

Expected result: Future jobs receive the corrected configuration.

How to confirm the workflow is complete

• Refresh the destination list or calendar and confirm the saved record appears only once.
• Check the unit, date, status, owner or assignee, and any linked record before leaving the page.
• Open the next downstream view mentioned in the guide and confirm it shows the same information.
• Record an internal note when the action corrects historical data or changes another person’s responsibility.

Common issues and what to do

The expected record is missing

Clear old filters, check the date and business context, then search by the most specific identifier available. If the data comes from a connected provider, check connection and mapping status before recreating it manually.

A button is disabled

Look for a required field, incomplete checklist item, missing permission, locked lifecycle status, or unresolved linked task. Complete the highlighted requirement instead of trying to bypass it.

The page shows different information after refresh

Another user or integration may have updated the record. Compare timestamps and the source system, then apply the correction in the system that owns the data.

You are unsure whether to continue

Stop before cancelling, overwriting, revoking, or issuing a financial document. Ask the workflow owner to confirm the intended outcome and add that decision to the internal record.

Best practices

• Use clear names that make sense to a new team member without extra context.
• Prefer the smallest safe scope for bulk actions, filters, permissions, and date ranges.
• Keep guest-facing communication separate from internal diagnostic notes.
• Verify a high-risk change in a second view before considering it finished.
• Update the source configuration when the same correction is needed repeatedly.