Sunday, July 20, 2008

Sharing Skeds

At WST, our desk schedule is revised almost every day. What about sharing desk schedules using the Google spreadsheet? Imagine the snow falling fast and furious and Chief ****** calling with the news that the libraries will be closed. Firing up the computer before the power goes out, the Branch Manager calls the morning shift with the news.

I know that the kebosh was put on posting the closing on a shared site (aside from our web site), but this would at least make things a bit easier. Perhaps the Meeting Room sked could go on a shared site. And, if branches wanted to be collegial, we could all look at each other's skeds. And dare I say it, perhaps we could even get hq to buy in and learn who's on an 8-4 sked, who's on an 8:30 to 3:30 sked, who's in the building, etc.



3 comments:

Meerkatdon said...

Personally, I think this is a real winning idea.

Oh, there would always have to be a paper copy for those who prefer their information that way, but the shared spreadsheet could be the master schedule.

What we need is a test branch, not too big and not too small, where the whole staff would buy into it. Once they were successful, it could spread slowly.

MAY springs to mind but from what they say about their BM, I rather think not. I know that BCY isn't ready yet....

The EEB said...

I checked my secret decoder ring and agree that MAY's branch manager might not go for the idea. However, HR seems to be able to talk him into anything, so who knows?

hravan said...

Speaking of MAY. . . .

AT just convinced our branch manager to let us do our floor schedule in Excel. Our monthly schedule is in Word, just like at WST (we copied your format) so now both schedules are kept on our common drive. Alas, we can't access them via the web. Its been about 2 years since we went paperless on the monthly schedule and I'm sad to report we still have people who write stuff on the printed-out copy and forget to change it on the electronic copy. . . (big sigh). But everyone says both are easy to read. The next step would be to put them online.

Hmmm, maybe we could link them or embed them in the branch wiki which any of us (most of us, rather) could access from home.