Internal Job Transfer Management System for Rig and Site Rotation
Kissflow tracks a request to move from one rig, site, or business unit to another, with the sending and receiving supervisor both signing off before the transfer is confirmed, and a complete transfer history HR can check at any time without chasing down old emails.
Trusted by energy operators worldwide
An employee who transfers from one rig to another needs both supervisors to agree, not just one.
A technician wants to move from an offshore rotation to an onshore assignment for family reasons, or a business unit needs to pull someone off another unit's crew for a short-term project. Both kinds of moves need the sending supervisor to actually release the person and the receiving supervisor to accept them, and when that agreement happens over a phone call between two site offices, the transfer date, the handover details, and the record of who approved what all live in someone's memory instead of anywhere HR can check.
Kissflow captures the transfer request with a destination and an effective date, requires sign-off from both the sending and receiving supervisor before anything is confirmed, and keeps a full transfer history that HR and both supervisors can check at any time, instead of reconstructing it from old emails when a dispute comes up.
HR configures approval routing and rig or site rosters in the visual builder, so a transfer request always reaches the right two supervisors regardless of which unit initiated the move.
Where an internal transfer loses its record between two supervisors
Approval is one-sided
A receiving supervisor accepts someone before the sending supervisor formally releases them.
No transfer date of record
The effective date of a move gets disputed after the fact.
Handover is undocumented
Nobody tracks whether the outgoing role was properly handed over.
No history
HR cannot see an employee's transfer history without asking around.
Three modules. Every transfer signed off by both sides before it is final.
Configure approval rules by site and business unit.
Transfer request
A move between rig, site, or business unit is requested with a destination and a proposed effective date.
Dual sign-off
Both the sending and the receiving supervisor have to approve the move before the transfer is confirmed.
Transfer history record
Every move is logged against the employee's record, giving HR a full transfer history to check anytime.
From request to system of record in four steps
Submit
A move is requested with a destination rig or site and a proposed effective date attached.
Review
The current supervisor confirms the release, so the sending side is officially accounted for.
Approve
The destination supervisor confirms acceptance before the move becomes official on either side.
Record
The transfer is finalized on the effective date and logged to the employee's history.
What changes when internal transfers run on Kissflow
| Process | Before Kissflow | On Kissflow |
|---|---|---|
| Transfer request | A phone call or informal ask | A structured request with an effective date |
| Sign-off | One-sided or undocumented | Both supervisors confirm before it is final |
| Effective date | Disputed after the fact | Fixed and recorded at approval |
| Handover | Assumed | Tracked as part of the transfer record |
| Transfer history | Not centrally available | One record HR and supervisors can check |
| Audit trail | None | Every transfer logged with both approvals |
Connects to your HRIS; Kissflow does not replace your system of record for employee data
Kissflow runs the transfer request and dual-approval layer. Your HRIS stays the system of record for the employee's official assignment.
.svg){kind=logo}
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
Built for how a rig or site transfer actually needs two signatures
Both sides have to agree
A transfer is not final until sending and receiving supervisors both sign off.
A real transfer history
HR can see every move an employee has made without asking around.
No disputed effective dates
The transfer date is fixed at the moment of approval.
Live in weeks
Configure approval rules in the visual builder, or describe the use case to the AI Builder.
Governed from day one
Role-based access and a full audit trail on every transfer.
One view for HR
Every pending and completed transfer in one place.
Related apps
Headcount Requisition & Approval Management System
Request a new position rather than move an existing employee.
Travel Request & Approval Management System
Approve travel tied to a rotation or transfer.
Field Personnel Competency & Passport Management System
Verify competency travels with the employee to the new site.
We help workforce teams move people between sites without losing the record
.gif)
“If a company cannot enable everybody to use AI, they will never get the true benefit of AI. Platforms like Kissflow allow us to put that capability in the hands of our users in a safe way.”
Vagesh Dave
GVP & CIO at McDermott International, Ltd
See The Full Story
“Advanced automation of all processes is easy to set up. I cannot imagine how to manage workflows without this software.”
Tanay Tiwary
Global Head - Digitalization & Business Improvement
See the Full Story
“Kissflow supports rapid application development by building a working application prototype in the shortest amount of time.”
Maria Theresa Cabigon
CIO, SN Aboitiz Power Group
See The Full Story
See what Kissflow can do for you
Talk to usGot questions? We're here to help.
Get SupportNo. Your HRIS stays the system of record for the employee's official assignment. Kissflow runs the transfer request and dual-approval layer.
Headcount Requisition requests a brand new position to be filled. This app moves an existing employee between an existing rig, site, or unit.
Yes, a transfer is not confirmed until the sending and receiving supervisor both approve.
Yes, every completed transfer is logged and available to HR and supervisors.
No, the effective date is fixed at the point of dual sign-off.
Yes, transfer types are configured for site, rig, or business-unit moves.
Configuration and AI-assisted app generation move delivery from a multi-month program to a matter of weeks.
Kissflow is certified to SOC 1, SOC 2, SOC 3, and ISO/IEC 27001, with role-based access on every record.
