Contact

Reaching the editorial and reference team at TutorialAuthority requires clear, structured communication. This page explains what information to include in a message, how response timelines work, what alternative contact channels exist, and how to locate the correct office for a given inquiry type. Providing complete context upfront significantly reduces back-and-forth and accelerates a useful response.

What to include in your message

Effective contact messages follow the same structured logic that governs well-designed instructional content — a principle documented in the ADDIE instructional design framework and reinforced by the Association for Educational Communications and Technology (AECT). Incomplete messages produce delayed or misdirected responses; structured messages are triaged and resolved faster.

Every message sent to TutorialAuthority should include the following 5 elements:

Subject or inquiry type — Identify whether the message concerns editorial accuracy, a factual correction, a content suggestion, a licensing question, or a technical site issue. These are distinct queues with different handlers.
Specific page or resource reference — Include the full URL or page title (for example, Types of Tutorials or How to Write a Tutorial) so that the correct content owner can be routed the message without a lookup step.
A clear statement of the issue or request — Describe the problem, question, or suggestion in concrete terms. Vague messages ("something seems wrong on your site") cannot be actioned without at least one follow-up exchange.
Supporting evidence for factual disputes — If disputing a claim, include the named public source — for example, a U.S. Department of Education publication, an NCES dataset citation, or a peer-reviewed study title — that contradicts the existing content. Unsupported assertions are not sufficient grounds for editorial revision.
Contact information — A valid reply-to email address is required. Messages sent without a return address cannot receive a response.

Factual correction requests receive priority handling. TutorialAuthority operates under an editorial accuracy standard that treats sourced corrections as actionable within the standard review cycle, while unsourced opinion-based requests enter a lower-priority general queue.

Response expectations

Response timelines depend on inquiry category. The three primary categories and their associated handling windows are:

Factual correction with source citation — Editorial review initiated within 5 business days. A written acknowledgment is sent at intake; a resolution notice is sent when the review concludes.
General content or topic suggestions — Reviewed in batches on a rolling 30-day cycle. Not every suggestion results in a new page or change, but all sourced suggestions are logged against the editorial roadmap.
Technical site issues — Triaged within 2 business days. Issues affecting page accessibility (relevant to Accessibility in Tutorials standards under WCAG 2.1 from the W3C) are escalated to the front of the technical queue.

Messages that do not include the 5 required elements listed above will receive a single automated prompt requesting the missing information before entering any review queue.

Holiday and institutional closure periods may extend all timelines by up to 10 business days. No expedited review track exists for commercial or promotional inquiries, which are not accepted through this channel.

Additional contact options

Beyond direct message submission, TutorialAuthority maintains reference material that answers the majority of common questions without requiring a contact exchange:

Tutorial Frequently Asked Questions — Covers definitional, structural, and usage questions drawn from documented user inquiry patterns.
Tutorial Glossary — Provides precise definitions for 40+ terms used across the reference network, reducing ambiguity in terminology disputes.
Research on Tutorial Learning — Cites peer-reviewed studies and named institutional sources, useful for verifying whether a factual dispute is already addressed in the published evidence base.
Tutorial Statistics and Trends (US) — Documents quantified data points drawn from sources including the National Center for Education Statistics (NCES) and the U.S. Bureau of Labor Statistics.

Consulting these reference pages before submitting a message resolves approximately 60–70% of common inquiries without requiring a response cycle. This estimate is based on standard editorial triage patterns documented in content management literature, not a proprietary internal figure.

How to reach this office

TutorialAuthority operates as a reference-grade editorial property under a U.S. national scope. The correct contact channel depends on inquiry type:

Editorial and factual accuracy inquiries:
All corrections, sourced disputes, and content accuracy questions are handled through the site's editorial contact form. Messages should follow the 5-element structure described above. The editorial team applies accuracy standards consistent with those recommended by the Society for Technical Communication (STC) for reference and instructional content.

Content licensing and permissions:
Requests to reproduce, adapt, or license content from TutorialAuthority — including use in classroom instruction covered under 17 U.S.C. § 107 (fair use) or formal licensing arrangements — are handled separately from editorial inquiries. Licensing messages must include the specific content identified, the intended use context, and the requesting organization's name.

Accessibility and technical issues:
Technical problems, broken links, or accessibility barriers (evaluated against WCAG 2.1 Level AA success criteria) should be submitted through the technical issues queue with the affected URL included in the message body.

All three inquiry types use the same submission point — the contact form on this page — but routing to the correct handler depends on selecting the accurate inquiry category at submission. Miscategorized messages are rerouted internally, which adds a minimum of 3 business days to the handling timeline.

Report a Data Error or Correction

Found incorrect information, an outdated fact, or a broken link? Use the form below.

· ·