 Welcome to the UK Data Service. This video outlines the most common issues that arise from the output requests made by secure lab users. Avoid these common errors, making it far more likely that an output can be released first time. This will save resources for researchers and the staff checking the outputs. Researchers place their requested output into the SDC folder. Within this folder, each request should be placed in a sub-folder adhering to the standard naming convention. This is the correct naming convention. It includes the project number and the date in a standard format. Sometimes we get folders that do not follow this convention. If a project is long-running, we can end up with a large number of outputs in this folder. We must ensure that it's clear which output we are being asked to check, otherwise results are wasted and the release of the output is delayed. Sticking to the convention means that the newest output will always be at the bottom of the list so we know where to find it. Researchers should give their file a meaningful name that corresponds with the one they used on the output request form. Researchers should not use output or some other generic name. If a reminder is needed, there is a PDF called Instructions for requesting outputs in the SDC folder. For security reasons, we have to check that there are no embedded objects in visible content or hidden text in the document. To check this in Word, go to File, check for issues, Inspect Document and then click Inspect. We can see here that embedded documents has been flagged. If we right-click Figure 1, you can see that it's still possible to edit the data. This shows that it's the embedded object and cannot be released. However, if we scroll down and we click on Figure 2, there is no such option and this is because it has been copied into Word correctly as a fixed image. Charts are the most common cause of embedded documents and if any are found, they must be removed before submission. If we find any, the output will not be released. We ask that if researchers are submitting text files that they're compiled. If they aren't compiled, it can be very difficult to check them, especially tables, which are very difficult to look at as columns tend to shift significantly. The one here is small, but imagine if it had 10 or more columns, twice as many rows, and if there were other similar tables in the output. These would be virtually unreadable if un-compiled. Researchers must close their output document before submission, otherwise we'll get a message like this. Being locked for editing means that researchers might make a change between the first and second statistical disclosure control checks. This would render the first checking valid and the whole process would have to begin again, wasting resources and causing delay. If we find an output that is locked for editing, we'll not check it until the output has been closed. The full data citation looks like this. The example here is for the Business Structure Database. Citations can be found in the study information file in the original data folder in the researcher's project area. We will only release outputs that include the full data citation, including the DOI number. Citing data is important. If data collectors cannot show that these data are being used, then it risks a withdrawal or reduction in funding for that study in the future. To ensure the threshold of 10 is met, we always ask for the unweighted underlying ends to be supplied. This example shows a histogram and a table, but the requirement for underlying ends applies to every aspect of an output, regressions, scatter plots, everything. It also applies to medians, minima and maxima, which can often represent a single observation or less than the threshold of 10. If these are not supplied, the output will not be released. We ask that researchers submit publishable outputs. The list of acceptable types is here on our website and in the secure lab handbook. Tables must be properly formatted and sufficient explanation on data used, methodology and what each aspect of the output shows must be included. We can't be experts on every dataset, field of inquiry or statistical technique the researchers may employ. If we're not 100% sure what we're looking at, then we'll have to contact the researcher for more information. This can significantly delay the release of the output. We hold a huge number of datasets, so we cannot be sure what every variable name in these datasets means. Therefore researchers must give all variables in every table, graph etc, meaningful names that we can understand at a glance. Look at this table. How could we possibly know for sure what these variable names mean and fully understand what this table shows? It is imperative that all tables, figures etc are numbered. If they're not this can make dialogue between output checkers and researchers unclear. The researcher in this example has at least done this. Researchers should allow four working days for a response about their output. If there are issues with an output then we will have to contact them. They will have to make changes to the output and it will rejoin the back of the queue and air in box, the full day response time then resets. Calling output checkers to chase up an output is not helpful to anyone. We will check each output as soon as we are able. While we're talking for a researcher on the phone we could be working our way through the queue of outputs. Researchers are fully aware that currently they can only access secured lab from the UK. We have known researchers to submit their output request from an airport and then head to another country for several months. If that output requires revisions they cannot be made until the researcher returns to the UK. This may cause a very long delay to the output being released and it happens more often than you might expect. We hope this short video has been useful. If researchers take note of the tips covered here then their outputs are much more likely to be released first time which is better for everyone. Please remember the output request checklist which is part of the output request form will help researchers to get it right first time. Researchers should also remember to make use of the secure lab user guide which is in the references driving secure lab.