Ferrow
Book a demo

For crews and support agents

Every closed job updates the runbook.

When a crew closes a job, Ferrow writes what they learned into the runbook page that job used. The next crew opens that page and gets the fix that worked yesterday, with a link to the job behind it.

Book a demo Watch a page update
Living record A piece of work slides into a record cabinet, a write head climbs to the file it changes and rewrites it; then the next piece of work arrives and rewrites another file.

Reads closed work from

  • Work orders
  • Tickets
  • Delivery logs

Updates

  • Runbook pages

01The problem

Your best tech fixed it last month. The runbook still says the old way.

Data warehouse Rows of data drop through a funnel onto a chart base, and its bars rise one by one.

01The dashboard.

Counts the jobs. Misses how they got done.

It shows how many jobs closed and how fast. The trick a senior tech used on site never turns into a number.

  • Job counts
  • SLAs
  • Reports
Seats Three desk terminals stand on a bench that only carries power. A note card slides into one of them and its screen writes the note out while the other two stay empty; then the screen clears and the card slides back out.

02Notes per person.

Good fixes stay on one screen.

Each tech keeps their own notes on a phone or laptop. When that person is off shift, so is the fix.

  • Notes apps
  • Phones
  • Group chats
Snapshot A file cabinet and an index box stand on one base. A new page goes into a drawer of the cabinet, and the index, still holding its old copy, shows a cross until a fresh copy rides the rail into it and its check comes back.

03The search copy.

Searches a copy saved in March.

Search tools answer from a saved copy of the manual. Until someone refreshes it, crews get last quarter's steps.

  • PDF manuals
  • Shared drives
  • Search

02How pages update

The page changes when the job closes. Not when someone gets round to it.

Each runbook page is a plain file. A closed job edits the page it used, the old version stays on file, and the edit carries the job number.

When each runbook page last changed, in a saved search copy and in Ferrow
Page Search copyBehindSaved once, then left alone. FerrowLiveEdited by the last job that used it.
boiler-reset.mdMar 20261s ago
router-swap.mdMar 20264s ago
refund-steps.mdMar 20267s ago
cold-chain-check.mdMar 202610s ago
returns-dock.mdMar 202613s ago
Pages with the latest fix 44% 96%

03Sources

Every step names the job it came from.

Tap a source to see the work order, ticket or parts entry behind a step, who closed it and when. Crews follow a step faster when they can check it.

Ask FerrowJob 4471

Unit 12 at the Harbor Road site keeps tripping. What do we try first?

Clear the condensate drain before you touch the board. The north crew moved this step to the top in May, after three repeat visits where the board was fine.

Sources

/notes/drain-before-board.md

Closed by
North crew
When
14 May

04Setup

Connect your job records once. Every new team starts from there.

Ferrow finds your work orders and tickets, strips out duplicates and test jobs, and clears who may read what. Add a second team or a new region and that work is already done.

Data foundation A block of data rides a rail through three stations in a line: find, clean and clear. The check on each station lights in turn as it comes through, and the data leaves ready on the far side.

05Access

Each person sees the pages their job needs.

A dispatcher can open customer records. Nobody in the field can open HR files. Ferrow checks every request, from a person or a bot, against the scope you set.

Read how access works
Scoped access Requests ride up to a gate in a wall; a scope plate beside it lets a request for CRM files through the opening and drops a request for HR files into a box below.

  • Scopes per role

    Set once what techs, agents and drivers may read or edit. Bots get the same rules.

  • A log you can export

    See who opened or changed a page, and which job made the change.

  • Undo any edit

    Old versions stay on file, so a bad change rolls back in one click.

06Teams

Where crews put it to work.

Runbook update A bell rings as a fix is found, and a new runbook page lands on the screen of a crew tablet standing in its dock.

Fix it on the first visit.

A tech finds the real cause on a repeat call and closes the job. Ferrow adds the step to that unit's page, and the next crew sees it on the tablet before they leave the yard.

Support desk Support tickets line up on a belt, and the answer desk takes the next one in as the line moves up.

Answer with the current fix.

Tickets come in one after another. Each agent opens the page for the issue and sees the fix that closed the last ticket like it, with a link to that ticket.

Depot routing A hub sits where four lanes meet. Each parcel slides onto its turntable, gets a check, and is turned to face the lane of the right depot, then slides into that depot.

Send it to the right depot.

When one depot finds a faster way to sort returns or load a van, a driver logs it on the run. Ferrow puts it on that depot's page, and every hub that sends parcels there works from the same steps.

Try it with one crew for 30 days.

Start a pilot Book a demo