Quick start
Log your first step
Every planChecked against the app on
Logging records that a sample went through a step, with the values you measured, the time and your name. Tap the sample in its batch, fill in the values, then tap the Log button, which carries the step’s name. The history on the sample’s page is the record.
In this guide you will learn how to:
- Open the log sheet for a sample
- Fill in a step’s values
- Log it, or mark the step as failed
- Read the sample’s record afterwards
On this page
Before you start
- You need a registered sample in a batch that follows a published protocol with at least one step.
- If you have not got one, start with register your first sample.
How to log a step
A sample is logged one step at a time, from its log sheet.
Open the batch and tap the sample. The log sheet opens at the sample’s next step, for example Inoculate, with the sample’s ID and Step 1 of 1.
Fill in the values the step asks for. Type 30 in Temperature: the unit, °C, is already there.
If something was off, write it in the note. If the step failed, turn on Failed this step.
Tap Log Inoculate. The button carries the step’s name. A message says Inoculate logged on S-029, and the sample’s row in the batch shows its new step.
To read the record, open the sample from the batch’s list or from Samples. The table below says what it shows.
What is on the log sheet
| Part | What it does |
|---|---|
| Step and ID | Names the step the sample is at, with its ID and how far through the protocol it is, for example Step 1 of 1. |
| Values | What the step asks you to record. The unit is already there. |
| Note | For anything that was off. |
| Failed this step | Turn it on when the step did not pass. It is under the note. |
| Log button | Carries the step’s name, for example Log Inoculate. |
What does a sample’s record show?
| Part | What it shows |
|---|---|
| Step | The step the sample is at. |
| Recorded values | The values logged so far, for example Temperature 30 °C. |
| Belongs to | The project, protocol and batch the sample is in. |
| History | A button at the bottom left, with the number of entries. The newest entry is first. |
What gets recorded
- Every entry carries a time and your name.
- The history is listed newest first.
- An entry can be removed, never edited. That is why the history on a sample’s page is the record, and why a status that someone overwrites is not.
For the thinking behind it, read how to keep track of lab samples.
Common questions
- Where do I read a sample’s history?
- Open the sample and tap the history button at the bottom left. Its badge shows how many entries there are, and the newest is first.
- Can I correct a mistake in a log entry?
- An entry can be removed but never edited, so the history stays trustworthy.
- What does Failed this step do?
- Turn it on when the step did not pass. It is on the log sheet, under the note.
What to do next
- How tinysamples is organisedHow the pieces of tinysamples fit together: a lab holds projects, a project holds protocols and batches, a batch holds samples, and every step logged becomes an entry in a sample’s history.
- What tinysamples does not doThe honest list of what tinysamples does not do: no notebook, no regulated-environment features, no freezer map, no parent link between aliquots, no API, and what to use instead.
Was this helpful?
Summarize with AI
Still stuck? Email support@tinysamples.com. It goes to Sunayda and Alvee.