How to Inspect an Aerial Work Platform Before the Shift Starts

At 5:50 in the morning a warehouse operator stands at the base of a scissor lift parked exactly where the night crew left it, keys in one hand and the operator manual's inspection page in the other, dock lights still coming on overhead. Nothing about the machine looks wrong. That is the moment the decision gets made, and it gets made by looking, not by starting the machine and finding out what happens.

On a Genie GRC-12 in US ANSI/CSA configuration, the pre-operation inspection is a release decision about whether this machine goes to work today. Everything below follows Genie manual 133573, Second Edition / Second Printing May 2014, covering serial ranges GRC11-1000–GRC16-2369, GRC16P-2370–GRC16P-4599 and GRCP-4600–GRCP-5999. It does not carry over to other models, and it is not a substitute for the page in your own manual.

Each Shift, Before Anything Moves

The manual places the pre-operation inspection in the operator's hands, before each work shift, and defines it as a visual inspection: the machine is looked at, not exercised. Its stated purpose is to discover if anything is apparently wrong with the machine before the operator performs the function tests.

That assignment matters more than it reads. Because the duty lands on the person about to run the machine and repeats every shift, the inspection is an operator task rather than a maintenance-department event, which means the sequence starts at the machine with whoever holds the key, not with a shop ticket raised at the end of the week. The interval is the shift, not the calendar day, so a unit that runs two shifts in one day is walked twice.

The order is fixed from there: operator, shift start, visual pass, and only then anything that moves.

Why the Visual Pass Has to Come First

A function test is a demand. The machine is asked to move and to perform its functions, and each of those commands sets fluid moving, switches closing and linkages taking load. The visual pass is the one window in which the machine is still and nothing is being commanded, which means it is the only point in the shift where a fault can be read as a static fact instead of inferred from behavior.

The reason the order matters is diagnostic. Whatever the manual's list asks you to look at, a departure from the as-delivered condition sits quietly on a parked machine and can turn into an intermittent symptom once everything is running and warm, and an intermittent symptom is the hardest kind of fault to pin down an hour later. Because the visual inspection exists to catch what is apparently wrong before function tests begin, testing first does not add information, it removes the clean baseline you would otherwise have had.

It comes down to what you are comparing against. On a still machine the reference is the machine as delivered; once it has moved and warmed, you are comparing a running machine to your memory of a parked one.

Which items to look at is not something to import from a general checklist. The list belongs to the manual for the specific serial range, and the GRC-12 list is written for the GRC-12.

One Damage Finding Stops the Shift

The manual is blunt about the outcome of a finding. If damage or any unauthorized variation from the factory-delivered condition is discovered, the machine must be tagged and removed from service, not noted, not watched, not run gently for the rest of the shift.

A tag-out costs throughput on that shift, since a machine sitting at the dock is a pick face nobody can reach, and that cost is precisely why crews defer it, usually with a sensible-sounding story about finishing the wave first. Here is the one judgment worth pressing: an inspection that never ends in a tag-out is evidence of a relaxed standard, not of a safe fleet. The condition that limits it matters as much as the claim — a unit already tagged and waiting on repair is not a candidate for release, and this covers only the pre-operation visual check on the GRC-12, not annual inspections, not other machine types.

Repair is not the operator's call either. Repair work is restricted to a qualified service technician working to the manufacturer's specifications, which means the operator's involvement ends at the tag, not at the repair.

Where Routine Maintenance Fits In

The same walk-around doubles as a maintenance trigger. The pre-operation inspection also serves to determine if routine maintenance procedures are required, and only routine maintenance items specified in the manual may be performed by the operator.

The reason that line is drawn so tightly is that the inspection is a detection tool, not a repair authorization. Spotting something on the manual's routine list and handling it as the manual describes sits inside the boundary; chasing why the condition appeared does not.

Which means the correct output of a maintenance finding is a handoff with a description attached: what you saw, where you saw it, and which machine. A tag plus a couple of sentences is worth more to the technician than a verbal “something's up with the lift” on Friday, because it preserves the still-machine observation the visual pass was designed to capture.

A Tagged Machine at Six in the Morning

Suppose a unit comes back from a night shift with a variation from its factory-delivered condition — something the operator can see, whatever the manual's list puts in front of them. This is a hypothetical walk-through rather than a reported incident, but each branch follows the manual's order.

The path is short. The machine is tagged and comes out of service on the spot; the repair goes to a qualified service technician working to the manufacturer's specifications; and when the work is done the operator performs the pre-operation inspection again before going on to the function tests. Note the repeat, because the machine that returns from repair is not the machine that was tagged.

The shortcut worth naming is running a function test first, to see whether it is really a problem. That inverts the order the manual sets, and it does so at the worst moment, since any motion you command is being commanded on a unit you already have reason to doubt. A close second is the half tag-out: entered in the log, no tag on the machine, machine still in the aisle. The next operator was not part of that conversation and sees a machine that looks available, so the tag-out never actually happened.

How You Know the Inspection Was Done Right

When the walk-around closes, the machine should sit in exactly one of three states. Nothing apparently wrong, so the function tests may proceed. Damage or an unauthorized variation found, so it is tagged and out of service. Or repairs completed, in which case the inspection is repeated before the function tests.

That is a reasoning test, not a record-keeping requirement; the manual does not ask the operator to certify which state applies. The logic is the manual's own, and it is unforgiving. If you cannot say which of the three you are standing in, the inspection has not been closed out, which means the machine is in an undefined state, and undefined never authorizes a lift.

Why This Stops at the GRC-12

Every passage above comes from one document: the GRC-12 operator manual 133573 for the US ANSI/CSA configuration, the same edition and serial ranges named at the top of this page. That manual warns against carrying its instructions over to the later GRCP-6000 edition, and the same caution applies sideways.

This is not a legal footnote; it is the mechanism the inspection runs on. A visual pass compares the machine in front of you to a defined as-delivered condition, and that definition lives in the manual for your serial number. A checklist from another model or another edition compares your machine against the wrong reference, and the mismatch shows up either as faults that are not there or as conditions that look normal but are not normal for your unit.

If your unit is not a GRC-12, three questions are worth settling before the next shift: which manual edition covers my serial number, is my machine in the configuration that edition describes, and does the nameplate match what the manual says it should? Those get answered from the nameplate and the manual in front of you, not from a forum post or a generic checklist. Settling them before the next shift takes a few minutes and determines which list you are even supposed to be walking.