
Maccauvlei Golf Club
Vereeniging, 06
Vereeniging, 06
Score
42
Net Score
35
Avg Putts
2.0
GIR
13%
Holes | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | Out | |
---|---|---|---|---|---|---|---|---|---|---|---|
Black Tees (yds) | 375 | 505 | 315 | 389 | 197 | 355 | 485 | 150 | 417 | 3188 | |
Handicap | 5 | 13 | 17 | 3 | 11 | 7 | 15 | 9 | 1 | ||
Par | 4 | 5 | 4 | 4 | 3 | 4 | 5 | 3 | 4 | 36 | |
Score | 5 | 7 | 4 | 5 | 5 | 5 | 7 | 4 | NA | 42 | |
Putts | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | NA | 16 | |
Fairway Hit | NA | 100% | |||||||||
Approach | NA | 17% | |||||||||
GIR | NA | 13% | |||||||||
Hole | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | In | Total |
Black Tees (yds) | 342 | 413 | 357 | 374 | 149 | 497 | 145 | 397 | 426 | 3100 | 6288 |
Handicap: | 6 | 2 | 10 | 8 | 14 | 12 | 16 | 4 | 18 | ||
Par | 4 | 4 | 4 | 4 | 3 | 5 | 3 | 4 | 5 | 36 | 72 |
Score | NA | NA | NA | NA | NA | NA | NA | NA | NA | 0 | 42 |
Putts | NA | NA | NA | NA | NA | NA | NA | NA | NA | 0 | 16 |
Fairway Hit | NA | NA | NA | NA | NA | NA | NA | NA | NA | 0% | 100% |
Approach | NA | NA | NA | NA | NA | NA | NA | NA | NA | 0% | 17% |
GIR | NA | NA | NA | NA | NA | NA | NA | NA | NA | 0% | 13% |
- 5
- 7
- 4
- 5
- 5
- 5
- 7
- 4
Comments
-
thiefcrazy98
Hi everyone! I was wondering: we at the company are thinking about implementing a system to optimize shift scheduling. And then I came across Shifton. What do you think, does anyone use this platform for automatic shift scheduling? How much should you rely on an automatic process? Are there any problems when you need to suddenly change the schedule, for example, if someone gets sick or asks to change a day? Did you like the flexibility of the system in such situations, or do you always have to intervene manually? I would love to hear your opinions!Mar 20th, 7:01 am -
EvanDuke
We started using https://shifton.com/shift-scheduling a couple of months ago, and I can tell you how it works for us. The system is definitely effective for creating schedules, especially when you have a large team or constant scheduling requirements. The main feature is that the schedule generator for employees can automatically take into account all parameters - working hours, employee wishes by day, shift features (for example, someone can only work in the morning, and someone only in the evening). This really speeds up the process and reduces the number of errors that usually occur when manually creating schedules. The system also helps to avoid overloading employees, because it automatically distributes working hours so that they do not exceed the permissible limit. However, it is worth understanding that despite all the automation, you can’t always rely on it 100%. For example, we have several people on our team with special wishes - one cannot work night shifts, another does not go to work on certain days because of school, and a third can sometimes change shifts at the last minute. And here is where the system sometimes fails to cope. If we did not have time to update all the data in advance, for example, someone did not indicate that they cannot work on this day, then Shifton can assign them to a shift that does not suit them. In such cases, you have to intervene manually to adjust the schedule.Mar 20th, 1:20 pm -
Tobias
I agree with you that automation is cool, but it is still not ideal. We also use Shifton, and despite the convenience of automatic planning, it happens that the system does not have time to take into account all the changes in time. This is especially noticeable when urgent adjustments appear in the schedule or if an employee falls ill right before the shift. In my opinion, it is important to combine automatic planning with manual edits, otherwise errors may occur.Mar 21st, 5:15 am
Round Comments:
No comment entered.