A controlled template needs more than a recognizable filename. Its file type should support reuse, its fixed instructions should remain fixed and a completed request should be saved as a separate issued document. Otherwise one person's response can become the next person's starting point.
Use the template identity, format and control properties together. The simulator stores those properties without a real document repository, version-retention policy or password encryption. Your task is to express the workflow in the document itself. A locked instruction differs from an editable response, and the issued copy has a different identity from the master. The final task prepares a fresh reusable form while leaving the response field blank, a small detail that prevents accidental reuse of a previous person's name.
The reusable starting point stays separate from the completed request.