Document Control is where your shop’s written procedures, work instructions, forms, and specs live under version control. Think of it as a wiki, but with revision history, review dates, and a clear record of who approved what.

How to get there #

Menu: Quality → Document Control
Direct URL pattern: https://yourdomain.com/?bizRt=quality/docs/manager

What belongs under document control #

• SOPs (Standard Operating Procedures) — “how we receive a shipment”, “how we do a PDI”, “how we close the shop”.
• Work Instructions — task-level: “how to build a Gravel Custom per the Ridgeline build sheet”.
• Forms & Checklists — PDI checklist, service check-in form, audit checklists.
• Specifications — torque specs, compatibility matrices, internal part number conventions.
• Policies — return policy, warranty policy, employee handbook.
• Quality Manual (if you run a formal QMS) — the top-level document.

What doesn’t belong here #

Invoices, bills, customer correspondence, and transactional records belong on the transaction records themselves. Document Control is for how the shop operates, not what the shop did on a given day.

Document fields #

Field	Meaning
Document Number	A unique ID like SOP-001, WI-014, FRM-003.
Title	Human-readable title.
Type	SOP, Work Instruction, Form, Spec, Policy, Manual.
Owner	The role or person accountable for keeping the document current.
Version	Semantic revision (1.0, 1.1, 2.0).
Status	Draft, Under Review, Approved, Superseded, Retired.
Approved By / Approved Date	Who signed off and when.
Next Review Date	When this doc must be re-reviewed (default 12 months).
Applies To	Department, role, or process the doc governs.

Creating a document #

1. Click New.
2. Assign a Document Number from your numbering convention.
3. Pick the Type and set Status to Draft.
4. Write or paste the content. A simple rich-text editor is available; or attach a PDF/DOCX if the document is an existing file.
5. Set the Owner.
6. Save as Draft.

Review and approval #

1. Move status to Under Review. Assign reviewer(s).
2. Reviewers add comments and request changes.
3. Owner incorporates feedback and re-circulates as needed.
4. When reviewed, assign an Approver.
5. Approver sets status to Approved. Bizuno stamps name and date, and increments version if this is a revision.
6. The new version becomes the current “in force” document; the prior version is retained with status Superseded.

Important: Only one version of a document is “Approved — In Force” at a time. Superseded versions stay accessible in history so you can always see what the procedure said on any past date — essential when investigating an old NC or customer complaint.

Version bumps #

• Minor (1.0 → 1.1): clarifications, typo fixes, formatting.
• Major (1.1 → 2.0): material process change. Requires re-training and acknowledgement.

Linking documents to work #

• Audit checklists in the Audit module reference the source document so the auditor opens the current version.
• Training records can require a specific document version to be read and acknowledged.
• CAPA action steps often include “update SOP-XYZ to reflect new procedure” — close the loop by linking the updated doc back to the CAPA.

Review cycle & expiration #

Each approved document has a Next Review Date (default 12 months). The dashboard widget flags documents within 60 days of expiration. At review:

• If unchanged, bump the review date without creating a new version.
• If changed, draft a new version and run the approval cycle.

Starter document set for Ridgeline Cycles #

• SOP-001 Receiving & Incoming Inspection
• SOP-002 Pre-Delivery Inspection (new bike PDI)
• SOP-003 Service Work Order Intake
• SOP-004 End-of-Day Close-Out
• WI-001 Shimano Torque Spec Reference
• WI-002 Tubeless Setup Procedure
• FRM-001 PDI Checklist
• FRM-002 Service Intake Form
• POL-001 Warranty & Returns Policy (customer-facing)
• POL-002 Shop Safety Policy

Tips for Ridgeline Cycles #

• Keep SOPs short. One page per SOP. If it’s longer, it’s a training document, not an operating procedure.
• Put the version number and approval date on every printed form so you can spot a stale checklist on the service bench.
• Don’t copy a procedure from a ISO-9001 manual verbatim; write it in the voice of your shop. People follow what they understand.
• Schedule the annual review cycle in batches — a “document review week” once a year beats one-off nagging reminders.

Where to go next #

• Training Records — assign employees to read and acknowledge new SOP versions.
• Audits — audit against the current approved version.
• Corrective Actions — process changes flow back into updated documents.