Site Issues & Audits

What Are Site Issues?

Site Issues (also called Audits or Clean Me items) are problems discovered during your daily walkthroughs. They're different from work orders — these are quick fixes that need documentation.

Examples:

• Trash on the ground
• Graffiti on a wall
• Broken sign
• Spill that needs cleanup
• Missing supplies
• Safety hazard

Creating a Site Issue

1. Go to Site Issues in the sidebar
2. Click + New Issue
3. Fill in:

- Photo — Take a picture of the problem (required)

- Category — General, Equipment, Chemicals, Safety, Grounds, or Building

- Description — What's wrong

- Assign to — Who should fix it

1. Submit

The assigned person gets notified immediately.

Issue Categories

Issue Lifecycle

New → Pending → Review → Completed (or Denied)

1. New — Just reported, assigned to someone
2. Pending — Assignee is working on it
3. Review — Assignee submitted proof, awaiting manager approval
4. Completed — Manager approved the fix
5. Denied — Manager rejected (needs redo)

Resolving an Issue

When the assigned person fixes the problem:

1. Open the issue
2. Click Submit Proof
3. Choose proof type:

- Photo — Take an "after" picture (recommended)

- Note — Write what was done

1. Submit for review

Manager Approval

Managers review submitted issues:

1. Go to Site Issues
2. Find issues in "Review" status
3. For each:

- View the before photo

- View the proof (after photo or note)

- Click Approve or Deny

1. If denied, add a note explaining what's still wrong

Reassigning Issues

If the wrong person was assigned:

1. Open the issue
2. Click Reassign
3. Select the correct team member
4. Save

Auto-Created Issues

Some issues are created automatically:

• Equipment goes offline — System creates an issue automatically
• When ALL issues for equipment are resolved, the equipment returns to "Online" status

How It Connects

Issue found during walkthrough
  ↓
Photo taken, issue created
  ↓
Assigned team member notified
  ↓
They fix it and submit proof
  ↓
Manager approves
  ↓
Issue closed, history saved

Issue History

Every issue keeps a complete history:

• When it was created and by whom
• Every status change
• Reassignments
• Proof submissions
• Approval/denial with notes

This creates accountability and documentation.

Best Practices

1. Take clear photos — Show the problem clearly
2. Be specific — "Graffiti on Bay 2 wall" not just "graffiti"
3. Assign to the right person — Don't always assign to yourself
4. Review promptly — Don't let issues sit in "Review" status
5. Use categories — Helps with reporting and patterns

Tip

Do a daily walkthrough with your phone. When you see something wrong, create an issue immediately with a photo. This builds a culture of accountability.