Deficiency feature

Keep deficiencies visible, specific, and separate from completed work.

A buried caption is easy to miss. A structured deficiency record gives the customer the condition, location, evidence, recommended action, and current status in one reviewable block.

Create my first report Review a sample PDF

Direct answer

Which workflow fits?

The deficiency feature helps a contractor document an observed condition without implying an engineering conclusion or completed repair. It keeps the note in the report and customer history instead of a separate text thread.

01

Write facts the recipient can act on

Start with the location and observable condition. Then state the effect on scope, the recommended next step, and who needs to review it.

  • Name the hood line, duct section, fan, or rooftop location
  • Describe what was visible without guessing at a cause
  • Attach a context photo and a useful close-up
  • Record recommended action and an owner when known

02

Preserve the open-item history

A deficiency should remain discoverable after the PDF email disappears from the inbox.

  • Keep the issue with the service date and job record
  • Show whether it is open, acknowledged, or resolved
  • Link follow-up evidence to the original observation
  • Retain the customer-facing wording that was actually issued

Decision

Use structured deficiencies when the customer needs to understand what remains open after the cleaning scope is complete.