> For the complete documentation index, see [llms.txt](https://help.simnetonline.com/instructor-experience/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.simnetonline.com/instructor-experience/getting-started/best-practices/naming-conventions.md).

# Naming Conventions

Naming SIMnet content and courses consistently helps instructors and students

After a few semesters of using SIMnet, the amount of content and courses can build up. To find and use your materials efficiently; get accurate and timely support; and avoid confusion, it is important to use specific, repeated naming conventions.

### Courses and Sections <a href="#courses-and-sections" id="courses-and-sections"></a>

Course names in SIMnet should include the name of the course as it appears elsewhere at your school. For example, many schools use SIMnet as a part of their Computer Science intro course. Their course name at the registrar's office and in their LMS is **CS 101**. The SIMnet course name should match.

Section names in SIMnet should describe which section of the course it is, when the course is taking place, who is teaching it, or when the course is meeting. If there are 4 sections in the Spring of 2026 taught by different instructors meeting on different days, those section names may be:

* Section 1 Spring 2026 Smith TH 12:15-1:10
* Section 2 Spring 2026 Smith WF 3:15-4:10
* Section 3 Spring 2026 Jones MW 9:15-10:10
* Section 4 Spring 2026 Harris F 5:45-7:35

The important thing is to select a convention and enforce it throughout SIMnet. There are reports that can be rolled up to a course with multiple sections, but only if the course names are correct.

If you have archived or deleted a course and cannot tell SIMnet Support what the course is called, it makes recovering that course more difficult and slower than it would otherwise be.

### SIMnet Content & Assignments <a href="#simnet-content" id="simnet-content"></a>

SIMnet content is typically used across many courses and can be more context-dependent than course names are. Content may be used by all of the courses at a URL, all the sections of a single course, or for a single instructor.

Remember that instructors are creating content like Lessons, Exams, SIMpaths, and Resources. Having a consistent naming convention makes it easier when you are managing multiple courses.

SIMnet content should mention the course name and the content covered in the assignment. It should also mention the version of the Office materials covered in the content. For example, simply naming the first quiz for an Access course Access Quiz 1 is hard to use when a school switches from 2021 to 365/2024 content. So the first quiz covering Access would be **CS 101 365 Access Quiz 1**.

You can then name the assignment differently if necessary so that it appears in the Gradebook and your LMS as you want it to.

### Template or Master Course <a href="#master-classes" id="master-classes"></a>

{% hint style="success" %}
Create a master course 'template' and name the section to include 'template' or 'master' to indicate the the course should only be copied. Remember to close registration for your template course so students can't enroll into it.
{% endhint %}

Creating a template course can allow you to copy a course without any of the modifications that individual instructors make to the course. This course should be clearly labeled as a Template course and should not have any students added or any associated grades. Adding students and allowing them to complete coursework in the template course limits the long term flexibility of your template course.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.simnetonline.com/instructor-experience/getting-started/best-practices/naming-conventions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
