What kind of data do you record as part of your shop operations? Right now we use a somewhat abused set of spreadsheets to track our pertinent info, but I&#39;m in the process of creating a more task-specific database (a web app) to handle it all better. Here is what we track now:<div>
<br></div><div>- Volunteer hours (to add volunteer sweat equity credit to  volunteers&#39; records)</div><div>- Sweat equity used (to subtract credit for purchase of bikes, parts, stand time)</div><div>- Bike sales: Bike ID, how it was paid (cash/equity), how it will be used</div>
<div><br></div><div>Our cash &amp; credit sales are tracked independently on a POS/register.</div><div><br></div><div>Right now that is all done on paper, then later entered into the spreadsheets. It&#39;s kind of a cumbersome process, but visitors are comfortable with a paper sign-in sheet, and volunteers are comfortable with a spreadsheet (vs. a database). </div>
<div><br></div><div>We don&#39;t track overall number of shop visitors (although we do hang on to our paper sign-in sheets), or gross volume of stand time provided. While we have contact info for all visitors on a waiver they fill out the first time they come in the shop, we would probably have a difficult time if we needed to quickly find an emergency contact for someone, since they are all just on paper right now. I&#39;d like to integrate that all together into the database.</div>
<div><br></div><div>Since I&#39;m writing this front desk app, I thought I&#39;d ping the community to see if these are common needs, or if there are other common needs that I could consider as I develop it. I&#39;d love for it to be useful enough to offer to the broader community at some point.</div>
<div><br></div><div>-Andy </div><div>Broke Spoke Community Bike Shop</div><div>Lexington, KY</div><div><br></div><div><br></div>