# Etiscope — the complete guide > The full Etiscope training curriculum: every lesson, in course order, as it appears on the site. Generated from the lesson manifests and the authored pages, so this file cannot fall behind them. Source: https://etiscope.com/support/guide/ Index: https://etiscope.com/llms.txt Lessons: 13 (12 with video) Content revision: series-0-v1 ## Course order Start here — What the product is, what it measures, and how the whole workflow fits together. 1. Etiscope: what it does and how the work flows Set up and capture — From an empty organisation to a saved, checked assessment with the information the sensors cannot know. 2. Set up your organisation, users and categories 3. Prepare the kit, sensors and app 4. Plan and create an assessment 5. Capture an assessment 6. Complete the record: Extra Information Read the results — Turn a score into a named movement, and get the right report to the right person. 7. Read the results and choose the right report 8. Review assessments in the dashboard Act, and check it worked — Choose where to act, put a control in place, and see whether it made a difference. 9. Decide where to act: triage and evidence 10. Create and track risk controls 11. Check whether a change worked Run the program — Keep an eye on your program week to week, and keep your records clean and reliable. 12. Monitor the program in the dashboard 13. Keep the data clean and get it out ## What Etiscope measures The five sensors measure movement of the neck, back and shoulders — posture, repetition and sustained positions. They do not measure below the elbow or the legs, and they do not weigh the load: load is entered by the assessor as perceived load. Etiscope is a screening instrument and works alongside traditional assessment methods rather than replacing them. --- --- id: v0-introduction slug: introduction sequence: 1 title: "Etiscope: what it does and how the work flows" url: https://etiscope.com/support/guide/introduction/ video_state: draft video_duration_seconds: 144.192 video_url: https://media-etiscope.jointaction.cloud/lessons/introduction/a7367d51aa10c94047960e99af797ed065b6ec7194293273539ded76717795d7/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/introduction/a7367d51aa10c94047960e99af797ed065b6ec7194293273539ded76717795d7/captions.vtt --- # 1. Etiscope: what it does and how the work flows Before you start, here's a quick tour: what Etiscope is made of, how an assessment travels from the shop floor to a risk control, and — just as important — what it doesn't measure. **Before this lesson:** nothing — this is where the course starts. ## What you'll be able to do The viewer can name the parts, describe the workflow from capture to risk control, and say what Etiscope measures and does not. - [name-the-parts] Name Etiscope's three parts: the five wearable sensors, Etiscope Capture, and the dashboard. - [describe-workflow] Describe the workflow from kit preparation and capture through to risk controls and re-assessment. - [state-measurement-limits] State what Etiscope's sensors measure and what they do not, including that load is assessor-entered. - [choose-a-starting-lesson] Identify which lesson path to start with next, based on their role. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/introduction/a7367d51aa10c94047960e99af797ed065b6ec7194293273539ded76717795d7/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/introduction/a7367d51aa10c94047960e99af797ed065b6ec7194293273539ded76717795d7/captions.vtt - YouTube (secondary): https://www.youtube.com/watch?v=nYtfRaC7V64 **Chapters:** 0:00 The problem · 0:18 The parts · 0:46 The workflow, end to end · 1:36 What it measures — and what it doesn't · 2:03 Where to start ## The lesson ### The problem Manual tasks injure people gradually. Not usually in one dramatic lift, but through posture held too long, the same reach repeated through a shift, and effort sustained past the point where the body can recover between cycles. That is what makes musculoskeletal injury hard to manage: the damage accumulates out of sight. The traditional answer is to send an expert to watch the job and score it by eye. That works well, but it's hard to stretch across every task on a large site. Etiscope takes a different route. It measures the movement directly, on the job, while the work is being done normally, and turns what it measures into a risk score you can act on. Rather than an opinion about the task, you get a record of how it was actually performed, with a number attached. ### The parts Etiscope has three parts, and every lesson in this guide sits in one of them. **Five wearable sensors** — Inertial measurement units, fitted to the head, upper back, lower back and both arms. They capture how the body moves through the task. **Etiscope Capture** — The Etiscope field app. It runs on an iPad or iPhone, records the task on video, in sync with the sensors, and scores it — so the number and the footage that produced it are the same record. **The dashboard** — In your browser. Assessments from every assessor and every site come together here for review, monitoring and risk controls. The sensors and the app do the capture. The dashboard is where capture turns into a program. > **On screen** — Head · Upper back · Lower back · Left arm · Right arm ### The workflow, end to end However large your rollout, the work follows the same path, and this guide walks you through it in that order. 1. **Set up, once.** An administrator builds your organisation's structure — business units, sites, work areas, jobs, shifts — and adds the people who will do the work. 2. **Prepare the kit.** Charge and assign the sensors, sign in to the app, and fit each sensor to its body location. 3. **Plan the assessment.** Decide what counts as one work task and where it starts and stops, then create the assessment against it. 4. **Capture.** Fit the sensors, **normalise** — record the worker's neutral standing posture as the baseline — then record the task and save. 5. **Complete the record.** Add what the sensors cannot know: how long the task runs, how often it repeats, how heavy it feels. The app calculates the Consequential Risk Score and the reports. 6. **Review and act.** In the dashboard, decide which assessments deserve action, create risk controls against them, and re-assess to see whether the change worked. The loop closes at step six. A control that goes in without a follow-up assessment is a change you believe in; a control with a before and an after is a change you can show. You'll see that idea come up throughout the guide. ### What it measures — and what it doesn't The sensors measure movement of the neck, back and shoulders — posture, repetition and sustained positions. It's worth knowing that coverage precisely, because it tells you which tasks Etiscope is the right instrument for. There are two things it doesn't do. It doesn't measure below the elbow or the legs — wrist, hand and lower-limb postures are outside the sensor set. And it doesn't weigh the load: **you enter load as perceived load**, which you ask the worker about. Entering a weight you read off a label won't change the score, and [Complete the record: Extra Information](/support/guide/complete-the-record/) explains why. Etiscope is a screening instrument. It shows you, at volume, which tasks deserve attention, and it works alongside the traditional assessment methods you already use. A high score is a reason to look closer, not a verdict. ### Where to start This guide is one path, in order, from here to running your program. Reading it end to end gives you the full picture, but if you have a job to do this week, one of these starting points will get you there sooner. - **You'll be doing assessments.** Carry straight on. [Prepare the kit, sensors and app](/support/guide/prepare-kit-sensors-app/) through to [Read the results and choose the right report](/support/guide/read-results-and-reports/) takes you from the box to your first report. - **You'll be reviewing assessments and managing risk controls.** Start at [Review assessments in the dashboard](/support/guide/review-assessments-in-dashboard/) and work forward. - **You're setting Etiscope up for your organisation.** Start with [Set up your organisation, users and categories](/support/guide/set-up-organisation/), and keep [Keep the data clean and get it out](/support/guide/keep-data-clean-and-get-it-out/) handy for later. Whichever you pick, each lesson lists what comes before it, so you can always step back if you need to. ## Not covered here - How the Consequential Risk Score is calculated, and what its grades mean — see lesson 7, Read the results and choose the right report (https://etiscope.com/support/guide/read-results-and-reports/) - Working in the app or the dashboard — the lessons that follow walk you through both — see lesson 2, Set up your organisation, users and categories (https://etiscope.com/support/guide/set-up-organisation/) **Next lesson:** 2. Set up your organisation, users and categories — https://etiscope.com/support/guide/set-up-organisation/ --- --- id: v1-set-up-organisation slug: set-up-organisation sequence: 2 title: "Set up your organisation, users and categories" url: https://etiscope.com/support/guide/set-up-organisation/ video_state: draft video_duration_seconds: 220.053 video_url: https://media-etiscope.jointaction.cloud/lessons/set-up-organisation/30b28bee8aa082fe7a92e939ef152688bce3234e26862c16151e8fff3eba1f2a/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/set-up-organisation/30b28bee8aa082fe7a92e939ef152688bce3234e26862c16151e8fff3eba1f2a/captions.vtt --- # 2. Set up your organisation, users and categories If you're setting Etiscope up for your organisation, this lesson is for you. You'll build the structure everyone files and finds their work against, add the people who will do the assessing, and make two decisions — roles, and whether to record people at all — that are far better settled now than changed later. **Before this lesson:** 1. Etiscope: what it does and how the work flows (https://etiscope.com/support/guide/introduction/) ## What you'll be able to do The viewer can create the organisation's category structure, bulk-import a list, add a user and choose Contributor vs Editor correctly, define a custom category, and decide on the People category. - [create-structure] Create the organisation's category structure — business units, sites, work areas, jobs and shifts — including by bulk import. - [add-user-choose-role] Add a user and choose Contributor vs Editor correctly. - [define-custom-category] Define a custom category for data the built-in categories don't cover. - [decide-people-category] Decide whether to enable the People category, following Etiscope's own recommendation. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/set-up-organisation/30b28bee8aa082fe7a92e939ef152688bce3234e26862c16151e8fff3eba1f2a/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/set-up-organisation/30b28bee8aa082fe7a92e939ef152688bce3234e26862c16151e8fff3eba1f2a/captions.vtt - YouTube (secondary): https://www.youtube.com/watch?v=QlqSorXS9GM **Chapters:** 0:00 Sign in and Settings · 0:34 Build the structure · 1:15 Bulk import · 1:42 Add users and choose roles · 2:48 Custom categories · 3:09 The People category decision ## The lesson ### Sign in and Settings The dashboard runs in your browser. Open the web address your organisation was given with its Etiscope account, and sign in with your administrator email and password. Then select **Settings**. Almost everything in this lesson lives here, and most of it you set up once. The category screens — **Business units**, **Sites**, **Work areas**, **Jobs**, **Shifts**, **Tags** — hold your organisation's structure. After the initial setup you'll only come back to them occasionally, when a new site opens or a shift pattern changes. **Users** and **Organization**, near the bottom of the list, appear because you are an administrator. Someone signing in as an assessor won't see them. The rest of this lesson follows the order that works best: structure first, then users, then the categories that are specific to your business. > **Definition** — This lesson: structure, then users, then custom categories ### Build the structure Every category screen works the same way, so once you've used one you know them all. Open **Sites** and choose **Add site** — or press **Command-N** (**Control-N** on Windows). Give it a name, notes if they are useful, and the business unit it belongs to, then save. That's the whole pattern, and it's the same for every category. One setting is worth a closer look. The **Users** section's **Contributor permissions** switch — **All users** or **Specific users** — controls which users below Editor can see this entry. It defaults to **All users**, and **that default is the right choice unless you have a specific reason to restrict it**. Narrowing it early can quietly hide work from the people who need to see it. Build the structure the way your organisation actually talks about itself, and build it top down: business units first, then sites, work areas, jobs and shifts. Keep names short and consistent — these become the filters everyone uses to find assessments for years to come, and a list where the same site appears three ways is hard for anyone to rely on. If a name would only make sense to the person who typed it, now is a good time to rename it. > **On screen** — Also on every category screen: Edit · Archive · Trash · CSV export > **Definition** — Manufacturing → Geelong Plant → Assembly Line A ### Bulk import You don't have to type your structure in one entry at a time. If you already have your sites in a spreadsheet, you can import them. Press **Command-K** — or **Control-K** — anywhere in the dashboard to open the command palette, and choose **Import** for the category you are filling. Pick your CSV file, choose the **Names column**, **Start row** and **End row**, assign the business unit it all belongs to, and import. The file is a CSV with one name per row in the column you choose, so saving the spreadsheet as CSV is usually all the preparation it needs. > **Definition** — A CSV file: one name per row; choose the column and rows > **On screen** — Work tasks · Work areas · Sites · Jobs · Shifts · Tags ### Add users and choose roles Open **Users** and choose **Add user**. Enter the person's name and email, then open the **Role** picker. The role controls what they can see and do, and for most organisations the choice comes down to two options. **Contributor** — Can capture assessments, but generally sees only their own. Choose this for assessors who only need their own work. **Editor** — Sees all assessments. Choose this for anyone who reviews across the team. The other two roles are narrower than they look. **Viewer** is for external parties you've given access to specific assessments, so it isn't suitable for anyone who captures. **Administrator** is for people doing what you're doing right now. It can be tempting to make everyone an Editor so nobody is ever blocked. An assessor who only needs their own work is usually better served by Contributor — a shorter list is easier to work from. When you pick a role below Editor, the **Contributor permissions** checkboxes appear. These let one user create particular things — a work task, a work area — without moving them to a bigger role. **Grant what their job needs, and no more.** An assessor who works across a site they can't add work tasks to will be held up in the field, while an assessor who can create business units may end up adding ones you didn't plan for. The same screen handles the rest of an account's life: each user's menu can **Set password** or **Copy password reset link**, and **Deactivate** an account when someone leaves. > **Definition** — Contributor = own assessments · Editor = all · Viewer = external · Administrator = setup · Owner = full control > **Watch out** — Roles starting with JA are for JointAction support staff; don't give them to your users > **Definition** — Tick only what they need to create. Work tasks are listed here as Manual tasks. > **On screen** — Edit · Copy password reset link · Set password · Deactivate · Delete ### Custom categories The built-in categories cover how most organisations divide work, but not all of it. If your business thinks in product lines, contract regions or asset classes, you can name your own. Open **Organization** and name one of the five custom categories. Naming it adds a new screen under **Settings**, and that is where you add its values — there are no fields to configure and no forms to design. Save them for a dimension you'll actually filter by. A custom category that nobody fills in becomes a blank column on every assessment. > **Definition** — One name → a screen, a field and a filter; add values on its screen ### The People category decision There's one more decision to make before you finish, and it's about policy rather than configuration. **Etiscope recommends against saving personnel details with assessments.** The assessment is of the task, not the person — the score describes how a job loads a body, and it does that whether or not you know whose body it was. The measurement doesn't need those details, and once they're stored they become something you have to govern, justify and eventually delete. We suggest leaving the **People** category off unless your organisation has a specific reason to track it. That's structure, users and categories done. Your assessors can now sign in, and everything they capture will land somewhere the rest of your organisation can find it. > **Watch out** — Leave People off unless you have a specific reason > **Definition** — The switch stays here in Organization if policy changes ## Mistakes that matter - Giving everyone Editor when Contributor would suit them better. It's quick to do and awkward to reverse once people are used to seeing everything. - Leaving the structure empty, so assessors have to invent it as they go in the field. Structure created a name at a time, under time pressure, on a tablet, is very hard to filter by later. ## Not covered here - Batch editing records, CSV exports and redaction administration — see lesson 13, Keep the data clean and get it out (https://etiscope.com/support/guide/keep-data-clean-and-get-it-out/) - Saved views — the filters your reviewers will build on top of this structure — see lesson 12, Monitor the program in the dashboard (https://etiscope.com/support/guide/monitor-the-programme/) **Next lesson:** 3. Prepare the kit, sensors and app — https://etiscope.com/support/guide/prepare-kit-sensors-app/ --- --- id: v2-prepare-kit-sensors-app slug: prepare-kit-sensors-app sequence: 3 title: "Prepare the kit, sensors and app" url: https://etiscope.com/support/guide/prepare-kit-sensors-app/ video_state: draft video_duration_seconds: 240.491 video_url: https://media-etiscope.jointaction.cloud/lessons/prepare-kit-sensors-app/a4220a5c27a3bb891ab17c84d6ed595d81f9514a1d822b21068881258e3b0272/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/prepare-kit-sensors-app/a4220a5c27a3bb891ab17c84d6ed595d81f9514a1d822b21068881258e3b0272/captions.vtt --- # 3. Prepare the kit, sensors and app Everything between opening the case and a fitted worker. These steps are tempting to rush, and they matter more than any others for data quality — a sensor that is loose, twisted or assigned to the wrong location produces a score for movement that never happened. **Before this lesson:** 1. Etiscope: what it does and how the work flows (https://etiscope.com/support/guide/introduction/); 2. Set up your organisation, users and categories (https://etiscope.com/support/guide/set-up-organisation/) ## What you'll be able to do The learner can take sensors from the case to assigned and correctly fitted, and knows the maintenance actions on the Sensors tab. - [describe-kit-and-charging] Describe the kit's components and how to charge and store the sensors. - [sign-in-to-app] Sign in to Etiscope Capture, including the sign-in-with-link and reset-password paths. - [assign-and-fit-sensors] Assign the five sensors to their body locations in the app's order and fit each one correctly. - [maintain-sensor-health] Use the Sensors tab maintenance actions — calibrate, update firmware, reset — and tell calibration apart from normalising. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/prepare-kit-sensors-app/a4220a5c27a3bb891ab17c84d6ed595d81f9514a1d822b21068881258e3b0272/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/prepare-kit-sensors-app/a4220a5c27a3bb891ab17c84d6ed595d81f9514a1d822b21068881258e3b0272/captions.vtt - YouTube (secondary): https://www.youtube.com/watch?v=Ijd3GvcRpYs **Chapters:** 0:00 Charge the kit · 0:45 Sign in · 1:07 Assign the sensors · 2:16 Fit the straps · 3:03 Keep the sensors healthy ## The lesson ### Charge the kit Your Etiscope kit is the case, five sensors, the charger, and the straps that hold each sensor in place: a head strap, an upper-back strap, two arm bands, and a waist strap for the lower back. Each sensor sits in its strap's mesh pocket, and **the sensors are labelled for their locations**. Those labels help you a lot later — they make fitting faster and much harder to get wrong. The charger is a single block with five leads, one per sensor. Charge the sensors before an assessment day. Plug each sensor into one of the charger's five leads and leave them to charge. For longer storage: the batteries are lithium polymer, so avoid leaving them completely empty or completely full for months at a time. Day to day, you don't need to think about it — just charge them before you head out. ### Sign in Open Etiscope Capture. Enter your email and choose **Next**, then enter your password to sign in. If you'd rather not type a password on a tablet on a work site, choose **Sign in with a link** and the app emails you a sign-in link that signs you in automatically. If you can't get in at all, **Reset password** is on the same screen. If the reset arrives and you still can't sign in, check with your administrator that your account is active — a deactivated account can't sign in. ### Assign the sensors Sensors are assigned to body locations, so the app knows which movement each one is measuring. Assignment belongs to the sensor rather than the assessment, so you do it once per kit, not once per capture. On the **Sensors** tab, open the menu and choose **Assign sensor locations**. The app looks for sensors and tells you how many it found. Choose **Continue**. It then asks for one location at a time, starting with the head. **The app accepts any sensor for any location** — it has no way to know which physical unit you're holding. That's why the labels matter: pick the sensor marked for the head and press its button, the grey circle on the front. The light turns green, and that sensor is assigned. Repeat for upper back, lower back, left arm and right arm, matching each label as you go. Keeping the labels true takes no extra time now and makes fitting straightforward for everyone who picks up the kit afterwards. When all five are assigned, the app finishes setup and confirms **Sensors assigned**. If the app says sensors need updating before they can connect, choose **Update sensors** and let the update finish. You can't use the sensors until it does, so leave yourself time rather than starting it just before a capture. > **On screen** — Head · Upper back · Lower back · Left arm · Right arm ### Fit the straps **Fitting is where good assessments begin.** A loose or twisted sensor measures movement that never happened, and nothing later on can tell the difference between that and a genuinely awkward task. Fit each sensor with its strap, at its location, with the sensor sitting flat against the body. **Head** — The head strap goes around the head, with its sensor centred at the back. **Upper back** — Worn at the base of the neck. **Lower back** — The waist strap holds this sensor centred at the small of the back. **Left and right arm** — The arm bands go around each upper arm, sensor on the outside. Each sensor is labelled for its location — match the label to where you are fitting it, and the assignment you did in the app stays true. Before you move on, give all five a quick check: secure, flat, and each in its own location. > **Do this** — Secure · Flat · Own location — five for five ### Keep the sensors healthy The **Sensors** tab is also where you maintain the kit. There are three actions here, and you'll rarely need two of them. **Calibrate sensors** checks each sensor's motion sensing and finishes when every location's accuracy reads high. Run it **only when a sensor is giving obviously wrong data** — the graphs don't match the movement you can see in front of you. You don't need it as a routine warm-up. These two words are often mixed up, so it's worth being clear: **calibration is sensor maintenance. Normalising is something you do with the worker before every capture.** They're unrelated, they live in different places, and doing one doesn't do the other. **Update sensor firmware** installs the latest sensor software. Once it starts it can't be cancelled, so run it when the sensors are charged and you have a few minutes to spare, rather than between two captures on a live site. **Reset sensors** resets every connected sensor. Use it when a sensor is misbehaving. Charged, assigned, fitted — and you know where to find maintenance when a sensor needs it. Your kit is ready; next you'll decide what's worth assessing. ## Mistakes that matter - Loose or misoriented sensors. This is where assessments most often go wrong, and it's invisible afterwards — the data still looks like data. - Confusing calibration with normalising. Calibrating before every capture costs you time, and skipping normalise because you calibrated corrupts the measurement. - Starting an assessment day on uncharged sensors. The pre-flight warning will catch it — but on site, with the worker already fitted and waiting. ## Not covered here - Setting up the organisation and its users — the administrator's side of getting an assessor signed in — see lesson 2, Set up your organisation, users and categories (https://etiscope.com/support/guide/set-up-organisation/) - Normalising, named here only to separate it from calibration — see lesson 5, Capture an assessment (https://etiscope.com/support/guide/capture-an-assessment/) - Detailed sign-in troubleshooting **Next lesson:** 4. Plan and create an assessment — https://etiscope.com/support/guide/plan-and-create-an-assessment/ --- --- id: v3-plan-and-create-an-assessment slug: plan-and-create-an-assessment sequence: 4 title: "Plan and create an assessment" url: https://etiscope.com/support/guide/plan-and-create-an-assessment/ video_state: draft video_duration_seconds: 177.963 video_url: https://media-etiscope.jointaction.cloud/lessons/plan-and-create-an-assessment/b134cfeef43ffea54181b4b82d1cb154f61635ef027d66fcbfbda3296e03155f/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/plan-and-create-an-assessment/b134cfeef43ffea54181b4b82d1cb154f61635ef027d66fcbfbda3296e03155f/captions.vtt --- # 4. Plan and create an assessment Before any sensor records anything, you'll decide what counts as one task and where it starts and stops. It's a judgement call, and it's worth taking your time over: a well-scoped task is what makes every measurement after it meaningful. **Before this lesson:** 1. Etiscope: what it does and how the work flows (https://etiscope.com/support/guide/introduction/); 3. Prepare the kit, sensors and app (https://etiscope.com/support/guide/prepare-kit-sensors-app/) ## What you'll be able to do The learner can state where a task starts and stops using the scoping guidance, create the work task, and create an assessment with the right categories. - [scope-work-task-boundary] Judge a work task's boundaries — what counts as one task, and where it starts and stops — using the scoping guidance, expressed in observable events. - [search-before-create-work-task] Search for an existing work task before creating a new one, and create a work task named so a colleague would recognise it. - [create-assessment-from-work-task] Create a new assessment from a work task, using the Categories tile grid and its Work Task picker. - [set-categories-and-title-mode] Set the categories that make an assessment findable, and follow the title behaviour your organisation set up. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/plan-and-create-an-assessment/b134cfeef43ffea54181b4b82d1cb154f61635ef027d66fcbfbda3296e03155f/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/plan-and-create-an-assessment/b134cfeef43ffea54181b4b82d1cb154f61635ef027d66fcbfbda3296e03155f/captions.vtt - YouTube (secondary): https://www.youtube.com/watch?v=g65r43SAWiE **Chapters:** 0:00 What's worth assessing · 0:41 Where the task starts and stops · 1:10 Create the work task · 1:30 Create the assessment · 2:08 Categories and title ## The lesson ### What's worth assessing A work task is one recognisable unit of work. Palletising cartons. Unloading the delivery. Dressing the line. If you described it to a supervisor in four words, they would know exactly which part of the shift you meant. As a guide, a task usually runs somewhere between one minute and twenty. - **More than twenty minutes?** It's probably several tasks chained together. Try splitting them up and assessing them separately. - **Under a minute?** You're probably looking at part of a task. Step back and capture the whole thing. These are guidelines rather than rules, and nothing in the app enforces them. Some tasks genuinely take thirty seconds, and they're usually worth assessing when heavy loads are involved. ### Where the task starts and stops Once you've picked the task, set its boundaries: the moment it starts and the moment it ends, **stated in things you can see**. "From lifting the first carton out of the cage to closing the empty cage" is a boundary. "The unloading part" is harder to pin down — two assessors could draw it in two different places, and their assessments wouldn't be comparable. Talk to the worker and the supervisor. They know where the seams in the work are, and they can point out a step that actually belongs to the next job before you include it. You'll capture within these boundaries. For a long or repetitive task you won't need all of it — a representative sample of a few cycles is enough. ### Create the work task In the app, open the **Work tasks** tab. **Search before you create.** If the task already exists, use it. Two names for the same work split its history in two, and neither half will show a clear trend. A quick search here saves a lot of tidying later. If nothing matches, choose the plus button. Name the task so a colleague would recognise it, add tags or notes if they help, and save. > **On screen** — New work task: Work task name (required) · Notes · Tags ### Create the assessment Now you can create the assessment itself. The work task is the reusable part; the assessment is one measurement of it. Open the work task you just made. Its screen lists its assessments. Choose **New assessment** in the top bar. A sheet titled **New assessment** opens, showing the assessment's details with the work task already filled in. The tiles across the top are the categories: **Work Task**, **Person**, **Location**, **Work Area**, **Job**, **Shift**, **Industry**. Tap **Work Task** and pick the task you just created. The picker searches as you type, and you can narrow it to tasks you can edit or ones you use often — useful once your organisation has hundreds. > **On screen** — Filters: All tasks · Tasks I can edit · Frequently used · Has notes ### Categories and title Set the categories that tell the rest of your organisation where this assessment belongs — the location, work area, job and shift you are assessing. **Categories are what make the assessment findable in the dashboard later.** An assessment with empty categories isn't lost, but it won't appear in any filtered view, saved view, or stats chart built against a site or a job, so it ends up outside the program it was captured for. The **Location**, **Work Area**, **Job** and **Shift** lists come from what your organisation's administrator has set up. **Location** in Etiscope Capture is what the dashboard calls a site. If the one you need isn't there, you can add it yourself if your contributor permissions allow it; otherwise, ask your administrator. It's worth checking the structure before a capture day so you're not held up during one. Depending on how your organisation has configured titles, the assessment title either fills in automatically or asks you to write one. The **Quick Insert** chips drop in the work task, site or date so titles stay consistent across everyone capturing. Add tags or notes if your team uses them. Your assessment is now created and ready for recording. > **Definition** — Titles are automatic, required or optional, as your organisation chose > **On screen** — Quick Insert chips: Person · Work Task · Site · Work Area · Job · Shift · Date ## Mistakes that matter - Assessing "the whole job" as one task. The score describes an average that matches no moment of the work, and the awkward thirty seconds that actually hurt people get lost in it. - Creating a near-duplicate work task instead of searching first. Two names for the same work split its history, and neither half shows a useful trend. - Leaving categories empty. The assessment is captured and scored, but every filter your organisation uses will miss it. ## Not covered here - Recording the assessment you have just created — see lesson 5, Capture an assessment (https://etiscope.com/support/guide/capture-an-assessment/) - The extra information the sensors cannot capture — duration, repeats and load — see lesson 6, Complete the record: Extra Information (https://etiscope.com/support/guide/complete-the-record/) - Creating the sites, work areas, jobs and shifts these category pickers draw from — see lesson 2, Set up your organisation, users and categories (https://etiscope.com/support/guide/set-up-organisation/) **Next lesson:** 5. Capture an assessment — https://etiscope.com/support/guide/capture-an-assessment/ --- --- 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/ --- --- 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/ --- --- id: v6-read-results-and-reports slug: read-results-and-reports sequence: 7 title: "Read the results and choose the right report" url: https://etiscope.com/support/guide/read-results-and-reports/ video_state: draft video_duration_seconds: 153.984 video_url: https://media-etiscope.jointaction.cloud/lessons/read-results-and-reports/9aa16881428f1b0e8034f68299088ecb46d41b5d97eb188aeff6202cc3052840/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/read-results-and-reports/9aa16881428f1b0e8034f68299088ecb46d41b5d97eb188aeff6202cc3052840/captions.vtt --- # 7. Read the results and choose the right report A number on its own can start a debate. Here you'll learn how a few seconds with the video turn a score into a sentence somebody can act on, and how to pick the report that suits whoever is going to read it. **Before this lesson:** 5. Capture an assessment (https://etiscope.com/support/guide/capture-an-assessment/); 6. Complete the record: Extra Information (https://etiscope.com/support/guide/complete-the-record/) ## What you'll be able to do The learner can read the score and grade together, scrub the video against the graphs to find and name the movement behind a peak score, use the key contributing factors as a map, and choose the right report — Summary, Detailed, Task demands or Combine — for the recipient. - [read-score-and-grade-together] Read the Consequential Risk Score and its grade together — the score for comparing tasks, the grade for communicating risk. - [scrub-video-to-find-the-moment] Scrub the video against the neck, back and arms graphs to find and name the movement behind a peak score. - [use-contributing-factors-as-a-map] Use the key contributing factors to decide which graph to scrub first. - [choose-the-right-report-for-the-recipient] Choose among Summary assessment, Detailed assessment, Task demands and Combine reports by recipient, and export the result as a PDF. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/read-results-and-reports/9aa16881428f1b0e8034f68299088ecb46d41b5d97eb188aeff6202cc3052840/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/read-results-and-reports/9aa16881428f1b0e8034f68299088ecb46d41b5d97eb188aeff6202cc3052840/captions.vtt - YouTube (secondary): https://www.youtube.com/watch?v=RCXzQU1d4c8 **Chapters:** 0:00 The score and the grade · 0:20 Finding the moment · 1:14 Contributing factors · 1:27 The four reports · 2:09 Combine and export ## The lesson ### The score and the grade Open the assessment. The number is the **Consequential Risk Score**, and next to it is its grade. The app shows them side by side, and it helps to read them together, because they answer different questions. **The score is for comparing** — It's a continuous number, so it ranks tasks against each other and shows movement between a before and an after. Use it when you're deciding where to spend effort. **The grade is for communicating** — It puts the score into a named band. Use it when you're explaining the result to someone who doesn't work with Etiscope day to day. The grade on its own doesn't have the resolution you need to prioritise, and the score on its own can be hard for a supervisor to interpret. Together, they give you both. > **On screen** — Grades, low to high: Low risk · Possible risk · Substantial risk · High risk · Very high risk ### Finding the moment The score tells you how much. The video tells you why. The video player and the three graphs — neck, back, arms — share one timeline. Drag the scrubber until the cursor line sits on the tallest peak in the back graph, and the video shows the exact moment that produced it. The video and the graphs both follow the scrubber. Play a few seconds either side and watch what the worker is actually doing. That movement, at that shelf, with that load, is what the number is made of. It's worth doing this **before you quote a score to anyone.** A score on its own invites debate about the number, while a score with the movement behind it moves the conversation to the shelf height — the thing that can actually change. Scrub, watch, name the movement. You'll use this skill more than any other: when you choose where to act, when you justify a control, and when you check whether the control worked. > **Do this** — The tallest peak marks the moment to watch > **On screen** — Scrub · Watch · Name the movement ### Contributing factors Below the score, the key contributing factors name what loaded the score most — which body region, and which kind of movement. Use them as your map. With three graphs and a two-minute capture there are a lot of peaks to choose between, and the contributing factors tell you which graph to scrub first, so you find the moment that matters rather than the first bump you land on. ### The four reports When someone needs this on paper, the **Reports** menu has four options. Rather than four levels of detail, think of them as suited to four different readers. **Summary assessment** — One page: score, body diagram, graphs and key factors. Right for a supervisor, or a toolbox talk. **Detailed assessment** — Four pages, with the physical demands and per-movement detail. Right for the safety team or an ergonomist. **Task demands** — Describes the physical demands of the task across a working day. It's used well beyond safety — in return-to-work and recruitment — under your organisation's own process for those decisions. **Combine reports** — Assembles selected pages into one document when someone needs a custom set. Match the report to the reader. If someone asked for a one-pager, the four-page detailed report usually means less of it gets read, not more. > **Definition** — Detailed assessment: four pages, from Hazard management to Contributing risk factors > **Definition** — Task demands: how often each physical demand occurs in an 8-hour day ### Combine and export To build a custom set, open **Combine reports**. Switch on the pages you want — **they all start switched off** — drag them into order, and generate. Whichever report you pick, it exports as a PDF through the standard share sheet. AirDrop it, email it, or file it into your own systems. The right report, to the right person, with the movement behind it — that's a result read well. > **On screen** — Pages you can combine: Assessment summary · Contributing factors · Task information · Capture data · Task demands ## Mistakes that matter - Quoting the score without looking at the movement. Showing the movement gives people something they can check for themselves, rather than a number they can only accept or reject. - Sending the four-page detailed report when a one-pager was wanted. Choose the report for the person reading it, however thorough the assessment. ## Not covered here - Finding and managing records across the whole organisation in the dashboard — see lesson 8, Review assessments in the dashboard (https://etiscope.com/support/guide/review-assessments-in-dashboard/) - Deciding which of these results actually deserves action — see lesson 9, Decide where to act: triage and evidence (https://etiscope.com/support/guide/decide-where-to-act/) - Creating a risk control once you have decided — see lesson 10, Create and track risk controls (https://etiscope.com/support/guide/create-and-track-risk-controls/) **Next lesson:** 8. Review assessments in the dashboard — https://etiscope.com/support/guide/review-assessments-in-dashboard/ --- --- id: v7-review-assessments-in-dashboard slug: review-assessments-in-dashboard sequence: 8 title: "Review assessments in the dashboard" url: https://etiscope.com/support/guide/review-assessments-in-dashboard/ video_state: draft video_duration_seconds: 148.693 video_url: https://media-etiscope.jointaction.cloud/lessons/review-assessments-in-dashboard/1c37d8ef656665c22e17eac999d836c5c0c100f821fcc783c657b024f2ef424a/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/review-assessments-in-dashboard/1c37d8ef656665c22e17eac999d836c5c0c100f821fcc783c657b024f2ef424a/captions.vtt --- # 8. Review assessments in the dashboard Working with a single record in the dashboard: finding it, reading what was captured, correcting anything filed in the wrong place, and deciding when it's ready to lock. **Before this lesson:** 1. Etiscope: what it does and how the work flows (https://etiscope.com/support/guide/introduction/) ## What you'll be able to do The learner can find an assessment by its context, read the Data tab with the shared cursor, edit categories, add an attachment, and lock a finished assessment. - [find-by-context] Find an assessment by its context using the sidebar's Add Filter controls. - [read-data-and-context] Read the Data tab with its shared video/chart cursor, plus Duration & load and Description, to understand what was captured. - [recategorise-records] Edit Categories so a miscategorised assessment becomes findable by every filter and view. - [attach-and-finalise] Add an attachment with a note, and lock a finished assessment. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/review-assessments-in-dashboard/1c37d8ef656665c22e17eac999d836c5c0c100f821fcc783c657b024f2ef424a/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/review-assessments-in-dashboard/1c37d8ef656665c22e17eac999d836c5c0c100f821fcc783c657b024f2ef424a/captions.vtt - YouTube (secondary): https://www.youtube.com/watch?v=kDloh7ACezA **Chapters:** 0:00 Find the assessment · 0:28 The Data tab · 1:04 Duration & load, and Description · 1:25 Fix the categories · 1:40 Attachments · 1:53 Archive, trash and lock ## The lesson ### Find the assessment Select **Assessments** in the sidebar. **Find records the way you'd describe them.** Choose **Add Filter**, then the field — the site, the work task, the date. The chips above the list show which filters are active; remove a chip and its filter goes with it. This is where your organisation's structure and the categories set during capture pay off. A record filed against its site, work area and shift is one you can reach in three clicks; a record filed against none of them is hard to find unless you already know it exists. **Risk controls** is its own destination in the sidebar, with its own list and its own filters. You'll use it in [Create and track risk controls](/support/guide/create-and-track-risk-controls/). > **Definition** — There's no filter by grade; sort by risk to see the highest first > **On screen** — Sidebar order: Home · Assessments · Risk controls · saved views · Settings ### The Data tab Open the assessment. The **Data** tab is the capture itself: the video, the posture chart, and the score with its grade and key contributing factors. The video and the chart **share one cursor** — drag the video's scrubber and the chart's cursor moves with it. Use that to find the moment behind the score. Drag to the tallest peak in the chart, and the video shows you exactly what the worker was doing when it happened. Watch a few seconds either side. It's the same skill you use in Etiscope Capture, in a different window, and the same idea applies: **a score you've traced to a movement is one you can act on.** > **On screen** — Tabs: Data · Duration & load · Categories · Description · Risk control · Attachments > **Definition** — Summary score also shows neck, arm and back region indicators ### Duration & load, and Description **Duration & load** shows what was entered in Etiscope Capture — repeats, continuous duration, perceived load and its proportion. In the dashboard these are **read-only**, so you're reviewing what was recorded rather than editing it. If a value looks wrong, it's corrected in the app, on the record, by someone who can check the answer with the worker. **Description** carries the task and environment text — what the job actually is, the conditions, the PPE, and any controls that were already in place when the capture was made. If you didn't perform the assessment yourself, it's worth reading this before you form a view about the score. > **On screen** — Repeats in shift · Continuous task duration · Perceived load · Proportion with that load ### Fix the categories **Categories** is where you can tidy up how a record is filed. If an assessment was filed without its work area or shift — or against the wrong site — you can fix it here. As soon as you save, it shows up in every filter and saved view the rest of your organisation uses. It's a small fix with a large effect. A miscategorised record is missing from the site's numbers, absent from the trend, and out of sight for the person whose job is to notice it. > **On screen** — Title · Work Task · Work Area · Site · Job · Shift · Industry · Tags ### Attachments The **Attachments** tab holds the evidence around the assessment — photos of the workstation, the standard operating procedure document, a link to a related record. **Add a note when you upload** so the next reader knows why it's there. An unlabelled photograph attached eighteen months ago is more of a puzzle than evidence. > **Definition** — Any file (photos, documents, PDFs, video) or a link ### Archive, trash and lock There are three ways to finish with a record, and each means something different. **Archive** — Tucks the record away without deleting it. Right for superseded work — the assessment that was true before the workstation changed. **Trash** — For records that should never have existed. A test capture, a duplicate, an assessment of the wrong task. **Lock** — For an assessment that is final — reviewed, categorised, evidence attached. The lock button sits at the top of the assessment next to the save controls, and appears once there are no unsaved changes. Locked means read-only, and a lock icon marks it in the list. Locking means **the record everyone quotes stays the record everyone saw**, so if a score is going to appear in a report or a meeting, lock it first. Archive is for "superseded but true". A longitudinal record keeps its history, so archiving rather than trashing is what preserves the trend over time. > **On screen** — Menu: Copy id · Download chart · Download video · Redact faces · Archive · Trash > **Watch out** — Redaction is admin-only and metered monthly ## Mistakes that matter - Leaving miscategorised records as they are. They stay out of every filter, view and chart your program runs on. - Trashing a record that should have been archived. Superseded isn't the same as wrong, and only wrong records belong in the trash. - Editing records that should have been locked. Once a score has been quoted, the record underneath it should stay as it was. ## Not covered here - Choosing which of these records deserves action — see lesson 9, Decide where to act: triage and evidence (https://etiscope.com/support/guide/decide-where-to-act/) - Creating and tracking risk controls — see lesson 10, Create and track risk controls (https://etiscope.com/support/guide/create-and-track-risk-controls/) - Saved views and the stats charts built on filters — see lesson 12, Monitor the program in the dashboard (https://etiscope.com/support/guide/monitor-the-programme/) - Redaction administration and the monthly anonymisation allowance — see lesson 13, Keep the data clean and get it out (https://etiscope.com/support/guide/keep-data-clean-and-get-it-out/) **Next lesson:** 9. Decide where to act: triage and evidence — https://etiscope.com/support/guide/decide-where-to-act/ --- --- id: v8-decide-where-to-act slug: decide-where-to-act sequence: 9 title: "Decide where to act: triage and evidence" url: https://etiscope.com/support/guide/decide-where-to-act/ video_state: draft video_duration_seconds: 114.496 video_url: https://media-etiscope.jointaction.cloud/lessons/decide-where-to-act/b587359bf4850e22f79b57b7c202f3dd27346ee39cd0c33f9900657645cc32c7/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/decide-where-to-act/b587359bf4850e22f79b57b7c202f3dd27346ee39cd0c33f9900657645cc32c7/captions.vtt --- # 9. Decide where to act: triage and evidence A running program produces more assessments than anyone can act on at once. Choosing between them is your call, and this lesson helps you make it with confidence. **Before this lesson:** 8. Review assessments in the dashboard (https://etiscope.com/support/guide/review-assessments-in-dashboard/) ## What you'll be able to do The learner can build a shortlist from the list, and for one candidate, name the movement and context driving its score, based on the video. - [state-judgement] State that choosing where to act is the reviewer's judgement — weighed against people, frequency and severity, not the score alone. - [build-the-shortlist] Build a shortlist using Home's High Risk Assessments card and a filtered, sorted assessments list. - [trace-the-evidence] Trace a shortlisted score to the movement behind it on the candidate's Data tab. - [state-the-evidence] State the evidence sentence — movement, place and load — that carries into the risk-control conversation. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/decide-where-to-act/b587359bf4850e22f79b57b7c202f3dd27346ee39cd0c33f9900657645cc32c7/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/decide-where-to-act/b587359bf4850e22f79b57b7c202f3dd27346ee39cd0c33f9900657645cc32c7/captions.vtt - YouTube (secondary): https://www.youtube.com/watch?v=UX50KIdqLjY **Chapters:** 0:00 You can't act on everything · 0:32 Build the shortlist · 1:11 Trace one candidate · 1:30 Say what the evidence shows ## The lesson ### You can't act on everything Once assessments are coming in at volume, the challenge shifts from measurement to attention. There are more scored tasks than there are people, budget and shutdown windows to address them. **Etiscope leaves the decision about which ones matter most to you**, because it depends on things only you and your team know. The score is the starting point. Weigh it with what you know about the work: - How many people do this task - How often it is done - How serious the likely injury is A moderate score on a task half the site performs every hour can matter more than a high score on a rare one. There's no formula that turns those four things into a ranking — how you weigh them depends on your site and your workforce. > **On screen** — Grades, low to high: Low risk · Possible risk · Substantial risk · High risk · Very high risk ### Build the shortlist Start on **Home**. The **High Risk Assessments** card orders by score, so it's the fastest way to see the top of the range. From there, go to the assessments list and use **Add Filter** to narrow to where you actually have responsibility — your site, this quarter. For a task at a site you don't run, the next step is a conversation with whoever does. Open the records near the top and skim their context: which task, which work area, what the assessor noted in the description. You're not analysing yet; you're working out which handful deserve a closer look. Note the few you'll take further — record IDs or titles, in whatever your team uses for its working notes. A shortlist you follow through is worth more than a long list you revisit. > **Do this** — Sort: Risk, highest first. It covers every date and clears a date filter. ### Trace one candidate **Before you take a shortlisted score into a conversation about controls, look at the movement behind it.** Open the candidate's **Data** tab and use the find-the-moment skill from [Review assessments in the dashboard](/support/guide/review-assessments-in-dashboard/): scrub to the peaks, watch what the worker is doing either side of each one, and check the duration and load the assessor recorded. This tells you two things the score alone can't. You learn whether the peak is a genuine feature of the task or a one-off in that capture, and you learn what specifically to change, which is a different question from how bad it is. A high score driven by repeated bending at the bottom pallet layer has an obvious lever. The same score with no traced cause gives the meeting nothing to work with. > **Watch out** — A locked (final) assessment is read-only ### Say what the evidence shows Then say what you actually saw, in task terms: which movement, where in the task, under what load. "Repeated forward bending at the bottom pallet layer, medium perceived load, most of the shift." That sentence — the score plus the movement behind it — is what you carry into [Create and track risk controls](/support/guide/create-and-track-risk-controls/), where it becomes a risk control. It's also what makes the control clear to everyone in the room: raise the bottom layer. With that sentence, your score becomes a proposal rather than a question for someone else to answer. ## Mistakes that matter - Acting on the score alone. It's one of four things worth weighing, and it's the only one the product can see. - Quoting a score nobody has traced to the video. It's hard to defend, and hard to turn into a specific change. - Spreading effort across everything instead of choosing a few. Half-addressed tasks rarely produce a measurable before-and-after; properly addressed ones do. ## Not covered here - The scrub-and-trace mechanics themselves, taught earlier and reused here — see lesson 8, Review assessments in the dashboard (https://etiscope.com/support/guide/review-assessments-in-dashboard/) - Creating the control once you have decided where to act — see lesson 10, Create and track risk controls (https://etiscope.com/support/guide/create-and-track-risk-controls/) **Next lesson:** 10. Create and track risk controls — https://etiscope.com/support/guide/create-and-track-risk-controls/ --- --- id: v9-create-and-track-risk-controls slug: create-and-track-risk-controls sequence: 10 title: "Create and track risk controls" url: https://etiscope.com/support/guide/create-and-track-risk-controls/ video_state: draft video_duration_seconds: 138.027 video_url: https://media-etiscope.jointaction.cloud/lessons/create-and-track-risk-controls/00b2353b73c4255853af435e2895ba91d37380a520fb2e5620138f02456537c8/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/create-and-track-risk-controls/00b2353b73c4255853af435e2895ba91d37380a520fb2e5620138f02456537c8/captions.vtt --- # 10. Create and track risk controls Here you'll turn the evidence sentence from Decide where to act into a risk control with an owner, a date and a status. You choose the control; Etiscope helps make sure it stays visible until it's done. **Before this lesson:** 9. Decide where to act: triage and evidence (https://etiscope.com/support/guide/decide-where-to-act/) ## What you'll be able to do The learner can create a control choosing its Type from the built-in hierarchy, link it from the assessment, move it through the status lifecycle, and read the overdue card. - [choose-control-type] Choose a control's Type from the product's built-in hierarchy of controls. - [create-and-assign-control] Create a risk control in form order, with a named responsible user and a real due date. - [link-control-to-assessment] Link a risk control to the assessment that justified it. - [track-control-status-and-overdue] Move a control through its status lifecycle and read the overdue card that tracks it. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/create-and-track-risk-controls/00b2353b73c4255853af435e2895ba91d37380a520fb2e5620138f02456537c8/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/create-and-track-risk-controls/00b2353b73c4255853af435e2895ba91d37380a520fb2e5620138f02456537c8/captions.vtt - YouTube (secondary): https://www.youtube.com/watch?v=wUbCl0300W8 **Chapters:** 0:00 The Type field is the hierarchy · 0:29 Create the control · 0:59 Link it to the assessment · 1:23 The status lifecycle · 1:46 Overdue — and the control's tabs ## The lesson ### The Type field is the hierarchy Etiscope has the hierarchy of controls built in. A risk control's **Type** is one of: **Eliminate**, **Substitute**, **Engineering**, **Administrative**, or **PPE** — **in that order, on purpose**. The order matters. Eliminating the hazardous movement protects everyone who ever does the task, permanently, without depending on anyone remembering anything. PPE protects the person wearing it correctly, today. Which control you choose is your organisation's own engineering and approval decision. Etiscope gives you the place to record that decision, assign it, and hold it to a date. It helps to treat the **Type** field as a prompt rather than a label. If everything on your list is typed **Administrative** or **PPE**, that tells you something about the program rather than the tasks. > **On screen** — Type: None · Eliminate · Substitute · Engineering · Administrative · PPE ### Create the control Select **Risk controls** in the sidebar, and choose **New risk control**. The form runs in order: the business unit, the work task the control addresses, the **Type**, a name that says what will actually change, the status, the due date, the responsible user, and a description. Name it for the change rather than the problem. "Raise bottom pallet layer to 400mm on Line A" tells the next reader what was agreed, whereas "Manual handling risk — Line A" only repeats what they already know. **Two fields carry the follow-through: a named responsible user, and a real due date.** Without a due date, a control never appears on the overdue card, so nothing flags it if it slips; without a responsible user, there's nobody to follow it up. ### Link it to the assessment Next, link it to the evidence. Open the assessment that justified it, go to its **Risk control** tab, and choose **Add risk control**. The picker is already locked to this assessment's work task, so you're choosing among controls that could plausibly apply — pick the control you just created. The link works in both directions, which is useful. Anyone reading the assessment sees what is being done about it, and the control lists this assessment among its evidence. > **Definition** — The button reads Add risk control, then Change risk control once linked ### The status lifecycle Status is three steps: **None**, **In Progress**, **Implemented**. When work starts, open the control, open the **Status** field and choose **In Progress**. When the change is actually in place, set it to **Implemented**. **Wait until the change is in place on the floor before you set **Implemented**.** The before-and-after comparison in [Check whether a change worked](/support/guide/check-whether-a-change-worked/) depends on it: if the status says the change is in place before it actually is, any assessment captured in between is compared against a control that wasn't there yet. > **Definition** — The Risk controls list shows when each control was started and implemented ### Overdue — and the control's tabs On **Home**, the **Overdue Risk Controls** card lists every control that is **In Progress** and due today or earlier. **Overdue isn't a status anyone sets** — it's worked out from the date. You don't have to maintain anything for the program to see what's slipping, which is why it's worth entering a realistic due date rather than an optimistic one. Each control also carries its own record across four tabs: **Details**; **Attachments**, for the before photos, the quotes and the approval; **Stats**; and the **Assessments** it covers. **Stats** leads into Check whether a change worked — it's where the assessments on this control's work task are charted, and where an accumulating before-and-after eventually becomes visible. > **Definition** — The control's Stats tab charts every assessment sharing its work task ## Mistakes that matter - Typing everything as Administrative or PPE without considering the higher-order options. The hierarchy is in the field on purpose, and defaulting to the bottom of it can leave a program retraining people around a hazard it could have removed. - Controls with no owner and no due date. They never go overdue, so nothing ever flags them. - Marking a control Implemented before the change is in place. The before-and-after comparison in Check whether a change worked depends entirely on that date being true. ## Not covered here - Deciding what the control should be, which follows your organisation's own engineering and approval process - Checking whether the control changed anything — see lesson 11, Check whether a change worked (https://etiscope.com/support/guide/check-whether-a-change-worked/) **Next lesson:** 11. Check whether a change worked — https://etiscope.com/support/guide/check-whether-a-change-worked/ --- --- id: v10-check-whether-a-change-worked slug: check-whether-a-change-worked sequence: 11 title: "Check whether a change worked" url: https://etiscope.com/support/guide/check-whether-a-change-worked/ video_state: draft video_duration_seconds: 160.811 video_url: https://media-etiscope.jointaction.cloud/lessons/check-whether-a-change-worked/60655de439d76ce1174025b788cfbd7f26ad0cd65009cd79e65f3c078796b4ec/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/check-whether-a-change-worked/60655de439d76ce1174025b788cfbd7f26ad0cd65009cd79e65f3c078796b4ec/captions.vtt --- # 11. Check whether a change worked One assessment tells you where the risk is. Two tell you whether something changed. Here you'll learn the two ways to get that second assessment, and the one boundary that keeps both honest. **Before this lesson:** 10. Create and track risk controls (https://etiscope.com/support/guide/create-and-track-risk-controls/) ## What you'll be able to do The learner can run both comparisons and knows the one boundary — changing entered values models the same captured movement; a change in how the work is done needs a new capture. - [choose-the-comparison] Choose between re-assessing after a control and modelling first, based on the question being asked. - [reassess-after-a-control] Re-assess after a control with Repeat from the original assessment, and compare the two side by side. - [model-with-duplicate] Model a proposed change with no new capture by duplicating an assessment, editing its entered values and saving to re-score it. - [read-effectiveness-chart] Read the risk control effectiveness chart as the spread of the assessments that exist on the control's work task. - [respect-the-boundary] State the boundary: what-if models exposure; a change in movement needs a new capture. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/check-whether-a-change-worked/60655de439d76ce1174025b788cfbd7f26ad0cd65009cd79e65f3c078796b4ec/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/check-whether-a-change-worked/60655de439d76ce1174025b788cfbd7f26ad0cd65009cd79e65f3c078796b4ec/captions.vtt **Chapters:** 0:00 Two ways to compare · 0:20 Re-assess after a control · 1:06 What-if modelling · 1:52 The effectiveness chart · 2:16 The one boundary ## The lesson ### Two ways to compare So far you've produced one number about one task. That's enough to decide where to act, but not enough to say whether acting worked. There are two ways to get a second assessment, and which one you use depends on the question you're asking. **Re-assess after** — The change is a control that has been built, installed or rostered. Assess the task again once it's genuinely in place. **Model first** — The change hasn't been made yet, and might not be. Model it against the capture you already have, before anyone spends money. Neither is better than the other. Modelling is the cheaper and more constrained of the two; re-assessment is the one that can show a change in how the work is actually done. ### Re-assess after a control When a control from [Create and track risk controls](/support/guide/create-and-track-risk-controls/) is implemented, assess the task again — **the same task, the same way you assessed it before**: same work task, same boundaries, a representative sample of the same work. Create that follow-up assessment in the app with **Repeat**: on the work task's screen, open the original, come back, and choose **Repeat** in the top bar. It carries over the work task, person, location, work area, shift, tags and notes, but not the job — set that again, and all that's left is to capture. As well as saving time, **Repeat** helps make sure the follow-up assesses the same thing as the original. Then open the two assessments and compare the scores and the graphs. **What you can say is what you saw:** the same task, before and after, and where the movement changed. Two assessments of one task are evidence about that task. Describe them that way, rather than as a controlled trial, and a good result will stand up to scrutiny later. > **Definition** — Repeat copies the last assessment you opened, except its job > **Definition** — Shown here: two assessments of one task, to demonstrate the screen ### What-if modelling The second comparison needs no new capture at all, and you do it in Etiscope Capture on the iPad or iPhone rather than in the dashboard. Suppose the proposal is fewer repeats per shift: a rotation rather than a rebuild. You'd like to know whether it's worth making the case before you make it. 1. In the app's assessment list, swipe the assessment's row and choose **Duplicate**. 2. Open the duplicate, then **Report actions** → **Add extra information**. 3. Change the value the proposal would change — repeats, duration, perceived load, exposure — and save. The duplicate re-scores immediately. The original is untouched, and the difference between the two scores is your model of the change. This is the technique behind a business case: a number attached to a proposal, produced immediately, from a capture you already own. > **Definition** — A duplicate shares the original's video and sensor data > **On screen** — Duplicate · Add extra information · Save ### The effectiveness chart Back in the dashboard, the control's **Stats** tab draws risk control effectiveness: the spread of scores for every assessment on the control's work task, as a box-and-whisker. As before-and-after assessments accumulate, this is where the population answer lives — not one task's story, but the distribution across everything captured on that work task. **Read it for what it shows:** the spread of the assessments that exist. It doesn't show that the control caused the shift, whatever the chart's title suggests. Open the records from the **Assessments** tab when you want the stories behind the spread. > **Definition** — Each box: the spread of scores for assessments linked to one control ### The one boundary One boundary keeps both comparisons honest, and it's the most useful thing to take away from this lesson. Editing values re-scores **the same captured movement**. So what-if models changes to exposure and organisation: durations, repeats, loads. Those are real changes and they move the score legitimately. It can't model a change in posture or technique, because the movement in the data hasn't changed. Editing a duplicate can't show the worker bending less, so a smaller number produced that way wouldn't mean anything. If the change alters how the body moves — new equipment, a redesigned workstation, a different way of doing the job — capture it again. **Model the paperwork; re-capture the movement.** ## Mistakes that matter - Modelling a technique change with what-if. The captured movement is unchanged, so a number produced that way doesn't describe the change. - Comparing captures of effectively different tasks. Different boundaries, a different sample or a different work task make the before and after hard to compare, however similar the titles look. - Reading the effectiveness chart as proof because of what it's called. It shows the spread of the assessments that exist. ## Not covered here - Capture mechanics — normalising, recording, checking — see lesson 5, Capture an assessment (https://etiscope.com/support/guide/capture-an-assessment/) - The extra information sheet this technique edits — see lesson 6, Complete the record: Extra Information (https://etiscope.com/support/guide/complete-the-record/) - Creating the control being checked — see lesson 10, Create and track risk controls (https://etiscope.com/support/guide/create-and-track-risk-controls/) **Next lesson:** 12. Monitor the program in the dashboard — https://etiscope.com/support/guide/monitor-the-programme/ --- --- id: v11-monitor-the-programme slug: monitor-the-programme sequence: 12 title: "Monitor the program in the dashboard" url: https://etiscope.com/support/guide/monitor-the-programme/ video_state: draft video_duration_seconds: 174.357 video_url: https://media-etiscope.jointaction.cloud/lessons/monitor-the-programme/125856cfd51659ff98fc1e6d0f3ac0cda6a8e3fd0a22f06b72ab86086ad745eb/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/monitor-the-programme/125856cfd51659ff98fc1e6d0f3ac0cda6a8e3fd0a22f06b72ab86086ad745eb/captions.vtt --- # 12. Monitor the program in the dashboard Set up the view you care about once and save it, so it's ready every time you come back. Then use it to find the records that need someone's attention — that's where monitoring leads. **Before this lesson:** 1. Etiscope: what it does and how the work flows (https://etiscope.com/support/guide/introduction/) ## What you'll be able to do The learner can build a saved view for a real scope in their organisation and use Home, the view and its stats mode to find the records that need attention. - [read-home-cards] Read the Home cards to see what came in, what stands out, and what is overdue. - [build-save-view] Filter the assessments list to a real scope and save it as a saved view. - [use-stats-view] Use the saved view's stats mode to read charts that describe the filtered scope. - [find-follow-up] Identify and open the records from a saved view that need follow-up. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/monitor-the-programme/125856cfd51659ff98fc1e6d0f3ac0cda6a8e3fd0a22f06b72ab86086ad745eb/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/monitor-the-programme/125856cfd51659ff98fc1e6d0f3ac0cda6a8e3fd0a22f06b72ab86086ad745eb/captions.vtt - YouTube (secondary): https://www.youtube.com/watch?v=IWc9jlStsaI **Chapters:** 0:00 What Home shows you · 0:54 Filter the assessments list · 1:21 Save the view · 1:51 The stats view · 2:27 From the list to follow-up ## The lesson ### What Home shows you Sign in to the dashboard and you land on **Home**. Home is a set of cards, and you can change which cards appear with **Edit dashboard**. Four of them are especially useful. **Activity Summary** — When assessments were captured over the last three months, and how their grades are distributed. Click any day in the heatmap and the dashboard opens the assessments list already filtered to that day. **Overdue Risk Controls** — Controls that are **In Progress** and due today or earlier. Overdue is worked out from the due date — it isn't a status anyone sets, so nothing has to be updated for a control to appear here. **Recent Assessments** — The last month's captures — what has come in. **High Risk Assessments** — The list ordered by score — what stands out. Between those four you can see what came in, what stands out, and what's waiting on someone. That's a status check, and it takes about a minute. > **Do this** — Click a day to list that day's assessments > **Figure** — Up to sixteen cards on Home > **On screen** — Risk control status: None · In Progress · Implemented > **Figure** — Recent Assessments — last month, eight rows ### Filter the assessments list Select **Assessments** in the sidebar. This is every assessment your role can see, which on a running program is a lot to look through. To watch one part of the organisation, add filters. Choose **Add Filter**, pick the field, and pick the values — one site, say. The chip above the list shows the filter is active, and the list updates as it's applied. Remove the chip and its filter goes; add it back and the list narrows again. > **Watch out** — User and Tag filters need Editor role or above ### Save the view If a set of filters is worth building once, it's worth keeping. Saving it as a view means you won't need to rebuild it each time you come back. When filters are active, a **Save** button appears in the app bar. Select it, name the view for what it watches — this site — and save. The saved view becomes a destination in the sidebar, below **Risk controls**. Anyone opening it gets these filters applied to the **current** data: the view stores the scope, and the results stay live. Think of it as a standing question rather than a snapshot. You can also add a saved view to Home as a card, so it's there as soon as you sign in. > **Definition** — A view stores a name, a view mode and the full filter set > **Definition** — Some screens still say 'query': a query is a saved view ### The stats view A saved view stores a view mode as well: assessments, or stats. Open the view-mode control above the list and choose stats. **The charts describe exactly the records your filters selected** — this site, not the whole organisation. It's worth keeping in mind, because a chart without its filter chips in view can look like a statement about the whole company. - **Risk score over time** appears when the scope has more than one point in time. - **Risk score spread by work task** shows how the scores are distributed within each task. - **Assessments risk grade distribution** shows the mix as a table and a pie. Any chart downloads as a PNG for a report. > **On screen** — Also: Manual task key contributing factors · Highest risk manual tasks ### From the list to follow-up **Monitoring leads you back to records.** Switch back to the assessments mode and open the records that need a closer look — the new high-risk capture, or the assessment behind the control that is overdue. The charts are there to point you to the records that need a decision, so it's worth clicking through. How often you check, and who follows up, is up to your organisation. Etiscope gives you the same saved view every time you look, and an overdue list that keeps itself up to date. ## Mistakes that matter - Rebuilding the same filters by hand each time, when a saved view would keep them ready for you. - Reading the stats charts as organisation-wide trends. They describe only the records the filters selected, which is usually a single site. - Treating dashboard activity as an outcome. Building views and exporting charts helps, but the outcome is records opened and controls closed. ## Not covered here - Acting on one assessment — reading it, correcting it, locking it — see lesson 8, Review assessments in the dashboard (https://etiscope.com/support/guide/review-assessments-in-dashboard/) - Creating the risk controls the overdue card tracks — see lesson 10, Create and track risk controls (https://etiscope.com/support/guide/create-and-track-risk-controls/) - Exports and batch corrections — see lesson 13, Keep the data clean and get it out (https://etiscope.com/support/guide/keep-data-clean-and-get-it-out/) - Review cadence and meeting practice, which are up to your organisation **Next lesson:** 13. Keep the data clean and get it out — https://etiscope.com/support/guide/keep-data-clean-and-get-it-out/ --- --- id: v12-keep-data-clean-and-get-it-out slug: keep-data-clean-and-get-it-out sequence: 13 title: "Keep the data clean and get it out" url: https://etiscope.com/support/guide/keep-data-clean-and-get-it-out/ video_state: draft video_duration_seconds: 168.555 video_url: https://media-etiscope.jointaction.cloud/lessons/keep-data-clean-and-get-it-out/9195b20f362a113684246da4fc0a865f3fbd97c5417aae2b5e3b4525a171ed48/video.mp4 captions_url: https://media-etiscope.jointaction.cloud/lessons/keep-data-clean-and-get-it-out/9195b20f362a113684246da4fc0a865f3fbd97c5417aae2b5e3b4525a171ed48/captions.vtt --- # 13. Keep the data clean and get it out A little regular housekeeping keeps everything you see in Etiscope reliable. Here you'll fix a filing error across a month of records in one action, send a scoped extract to another system, and find the anonymisation allowance so you can answer questions about redaction quickly. **Before this lesson:** 2. Set up your organisation, users and categories (https://etiscope.com/support/guide/set-up-organisation/) ## What you'll be able to do The learner can correct a filing error across a filtered set in one action, produce a scoped CSV extract, choose archive over trash, and find the anonymisation allowance that explains a refused redaction. - [filter-before-batch] Filter first and read the selection count, because the selection — not the filter — is what gets edited, and the list loads a hundred at a time. - [batch-edit-relations] Batch-edit the relation fields — work task, work area, site, job, shift, business unit — across a selected set, then spot-check. - [export-scoped-csv] Export a list as CSV with chosen, ordered columns, using the dialog's preview to confirm the scope before saving. - [archive-versus-trash] Choose archive for what is superseded but true, and trash only for what should never have existed. - [read-anonymisation-allowance] Read the month's anonymisation allowance, and know that usage is reserved when a video is queued rather than when it finishes. ## Video - MP4: https://media-etiscope.jointaction.cloud/lessons/keep-data-clean-and-get-it-out/9195b20f362a113684246da4fc0a865f3fbd97c5417aae2b5e3b4525a171ed48/video.mp4 - Captions (WebVTT): https://media-etiscope.jointaction.cloud/lessons/keep-data-clean-and-get-it-out/9195b20f362a113684246da4fc0a865f3fbd97c5417aae2b5e3b4525a171ed48/captions.vtt - YouTube (secondary): https://www.youtube.com/watch?v=PsN9wEl9qrE **Chapters:** 0:00 Batch edit · 0:59 Exports · 1:44 Archive and trash at volume · 2:00 Redaction administration ## The lesson ### Batch edit When a filing error repeats — a month of assessments under the wrong work area — fix them together rather than one at a time. **Start by filtering the assessments list to exactly the records that need fixing, and check the chips before you make any changes.** Filtering first is what keeps the next step safe — a batch edit on a set you haven't checked can turn twenty errors into thirty. Now choose **Select assessments**, then **Select loaded assessments**. It's worth reading that label carefully. It selects what the list **has loaded**, and the list loads a hundred at a time. The selection bar shows how many records it's holding, and that number — rather than the filter — is what gets edited. If your filtered set is larger than the bar says, narrow the filter and do it in passes. Then choose **Edit**. You can set the work task, work area, site, job, shift or business unit across every selected record at once. On a large selection the dialog shows a summary step first — the field, its new value and the record count — so take a moment to read it before you continue. Apply it, then spot-check a couple of records to confirm the change landed. > **Figure** — Select loaded assessments: up to 100 at a time > **On screen** — Work task · Work area · Site · Job · Shift · Business unit > **Watch out** — A category ticked with no value writes None to every selected assessment ### Exports Every category screen exports its list as CSV, and the assessments list exports too. This is how Etiscope data reaches your safety management system, your reporting, or a spreadsheet. **Set the filters first: the export takes the scope you're looking at.** **Export data** opens with the columns down one side and a preview of the rows beside them. Remove any columns you don't need, drag the rest into the order the receiving system expects, and check the preview — it shows the records that will be written, so you can *see* the scope for yourself. Then **Save CSV**. The app's reports come from the app rather than the dashboard. Summary assessment, Detailed assessment, Task demands and combined reports are produced in the app, per assessment. The dashboard downloads basic PDF reports, as a ZIP, for up to 15 selected assessments at a time, so if you're looking for the full reports, you'll find them in the app. > **Definition** — Need PDFs? Select up to 15 assessments and choose Download basic reports (ZIP) > **Definition** — Default columns include work task, site, the scores and key contributing factors ### Archive and trash at volume Archive and trash work from the list too, not just one record at a time, so it's worth taking a little extra care with them. Archive what is superseded but true. Trash what should never have existed. **If you're unsure, archive.** It's reversible housekeeping rather than deletion, and an archived record can come back when someone asks about the year before the workstation changed. ### Redaction administration Redaction blurs faces in assessment video so footage can be shared more widely. It's an administrator action on the assessment's menu, and **it's metered**. **Settings**, then **Organization**, shows the month's allowance — the screen calls it anonymisation — as minutes used against your limit. The line under it answers the most common question about this feature: **usage is reserved when a video is queued, not when it finishes.** So if a redaction is refused, it usually means the month's allowance is already committed rather than that anything has failed. This screen is the first place to check. Redaction helps share footage more safely. Who footage may be shared with is still your organisation's decision — Etiscope makes a version that's safer to circulate, and you decide where it goes. Clean records in, clean extracts out. That's what keeps everything else in Etiscope reliable. > **Definition** — Usage is reserved when a video is queued, not when it finishes ## Mistakes that matter - Batch-editing a set that wasn't filtered correctly. The filter is your safety check, so confirm it before you edit. - Trashing instead of archiving. Superseded isn't the same as wrong, and only wrong records belong in the trash. - Assuming the dashboard produces the app's reports. Summary, detailed, task demands and combined reports come from the app; the dashboard exports CSV, chart PNGs and basic PDF reports. ## Not covered here - Creating the structure and importing lists in the first place — see lesson 2, Set up your organisation, users and categories (https://etiscope.com/support/guide/set-up-organisation/) - Saved views and the stats charts — see lesson 12, Monitor the program in the dashboard (https://etiscope.com/support/guide/monitor-the-programme/) - Reviewing and correcting a single assessment — see lesson 8, Review assessments in the dashboard (https://etiscope.com/support/guide/review-assessments-in-dashboard/) **Next lesson:** none — this is the end of the guide.