What’s New in FUYL: Loaning Terms and Device Condition Reports

Self-serve device access saves time, but it also raises the bar for clarity and accountability. Teams need a simple way to set expectations before a device is borrowed, and better visibility into issues when that device comes back.

That’s why we’re introducing two new updates in FUYL: Loaning Terms and Conditions and Device Condition Reports. Together, they add a clearer accountability step to checkout and a more reliable issue-reporting step to returns — without changing the self-serve nature of the loaning experience.

If you’ve been following our recent software updates, these new features build on the same goal behind improvements like advanced loan controls and loan plug-in alerts: giving admins more visibility and control over self-serve device workflows.

Loaning Terms and Conditions

Loaning Terms and Conditions gives admins a simple way to present borrowing expectations during checkout. Instead of relying on separate forms or follow-up, teams can require users to acknowledge a custom message before completing a device loan.

Admins can type or paste their own message to reflect local policies, device care guidance, or borrowing expectations. That keeps the experience self-serve for users while giving organizations a more consistent way to communicate expectations at checkout.

Here’s what that looks like in practice:

• • Admins add a custom terms and conditions message to the loan workflow.
  • The message appears during checkout.
  • The user must accept the terms to continue.
  • If the user declines, they can’t proceed with the loan.

Why this matters:

• Clearer accountability: Users see expectations before they complete a loan.
• No extra paperwork: Teams can add a required acknowledgment without adding manual admin steps.
• Flexible for different environments: Schools can reinforce shared-device responsibility, and workplaces can tailor language to internal policies and care standards.

Device Condition Reports

In a self-serve loaning environment, admins do not always get a visual check of devices when they are returned. That can make it harder to catch damage before the next user borrows the same device. Device Condition Reports adds that check to the return process.

Admins can turn on device condition reports for any loan workflow. When a user returns a device, they’ll see an additional screen where they can report a problem, including software-related issues. If an issue is reported, the admin is notified, the device becomes unavailable in the Portal, and the bay light turns yellow to show that the device needs attention.

Admins can then review the device history in the dashboard, investigate what may have happened, and return the device to the loan pool once it’s ready. That gives teams more visibility into returned devices and helps ensure a reported device is reviewed before it can be loaned again.

Here’s what it enables:

• Users can report device issues as part of the return flow.
• Reported devices are automatically made unavailable until they’re reviewed.
• Admins receive a notification and can investigate through the dashboard.
• Device history gives teams more context for follow-up.
• The next borrower is less likely to receive a device that needs attention.

Why this matters: it gives admins a more reliable way to catch issues at return, review what happened, and keep affected devices out of circulation until they are ready to be loaned again.