Vendor access

This part is for Aigna staff

Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.

Go to your installation

Keia Method· Level 2 · 2.4 · idea 4 of 5

Own it, hand it on

Give every job one named owner, and when it has to move, move all of it.

Try it in the demo

Idea 4

Own it, hand it on

Instead of: passing a job up a chain where each team starts again.
You: give every job one named owner until whoever it affects can work again. If someone else must act, hand it over whole: what is known, what was tried, why it is theirs.
You'll know it's working when: nobody asks "who has this?", and nobody is asked the same question twice.

In Keia Atlas: each job says who has it and why, with its whole history attached.

In the morning story, this is 08:15: Liam finds that Tuesday's update turned the room's network port off. He cannot change the switch, so he hands the job to the network team with everything he found. The job now reads "With Network team: needs the port for 3.09 turned back on." Read the story

In full, with no software

Instead of: Escalating through tiers, where each team starts again. Each reassignment cuts satisfaction by about 10 points and takes the time a person loses from about 2 h to about 9.5 h (HappySignals, 2025 and 2026).
You: Every job has one named owner: the person who took it, or the service owner who approved the rule that runs it. The owner keeps it until the person is back working, or hands it on whole: the record moves with its history, evidence and context, and says who has it now and why. Vendors, integrators and managed service providers are peers in the same record, with access scoped to the job and ending when it closes. Routine work is handed to a standing rule owned by a person.
The moves: Take pick it up
Hand to pass it as a peer, with why
Park one minute: where I stopped, the next step, the open question; resuming takes one glance
Run a standing rule does the outcome
Roll back or Undo where the rule has one
The default when nothing moves: Work not taken within the service's response target goes to the service owner. A major incident names one commander. A hand-off to a vendor carries the contract's clock, visible to both sides.
Cover: Handover for leave or a shift is a fixed short card (open, fragile, who owns it, what changed), not a chat thread. Coming back opens with what changed, what is yours and what was handled.
You'll know it's working when: Jobs change hands less often; no job sits with nobody; every parked job has a resume note; vendors answer within their contract, read from the record. Measure all four.

In Keia Atlas

The job moves; the record stays

With you · since 08:10

Incident · 3.09 Whooper Swan · opened 07:52

Video bar cannot be reached by its name

07:52 Opened from the fleet tool alert; space, unit and last change filled in
08:10 The unit answers on its address, not on its name
08:14 The DNS record holds an old address; the build sheet has the right one

You took it. You keep it until the person is back working, or hand it on as a whole.

Every job carries a With line: "With Network team: needs a switch config change." Waiting on names what it is stopped for. A vendor sees only the jobs handed to them, with the contract's clock on each. Handing on is one action, and the history, evidence and context go with it.

Why it works, and its limits

Why it works: Each reassignment multiplies lost time and cuts trust; a structured handover cut medical errors by 23%; external change approval does not reduce change failures. Peers with context beat tiers without it.
Limits: Escalation exists for reasons: contractual clocks, skills, command in a crisis. The default owner, the commander and the visible clock answer those without a tier.

What it maps to

On screen	Plain meaning	Maps to
With you / With Anna / With Network team / With Poly (vendor)	Who holds the work now, and why	Replaces assigned, escalated, tier
Ready for you	Prepared and waiting for you	Replaces needs you, action required, assigned
Waiting on + who or what	Stopped until something outside the record moves	ITIL on hold; replaces blocked, pending
Verbs: Take, Hand to, Park, Run, Run again, Undo, Roll back, Accept all, Prepare, Propose, Approve, Capture, Export	Pick it up; pass it as a peer; leave a resume note; do the outcome; retry; put it back; restore the declared previous state; verify a batch at once; get a draft ready; suggest an edit; say yes; record a fix; take the data with you	Replace assign, escalate, execute, submit
Done automatically	Run under a standing rule, read back, recorded, with "How was this done?"	Automated standard change

Try it in the demo

Opens as Liam, the Dublin technician. Everyone in the demo is made up; nothing you do leaves this browser.

Open the booking panel incident: it says who holds it and what it is waiting on.
Read its history: every hand-off keeps the evidence with it.
Switch View as to Anna: the same record, the same history.

Open the Whooper Swan booking panel incident

This part is for Aigna staff

Own it, hand it on

Own it, hand it on

In full, with no software

In Keia Atlas

The job moves; the record stays

Why it works, and its limits

What it maps to

Try it in the demo

View as

Suggested

Delivery

Support and service

The Lab

Leadership

Partners

Overview

Settings

Tell the team