Social & Labor Convergence Project. Proto2 SLCP Assessment Framework Element 1- Data Collection&Verification Tool Send out Guidance - 1 November 2017

Transcription

1 Social & Labor Convergence Project Proto2 SLCP Assessment Framework Element 1- Data Collection&Verification Tool Send out Guidance - 1 November 2017

2 1. Initial Opening Speed Initial Opening Speed - When opening the document initially, the user is going to need a bit of patience depending upon their computer processing speed. Due to the hidden row conditionality (that affects what the facility sees based on their answers, and what the verifier will see as a secondary user), the document has to run a lot of initial background code to become fully operational. We will continue to optimize the user experience on this right up until the pilot officially begins.

3 2. Macros must be enabled Macros MUST be enabled In order of the tool (and especially the hidden row conditionality) to work correctly, Macros must be enabled. This important point will be discussed during the trainings for both the initial pilot respondents as well as the verifiers. There is also a big Macros must be enabled image as the first thing that you see in the tool once it opens as a reminder.

4 3. Three separate modes Three Separate Modes There are three modes for the tool, see next slides for details a. A Facility Mode b. A Verifier Mode c. A Developer Mode

5 4. Facility Mode The Facility Mode is the default-viewing mode and requires not password. It is the mode that facilities (by Self (SA)- or Joint Assessment (JA)) will use to initially fill out the tool.

6 5. Verifier Mode The Verifier Mode is the facility mode + some additional columns and tabs (in blue) that are just for the verifier. The idea is that the Verifier will receive a filled out tool in Facility Mode and transition it to Verifier Mode. You can test out the Verifier Mode by going to the top right corner of any sheet and clicking the Verifier icon. It will prompt a password, sent to the verifiers participating in the pilot: "VerfPilot2 (please use as written here, 2 capitals, rest lower case). As with the initial tool opening, when switching to Verify mode, please have a little patience to allow the workbook to work through the logic and make the initial transition.

7 6. Developer Mode The Developer Mode is all the back end logic. If you are really keen to look behind the hood, you will also find an icon at top right hand corner of any sheet that says Developer Mode. Upon clicking, it will prompt a password, all uppercase (available at secretariat only). As with the initial tool opening, when switching to Developer mode, please have a little patience to allow the workbook to work through the logic and make the initial transition.

8 7. Verification Tabs Verification Tabs - One thing that we wanted to highlight that s different on this tool (V2) versus the previous tools (V1) is the Verification Summary and Verification Report. The tabs are both blue and are only visible when you are in Verifier Mode.

9 8. Verification Summary The Verification Summary is a recap of sorts for the tool and has three parts: a. Completion Index (a % of questions completed on the tool) b. Accuracy Index (a % of questions that were accurate based on those answered) c. List of all questions found to be inaccurate by the Verifier

10 9. Verification Report The Verification Report asks a few observational questions of the Verifier about how the verification process went (i.e. cooperativeness of the facility etc.)

11 10. Password Protection Password Protection - As of the current version that you are looking at now, password protection only applies to the different viewing modes (i.e. Facility/Verifier/Developer). For the pilot, we have also protected most of the columns so that can t be edited. The notable and obvious exception would be the various response columns where answers are needed.

12 11. Bugs within the tool Bugs within the tool The hidden conditionality that has been added in Version 2 of the tool has really brought us to another level in terms of excel complexity. As such, we have identified and corrected bugs in the past few weeks. Especially in terms of conditionality, speed, formatting (the cell colors changing based on certain answers) and functionality on Macs. There may be some additional bugs that we ve not identified before and that you come across during the pilot. We d invite you to list them and convey them to us (there s a specific question in the on-line survey). We ll address them in the next version.