--- id: v4-capture-an-assessment slug: capture-an-assessment sequence: 5 title: "Capture an assessment" url: https://etiscope.com/support/guide/capture-an-assessment/ video_state: unbuilt --- # 5. Capture an assessment The recording itself. It takes about five minutes of screen work, and there's one thing to keep in mind throughout: check your capture before you leave site, because it can't be fixed afterwards. **Before this lesson:** 3. Prepare the kit, sensors and app (https://etiscope.com/support/guide/prepare-kit-sensors-app/); 4. Plan and create an assessment (https://etiscope.com/support/guide/plan-and-create-an-assessment/) ## What you'll be able to do The learner can take an uncaptured assessment to a saved capture they have checked, and can state when to redo one. - [check-before-recording] Check all five sensors are connected and frame the camera on the whole task before recording anything. - [normalise-and-clear-warnings] Normalise the worker's neutral posture before every capture, tell normalising apart from calibration, and respond to each pre-flight warning the app raises. - [record-a-representative-capture] Record enough of the task to represent how it is actually done, and use Pause and Resume for an interruption rather than Cancel. - [stop-save-and-recover] Stop and save the capture, and let the app download data from any sensor that lost connection during the recording. - [review-and-accept-or-redo] Review the capture against the graphs before anyone removes a sensor, and decide on site whether to accept it or redo it. ## Video This lesson's video has not been filmed yet. The written lesson below is complete. ## The lesson ### Before you record Before anything is fitted or recorded, **your organisation's own briefing and consent process with the worker comes first**. Your organisation sets that process, so follow it as you normally would. Then open the assessment you created. Because it hasn't been captured yet, it opens straight onto the capture screen. The capture screen has three regions, and you'll use all of them. The live camera view fills most of it. A row shows the connection status of each sensor. Three graphs — neck, back and arms — sit ready to move. Check the sensor row first. **All five sensors need to show as connected.** A sensor that is flat, out of range or still in the case is easier to fix now than after the worker has performed the task. Then position the device so the camera sees the whole task — the worker, the load, and the equipment they use. The video is the evidence you'll scrub against the graphs when a score needs explaining, so a frame that cuts off the pallet cuts off half the answer. > **On screen** — Live camera view · Sensor connection status · Neck, back and arms graphs ### Normalise Every capture starts by normalising. Normalising records the worker's neutral posture, and every movement in the capture is measured against it. It's the zero point, so if it isn't done properly, the assessment won't be valid. Ask the worker to stand naturally: upright, arms relaxed at their sides, looking straight ahead. When they're still, select **Normalise**. The app streams for a few seconds, then sets their resting posture. If something is wrong, the app stops you here so you don't record unusable data. **Sensors not connected** or **Sensors aren't assigned** sends you back to the **Sensors** tab. A low battery warning lists each sensor and its charge — you can go back, or continue if the charge will last the capture. **Invalid sensor placement** means a sensor isn't sitting correctly: refit it, and normalise again. If the worker was mid-movement, or a sensor was loose, normalise again. It only takes a few seconds. > **Definition** — Normalise: the worker's neutral posture, before every capture. Calibrate: sensor maintenance, rarely. > **On screen** — Sensors not connected · Sensors aren't assigned · Low battery · Invalid sensor placement > **Watch out** — Worker moving or a sensor loose? Normalise again. ### Record Select **Start**. The graphs begin to move with the worker, and the elapsed time runs at the top. Let the worker perform the task as they normally would. **Your role is to observe and keep the camera on the work**, rather than to direct, correct or improve what you're seeing. If someone does the job extra carefully because they're being filmed, the capture shows a version of the task nobody actually performs. Record enough of the task to represent how it is actually done. If the task repeats, a few full cycles is usually enough — you don't need to capture a long task from start to finish. > **Definition** — At least ten seconds; a few full cycles of a repeating task If the work is interrupted, use **Pause**, and **Resume** when it restarts. **Cancel** discards the capture, so the app asks you to confirm first. The two buttons sit close together and do very different things, so take a moment before you tap. > **On screen** — Start · Pause · Resume · Cancel · Stop & save ### Stop, save and recover When the task is done, select **Stop & save**. The app writes the capture to the assessment. If any sensor lost connection while you recorded, the app opens **Downloading data from sensors** automatically and pulls the missing data straight from the sensor's own memory — the sensors record locally as well as streaming, so a dropout during the task is usually recoverable rather than fatal. Keep the sensors near the device until it finishes, and choose **Retry** if it asks. Stay with the device until this step is done. > **Definition** — On screen: Downloading data from sensors ### Check your capture **Before anyone removes a sensor**, open the assessment and review it. This is the last moment a redo is quick. Play the video. Check the graphs moved when the worker moved, and that the whole task is inside the capture. This is a quick sanity check rather than an analysis. Three questions cover it, and they're the same three every time. > **On screen** — Breaks in the data? · Graphs jumping? · Graphs match the video? If any of those look wrong — or the task wasn't done the way it normally is — redo the capture now, while you're still on site. Re-fitting five sensors and asking for one more cycle takes a few minutes, whereas coming back next week means rescheduling, and that often doesn't happen. A good capture, saved and checked. Next, you'll add the information the sensors can't know. > **Watch out** — Redo it now, on site: a bad capture can't be fixed later ## Mistakes that matter - Skipping or rushing normalise. It can feel like a formality, but it's the measurement's zero point. - Accepting a capture without reviewing it. Nothing later in the workflow can tell a bad capture from a bad task. - Tapping cancel when you meant pause. Cancel discards the data, and the confirmation dialog is your last chance to keep a long capture. ## Not covered here - Fitting the sensors and assigning them to body locations — see lesson 3, Prepare the kit, sensors and app (https://etiscope.com/support/guide/prepare-kit-sensors-app/) - The extra information sheet — duration, repeats, perceived load — see lesson 6, Complete the record: Extra Information (https://etiscope.com/support/guide/complete-the-record/) - Interpreting the score the capture produces — see lesson 7, Read the results and choose the right report (https://etiscope.com/support/guide/read-results-and-reports/) - Worker briefing and consent, which follow your organisation's own procedure **Next lesson:** 6. Complete the record: Extra Information — https://etiscope.com/support/guide/complete-the-record/