Examples

See the job.
Zoom out.
See the context.
Now decide.

Port
10:17 AM. Berth 4.

A contractor is waiting to start hot work.

The permit is complete.
The controls look right.

Would you approve it?

Zoom out.
Bunkering is underway nearby.
A cruise ship is alongside.
Buses carrying passengers are moving through the adjacent route.
Another maintenance crew has opened work further along the wharf.
One nearby asset has been taken out of service.
And the port hasn’t stopped while somebody reviews the permit.

Now would you approve it?

Maybe. Maybe not. Maybe the work simply needs to move an hour.

But first, somebody needs the whole picture.

HANK puts the permit in context.

Where the work is happening.
What is happening nearby.
Relevant assets and infrastructure.
Their current state.
The risks created by that combination.

Not to make the decision for you.

To help the person making it see more of what matters before work starts.

Because they aren’t just approving a form.

They’re allowing work to happen inside a live operation.

The ship still needs to move.
The work still needs to get done.

And the people doing it need to get home safe.

Campus
8:05 AM. Monday.

A water main has failed beneath a large campus.

Hundreds of people are already arriving.

A contractor can be there within the hour.

They need to excavate.

Get the repair started?

Zoom out.
The excavation crosses a primary pedestrian route.
A gas service runs nearby.
The building beside the work houses hundreds of people.
An accessible entrance will be blocked.
A delivery is scheduled through the same area.
And one of the normal access routes is already closed for planned work.

There’s something else.

An ambulance may need to reach the building.

Now it isn’t just an excavation.

It’s an operational decision.

HANK puts the job in context.

The failure.
The excavation.
The underground infrastructure.
The buildings and access routes.
Other planned activity.
The people who could be affected.

And the risks that matter here, now, for this job.

The contractor might still start at 9.

The excavation might move.

Another job might pause.

Access might be rerouted first.

HANK doesn’t make that judgement.

It gives the people who do a better picture to make it from.

Because somewhere in all that complexity is a contractor about to put a bucket into the ground.

A student walking to class.

Someone using the accessible entrance.

Someone who might need that ambulance.

Context isn’t abstract when you’re standing in it.

Infrastructure
9:40 PM. Major road project.

A crew is preparing to move traffic onto a temporary alignment.

The traffic management plan is approved.
The barriers are ready.
The crew is in position.

Ready to make the switch?

Zoom out.
Another contractor is still working inside the closure.
A piece of plant needed for the changeover is out of service.
Temporary lighting has moved.
An underground service crosses the work area.
Emergency access needs to remain open.
And live traffic is still moving metres away.

Now are you ready?

The switch might still go ahead.

Another job might need to finish first.

The sequence might need to change.

But first, somebody needs the whole picture.

HANK puts the job in context.

The work zone.
The contractors.
Plant and infrastructure.
Other activity.
What’s changed.
The risks that matter.

Not to make the decision for you.

To give the people coordinating the work more of the information that matters.

Because this isn’t just a traffic plan.

It’s people working metres from live traffic in an environment that keeps changing.

HANK is being built to bring more of that context into the decision before work starts.

So the project can keep moving, the work can get done, and the people doing it can get home safe.