--- id: v5-complete-the-record slug: complete-the-record sequence: 6 title: "Complete the record: Extra Information" url: https://etiscope.com/support/guide/complete-the-record/ video_state: draft video_duration_seconds: 181.696 video_url: https://media-etiscope.jointaction.cloud/lessons/complete-the-record/0c70ca17a62edffc71b8edaef0a815bb2fe815ca55ebd9de37e167739d2a126f/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/complete-the-record/0c70ca17a62edffc71b8edaef0a815bb2fe815ca55ebd9de37e167739d2a126f/captions.vtt --- # 6. Complete the record: Extra Information Think of this as a conversation with the worker rather than a form. Four of their answers can move the score more than anything else on this sheet, and because every field is optional, it helps to know what leaving one blank means for the score. **Before this lesson:** 5. Capture an assessment (https://etiscope.com/support/guide/capture-an-assessment/) ## What you'll be able to do The learner can elicit and enter duration, repeats, perceived load and exposure from the worker, judge when the detailed factors and description are worth the minutes, and know that every field is optional but the score is only as defensible as what's entered. - [state-optionality-and-stakes] State that no field in Extra Information is mandatory, and that the score is only as defensible as the inputs behind it. - [elicit-duration-and-repeats] Elicit and enter a task's real continuous duration and how many times it repeats in a shift, not the whole-shift answer. - [elicit-load-and-exposure] Elicit the worker's perceived load and set the exposure it unlocks, without mistaking handled weight for a scored input. - [judge-detail-description-and-save] Judge when the detailed factors and description are worth completing, leave the unknown unknown, and save to trigger the recalculation. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/complete-the-record/0c70ca17a62edffc71b8edaef0a815bb2fe815ca55ebd9de37e167739d2a126f/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/complete-the-record/0c70ca17a62edffc71b8edaef0a815bb2fe815ca55ebd9de37e167739d2a126f/captions.vtt - YouTube (secondary): https://www.youtube.com/watch?v=hj0cew5uqDA **Chapters:** 0:00 Why these inputs exist · 0:34 Duration and repeats — the interview · 1:16 Perceived load and exposure · 1:47 The detailed factors · 2:22 Description · 2:46 Save — and what saving does ## The lesson ### Why these inputs exist The sensors measured the movement. What they can't know is how long the task runs across a shift, how often it repeats, or how heavy the load feels to the person doing it. Those answers come from people, and they change the score. A movement performed twice a shift and the same movement performed sixty times are very different exposures, and no accelerometer can tell them apart from a ninety-second capture. Open **Report actions**, then **Add extra information**. **Nothing in this sheet is mandatory.** Every field starts at **None** or **No adjustment**, and the assessment will score without them. What matters most here is honesty: fill in what you can find out, leave the rest as it is, and remember that the score is only as defensible as what's behind it. > **On screen** — Tabs: Extra info · Manual input · Detailed data · Description. Which you see depends on your plan and the assessment type. ### Duration and repeats — the interview Start with **Full task duration**. Ask the worker how long they do this task, and don't be surprised if the answer is "all day". That usually describes the whole shift rather than the task, and it's the answer that most often needs a follow-up question. The question that usually gets the real answer is: **how long do you do this continuously, without a break to do something else?** The app counts the task as continuous across gaps of under a minute, so a worker who pauses to reposition a pallet is still doing the task. Enter that continuous duration. Then **Task repeats per shift**: how many times that continuous run happens in a shift. Together, duration and repeats tell the score how much of the day this movement fills. That's why they're the two most worth getting right, and why they deserve a proper conversation with the worker rather than a quick estimate afterwards. > **Definition** — Full task duration: No adjustment, then 1–120 minutes > **Definition** — Task repeats per shift: 1× to 80× ### Perceived load and exposure **Perceived load** is how heavy the handling feels to the worker: light, medium, or heavy. Ask them. **It's their perception rather than a measurement**, and that's intentional — the same twelve-kilogram carton is a different load at the end of a shift, at height, or held away from the body. Once you set a load above **None**, the **Exposure** field appears, asking a second question: for how much of the task duration is that load being handled? A worker carrying for the whole task and a worker carrying for the last tenth of it face very different demands. **Handled weight** is a different field and behaves differently. You can record the actual weight for reference, and the caption on the field explains that **it isn't used to calculate the risk score.** The score uses perceived load. This catches a lot of people out. Entering an accurate weight feels like the rigorous thing to do, but it won't change the number on the report. > **On screen** — Exposure, as a share of the task: 10% · 25% · 50% · 75% · 100% > **Definition** — Handled weight (kg/lbs): 1–60, not used in the score ### The detailed factors The **Detailed data** tab, on the Premium plan only, holds sixteen factors in three groups: repetitive and sustained positions like squatting or kneeling; heavy and high loads; and difficult or awkward handling. Open it when you've seen one of these in the task, or the worker tells you about one. Set the factor's exposure — and for load factors, the load level first. **If you didn't see it and can't find out, leave it blank.** A blank factor says nothing, while a guessed one can say something untrue — with the same authority as everything else on the report. It's worth setting aside a few extra minutes for this tab on a task you already know is a problem, and it's fine to skip it on a routine screening capture. > **On screen** — Difficult or awkward, for example: Gloves required · Unstable or unbalanced · Vision obscured · Shared team lifting · Smooth or slippery ### Description The **Description** tab helps the record make sense to someone reading it in a year's time. It covers the industry, what the task is, the physical environment, PPE, and any controls already in place. A couple of minutes here makes the record much clearer later. The **Controls implemented** field matters too: **it's printed on the Summary assessment report**, so whoever reads the report sees what's already in place. The app doesn't generate recommendations of its own. > **On screen** — Industry · Task · Physical environment · PPE · Notes · Controls implemented · Age range ### Save — and what saving does When you're ready, save. The app re-runs the entire risk calculation immediately, and the score changes as your inputs land. It's worth watching once, because it shows the whole system in a single moment: movement from the sensors, context from you, one score. It also shows why these answers matter. The same captured movement, with four honest answers added, can move a task from one band into the one above it — not because anything about the work changed, but because the record now describes how much of the day the work occupies. That's the best reason to take your time over the conversation with the worker. > **Definition** — On screen: 43.0 before saving, 361.0 after — Possible risk to High risk ## Mistakes that matter - Guessing instead of asking. Every field here exists because it holds knowledge the sensors don't have, and a guess turns an assumption into a number that looks like a fact. - Accepting "all day" as a duration. It usually describes the shift rather than the task, and it inflates the exposure the score is built on. - Entering handled weight expecting it to change the score. It's recorded and it's useful context, but the calculation doesn't use it. ## Not covered here - Recording the capture this information is attached to — see lesson 5, Capture an assessment (https://etiscope.com/support/guide/capture-an-assessment/) - Reading the score that saving produces — see lesson 7, Read the results and choose the right report (https://etiscope.com/support/guide/read-results-and-reports/) - Re-using this sheet on a duplicate to model a proposed change — see lesson 11, Check whether a change worked (https://etiscope.com/support/guide/check-whether-a-change-worked/) **Next lesson:** 7. Read the results and choose the right report — https://etiscope.com/support/guide/read-results-and-reports/