Apply: Put It to Work, Safely

1. What this stage is for

Apply moves new capability into real work, preferably quickly and in bounded conditions. It's the bridge between practice and normal operations: the first coordination meeting run the new way, the first pour inspected against the new plan, the first month-end closed in the new system, the first maintenance job done with the new procedure. #2 · #56

Two forces work against this stage. The first is time. Skills that aren't used within days or weeks of learning start to fade, so a gap of two months between training and first use quietly undoes much of the investment. The second is pressure. The first real use usually happens on a live project with a deadline, where the new way feels slower and the old way is right there. Without deliberate support, people revert, and the organization concludes that the training didn't work. LSC-TRF-03 · #11

The goal of Apply is not perfection on day one. It's a controlled first use that produces evidence: what worked, what didn't, where people needed help and where the defined workflow itself was wrong. That evidence feeds Verify, which confirms people can do the work to standard, and Adapt, which fixes the system. #64 · SOP-USE-01

2. Start bounded

Pilot on one live project before scaling, and when AI is involved, pilot one bounded workflow with human review. A bounded first use limits the cost of the problems you'll certainly find, keeps support close, and gives you a clean comparison with work that hasn't changed yet. In manufacturing, studies of digital initiatives find that scaling, not the technology, is usually the bottleneck; a pilot that never had a path to scale is a demonstration, not a step. #1 · #12 · DM-ARC-07

Within the bounded first use, apply three rules that come from field procedures and work in any setting:

• Prepare, verify the first work, then keep watching. Check the first instance of new work closely, before it's repeated, then keep checking at a lower intensity. The first pour, first model issue or first close is where misunderstandings show up cheaply. SOP-USE-06 · SOP-USE-04
• Give graded responsibility. Start people on work where mistakes are recoverable, and widen their authority as they show they can handle it. Rotations and steadily growing design authority turn supervised experience into capability. LSC-MNT-04 · #28
• Keep irreversible steps supervised. Hold points before concrete or grout hides the evidence, publishing a model for construction, releasing a payment, changing a controller: these need a second person until competence is verified. QMS-ITP-02 · BM-CDE-01 · FIN-CTL-03

Make the first use part of the project, not an extra. Build the new practice into project mobilization, so it's in the plan, the budget and the meeting cadence from the start. A new coordination process that depends on someone remembering to run it will not survive the first deadline. #56 · BM-COO-04

3. Expect the dip

Almost every meaningful change makes people slower before it makes them faster. Plan for an initial productivity dip, tell people and managers it's coming, and protect it in the schedule. Industrial AI follows a similar J-curve, with costs and disruption first and gains later. A rollout that treats the dip as failure tends to abandon the change at its lowest point, just before it would have paid off. #11 · DM-AIM-01

Three things shorten and soften the dip:

• Managers who coach. Supervisor support is among the strongest predictors of whether training is used on the job. The manager who asks "how did the new clash process go?" on Monday does more than another course. #53 · LSC-TRF-04
• Coworkers who know. New engineers learn mostly from the people around them, not from managers. Put people who have done the new work next to those starting it, and prepare both. LSC-MNT-03 · #33
• Debriefs after real work. Ten minutes after the first coordination meeting or the first pour, asking what happened and what to change, turns experience into learning. SOP-TRN-02 · PM-23

Make inefficiency visible as well as the dip. Experienced people can keep slow methods for years because their results look fine. Showing them the time their own tasks took with the old and new methods is more persuasive than any course outline. LSC-SFT-02 · LSC-SFT-01

4. Help at the moment of need

During Apply, most questions arise in the middle of a task. Put performance support in the flow of work: short, searchable guidance inside the tools people already use, at the step where they need it. A two-minute answer inside the CDE, the CMMS or the ERP is worth more than a course the person would have to leave the work to find. Provide one discovery point for everything else, so nobody has to remember which of four portals holds the answer. #22 · IDE-TEC-05 · #30

Use checklists for the steps that matter, designed the way that works. Read-and-do checklists suit novices and rare tasks; do-and-confirm checklists suit experts. Keep only the items that kill or cost, because a long checklist trains people to tick without looking. And remember that a checklist works through how it's introduced, with the people who use it, not because it exists. SOP-CHK-01 · SOP-CHK-03 · SOP-CHK-02

Pre-task planning deserves its own mention on construction sites and in plants. A short pre-task briefing works best when it trains people to spot hazards in the task in front of them, not when it's a form signed at the start of the shift. Keep one current version of every procedure at the point of use, with version stamps on printed and offline copies, so nobody follows a superseded method. SOP-CHK-05 · SOP-DIG-01 · SOP-DIG-03

For complex procedures, small practical aids help: marking your place in a long procedure, putting the warning before the step rather than after it, and designing for the field with pictures and plain words. These are cheap, and they prevent a surprising share of errors. SOP-USE-02 · SOP-DES-04 · SOP-DES-05

5. When the procedure doesn't fit

The first real use of any new procedure will find cases it didn't anticipate. What people do at that moment decides whether the procedure improves or quietly dies. Treat deviation as data: a record of where the written method and the real work disagree. A normal, routine shortcut is a warning, not a convenience, because it means the procedure and the work have drifted apart. SOP-USE-01 · SOP-USE-05 · DGN-GAP-01

Supervisors play a particular role here. Supervisors verify in the field, not from the office: walking the work is how they see where the procedure and the site disagree. A ticked box isn't a verified outcome, and a field change is a design change, with the same review. Where several employers share a site, coordination between them needs its own procedure, because each firm's method statement assumes the others aren't there. SOP-USE-04 · SOP-CHK-04 · SOP-GOV-03 · SOP-USE-07

When the stakes are high and time is short, the crisis rules apply. Put one accountable lead in charge, brief facts, interpretations and projections separately, act on partial information only where the step can be undone, and keep safety decisions apart from commercial ones. In a plant incident involving control systems, safety comes before the investigation. DQ-RT-06 · DQ-RT-04 · DQ-RT-14 · DQ-RT-10 · NIST-OTX-03

6. AI at work

AI tools are often the first new capability people apply, because they're easy to start using. That ease is the risk. A few rules make first use safe and useful:

• Write a brief, not a magic phrase. A good request names the task, the audience, the constraints and the format. Ask for structured outputs and, for anything consequential, for the strongest case against the answer. PRM-BIZ-01 · PRM-BIZ-04 · PRM-BIZ-06 · PRM-EVD-01
• Give it the source. Supply the document, standard or record and require answers from it; no citation, no answer. PRM-CTX-01 · SOP-DIG-05
• Verify, then trust. Recompute numbers outside the model; a model checking itself isn't verification. PRM-VER-01 · PRM-VER-03 · PRM-VER-04
• Keep a named person accountable. In engineering, the licence holder stays responsible for AI-assisted work, and AI output is never a safety function in a plant. DQ-AI-03 · PRM-ENG-01 · PRM-MFG-01
• Start with document work. Generative AI is most reliable on drafting, summarizing and checking documents, with human verification, rather than on control or safety decisions. CM-WRK-02 · DM-AIM-04

Measure whether the AI actually helps. Speed-ups that people report and speed-ups that are measured often differ, and in one controlled study experienced developers working on familiar code were slower with AI assistance. Expect modest, context-dependent gains, and check them in your own work. PRM-EVD-08 · SWD-AI-02 · SWD-AI-01 · FAM-WRK-03

7. By team: what first use looks like

Bounded first use, help at the moment of need and deviation as data apply everywhere. The boundary and the risks differ by team. #1 · SOP-USE-01

Technology and software teams

For software, the bounded first use is a staged release: a small batch, to a small group, with automated health checks, a kill switch and rollback ready. Mitigate first and fix the code later when something breaks, run incidents with defined roles, and give communication its own owner so the people fixing the problem aren't also answering the questions. A first use without a way back isn't bounded, however small the audience. SWD-REL-01 · SWD-REL-03 · SWD-INC-01 · SWD-INC-03 · SWD-INC-04

Project and construction teams

On a project, first use usually means the first package, zone or pour done the new way. Run the coordination meeting with decision-makers present, report clashes as clusters with an owner and a date, and enforce the information states so that "shared" and "published" mean something. Commit only to work that's ready, and record why commitments were missed; those reasons are the deviations of the planning process and the best guide to what to fix. BM-COO-04 · BM-COO-02 · BM-CDE-01 · CM-LEAN-01 · CM-LEAN-03

Plants and operations

In a plant, the first use of a new procedure or system often coincides with a start-up or a shutdown, the most hazardous hours of operation. Treat every temporary change through management of change, keep the first runs supervised, and use short control cycles so problems surface in hours, not weeks. If AI is involved, use it for knowledge and documents, never for control or safety functions. TAR-SAF-01 · TAR-SAF-04 · TAR-EXE-01 · DM-AIM-04 · PRM-MFG-01

Safety and emergency roles

For safety-critical work, first use is where stop-work authority gets tested. Set the stop-work conditions in advance, make sure new people know they'll be backed for using them, and resolve every stop in writing before work restarts. Pre-task planning should train people to spot the hazards in the task in front of them, rather than to sign a form. SOP-USE-03 · DQ-RT-02 · SOP-CHK-05 · CS-06

Finance and contract teams

In finance and contracts, first use is often a deadline: the first prompt-payment clock under new legislation, the first close in a new system, the first notice under a new form. Run statutory clocks exactly, keep the notice register live, and administer contracts after signature, not just before. Confirm any change to payment details by phone, on a number you already had, because the first weeks of a new system are when fraudsters find gaps. VCM-PAY-01 · VCM-ADM-01 · VCM-ADM-04 · NIST-PRT-02 · FIN-CTL-03

An illustrative example

A 200-person precast manufacturer introduced a new inspection-and-test plan for its yard. Instead of switching all three production lines at once, it started on one line for one product family. The quality lead checked the first ten elements personally, the foreman kept a one-page aid at the casting bed, and every deviation went into a shared log. In the first fortnight the log showed the same problem four times: the plan asked for a measurement the yard's tools couldn't take at that stage. The plan was fixed in a day. Had all three lines switched at once, the same problem would have appeared on every line, and the plan would probably have been blamed rather than fixed. QMS-ITP-01 · SOP-USE-06 · SOP-USE-01 · #1

Common mistakes

• A long gap after training. Apply within days, not months. #2 · LSC-TRF-03
• Scaling before the first ring has produced evidence. #1 · DM-ARC-07
• Treating deviations as discipline problems. They're information about the procedure. SOP-USE-01
• Abandoning the change at the bottom of the dip. #11
• Trusting AI output because it looks finished. PRM-VER-01

8. Handing it on

Apply hands Verify a group of people who have done the new work for real, in bounded conditions, with records of what happened: first-work checks, deviations, debrief notes and the questions they asked. Before handing on, make sure that evidence exists and is in one place. Verify needs it to judge whether people can do the work to standard, and Adapt needs it to fix what the first use exposed. SOP-USE-01 · #64

Look especially for patterns. If three people asked the same question in the first week, that's a gap in the performance support or the training, not three individual weaknesses. If the same deviation appeared on two sites, the procedure is probably wrong. These patterns are the most valuable output of Apply, and they're easy to lose if nobody collects them. #32 · KIN-SIG-01 · DGN-RCA-04

For small organizations, Apply can be as simple as choosing the next real job, assigning an experienced person to check the first attempt, putting the job aid on the shared drive, and spending ten minutes afterwards on what to change. The bounded first use and the debrief matter far more than any platform. #1 · SOP-TRN-02

The checklist. Apply within days of learning. Pilot on one project, in widening rings. Verify the first work, then keep watching. Keep irreversible steps supervised. Expect the dip and protect it. Put help in the tools, at the step. Treat deviation as data; let anyone stop work, and resolve it in writing. Brief AI properly, give it the source and verify its output. Collect the patterns. Then go to Verify.