Product · Service requests

Requests from the labs, nowhere to get lost.

In Streamcell each service request becomes a record that moves through your steps: Submitted, Accepted, In progress, Done. Facility staff see the open requests on one board, and the workflow emails the lab that asked as the request moves, until the lab accepts the finished work.

Who it's for
Facility managers, core facilities, the labs they serve
Records
Service request, husbandry task, animal transfer request, billing change request
Links to
The SoftMouse animals the request is about

01Why do vivarium service requests get lost?

Why do vivarium service requests get lost?

Because they arrive by email, PDF and phone, and nobody's list holds all of them.

Of 15 facilities whose procedures we read, 5 take requests on a web form and 5 by a PDF or an email, and we found 7 ways the work is passed on. When a request lives in one person's inbox, the lab has to chase it. In Streamcell the request is a record the whole team can see.

02How does a request move from the lab to done?

How does a request move from the lab to done?

The lab fills in one form, and the workflow tells the next person what to do.

  1. Submitted

    The lab asks on a form your team built, with the protocol and the animals on it.

  2. Accepted

    Facility staff take it on, and the lab is emailed that it is in hand.

  3. In progress

    The work runs as tasks, with the hours recorded against the request.

  4. Done and accepted

    A completion report goes to the person who asked, who accepts the finished request.

You choose who hears about each step and write what they read. Cores that already keep their colonies in SoftMouse can link each request to the animals.

Last reviewed

Built around your facility

Give every request a place to go

A demo follows one request from the lab's form to the finished work and the lab's sign-off.

Book a demo