Ask once.Find it
forever.

Selvian is a knowledge base and team wiki for small businesses. Write down how things are done here, from closing up to what to do when an alarm goes off, and anyone on the team can find it in seconds.

Plans are prepared on request for each team.

Example: searching “how do we close on Sundays” returns the page “Closing the shop on Sundays” with the matching passage marked.

Interface preview · demo data

q: before

The answers exist.Just not anywhereyou can search.

In most small teams, the way things are done lives in someone’s head, a group chat from last spring, or a binder by the back door. Every new question becomes an interruption, and every departure takes a little of it away.

  1. alarm code for the side entranceIn Sam’s head0 results1 page
  2. how long to keep delivery notesA chat thread, somewhere in March0 results1 page
  3. reset the walk-in thermostatBinder, back office, page torn0 results1 page
  4. who signs off on holiday rota swapsDepends who you ask0 results1 page
  5. set up the label printerThe person who knew has left0 results1 page

The same five questions, once each is written down in Selvian.

q: one page

One page,linked to everythingit touches.

A Selvian page has an owner, a date to review it by, and steps anyone can follow. Link to other pages as you write, and each page shows what links to it, so the freezer log knows which procedures depend on it.

Front of house › Closing

Closing the shop on Sundays

Owner Dana R., Shift leadReview by Jan 12
  1. 1At 5:30, put the “closing soon” sign out and stop seating walk-ins.
  2. 2Fill in the Fridge & freezer log with both readings.
  3. 3Lock the loading door; the key goes back as described in Keys & alarms.
  4. 4Switch off and rinse the espresso machine, following Nightly machine clean.
  5. 5Leave a note on the Shift handover page for Monday’s opener.
  • KitchenFridge & freezer log4 pages link here
  • BuildingKeys & alarms6 pages link here
  • Front of houseNightly machine clean2 pages link here
  • TeamShift handover9 pages link here
  • KitchenWho to call: emergencieslinked from Keys & alarms

Threads are page links. Each page lists the pages that point to it.

Interface preview · demo data

Interface preview · demo data

q: review by

Pages that say when they need a second look.

Every page carries an owner and a review-by date. When the date passes, the page is marked for review and its owner is reminded, so nobody follows last year’s steps by accident.

  1. ReviewedMar 4 · Ken M.
  2. Review bySep 4
  3. Marked for reviewSep 5 · owner reminded
  4. Reviewed againSep 9 · two lines updated
q: first week

A reading listfor day one.

Put together the pages a new starter should read, in the order that makes sense for the job. They work through it at their own pace; you see which pages they have opened.

q: what changed

Every edit kept.Every change visible.

Selvian keeps a version each time a page is saved. Put two versions side by side to see exactly which words changed, who changed them and when, and bring back an earlier one if an edit went wrong.

Interface preview · demo data

q: who can edit

Everyone reads.The right people edit.

Set read or edit rights by role, space by space. Floor staff see the procedures they need, shift leads keep them current, and owners decide who belongs where. Anyone who can read a page can leave a comment on it.

View as

Can read · can comment

Viewing as Floor staff: Can read · can comment.

Interface preview · demo data

q: define team

Made for teams that workin shifts, sites and rooms.

kitchen/ˈkɪtʃ.ən/noun
Where the allergen sheet, the fridge log and the closing routine should never depend on someone’s memory.
front desk/frʌnt dɛsk/noun
The same handful of visitor questions, answered by a different person every few months.
warehouse/ˈwɛər.haʊs/noun
Loading-door routines, who signs for what, and the steps for when the label printer jams.
field crew/fiːld kruː/noun
Instructions that need to be right on a phone, in a van, before eight in the morning.
back office/bæk ˈɒf.ɪs/noun
Supplier contacts, house policies and the documents everyone asks for twice a year.
second site/ˈsɛk.ənd saɪt/noun
The moment “how we do it” has to be written down, because you can no longer just show people.
q: everything

What’s insidea workspace.

Every feature in detail →
Features of a Selvian workspace
Full-text searchSearches page titles and page text across every space you can read.freezer alarm
SpacesOne area per team or site, each with its own pages and its own access.Kitchen · Front of house · Warehouse
Links between pagesLink pages as you write; every page lists the pages that point to it.Keys & alarms ← 6 pages
Page templatesStart procedures, checklists and contact sheets from a shared layout.New page from “Checklist”
Version historyEach saved change, with who made it and when, and a way back.v15 · today · Sam K.
Owner and review-by dateA named person per page and a date to check it again.Ken M. · review by Sep 4
Onboarding pathsOrdered reading lists for new starters.Week one: floor team · 6 pages
Read and edit rightsAccess set by role, for each space.Floor staff: read
CommentsQuestions and suggestions on the page itself, where the next reader sees them.“Before or after the lights?”

Example in the right-hand column: what you would type or see.

q: start

Three levels. That is the whole setup.

  1. Workspace

    1Tell us about your team. We prepare your plan and open a workspace with your first owner account.

  2. Space

    2Create a space for each team or site, and choose which roles can read it and which can edit it.

  3. Page

    3Write or paste your procedures, or start from a template. Give each page an owner and a review-by date, then invite the team.

q: data

Data and security

where is our data and who can see it

5 results · from this website and our legal pages

  1. 1

    Security › Infrastructure

    Hosting

    Selvian runs on infrastructure operated by a professional hosting provider. The list of our technical service providers is available on request.

  2. 2

    Security › Access

    Connections

    Traffic to this site and to the service is encrypted in transit (HTTPS). Reaching a workspace requires signing in.

  3. 3

    Legal › Data processing

    Who owns your pages

    Your content stays yours. We process it only to provide the service, under our Data Processing Agreement.

  4. 4

    Workspace › Roles

    Inside your team

    Read and edit rights by role and space. Version history shows who changed what, and when.

  5. 5

    Legal › Cancellation

    When you leave

    Ask us for a copy of your workspace content before your subscription ends; it is then deleted as set out in our terms.

Plans are shapedaround your team.

Opens your email app, addressed to contact@selvianllc.com.

There is no price list on this site. Tell us how many people and how many sites you have, and we will come back with a plan and a quote for your subscription.

Contact pageHow plans work