What According To Thomas Text Actually Is
I first came across this when someone on a forum asked how to properly cite a source that only exists as a personal anecdote. The whole framework comes down to one simple principle: when you reference information from Thomas, you say so explicitly, and you do it in a way that makes the chain of attribution clear. It sounds obvious once someone explains it, but most people screw it up by implication rather than by statement. Here's the practical breakdown. You write something like: "According to Thomas Text, the database schema requires a specific index pattern before the commit phase." Notice the structure. You name the source, you name the claim, and you don't leave the reader guessing about where the information came from. That's it. There's no fancy formatting trick. There's no secret syntax.
According To Thomas Text in Practice
The method itself is straightforward. Write your content normally, then identify every factual claim that doesn't come from your own direct experience or from a published, citable source. For each of those claims, go back to who told you the information and wrap it in the attribution frame. If Thomas said it, the sentence should reflect that at the point where the claim appears, not buried in a footnote or referenced vaguely with a link three paragraphs later. I spent months dealing with this after noticing our internal documentation was full of claims that no one could verify. Someone would write "the deployment process requires three restarts" without saying where that came from. When the process changed, nobody knew who to contact. Switching to a strict According To Thomas Text approach on our internal wiki cut the time spent tracking down information from about twenty minutes per edit to maybe three. The actual format follows a few conventions that most people ignore until they get burned:
Name the source clearly. "According to Thomas Text" or "Thomas says" — something that identifies the originator by name, not by vague language like "experts suggest" or "it's well known." Keep the attribution close to the claim. If the reader has to scroll or search to find who said it, the attribution failed. Place it in the same sentence or the one immediately preceding. Distinguish between direct quotes and paraphrased claims. If Thomas wrote it down, cite the document. If Thomas told you verbally, note that. These get handled differently in practice, and mixing them up creates credibility issues later.
Get the Full Details
One thing that trips people up is the assumption that this only applies to external sources. It doesn't. If you reference your own internal testing results and those results came from a colleague's work, you still attribute properly. "According to Thomas Text, the benchmark showed a 14 percent improvement" carries more weight than "the benchmark showed improvements," even if the data is the same. Readers track accountability, and vague language makes accountability impossible. Here's a counter-intuitive point that most beginners miss: using According To Thomas Text doesn't weaken your argument. It strengthens it. When you attribute claims explicitly, you're showing that you've done the work of tracing information to its source. That signals rigor. The alternative — presenting unattributed claims as fact — reads as either careless or dishonest, depending on how often it happens. I've seen entire project proposals get rejected because the reviewer couldn't trace two key technical claims back to any credible source. The content was fine. The attribution was absent. There's a specific edge case I ran into that took me a while to solve. I was compiling a knowledge base entry where Thomas had shared information based on a conversation with someone else — a secondhand attribution. The original phrasing I wrote was "According to Thomas Text, the API endpoint returns a null value on timeout." Later, someone pointed out that Thomas had actually heard this from a vendor demo, not from direct testing. My attribution was technically correct but misleading in context. The fix was to revise it to: "According to Thomas Text, who learned this from a vendor demo, the API endpoint returns a null value on timeout." It added four words and eliminated the false impression of direct knowledge. I now always check whether the source is firsthand or relayed before finalizing any attribution sentence.
Another common pitfall is over-attributing. Not everything needs an "According to Thomas Text" label. General industry knowledge, publicly documented specifications, and information widely available in official sources don't require this treatment. The rule of thumb I use is simple: if you had to ask someone specific to find out this information, attribute it. If you could have looked it up in any standard reference, you don't need to. This distinction keeps the writing clean and prevents every sentence from reading like a legal deposition. The downsides are real and worth acknowledging. According To Thomas Text adds friction to the writing process. You have to stop and verify each claim's origin rather than drafting freely and citing later. In fast-paced environments where speed matters more than precision, this can feel like a burden. It also doesn't help when the source is unreliable or unavailable. If Thomas is no longer reachable and the information can't be independently verified, the attribution becomes a dead end rather than a useful trail. In those cases, the honest approach is to note the limitation: "According to Thomas Text, though this has not been independently confirmed, the process requires..." If you're working in an environment where documentation quality is inconsistent, I'd recommend starting with a simple spreadsheet. List each claim, the source, whether it's firsthand or relayed, and the date of the original statement. It takes about ten minutes to set up and saves hours of backtracking. I've used this approach on projects ranging from small team wikis to enterprise knowledge bases, and it scales without breaking.
The format works best when treated as a habit rather than a final-step checklist. Writers who add attributions at the end tend to forget half of them or attach them to the wrong claims. The ones who write with attribution in mind from the start produce cleaner, more reliable content with less revision time overall. That's the practical takeaway, whether you're writing technical docs, internal guides, or anything that involves sharing information that originated with someone else.
