Website Operating Procedures
The District 26 Website Operating Procedures were created to address security, approval and publication of documents to the website, and to inform users of the process of requesting changes to the various pages. Click on the link below to download the PDF version.
District 26 Website Operating Procedures
In 2017-2018 District 26 Toastmasters updated the D26 Website to create a webspace with a unified, cohesive look and feel with modules and modalities to allow all users to utilize the site and to create a space for updated District News and Information.
Now that the site is in place, the District would like to keep this site as clean and uncluttered as possible as not to overburden the site or the users with unnecessary content and media. To uphold this quest, we have developed the following set of operating procedures for best practices.
For site security only the web team will have Administrator Access.
Editor Access will be granted only to the District Director and the Blog Editor.
All others will submit requests as follows:
- Article/Blog Requests directly to the Blog Editor
- Website submission requests via the D26 Helpdesk
- Enter name, request desired and reason for request
- Add any files you desire to be used (All files must be editable by Web Team)
- Add any images you desire.
- State your priority (PR 1- Due Immediately, PR2-Due within 2 working days, PR3-Due within 7-10 working days, PR4-Due at Web Team’s earliest convenience)
- Reasoning associated with the priority
- The Web Team will review request and get back to you within 24 hours
All documents submitted to web team will be reviewed for the following prerequisites:
- Can the document be used for content on the site instead of loading it to our media library to be used as an attachment?
- If the document needs to be loaded, is it evergreen or can it stay for a year or more?
- If the document is not evergreen, should it be added to our repository?
- If the document will be printed outside of the website, the document must have proper branding since it will be considered a stand-alone document once it is printed.
- Is there a signature tied to the document? If “yes”, does this signature represent a current leader whose signature might be replaced by the successor to this role? If so, the web team will need to add it to an End-of-Year checklist for documents that will need to be updated and alert the incoming roles for proper updates.
- Procedures apply to all members equally including leaders
The District Director grants the web team authority to have first approval of all items for the timely publication on the website. Toastmasters International Protocol 4.0.2 indicates that the District Director is ultimately responsible for all district website content. Therefore, the District Director will have final approval of all content placed on the website. This is to ensure best practices and ensures no favoritism towards any leader or member.
If the item is approved for content on the site, it does not need branding as the site already has branding. If the item will be printed offline, it must have proper branding because it is considered a stand-alone document therefore must abide by Toastmaster branding rules.
Website Help Desk Procedures
▢ Open District 26 Toastmasters Webpage
▢ Open 26 Helpdesk (link at the bottom of website)
▢ Submit a ticket with website submission request. Answer all questions.
▢ (Greg will create a ticket submission form with name, request, reason, place to submit an image or document, and priority level. Also please add a place for In Review, Pending, Approved, Adopted, etc as needed) (also add Task Assignment if not already there)
▢ Standard reply will go out to all submissions “Thank you for your request. The web team will review your request and get back to you with an answer within 24 hours”
▢ All members of the web team will review request and take action within TAT (Turn Around Time).
▢ Task will be assigned to one of the web team members and they will get back to requestor to complete the request
▢ Once the submission has been resolved, ticket will be closed
With the new procedures in place this will change the direction of how the blog is handled.
▢ Submit Blog article or idea via Submission Form
▢ Or send blog article/idea to blog Editor with required documentation and image links
Glossary of terms
SLA-A Service Level Agreement (SLA) defines the expectations and requirements for delivering a service, including the allowable time frame for the delivery.
The SLA time frames that are associated with Web Team processes are as follows:
Overall time frame
The actual time frame that is defined in the SLA.
Internal time frame
Intermediate time frames for completing the process steps. These time frames are shorter than the overall time, to allow the support team to complete the service well within the overall SLA time frame.
TAT (Turn-Around Time): Time taken to complete a certain task.
A new repository will be created for all District Documentation to replace Dropbox and Google Drive. The Repository will be an offsite server linked to our current website. The repository will be managed by the Website Admin and proper access given as needed for folder management. If you need access please submit a helpdesk ticket requesting permission and the reason you need it. The web team will review your request and get back to you within the SLA time frame requested.