Playbook, bike shop
The part a rider points at is rarely the part making the noise
There are two separate reasons not to diagnose a bicycle in a chat window and only one of them is about safety. The other is that the evidence is bad: a frame transmits sound, so a creak reported at the bottom bracket is as likely to be a saddle rail, a pedal or a dry seatpost, and the rider's own localisation is the least reliable part of the message. Build the material around those two facts and the assistant becomes useful without ever concluding.
Why this is not the general answer
The handling pattern for technical troubleshooting holds across every trade. What follows is the part that does not.
- The rider's account of where a noise comes from is unreliable evidence before any question of safety arises, because a frame carries sound and a creak felt underfoot at the cranks is regularly a saddle rail, a pedal or a seatpost that has dried out.
- The faults divide into two lists rather than along a scale of severity. One list contains things that spoil a ride if the guess is wrong. The other contains things that put somebody on the ground at speed. There is no middle band where a written guess is acceptable.
- Everything on the brakes, the fork, the steerer, the stem, the bars, the frame or a wheel belongs on the second list without exception and without regard to how mild the description sounds, because mild descriptions are exactly how those faults present.
- The specific hazard here is a well stocked library. An assistant given a shelf of maintenance articles will always find something to say, and the article nearest to a described noise is frequently a repair guide for the component that must never be adjusted by the person asking.
How it arrives
- theres a clicking noise when i pedal
- my chain keeps dropping off the front
- something is rubbing every time the wheel goes round
- it wont shift into the biggest sprocket
- the bike creaks when i stand up on the pedals
- should i be worried about a clicking sound
What has to be indexed for this to work
| The two lists, written as lists | What may be described and what may never be, named by component rather than by severity. A list is enforceable and a principle is not, and this is the one document that decides whether the assistant is an asset or a liability in this category. |
|---|---|
| Descriptive maintenance material only, with the instructional kind held back | Index what explains how a system works. Do not index what tells somebody how to adjust it. The distinction is the difference between a rider who understands why a chain drops and a rider with a hex key at a stem bolt. |
| The safe checks, named exactly | A loose bottle cage, a pedal, a saddle bolt, a quick release, a mudguard stay. Listed specifically so that the assistant has somewhere to go other than a repair guide, and cut off deliberately before anything that holds a wheel or a bar in place. |
| Your position on riding with a known fault, written per list | A rider whose chain drops wants to know whether to ride home, and can be told. A rider with a soft lever must be told not to. Writing the two positions separately is what stops one answer being applied to both by an assistant looking for a pattern. |
The reply
Worth knowing before you go hunting for it: a frame carries sound, so a click that feels like it is coming from the cranks very often is not, and riders spend evenings on the wrong end of the bike because of it [1]. The things worth checking yourself are the ones that need no tools and hold nothing important on: a bottle cage bolt, the pedals, the saddle clamp and a mudguard stay touching a tyre [2]. If it is none of those, that is the point to stop rather than the point to start taking things apart, because the next candidates are bearings and they are a stand job. Bring it in and somebody will find it in a few minutes with the bike off the ground.
Leading with the acoustics gives the rider something genuinely useful and explains why their own diagnosis is not trusted, which is more persuasive than a policy about safety. The safe checks are named as a closed list, so there is nothing to extend by analogy. Ending at bearings names the boundary as a technical one rather than a legal one, which is why riders accept it.
Where it stops
The trigger. Any description touching brakes, steering, a fork, a frame, a stem, bars or a wheel, and any noise that survives the published safe checks.
I am not going to guess at a noise, because a bike carries sound and the answer is usually somewhere else on the frame. Bring it in, or leave your name, an email and what it does and when, and the workshop will get back to you.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never name the cause of a noise, because a bicycle carries sound through the frame and the part the rider points at is regularly not the part making it.
- Never talk somebody through adjusting a brake, a headset, a stem bolt, a fork or anything holding a wheel in place.
- Never convert a described symptom into a part that needs replacing, since a rider told they need a bottom bracket buys one, fits it, and arrives having ruled out nothing.
- Never quote a torque figure or a service interval for a safety critical fastener from indexed material, because it belongs to a specific component that nobody here has identified.
Questions
- If it refuses the interesting half, is it worth having at all?
- Yes, because the useful half is genuinely useful. The acoustics point saves people an evening, the safe checks resolve a fair share of clicks outright, and the questions it asks about when the noise happens are the ones the workshop asks anyway.
- Which of our own material should we deliberately withhold?
- Repair guides. A workshop with a good maintenance library naturally wants to index it, and it is the worst possible material here, because the assistant will retrieve the nearest guide to whatever was described and hand somebody instructions for a job that needs a stand.
- People will just search for the answer anyway. Why refuse?
- They will, and it will not carry your name. Advice given on the shop's own site is the shop's advice, and the difference between a rider following the internet and a rider following you is the difference between a bad afternoon and a claim.
Keep reading
- Everything for a bike shopFrame sizing, service turnaround and whether a part fits are the daily questions. Safety critical repair advice is an escalation.
- Handling technical troubleshooting in generalThe dominant failure is an answer taken from the wrong release. A refusal beats a confident step list for software nobody is running.
- Everything that happens before a workshop slot is agreedIt cannot take a slot. It can answer the four questions that come before one and hand over an enquiry ready to schedule.
- Frame cover, component cover and the parts designed to wear outFrames and wearing parts run on different clocks, and a worn chain is not a fault. What can be stated without seeing the bike.
- Standards the shop can state, on a bike it cannot seeFreehub bodies, axle standards and shell widths are facts. What a previous owner changed is not, and that decides it.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.