5 ways to automate tool and asset checkouts

#1 - The basic check-in

Who it's for: Small teams sharing a few tools, where everyone knows everyone and you just need a record of what went out and when it is due back.

What it is: A tool and asset checkout is a short log that captures a piece of kit leaving its usual home: what it is, who took it, the condition it was in, and when it should return. Four steps on a phone. Type the asset and the person, pick the condition from a list, set the expected return date. Each completion is one record. The borrower runs the canvas once when they take the asset, and the open log is the list of everything currently out.

In practice: Take a three-van electrical firm sharing one set of expensive test meters and a thermal camera. An electrician grabs the thermal camera on their way to a fault call, opens the canvas, types "FLIR camera, asset tag E-04", types their own name, picks "Good" for the condition, and sets the expected return to "End of shift today". One record, ten seconds, before they leave the unit. Now the office knows the camera is with that electrician and due back tonight, rather than discovering at 8am tomorrow that nobody can find it.

Why it works: The checkout is the record. The kit itself does not change, and how people use it does not change. What changes is that the moment an asset leaves, there is a named person, a condition, and a due date attached to it. When something does not come back, the manager knows who had it last and when it was meant to return, instead of asking around the team.

Steps included:

• 1 text input (the tool or asset)
• 1 text input (who is checking it out)
• 1 single-choice step (condition at checkout: Good, Fair some wear, Poor flag for repair)
• 1 date and time input (expected return)

#2 - With written guidance

Who it's for: Sites with lots of shared kit and rotating borrowers, where the people taking tools change week to week and the rules need to be on the screen, not in someone's head.

What it is: The basic check-in with a guidance note at the top: what counts as a checkout, so people do not skip logging the small stuff. A second guidance note at the end tells the borrower exactly what to do if they cannot get the asset back on time.

In practice: Take a busy events company with a storeroom full of speakers, lighting rigs, radios, and trolleys. Different freelance crews come in for different jobs, so the borrowers are never the same two weekends running. A freelancer grabs two radios for a wedding setup. The opening panel reminds them that radios count, even though they feel too small to bother with. They log both, pick "Good", and set the return for Sunday night. The closing panel tells them that if the job overruns and the radios are not back by Monday, they message the duty manager rather than just keeping them. The storeroom stays accurate even though the faces change every week.

What it adds to the basic check-in:

1. A "what counts as a checkout" panel at the start, so small or borderline items get logged instead of slipping out unrecorded
2. A "what to do if you can't return it on time" panel at the end, giving the borrower a clear action instead of wondering
3. Consistent records across rotating borrowers, because the rules are on the screen rather than relying on a handover chat

Why it works: Written guidance sits inline at the moment the borrower is about to act. The freelancer reads what counts as a checkout right as they are deciding whether the radios are worth logging, and reads the late-return rule right as they are setting a date they might miss. It is not a policy document they were sent on day one and never opened.

Steps included:

• 1 guidance note (what counts as a checkout)
• 1 text input (the tool or asset)
• 1 text input (who is checking it out)
• 1 single-choice step (condition at checkout)
• 1 date and time input (expected return)
• 1 guidance note (what to do if you can't return it on time)

#3 - With a signature

Who it's for: Businesses where the borrower needs to sign for the asset at checkout and sign again when they hand it back, so responsibility is explicit at both ends.

What it is: The basic check-in plus two signatures on the same record. The borrower signs once when they take the asset, confirming they have it. They sign again when they bring it back, confirming it has been returned. One record now carries the asset, the person, the condition, the due date, and two finger-drawn signatures: one out, one back. The whole life of that loan sits on a single timestamped record.

In practice: Take a film and TV rental house that loans out cameras and lenses worth thousands to visiting production crews. A camera assistant checks out a lens kit for a three-day shoot. They sign on the touchscreen to confirm they have received it. Three days later they return it and sign the second signature to confirm the return. If a lens turns up scratched a fortnight later, the record shows the assistant signed it back in, which closes the question of when the damage happened and who was holding it.

What it adds to the basic check-in:

1. A signature step at checkout, where the borrower signs to confirm they have taken the asset
2. A second signature step at return, where the borrower signs again to confirm the kit is back
3. Responsibility that is explicit at both ends on the same record

Why it works: The signatures are what close the loop at both ends. The first signature adds that a named person accepted the asset; the second adds that the same person handed it back. On the same record, the two signatures turn a one-sided log into a confirmed exchange, which matters when the asset is expensive and the borrower is from outside the team.

Steps included:

• 1 text input (the tool or asset)
• 1 text input (who is checking it out)
• 1 single-choice step (condition at checkout)
• 1 date and time input (expected return)
• 1 signature (sign-off at checkout and return)

#4 - With photo evidence

Who it's for: Businesses wanting a photo of the asset condition at checkout, so a dent or scratch on return can be traced back to the moment it went out.

What it is: The basic check-in plus a photo of the tool or asset taken at the moment it leaves. The borrower takes a photo showing the asset and its condition. The photo lands in the same record as the typed condition and the due date. When the asset comes back, anyone can compare the return against the photo taken at checkout and see straight away whether damage is new or pre-existing.

What it adds to the basic check-in:

1. A photo of the tool or asset, captured at the moment of checkout
2. A condition baseline that is visual, not just a word picked from a list
3. A way to settle return disputes by comparing the asset against the checkout photo

Why it works: A picked condition is a word. A photo is the actual state of the kit. The two together make damage traceable in a way neither does alone. Captured at the moment of checkout, on the borrower's own phone, the condition cannot be reconstructed or argued about after the asset comes back marked.

Steps included:

• 1 text input (the tool or asset)
• 1 text input (who is checking it out)
• 1 single-choice step (condition at checkout)
• 1 date and time input (expected return)
• 1 photo of the tool or asset

#5 - With Poppi checking the photo

Who it's for: Teams where checkout photos get taken but nobody reviews them. Multi-site operations where head office cannot review every location's photos as kit moves around.

What it is: A photo-checked checkout is the basic check-in plus a photo of the tool or asset that Poppi (AI) reviews the moment it's saved. Poppi answers one question about that photo, set by you: does the photo clearly show the tool and its condition at checkout? If the answer is no, Poppi posts what it spotted to the team chat, so the problem gets sorted on the spot.

In practice: A multi-branch tool rental firm checks out power drills across three locations. A site supervisor photographs the drill at the point of checkout. Poppi reviews the photo: clear image of the drill showing its condition. Verdict yes, and nothing changes. A rushed handover means the photo is blurry and doesn't show the condition clearly. Poppi answers no and posts the reason to the team chat. The supervisor retakes the photo while the tool is still in the building.

What it adds to the basic check-in:

1. A photo of the tool or asset that gets checked the moment it's saved, not just stored
2. A team chat message with Poppi's reason the moment a photo fails the check
3. Sites stop being the only people deciding whether photos are good enough

Why it works: The check happens in the seconds between the photo being taken and the tool leaving. That is the only moment the problem is still cheap to fix. A manager reviewing photos the next day can only record that the photo was poor; Poppi catching it at the moment of handover gets it redone while the tool is still there.

Steps included:

• 1 text input (the tool or asset)
• 1 text input (who is checking it out)
• 1 single-choice step (condition at checkout)
• 1 date and time input (expected return)
• 1 photo of the tool or asset
• 1 Poppi decision (judges the photo against your question)
• 1 Poppi action (posts to the team chat if the photo fails the check)

How to pick the right version

You do not need to know how the canvas builder works to pick the right version. Every version here is the basic check-in plus one addition, so pick the additions your team actually needs.

Do other people run this, or just you?

If you run checkouts yourself and know the routine, the basic check-in (#1) is enough. The moment borrowers rotate or new people come in, the guidance panels tell everyone the rules on the screen: #2.

Does the borrower need to sign at both ends?

If a record is all you need, skip this. If the asset is valuable or the borrower is from outside the team, signatures lock responsibility at checkout and return: #3.

Do you need a photo as proof?

A typed condition is a word. A photo shows what actually happened. If you want visual proof of how the asset looked when it went out: #4.

Does anyone actually look at the photos?

If a manager genuinely reviews every photo, #4's record is enough. If photos get taken and filed unseen, Poppi (AI) checks each one as it's saved and tells the team chat when something's wrong: #5.

Need more than one addition? Open the version with the addition that matters most in the playground and add the others as steps. That's how the product works anyway: every option here is one step added to the same log.

Related workflows

• 4 ways to automate damage reports
• 4 ways to automate vehicle key handovers
• 4 ways to automate maintenance fault reports
• 4 ways to automate deliveries received
• 4 ways to automate job completion sign-off

Conclusion

A tool and asset checkout is a short record of a piece of kit leaving its home: what it is, who took it, its condition, and when it is due back. Every version above is the same basic log plus one addition: guidance, a signature, a photo, or an AI check on the photo. Pick the ones your team needs and combine them in the playground.

→ Build your own tool and asset checkout on Pilla.