--- 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/