# data[].attributes.body
is the 1000 item quota right for us?

# data[].attributes.body
48 items currently flagged as requiring more information (i.e. basic information set has not been supplied)

# data[].attributes.body
On-time return percentage is currently 42% (18/31 check-outs returned late). How can we improve this?

# data[].attributes.body
Feedback received from users that boilerplate overdue notices were harshly worded. These have been adjusted and split into two:

1. Check-out overdue by 1 hr: Friendly reminder to user to return item or make contact if they need to extend. Send to user and Cheqroom mailbox.

2. Check-out overdue by 24 hrs: Notice to user to return the item immediately. Send to user, Cheqroom mailbox and technical manager.

# data[].attributes.body
Most of our transactions so far have been check-outs, rather than reservations. We should encourage users to book in advance rather than creating check-outs on their behalf.

# data[].attributes.body
1 Jan - 7 Nov 2023

96 items onboarded, 904 still available

35 registered users, 20 have 'used' the software

6.3 logins per week by 3 users (x̄)

18 reservations recorded with 36 items

31 check-outs converted totalling 69 items

# data[].attributes.body
I've entered 3 new items into CR and invited 2 people to join and loan out items...

# data[].attributes.body
Need to schedule in time to gather the necessary item info to enter into the spreadsheet...

# data[].attributes.body
I've canvassed the most popular items in this lab and come up with 90 individual items and allow for an additional say 50 items I will look to get these into the CR DB over teh summer. Keep this in mind when deciding about how many items we will subscribe for in the following year...

# data[].attributes.body
When I invited a new user to join CR they received a jumbled message...? after they went to forward the message it became legible...??

Perhaps query with the CR team as to why this occurs?

# data[].attributes.body
It is easy to sign in and search.

Equipment is categorized for easy searching.

Developed smart label and storage system

# data[].attributes.body
A software that is very easy to access and search. Developed the instruction that is clear and easy to follow.

# data[].attributes.body
How will Cheqroom inform RATAM?

i.e. items on loan on a certain date that can be added at any inventory take.

# data[].attributes.body
§  Continue the roll-out to include other spaces that haven’t been covered

§  Keep up to date with the upgrades and up and utilise the resource as much as possible.

# data[].attributes.body
It is rather easy to use

Thomas did an excellent job with the date capture for the items that have been added to the system.

# data[].attributes.body
I am not aware of major roadblocks.

# data[].attributes.body
Conceptual development has been good.

Roll-out to some labs has been well executed. It aligns pretty well with the project goals to create visibility, standardising the loan system to create accountability and capturing data that can be used for decision making and procurement purposes.

# data[].attributes.body
Any questions or suggestions for the meeting with Cheqroom? 7 November @ 20:30

# data[].attributes.body
What's next? How will we go about this? Who and when?

# data[].attributes.body
What's the feedback from project team members? Equipment users? Other stakeholders? What are their insights? Any feedback?

# data[].attributes.body
What obstacles and challenges have we encountered so far? Are these likely to recur? Are there any roadblocks that we can see in the future?

# data[].attributes.body
What did these roadblocks teach us? What can be done differently next time?

# data[].attributes.body
What have we done so far? What went well? How did this align with the project aims and outcomes?