Re: Hours worked
 

I log hours volunteered to my company can provide a donation to the team.

Logged approx 175 hours from July-December 2014 running summer workshops, planning training sessions and a preseason build, and running 2x/week training sessions + mock kickoff.

Logged 168 hours from Jan 3 - Feb 13. Will be 40 more hrs Feb 14-17 (208 total). Then at least 2 competitions after that..

So that's approx 400-450 hrs/year

Yep, definitely don't have a life outside of robotics during build season, haha

Re: Hours worked
 

I've been logging my hours for the first time this year, as my new company does verification for the PVSA . Assuming we bag at 9 PM TONIGHT like we plan, I'll have put in 171 hours during the build season. I should easily break 300 hours by the time we hold our end of the year banquet, and probably break 500 hours by the end of the calendar year.

Re: Hours worked
 

Our team does track student time at the build site, though I don't keep the records. We have had six sessions of about six hours and about 15 three hour sessions, plus the 13-hour wrap-up session, for a total of 94 "whole team" sessions, which had an average of about 30 students and six mentors. Programming had a couple of six-hour sessions which had about eight students and one or two mentors. I get something like 3000 hours at the build site. Then there's the out-of-shop thinking, research, engineering, planning, buying, prototyping, programming, and scouting. My estimate is therefore 3946 hours.

Re: Hours worked
 

We either need to automate FIRST or automate our jobs more.
Then we can all marvel at the quality of the time spent instead of the quantity. :)

Re: Hours worked
 

One year when I was doing both FRC and VEX I tracked 1200 hours in a single year. The real killer for time was events, show up at 7AM, leave at 10PM, four/five days in a row.

Re: Hours worked
 

So as team captain, I've only missed 1 day during the six week build season.

Now mind you we met 6 days a week. School week meetings runs from 3-8pm, Saturdays are 9-6pm.

Doing the math, I've put in about 198 Hours minus the day I was not present. Factor in the extra hours this last week and I'm over the 210 mark.

Crazy to think how much time is well spent right?!

Re: Hours worked
 

Looking at all of these posts, I didn't know that clocking in and out was a common thing. I kinda like the idea though. I might talk to a programmer about making a system. Sounds like a good offseason project for them.

I have been doing some rough estimations of hourly contributions with a few other people out of curiosity, and this is what I have come up with. I am CAD subteam captain, and I also worked on Build. Because of college classes, my school, day ends at 1:00. I put in at least 300 hours, possibly up to 320 or 330. There are three other people on my team who put in the same amount of time as me (roughly), a few in the 200-250 range, and around 20 at around 100. Five major mentors, putting in around 180 hours each. A few others putting in around 50-70. So that's between around 4820 and 4400 hours from students, and around a thousand mentor hours. A lot. Of time. Fortunately, my schedule this year features little homework, so I am lucky there.

Re: Hours worked
 

Actually, rather like our scouting, real-time data collection is done on paper for reliability, and entered into a spreadsheet a bit later.

Re: Hours worked
 

hmmmm....the students log their hours, but I don't.

4-8:30 for 30 days = 135 hours

9-3 for 6 days = 36 hours

that's only 170 hours. But we'll make up the difference during the competitions, I'm scheduled to go to five in a row

Re: Hours worked
 

My school has required sport credits and two years ago we got recognized. We require 110 hours to get the credit, but by the end of the build season the core group (including myself) easily surpass 200 hours. It is also easily the best 200 hours spent!

Re: Hours worked
 

I got excited last night when my Google spreadsheet that I've been logging robotics hours with told me a beautiful thing: I've spent exactly (to the nearest half hour) 250 hours at robotics during this build season, which averages out to about 41.67 hours per week.

The final weekend was craziest. 15 hours on Saturday, 18.5 on Sunday, and 14 on Monday for a total of 47.5 on those three days alone.

Re: Hours worked
 

My team of 12 students and 9 mentors logged a total of 1109 hours. 7 of those students qualified to attend regionals by getting 50 hours during build season.

My personal total was 180 hours. I am extremely proud of the result of those hours.

Re: Hours worked
 

We're so small now compared to 10+ years ago (roughly 25 students) so we tend to know who's showing up and who isn't there.

We meet 4 days a week to try and not get burned out too quickly. Sometimes it works against us as we end up working 6 to 7 days a week in Weeks 5 and 6 but this year, we did pretty good with our timelines.

Re: Hours worked
 

Just ran the calculations for myself, I'm somewhere around 250 hours in the shop this build season. Taking a day off then its back to driving practice at 30 hours a week until at least week 6.

Re: Hours worked
 

I remember my senior year (which was the 2013 season), me and a few other members passed 500 hours each by week 7 of competition season. We have a time clock where we clock in/out and my exact number was 504 hours.