Posts

QSClock Created Shift – Start and End Time Match Exisitng Shift

This QSClock tutorial details the proper way to use the QSClock Created shift function to Clock in to a shift that a staff is picking up or covering for another staff. We all know how it goes: Staff A calls in “sick” so Staff B gets called in to replace Staff A. Well, when because Staff B has not been previously scheduled in QuickSolvePlus a shift must be created to clock in to. And, if it has the same client and start and end time of the existing scheduled shift/staff a “Shift Exists” prompt will appear and selecting “Yes” to it will prevent a No Clock In notification from triggering for the staff who is being covered for (Staff A, in this example). Another prompt will ask for a Reason as to why this shift is being created and full details can be written here by Staff B as to why they created the shift.

When selecting the appropriate client to create a shift for, the staff will only see the client faces that have the same office designation of the staff. For example, a staff in the North office will not see pictures of clients in the South office. Also, when using the QSClock Created Shift function, staff must be sure to enter the date and time correctly. Go get ’em!

 

/by

QSClock Tutorial: Clocking Out Early

Early Clock Out

Not every shift is created equal. As staff serve clients in the client’s own home, there is often going to be schedule adjustments that happen. Perhaps staff is on shift and they get called to fill in at another home. Or, the next staff comes early to relieve the current staff. Whatever the case, with QSClock, it’s easy to clock out early and indicate the reason why you are clocking out early prior to the scheduled end time in QSP. The end time will then be automatically be updated in your QuickSolvePlus schedule to reflect the time you actually left!

What does QSClock consider as “early”:

Within your company’s QSP settings is the place to customize what time frame QSClock should consider as “early”. When staff clock in or out before this set amount of minutes of when a scheduled shift is supposed to start or end, a notification will trigger and be sent via email to the appropriate office personnel. Not only that, but the actual clocked time will automatically update the scheduled time in QSP! Since the Schedule in QSP drives payroll and billing reports, this accuracy and automation that QSClock provides is extremely beneficial.

/by

QSClock Tutorial: Clocking In Late

Late Clock IN

In the rare event that a staff ever clocks in late to their scheduled QSP shift, the QSClock mobile app will allow them to clock in late, as well as prompt them to provide a reason as to why they are clocking in late. This “reason” is sent as an email to the appropriate office personnel. Once clocked in, the scheduled shift is automatically updated in QuickSolvePlus to reflect the actual late clocked in time!

What does QSClock consider as “late”:

Within your company’s QSP settings is the place to customize what time frame QSClock should consider as “late”. When staff clock in after this set amount of minutes of when a scheduled shift is supposed to start, a notification will trigger and be sent via email to the appropriate office personnel. Not only that, but the actual clocked time will automatically update the scheduled time in QSP! Since the Schedule in QSP drives payroll and billing reports, this accuracy and automation that QSClock provides is extremely beneficial.

/by

QSClock Tutorial: Clocking Out On Time when Leaving Late

Be On Time Clocking Out Late

QSClock provides the choice for users to clock out “on time” to their scheduled shift in QSP whenever they leave late! Now when a field staff departs late, perhaps they forgot to clock out when they left their shift, they have the option to clock out “on time” despite clocking out “late”. Of course, if it’s necessary for them to clock out late, and therefore get paid after their scheduled end time, then they would continue with the late clock out option. To recap, when clocking out late of a scheduled shift staff have two options: Clock out late and update the scheduled end time of the shift, or clock out “late” but choose “on time”, leaving the scheduled end time unchanged. Watch this short video to see QSClock in action.

What does QSClock consider as “late”:

Within your company’s QSP settings is the place to customize what time frame QSClock should consider as “late”. When staff clock in or out after this set amount of minutes of when a scheduled shift is supposed to start or end, a notification will trigger and be sent via email to the appropriate office personnel. Not only that, but the actual clocked time will automatically update the scheduled time in QSP! Since the Schedule in QSP drives payroll and billing reports, this accuracy and automation that QSClock provides is extremely beneficial.

/by

QSClock Tutorial: Clocking In On Time When Early

Be On Time when Clocking In Early

QSClock provides the choice for users to clock in “on time” to their scheduled shift in QSP whenever they arrive early! Now when a field staff shows up early, instead of waiting around to clock in at their scheduled start time, they have the option to clock in “on time” despite arriving early. Of course, if it’s necessary for them to clock in early, and therefore get paid prior to the scheduled start time, then they would continue with the early clock in option. To recap, when arriving early to a scheduled shift staff have two options: Clock in early and change the scheduled start time of your shift, or clock in “early” but choose “on time”, leaving the scheduled start time unchanged. This video details that latter. Enjoy!

What does QSClock consider as “early”:

Within your company’s QSP settings is the place to customize what time frame QSClock should consider as “early”. When staff clock in or out before this set amount of minutes of when a scheduled shift is supposed to start or end, a notification will trigger and be sent via email to the appropriate office personnel. Not only that, but the actual clocked time will automatically update the scheduled time in QSP! Since the Schedule in QSP drives payroll and billing reports, this accuracy and automation that QSClock provides is extremely beneficial.

/by

July 2015 Newsletter – QSP is two, QSP Web Chats, Recent Fixes

Two Years, Too Quick

Leaving our toddler years behind!

It’s true! This month marks two full years in business for us! In July 2013, we sent our first brochure in the mail and made our first calls to communicate to California Service Providers who we were and our solution: QuickSolvePlus! Many of our current customers were on the receiving end then.

We’ve had tremendous growth these last two years, both in our product offerings as well as our business acumen. Did you know that since our inception, over 3,500 QSP users have created over ONE MILLION shifts for over 2,500 clients?!?! Can we do 2 million?

These last 12 months alone we rolled out QSMobile and QSClock for iOS and Android, as well as engineered an SLS OT tool!

We all must learn to walk before we run, and we are eager to continue to earn your complete satisfaction. Thank you for a tremendous first two years!

QSP University

Wait! QSP has a university?! Not technically. But, we do have a complete online Web Chat Curriculum Series that include over 7 hours of video that teach the basics of QSP! (*Diploma not included). You can access it at any time by going here: www.quicksolveplus.com/web-chats

Recent Fixes

  • Previously, when creating an SLS-Shared shift that conflicted/overlapped with another shift with the same staff and client, there was an issue with only part of the shared shift saving, and the linked part that conflicted with the same client and staff would not save. To solve this, any time an SLS-shared shift is created and one of the clients linked to this shift conflicts with the same staff and same client already scheduled, a prompt will alert you that the shift cannot be scheduled. Below is a pic of what the issue looked like from the Worker View, only showing one client initials versus two.

  • Client IHSS NOA History: There was an issue with entries not saving.This has been resolved.
  • QSClock Field Staff Created Shifts: The Split and Validate process has been cleaned up to allow for variations on when data is entered in the process.
  • Scheduler: There was an error message that users were getting when they woudl select multiple days, then unselect all but one day, and then go through the process of creating a shift. This has been resolved.
  • Overlap and Break Reports:  Shift validations for Previous and Next shifts have been added when editing a shift within these reports. Client name is now displayed in this edit shift screen as well.
  • Shifts with Missing Workers: Cancelled shifts were appearing on this report. This is now resolved

Check back for often for more updates!

/by