 Welcome to the UK Data Service. This video will help you to use the SecureLab environment efficiently, saving time for you and for the support team. Today we're going to look at the project area folder structure, submitting outputs and what you must include and what to do if you're asked to make any changes. Let's look at the folders in your project area. The original data folder contains the data sets that you've been granted access to. It's a read-only folder so that you can't accidentally overwrite the clean data. Copy the data files from the original data folder into the working folder to begin your analysis. Many researchers will link two or more data sets together in SecureLab. If this applies to you, then please remove anything that you don't actually need for your analysis, such as duplicate variables. It's really rare that we have any issues with space or memory on our servers, but if you create a really huge data set, it may slow down the system for you and for others. To keep your project area manageable, there is a designated folder for you to store your syntax files. The uploads folder is where we can put anything that you ask us to import into your project area once it has been virus and content checked. If you're submitting syntax or material written outside of SecureLab, such as a methodology section or other explanatory material, it must not contain data. To do this, you'll need to complete an import request form. This can be found on the UKDS website. If you want to import data, then permissions may have to be sold, unless this has already been covered in your initial research proposal. The SDC folder is where you must place any outputs you wish to have released to you. Outputs must be placed in the SDC folder in a subfolder with the correct naming convention. The name contains the project number, gear, month and day of the month in a particular format. This is important. If your project is long-running, this folder may become busy and potentially confusing if the subfolders are named incorrectly. If it's not clear which output we're supposed to check, we'll contact you for clarification and this will delay the release of your output. We have finite resources and cannot waste time checking erroneous outputs. Please give your file a meaningful name, not something generic like output release. Please refer to this file name when you fill in the output request form so that everything is really clear. When you wish to make an output request, you must use the form on the website. Then you must fill in your details. And finally, there is a tick box list, which is a reminder of the minimum output criteria. This is very important. Please only tick these boxes if you have genuinely complied with each statement. This will save wasting your time and ours. Imagine it's a busy period and we cannot check your output until maybe three or four days after submission. We then open your output and find that despite you having ticked all the boxes, you very obviously not satisfied some of the minimum requirements. We will then have to terminate the checking process and ask you to make changes. When you have made your changes and let us know that this has been done, your output will re-enter the queue at the back. We have minimum requirements for outputs because the clearer your output is, the easier and quicker it is to be checked. Our requirements are around expediency, resource management, safety and security. If you get this right first time, you're much more likely to receive your output quickly, which is better for everybody. Sometimes outputs are missing pieces of information that would enable us to make an informed decision about their safety. Other times there is something obviously disclosive that has been missed by the researcher. In either case, we'll contact you to ask you to make changes or supply more information. Please do not send any clarifying information, for example underlying ends, via email. This is essentially removing something from the secure lab environment and is a breach. As we say on the training course, you must not write anything down from the screen. Please don't be afraid to ask the support team if you're not sure about something. The more care you take to submit an output that satisfies the minimum criteria, the sooner you'll get your output returned to you. Further details on output requirements, import requests and much more can be found in the Secure Lab User Guide, which is in the references folder in your project area. The best way of contacting us is via the online forms. Using these means that your message will go directly to the right people. We hope this video has been useful. Please let us know if you have any questions.