Recommended workflow for drafting, translating, and registering Welsh Statutory Instruments

The following steps outline a complete workflow for drafting, translating, reviewing, and finalising a WSI. The workflow is relevant to:

• Drafters of WSIs,

• The Translation Business Unit,

• Translators,

• Equivalence checkers, and

• The Legislative Codes Office.

Workflow

1. The drafter creates a project and drafts the WSI (usually in English). 
   (This step includes quality control processes such as second pair of eyes peer review. Future versions of the workflow will expand on this step.)

2. Once satisfied with the draft, the drafter duplicates the version into a new folder called “For translation” and sends an email to the Business Unit providing the project link, folder and working version name. (See: Duplicating a document version.)

   

3. The Business Unit logs into Lawmaker and exports the document for translation - see Exporting an English or Welsh rendition for translation. They then create a Trados project, upload the exported document and add a link to the project and the folder name [in the project description/as custom fields]. The Business Unit then assigns it to a translator. 

4. The translator completes the translation in Trados. 

5. The translator logs into Lawmaker, navigates to the project specified within Trados and uploads the translation against the correct working version (expected to be in the “for translation” folder). See Managing Welsh and English renditions for how to import the translated document.

6. The translator reviews their translated version within Lawmaker and makes any necessary edits directly in the Editor (e.g. reordering definitions).

7. The drafter and translator work together within Lawmaker to further update the English and the Welsh as necessary, e.g. in light of comments from the translator or due to further changes being made to the original version after translation.

8. Once both language versions are settled, the drafter duplicates the working version containing both into a new folder called “For equivalence” and contacts the equivalence checker providing the project link, folder and working version name.

   

9. The equivalence checker logs in to Lawmaker and works on the version in the For equivalence folder (e.g., adding comments or track changes to the English, Welsh or both renditions). 

10. The drafter, translator, and Equivalence Checker collaborate on that working version. Communication about readiness will take place outside Lawmaker.

11. Once both languages are finalised, the drafter duplicates the version in the For equivalence folder into a new folder called “For signing” and contacts the Legislative Codes Office providing the project link, folder and working version name.

    

12. The Legislative Codes Office team follows the signing procedure set out in Getting a WSI signed and submitted to TNA. 

13. The Legislative Codes Office team updates the “for signing” version to reflect the signature (e.g. adding dates). 

14. Once the signing process is completed, the Legislative Codes Office submits the final version to TNA by downloading the zip file, and uploading it to TNA’s publishing system as specified in Getting a WSI signed and submitted to TNA .