My thoughts were having different coloured tags - red for needing induction, green for not needing induction. So it can be identified at a glance.
I just used google the QR code generated for the mock up - but Ruby has new data merge features…but if we’re lucky might include a QR generator - will report back once i’ve had a play
Having it both encoded in the colour and explicitly spelt out gives some redundancy and helps people know that the colours aren’t just a artistic choice 
Had a stab at putting my Graphic Design degree to use:
Key changes:
I think that we should still have the safe system of work signs up like that which @Dorine made for her area, as you should ideally provide a list of start-up, in-use and shut-down procedures for tools next to them, but for smaller tools, these business card sized QR codes would be great.
Anyway, key point here is we should probably setup Shlink to make short URLs possible otherwise we’ll end up having to reprint QR codes if Discourse ever changes it’s URL schema or we want to move to a different CMS.
Looking good! If you want them printed on sticky back vinyl just let me know 
The advantage of having the name of the item (for example Trotec Speedy 300 vs Laser Cutter) is that if there is an issue with the QR code, or if the URL of the tool page changes, the user can still search for the tools page or do further research on the item.
I think there should only be the comments/bottom part if Induction is needed, or if no lone working, or other hazards. So it’s easier to see at a glance if there’s an action needed
Quick note on the URL: there’s an easy way to keep those stable. Looking at the one for tool sharpening for example:
https://discourse.southlondonmakerspace.org/t/wood-tool-sharpening-chisels-and-plane-blades/31592
By default notice how the tool page name is in the URL to make it human readable but can change, then it’s followed by the page ID, which does not change. You can actually get rid of the name and make that link non-human readable, but much more stable:
https://discourse.southlondonmakerspace.org/t/31592
If the page name gets changed, that bottom link should keep working.
Here’s a tweaked version of my mockup taking on the comments
My thoughts on URL - with the name of the item already on the tag a user can go to Discourse (or what ever our future tools are) to search for the item if the QR code fails/URL it links to has changed. What is the likely hood of a user manually typing a URL printed on a 70x40cm (approx) bit of laminate vs searching the name of the tool?
The file is here:
Things to ensure:
The link think you can take or leave, it would require shortening otherwise it won’t work. The point I was making though is that @systems should probably implement this anyway because otherwise if the URL format of Discord changes at all with an update all the QR codes would need replacing in future.
I would emphasise that you need to consider people who don’t know what a “Trotec Speedy 300” is.
Inclusive design and language avoid relying on implicit knowledge like technical names and specs, so I suggested calling it “Laser Cutter”, not “Trotec Speedy 300”, but you could do both:
Think whatever we do would look good lasered on something like this:
My understanding is that the official font of the space is Source San Pro (https://discourse.southlondonmakerspace.org/t/logo-brand-assets/5475) - If that’s changed please let me know as I’ll have to tweak some projects to keep things consistent
Very good point re:having the name of the type of machine the tag is attached to, i’ve added it to my mock up.
I’m going to keep the QR code centred (and as big as possible) as i think to looks better and reduces dead space, specially as i’m trying to avoid making the tags too big.
Personally i prefer the one on the left, i think saying you can do something (in this case Lone Work) is a bit redundant and the tag should only contain ‘stoppers’ to keep the tag glanceable.
I’ll explore how the design lasers on the weekend and report back
Re: Fonts.
I don’t know what the official answer is, if there even is one, but the original font and the one used on the logo full is Dosis.
I worked with some other members to update the brand and create all those templates, and introduced Source Sans Pro for the previous version of the website, but it doesn’t seem like the design scheme I did stuck after I left for a bit.
I am not really sure what the answer is, but the feedback from members at the time was they preferred Dosis as a headline typeface.
Either way, I agree with the point that showing lone working permitted is redundant and could be less clear.
Both of these look good to me.
Kyle’s process is currently a simple script that takes in a list of tools and their details (lone work, induction, names, link) from a csv and pops out all of the tags onto a simple print sheet.
It’s fast, quick, and easy, which means that we will be able to maintain the tags over time, get new ones for new tools, etc. That means that If we want to do one of these formats, I would highly recommend that a script is written that pops the tags out in a similar manner.
Happy to explore building a script once we lock in the design
Looks good to me!
I would suggest putting the text at the bottom in bold, as these labels may fade and it’s important safety information, so should stand out more. But I don’t want to get into a “painting the shed” style discussion.
my 2p:
I like the formatting and content of Martyn’s most recent one, with the logo, bold tool type, not bold tool number, big QR code, then depending on the tool (caution) INDUCTION REQUIRED and/or (x or o with a line through it) NO LONE WORKING. Font choice should be tied to our branding, whatever we choose that to be - looks like there might be something to resolve there.
If we had a script, I think it would make sense to have the option to have it pop out either:
Another thing I’ll add. Some of the tool pages are more process rather than tool related. For example I’m currently building out this page for sharpening, which covers a few tools (tormek, veritas jig, sharpening stones, strop) is different from the sharpening process used for lathe tools, but also uses the Tormek. I’d also like to do one that links to wood shop policies, the basic induction, maybe a few more. Rather than just a qr code tag, my thought was for signage something like this:
Now that I’ve typed this all out, I think this is just a separate project that would be more one-offs, and I’d copy whatever formatting we choose for these tags.
Edit: I think some kind of standardized information plaque would be a good idea to have as well. A lot of the how-to pages should probably have a physical link in the space
As someone with Dyslexia I have to agree with this. I find it much easier to read when its not in caps
Proof of Concept done - looks great and now above the Laser Cutter’s Tool Control.
What do you think?
Throwing in my 2p.
Love how the prototype turned out, especially red on white contrast.
Is it a lot of trouble to put the lone working or not on all signs? It’s easy to assume here in a thread online that people will “just know” that the default unmarked is “yes lone working okay”, but overcommunicating can be very helpful, specifically for newer members. Especially since different people have different personal ideas of fear or danger.
Echoing Neil’s comments re: contrast.
I’ve previously made comments about how some of our safety signage is worryingly low-contrast so I was eager to ensure this wasn’t repeated, but I think the prototype contrast looks really good.
I like Max’s idea of categorising tools of a ‘type’ together for important functions. I’m not sure the correct implementation but I think it’s heading in the right trajectory. Maybe we should generalise it and think about what other categories might exist, and see if looking at the broader picture might lead us to the right answer?
I also think short text URLs are good but discourse.slms.etc.etc/[numbers] is probably too long. slms.to/[numbers] (the same as the full URL) could be sufficient?
I know I don’t have the answers, mainly because these aren’t easy problems to elegantly solve and if they were you’d already have solved them.
Perhaps one additional comment is for us to think about the overlap/alignment between QR codes for ‘work spaces’ and serialisation of the tools that exist within them. For example, I wouldn’t expect a QR code on every hand power tool, but ideally it’d be good to have some unique traceability from tool to maintenance record/any specific info/consumables/etc. The QR code could direct to a list of tools within the work space, for example. For spaces such as the laser cutter where the space is the tool, that’s redundant but the page could include reference to e.g. permitted materials, recommended suppliers, etc.
I think once there’s a consistent and broad effort of capturing this info and having an easy means of retrieving it, it becomes much easier to support newbies by being able to consistently encourage referring to that. Lowering the barrier to tool page access via these QR codes works towards that goal.
I agree - also the lone working warning, being at the bottom of the label, is prone to being obscured or cut off. If there’s always a lone working allowed/prohibited message then we condition people to expect it to be there and verify when it isn’t, rather than assume it’s OK.
