Zoolsite
EN
Request a demo
How it works

From report to close-out

A clear process for site issues, department requests and daily work. Every item has an owner, a due date and a full record.

The issue journey in four steps

How a real issue moves from a site report to a verified close-out.

  1. T1-0001

    Cracked slab at grid C4

    Reported
    • Block A / Level 2
    • Site engineer

    Nov 10

  2. T1-0001

    Cracked slab at grid C4

    Assigned
    • Procurement

    Nov 12

  3. T1-0001

    Cracked slab at grid C4

    In progress
    • Survey and measure (Done)
    • Repair and cure (Not done yet)

    1 of 2 completed

  4. T1-0001

    Verified

    Cracked slab at grid C4

    Resolved
    • Repaired and cured (Done)
    • Verified on site (Done)

    Nov 14

Office and site handoffs

Work moves between the site and office departments with a clear ball in court, owner and date.

Site

Site team in the field

Office / department

Project and company teams

  1. Site engineer

    Reports the issue

    Nov 10, 08:29

  2. Procurement

    Reviews and orders materials

    Nov 11, 09:00

  3. Site engineer

    Carries out the repair

    Nov 13, 14:20

  4. Project manager

    Verifies and closes

    Nov 14, 16:45

Escalation of overdue items

Overdue work is flagged and the right people are notified, so it does not slip quietly.

  1. Nov 12

    Due date set

    T1-0001 due for Procurement.

  2. Nov 13

    Overdue

    Due date passed. The issue is marked overdue.

    Overdue
  3. Nov 13

    Notifications sent

    Alert to Procurement and the project manager.

  4. Nov 14

    Resolved

    Repair completed and verified.

The daily rhythm

Keep a live record of site progress with daily reports and a 14-day roll-up for quick visibility.

Daily report

Sun, Nov 15

Approved
  • Level 2 slab poured
  • 12 workers on site
  • Sunny, 31 °C

14-day roll-up

See it in action

Get a personalised demo and see how Zoolsite fits your projects.

Request a demo