01 — Case study · New Zealand

Design-and-build fitout firm.

Resourcing, forecasting and integration platform, synced live with the project, file storage and timesheet systems.

9
blocks
42
users

Forecast horizon

From 2 weeks
to three months

02 — The shift

From information in five places to one single source of truth.

Before

Before. The systems: project system, timesheet system. What a person did: retype the job details, re-key the dates, reconcile the hours, copy to each tab, rebuild the forecast. Where it landed: department workbooks. What people worked from: a tab each, the labour plan, out-of-date copies. Project system Timesheet system Department workbooks A tab each The labour plan Out-of-date copies
  • Project system
  • Timesheet system
  • Department workbooks, a tab each

The same information typed in three times, never in sync, and a forecast that ran out after two weeks.

After

After. The systems: project system, timesheets, file storage. The hub: central hub. What people look at: staff forecasts, health and safety. Every cell shares an edge with the hub: live sync, entered once, always current. Project system Timesheets File storage Staff forecasts Health and safety Central hub

Live syncEntered onceAlways current

03 — The story

This client was using two legacy paid systems, one for managing projects, and another for recording labour hours across their team per project, however their labour planning lived in separate workbooks with a separate tab for each department. This meant that there was a lot of double entry and manual entry which was unnecessary, the same information was also being duplicated in many places manually which meant systems got out of sync, and they were only able to forecast two weeks ahead. Our solution was to build one central platform to replace these workbooks and a new forecasting model which allowed them to use the valuable data they had accumulated to forecast labour requirements far out into the future based on current workloads.

In addition to this we also identified and built a unique system to integrate their individual staff members' labour forecasting with their timekeeping entries, making this whole process very streamlined for them, as well as linking their health and safety system and their project file storage system up to the central hub, meaning that files updated in their main file management platform were also live synced to other platforms.

More time on the work that drives revenue.

Overall this resulted in a big productivity improvement for the organisation and increased overall information accuracy, allowing them to spend more time on things that drive revenue for the company.

04 — Block by block

9 blocks.

Block 01

The week

Every person plans their own week on a grid, picking the job from the live register and placing blocks of hours in their days.

Block 02

Team week

Leads open their team's week in the same layout as the old sheet, with the footers that reconcile it; leave sits in the same grid.

Block 03

Projects

The projects register and the programme, one bar per project drawn from its current stage, in the project system's own stage names.

Block 04

Labour forecast

An allowance per team per job, drawn down by every scheduled and worked hour, so leads see available hours against required hours by department about three months ahead.

Block 05

Dashboards

KPIs, charts and the health and safety tracker, all reading the same hub, so every screen shows the same current figures.

Block 06

Timesheets system sync

Completing a task writes the timesheet into the timesheet system, and actuals come back every fifteen minutes, deletions included.

Block 07

Health and safety system sync

Inspections and forms from the site app and incidents and checklists from the project system land in one health and safety tracker, reconciled line by line.

Block 08

File storage system sync

The project document libraries kept in step with the file storage system hourly, with a separate lane for large files.

Block 09

Projects system sync

Project dates and role assignments flow in on a fifteen-minute poll and edits made in the platform go back; financials, schedules and safety records come across nightly.

05 — The process

10 steps.

Discover

  1. Initial discovery meeting with the MD to scope and identify the opportunity for efficiencies and improvements.
  2. Project engagement, and meetings with individual department heads across the organisation to gather information as to how they currently do things.
  3. Existing systems documented and explored.

Plan

  1. Integration — secure access to systems to enable development.
  2. Plan developed and signed off, including wireframes.

Build

  1. Build and test phase.
  2. Initial deployment.
  3. Debugging phase.

Run

  1. Wider rollout.
  2. Ongoing maintenance and system security.
06 — Contact

Ready to build?

A short call about your systems, and what they could be doing for you.

Book a conversation

← All systems delivered