Guidenor Compass LLC Est. 2026

Every Process Deserves a Clear Direction .

A documentation and knowledge design studio. We turn tangled processes into structured guides, manuals and knowledge systems people actually follow — planned, drafted and delivered remotely.

Remote
Fully collaborative
3 weeks
Studio age, openly
10
Documentation services
Chapter 01    Map Locations

Seven locations we have charted

The studio is three weeks old, so these are sample projects built to show how we plan and structure work — real method, honest labelling. Open a location to see the planning notes behind it.

Planning notes

  • Mapped the first 30 days into four arrival stages
  • Interviewed two managers to find repeated questions
  • Checklist blocks after every chapter

Process diagram

Deliverables

  • Structure map PDF
  • Welcome chapter PDF
  • Day-one checklist PDF

Sample project

Planning notes

  • Category naming based on real support tickets
  • One article template: symptom, cause, steps, related
  • Tone guide for support writers

Process diagram

Deliverables

  • Category tree PDF
  • Article template PDF
  • Tone guide PDF

Sample project

Planning notes

  • Each SOP fits a single printed page
  • Ownership and review date on every document
  • Version log kept beside the collection

Process diagram

Deliverables

  • SOP format PDF
  • Review calendar PDF
  • Version log PDF

Sample project

Planning notes

  • Organised by user goal, not by menu
  • Annotated UI captures for every step
  • Troubleshooting appendix

Process diagram

Deliverables

  • Task index PDF
  • Annotated captures PDF
  • Troubleshooting PDF

Sample project

Planning notes

  • Swimlane diagram per department
  • Handoff points marked explicitly
  • Exception paths documented separately

Process diagram

Deliverables

  • Swimlane diagram PDF
  • Handoff table PDF
  • Exception paths PDF

Sample project

Planning notes

  • Chapters sized to ten-minute sessions
  • Three-question check closes each chapter
  • Facilitator notes in the margin

Process diagram

Deliverables

  • Chapter plan PDF
  • Knowledge checks PDF
  • Facilitator notes PDF

Sample project

Planning notes

  • Weekly, monthly and quarterly routines separated
  • Escalation ladder with named roles
  • Living document, quarterly review

Process diagram

Deliverables

  • Routine calendar PDF
  • Escalation ladder PDF
  • Review ritual PDF

Sample project

Chapter 02 Documentation Philosophy

Good documentation is a route,
not a wall of text.

Idea

STAGE 01

A question arrives: “how does this actually work?”

Research

STAGE 02

We sit with the people who do the work and take notes.

Structure

STAGE 03

The outline comes before a single sentence is written.

Documentation

STAGE 04

Drafting in plain language, with diagrams where words strain.

Testing

STAGE 05

Someone unfamiliar follows the steps. We watch where they pause.

Improvement

STAGE 06

The pauses become edits. The edits become clarity.

Successful Adoption

STAGE 07

The document is used without being explained.

We are a young studio. What we can promise is method, patience, and documents that are still useful six months after we hand them over.

Chapter 03 Navigation Desk

Tell us what needs documenting.

Send the outline of your project and we will reply with a structure proposal, a realistic timeline and a fixed quote — usually within one working day.

Required
Enter a valid email

Your outline is with us. Expect a reply at the address you provided.

Direct lines

Address
4135 Alexandria Pike, Cold Spring, KY 41076

Business hours

Mon – Thu
09:00 — 18:00
Friday
09:00 — 15:00
Sat – Sun
Closed

Eastern Time. Fully remote studio.

Bring these folders

Project brief

Scope, audience, timeline

Existing material

Anything already written

Access notes

Who we should speak with

Chapter 04 The Handbook

Ten chapters of work we take on

Prices are starting points for a well-scoped project. Every quote is confirmed in writing after the outline is agreed — no open-ended billing.

  • A single, self-contained guide with a clear reading order, consistent headings and a layout that survives both screen and print.

    • Outline approval
    • Two revision rounds
    • PDF + editable source
  • Numbered procedures written from the reader's position, with prerequisites stated up front and a check at the end of each sequence.

    • Task breakdown
    • Screenshot annotation
    • Verification steps
  • A full manual organised around what the user is trying to achieve, with a reference section and a troubleshooting appendix.

    • Task index
    • Reference tables
    • Troubleshooting appendix
  • Category architecture, article templates and writing rules so the base stays coherent as more people contribute to it.

    • Category tree
    • Article template
    • Contributor guide
  • Each process drawn as a diagram first, then written out with owners, inputs, outputs and the exceptions nobody usually records.

    • Swimlane diagram
    • Owner map
    • Exception handling
  • A staged arrival path — first day, first week, first month — so a new colleague always knows what comes next.

    • Stage plan
    • Checklists
    • Manager notes
  • Lesson-shaped materials with objectives, worked examples and short checks that fit into real teaching sessions.

    • Learning objectives
    • Worked examples
    • Assessment checks
  • A linked handbook with navigation, cross-references and expandable detail, delivered in Notion, web or interactive PDF.

    • Navigation design
    • Cross-linking
    • Platform setup
  • A consistent SOP format applied across your procedures, with owners, review dates and a version log from day one.

    • Shared format
    • Version log
    • Review schedule
  • A review of what you already have, where it fails readers, and a written plan for fixing it in a sensible order.

    • Documentation audit
    • Priority plan
    • Working session
Chapter 05 Field Notes

What early collaborators say

N 41°
"We had instructions scattered across three tools. Guidenor pulled them into one SOP set with a format we can keep using ourselves."

Marta Ilves

Operations Manager, logistics SME

S 08°
"Clear, patient collaboration. They asked good questions and turned my messy course notes into materials students can follow."

Priya Raman

Educator, vocational training

N 19°
"As a freelancer I needed a client-facing process guide. Delivered on time, priced sensibly, and easy to edit later."

Jess Kowalczyk

Independent designer

E 12°
"The outline they sent before writing was the useful part — it showed they had understood our workflow before touching a document."

Daniel Roth

Co-founder, early-stage SaaS

W 27°
"Our onboarding handbook is short and actually read. Two new hires got through their first week without pinging me constantly."

Tom Verhoeven

Team Lead, software company

E 34°
"They were upfront that the studio is new. The work spoke for itself — organised, careful, no filler text."

Andre Silva

Owner, small retail business

Chapter 06 Knowledge Library

An archive of what we have learned so far

Short pieces on structuring information. Hover a folder to lift it, open it to read the summary.

Chapter 07  ——  Interactive Compass

North — Bearing 000°

Clarity

One idea per section, plain verbs, and no sentence that needs to be read twice.

Chapter 08 Marginalia

Questions, answered plainly

Digital guides, step-by-step instructions, user manuals, knowledge bases, business process guides, onboarding material, educational resources, interactive handbooks and SOP collections. If it explains how something works, it is in scope.

Yes, and it is often the fastest route. We audit what exists, keep what works, restructure what does not, and hand back a consistent set with a plan for maintaining it.

Most of our work is with small teams, founders and independent professionals. Projects are scoped so a single guide or one SOP is a perfectly reasonable place to start.

Typically PDF for reading, plus an editable source — Google Docs, Word, Notion or Markdown — so your team can keep the document current. Other formats on request.

Yes. Flowcharts, swimlane diagrams, annotated screenshots and simple schematics are included where they make a process clearer than prose would.

Entirely remote: a short kickoff call, a written outline for approval, drafts shared for comment, then two revision rounds before final delivery. You always know which stage we are in.