Superintelligence Prep for Crane Rental: Lift Requests and Permits
How crane rental teams can use AI agents for lift request intake, permit tracking and operator certificate records, and which safety holds stay with a person.

A superintelligent agent for a crane rental company can take lift requests in one consistent format, track permit status against the jobs they affect, and keep operator certificate records current enough to flag gaps before a crane is booked. It should not decide whether a lift is safe, whether a permit covers a specific site, or whether an operator may work a given load. Those decisions belong to a qualified person, and the agent's job is to make that person's decision faster, better documented and harder to skip.
Key takeaways
- An intake agent collects the facts a lift planner needs (load, radius, site, ground, date window) and holds incomplete requests before they reach dispatch.
- Permit tracking should report what the issuing authority's record shows, including status, conditions and expiry, and never an inferred approval.
- Operator certificate records need expiry checks tied to each assignment, so gaps surface before the job is confirmed.
- Wind limits, ground doubt, power line proximity, lift plan changes and certification gaps stay with a named qualified person.
- Start with one request type and one observable success criterion, then widen the agent's scope only after the holds have proven reliable.
What the intake agent should collect
Lift requests arrive by phone, email, web forms and text messages, and most of them arrive without the details a lift planner needs. A customer who asks for a lift on a Tuesday often knows the building, the load and the reason for the job, but not the ground conditions or the obstacles above the work area. An intake agent reads each request, fills a structured record and lists what is still missing. The minimum set usually looks like this:
- Customer, billing contact and the person on site who can answer questions
- Site address, access route and access hours
- Load description, estimated weight and lift points as the customer knows them
- Required reach, height and boom or jib configuration, if the customer knows them
- Ground conditions, including any mats, outrigger requirements or bearing information
- Overhead obstacles, nearby power lines, pedestrian routes and occupied buildings
- Requested date window and the name of the person who can approve the lift plan
The agent confirms what it received, asks for what is missing and writes a request record with each answer tied to its source message. It does not calculate capacity, choose a crane or promise a slot. Those steps stay with the rental company's qualified staff or its engineering process. A request record that is complete on first submission saves the dispatcher from a second round of questions, and it gives the lift planner a clean starting point instead of a chain of forwarded emails.
Permit tracking that reports the record, not the hope
Many lifts need permits from a city, county, port authority, utility or property owner, and the status of each permit can change while the crew is already scheduled. The common failure is simple: a permit is applied for, the dispatcher remembers it as approved, and nobody checks the document. Permit tracking should store what the authority actually said, with the date and the source, and it should make the gap between requested and granted visible. A practical sequence for the agent and its human owners looks like this:
1. Create a permit record when the request is accepted, linked to the job, the site and the responsible person. 2. Store the status exactly as the authority or the permit document shows it, with the date it was recorded and the file that holds it. 3. Flag any job that is confirmed while its permit status does not read approved in the source record. 4. Show expiry dates and renewal windows to the person who schedules work, well before the job date. 5. Route every permit condition, such as hours, closures or flagger requirements, to the site lead before dispatch. 6. Escalate a rejected, expired or unclear permit to a named human the same working day.
The agent can draft the follow-up message to the authority or the customer, but a person sends it when the file calls for a decision. This keeps the permit trail accurate, which matters more on the day a crew arrives at a closed street than on the day the application was filed.
Operator certificate records and job assignments
Each operator's certificates, licenses, training records and site-specific inductions should be stored with issue dates, expiry dates and the equipment categories they cover. The agent's useful work is matching. When a job requires a certain crane category or a specific rigging role, the agent checks whether the assigned person has a current record for that category and warns the dispatcher if the record is missing, expired or ambiguous. The agent does not judge competence from a document, and it does not reassign people on its own. A useful record usually contains:
- Certificate type and issuing body, as printed on the document
- Expiry date and the date the next renewal review is due
- Equipment categories and rigging roles the operator is recorded for
- Site-specific induction records for customers who require them
- Signal person or rigger records, where your own policy tracks them
- The date of the last verification and the name of the person who checked it
Certificate data is personal data about named employees. Limit read access to dispatch, compliance and operations roles, define how long expired records are kept, and make sure the agent cannot export the full file to a customer or subcontractor by accident. Records like these are easiest to keep accurate when the same person who verifies a certificate is the one who updates the system, and the agent's log shows who did what and when.
The safety holds that stay with a qualified person
A safety hold is a condition under which the agent stops moving a job forward and routes it to a human. Holds are where the agent's design matters most, because a convenient default can quietly turn a scheduling tool into a decision maker. Defining these boundaries before launch is part of managing AI risk in the way the NIST AI Risk Management Framework describes: decide in advance where human judgment is required, who holds it, and how the decision is recorded. The holds below should release only when a named person records the decision:
- Wind or weather readings near the limits written in the lift plan, where a qualified person decides whether to proceed
- Ground bearing that is uncertain, missing or no longer matches the assessment on file
- A lift plan revised after the request was accepted, so dispatch must wait for the reissued plan
- Proximity to overhead power lines or underground services, until the utility or site owner confirms clearance
- An assigned operator with no current record for the crane category or rigging role
- A permit that is unclear, expired, rejected or conditional without a named owner for the condition
- Changes to public access, pedestrian routes or adjacent occupied buildings
- Any incident, near miss or damage report, which stops automated messages to the customer about the job and opens a review
The agent may draft a message explaining that a job is on hold, but it should never tell a customer that a lift is safe to proceed. For incident handling, the discipline is similar to the one described in incident logs for security firms, where the record must show what was known, when, and who made the call.
Illustrative scenario: a Friday request with a missing ground report
Illustrative scenario, not a client case: a customer asks for a lift on a Friday to place rooftop equipment. The request includes the load and the required height but leaves the ground field empty. The intake agent marks the request as incomplete, checks the assigned operator's record against the crane category and finds that the street closure permit reads submitted rather than approved in the source document. The agent places the job in a pending state, sends the customer a short list of the three open items and notifies the dispatcher and the site lead. The dispatcher does not confirm the Friday window until the ground assessment arrives and the permit status is confirmed by the authority's record. On Monday, whoever picks up the file can see each source, timestamp and decision without reconstructing the chain from memory. Equipment businesses with similar return and damage questions can compare notes in the equipment rental guide.
How Be Human runs this as a managed service
Be Human designs the first engagement around one useful role, here the lift request intake and permit tracking function, along with the memory and tools that role needs, the approval boundaries described above and a success criterion the operations lead can observe, such as the share of requests that arrive complete on first submission. Managed operations then cover monitoring of the intake queue, recurring reviews of which holds fired and whether they were right, permission reviews on every system the agent can read or write, incident response when a hold fails to trigger, and controlled changes to the agent's rules that are tested before they reach dispatch. Operator certificate data stays in the company's own systems with access limited to named roles, and the agent's actions are logged so a person can audit them.
If you want to find the first task worth handing to an agent, take the free Be Human AI diagnostic.
Frequently asked questions
Can an AI agent approve a lift or sign off on a lift plan? No. A lift plan, capacity decision and go or no-go call belong to a qualified person in your company, and the agent should be configured so it cannot mark a job as cleared for lifting. Its role is to collect the facts, flag what is missing and route the decision to the right person with the evidence attached. The approval itself should be recorded under that person's name.
How does the agent know a permit is valid for a specific site? It does not know that from a message or a status field alone. The agent should store the status as the issuing authority's document or record shows it, with the date and the source, and it should flag any job that is confirmed while the record does not say approved. Whether the permit covers the exact site, hours and conditions is a judgment for a person who reads the permit itself.
Do we need to store operator certificate data inside the agent? The agent needs access to the fields that support matching, such as certificate type, category, expiry and last verification, but it does not need copies of every document. Keep the source records in your own systems, limit access to dispatch, compliance and operations roles, define how long expired records are kept and log every read and update. Review those permissions on a regular schedule, not only when something goes wrong.
Where should a crane rental company start? Start with one request type, such as standard lift requests for a single equipment category, and define the holds and the success criterion before any automation goes live. Run the intake and permit tracking alongside your current process for a while, compare what the agent flagged with what your people decided, and widen the scope only when the holds have behaved the way your qualified staff expect.
Your next step
See where an AI agent fits in your company first.
Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.
Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.


