Three decisions instead of one signature
A contractor team arrives at a German steelworks for planned maintenance. Identification and a training certificate are available at the gate, the equipment appears idle, and production wants a quick restart. None of this establishes whether the people understand the particular work area, whether protective measures are actually in place, or who will accept the equipment back. A dependable process therefore separates three decisions: access following induction, permission to begin the specified task, and return to operations. One decision must never be treated as automatic evidence for the other two.
This guide develops a practical induction and handoff record for that purpose. It is a recommended organisational aid, not a universal statutory form or a technical instruction for hazardous tasks. Its details must reflect the risk assessment, equipment and local procedures. The discussion of online occupational safety instruction explains the broader boundary between digital learning and site-specific instruction. This article focuses instead on interfaces between the client, contractor, other trades and the next shift. The English version retains the German legal context; it does not import a foreign permit regime.
What the official sources actually require
Cooperation between employers under section 8 ArbSchG requires coordination of protective measures and, where necessary, exchange of information about hazards when employers work together. Depending on the activity, the host employer must also satisfy itself that outside workers have received appropriate instructions about site hazards. This does not mean that a reception signature fulfils every obligation. In practice, the works needs a traceable comparison of existing competence, task instruction supplied by the contractor and information only the local operation can provide. Unclear responsibilities must be resolved before the work begins.
For work equipment, section 13 BetrSichV specifies how cooperation works: the client must choose competent contractors and explain hazards arising from its equipment and particular conduct rules. The contractor must explain hazards created by its own work. Where risks to other employers' workers cannot be excluded, employers cooperate in their risk assessments. In the provision's specified circumstances of increased danger to other employers' workers, a coordinator must be appointed in writing. This is not a blanket claim that every visit requires one. Appointment expressly does not remove the participating employers' own responsibilities.
For maintenance, section 10 BetrSichV addresses matters including effective communication, protected work areas, dangerous energy and systems for authorising specified work. Competent and authorised people determine the necessary technical safeguards for the particular job. The handoff record references those procedures and their evidence instead of inventing technical steps itself. Section 12 ArbSchG requires instruction related to the workplace or task and adjustment to changing hazards. A general course completion is therefore no substitute for addressing modified equipment or a new working situation. The record supports these decisions but cannot make them on its own.
Before arrival: connect the job with its owners
Procurement should arrange more than a scope of services: it should establish a named site contact and trigger coordination with the equipment-owning department. Before arrival, record the location, task, planned times, participating people, subcontractors and possible interactions. The contractor identifies methods and equipment that could introduce additional hazards. The operating department adds local conditions and concurrent work. A role matrix between operator and service provider offers a useful organisational model; its logic transfers, not every building-specific duty. Having one contact is convenient, but it does not replace clear allocation of technical decisions.
The record distinguishes at least four functions: who specifies and commissions the task, who assesses the equipment state, who leads the contractor team, and who decides whether operations can take it back. Depending on the organisation, one person may cover several functions if competence, authority and an available deputy genuinely fit. Principles for selection, briefing and control when delegating duties help prevent this becoming a mere list of names. Authority boundaries matter: a coordinator cannot issue electrical, process or other specialist approvals simply because their phone number appears at the top of the form.
At the work location: induction with teach-back
Site induction connects general works rules with the assigned area. It covers safe access routes, adjacent activities, required protective equipment, reporting routes, alarms and the boundaries of the job. Rather than simply asking whether everyone understands, the instructor asks workers to explain the intended access and escalation route. Language support must enable understanding of the actual safety information. A translated standard video does not automatically achieve that. Record the area, content, time, instructor and unresolved questions. Safety-relevant open questions prevent approval of the affected task; a completed attendance field does not neutralise them.
Three kinds of evidence remain separate: general knowledge, practical competence and job-specific induction. If a contractor worker is also expected to operate a crane, general site induction is not sufficient. The distinction between instruction and competence for crane work explains why such roles need separate checks. Previous work at another site likewise does not prove familiarity with the current equipment. The record should therefore reference required competence and authorisation evidence in a verifiable way, without indiscriminately copying entire personnel files. Missing prerequisites become an open decision with a responsible owner and a due time.
Permit record: eight fields that expose the decisions
A usable layout begins with four fields: first, a unique job reference, equipment identifier and physical boundary; second, the precise task including explicitly excluded work; third, participating companies, team leader and current personnel; fourth, agreed hazards and interfaces. A maintenance order might specify replacement of a component within a bounded area while excluding neighbouring equipment. The description must be precise enough for the next shift to recognise an extension of scope. Vague descriptions such as “repair in hall three” help neither the approval decision nor a later investigation into what actually happened.
The remaining four fields address, fifth, agreed protective measures with owners and verifiable implementation status; sixth, the start decision with approver, time window and conditions of validity; seventh, interruptions and changes; and eighth, return and acceptance by operations. Referenced specialist procedures remain authoritative: a green checkbox is not technical evidence. Useful statuses might include “in preparation”, “released”, “suspended” and “returned”. These are suggested local terms, not a legally prescribed taxonomy. Each change receives a time, responsible person and understandable reason, avoiding the need to reconstruct the sequence from memory afterwards.
Every job needs agreed triggers that return approval for review. Typical examples are a different working method, an additional equipment section, changed surroundings or a personnel change with unresolved induction. Adjacent welding, for example, can affect people beyond the welding station itself. The article on welding fume instruction explores that specific hazard; the contractor record identifies who assesses the interface and which conditions must be maintained. It should explicitly provide for stopping when a deviation remains unresolved and contacting the responsible person, rather than allowing an informal continuation outside the approved scope.
AI-generatedThree scenarios for a joint exercise
Scenario one: the expected team arrives with a substitute whose identity and induction status are not recorded. The task is unchanged, but a personnel prerequisite has changed. Reception passes the deviation to the site contact and contractor supervisor. They establish the required evidence for the role and arrange local instruction before deployment. The correct exercise answer is not automatically “send everyone away”, but “do not assign an unchecked person to the affected task”. The completed record states what was missing, how it was resolved and who accepted responsibility for the subsequent deployment.
Scenario two: during a repair, another trade starts nearby work that changes the agreed access route or protective conditions. The team does not assume that separate permits held by each company settle the interaction. The affected activity is suspended under the local procedure while the parties review the changed interface. In the exercise, participants identify the added hazard, locate the appropriate contact and explain the conditions for renewed approval. Assessment focuses on the quality of that decision, not on how quickly the form can be made to display a green status again.
Scenario three: the job is unfinished at shift change, but the original approver has left the site. “The next team knows about it” is not a handover. A dependable deputy matrix for knowledge and approvals identifies available people with appropriate authority. The outgoing shift records progress, remaining hazards, safeguards still in place and open decisions; the receiving role confirms understanding and the continuing status. If nobody authorised can assess the conditions, time pressure does not justify continuing. This scenario tests availability, access to documentation and real decision-making authority at the same time.
AI-generatedReturn does not automatically mean restart
At the end of the job, the contractor first reports what was actually completed, remaining deviations and whether the work area and personnel have been accounted for. The responsible specialists then assess necessary checks and removal of safeguards under the applicable procedures. Only the authorised operating role decides on acceptance and, where appropriate, restart. A contractor's completion notice does not replace that decision. Outstanding defects, restrictions and additional inspection tasks remain visible in the record; neither commercial acceptance of an invoice nor expiry of the agreed time window makes them disappear.
For later review, induction evidence, work approval, change history and return records must connect through the same job reference. Traceable training records without spreadsheets support visibility of learning status, but do not automatically describe the actual equipment state. Retain the relevant versions and decisions in an agreed record system. Access, retention and deletion follow applicable requirements and the operational purpose, not an invented universal period in this article. The central sample-check question is whether someone outside the team can establish who authorised each next step, and on what basis they did so.
Review one bounded pilot job
Start with one clearly bounded job and review the record with the operating department, contractor and safety function. Walk through the process as a tabletop exercise before work starts, then examine the real job for missing information and unavailable decision owners. Useful internal improvement measures include unresolved interfaces before the start, traceable changes and completed return decisions. A low number of reported interruptions is not itself success: it could mean people are reluctant to raise deviations. Good review therefore also checks whether workers know and can actually use the stop-and-escalate route.
Digital learning can prepare shared terminology, typical deviations and how to read a handoff record. Site risk assessment, required practical qualification and authorised work approval remain separate. The current ConformBase steel offering describes source-based courses but also states that booking follows the final content review; expressions of interest are currently accepted. This must not be interpreted as immediate availability or a state-recognised qualification. For a local pilot, complete the site procedure first. Learning supports that procedure only when its examples and escalation routes match the actual works, rather than presenting a generic completion certificate as operational permission.
ConformBase
Turn knowledge into training that works.
Bring compliance, privacy and security awareness into a format your people want to complete, with certificates and audit-ready evidence.
Start free trialAsk about custom courses →
