{"id":405,"date":"2026-08-17T04:57:20","date_gmt":"2026-08-17T04:57:20","guid":{"rendered":"https:\/\/texttoolz.com\/blog\/?p=405"},"modified":"2026-08-17T04:57:42","modified_gmt":"2026-08-17T04:57:42","slug":"clear-brain-lab-review","status":"publish","type":"post","link":"https:\/\/texttoolz.com\/blog\/clear-brain-lab-review\/","title":{"rendered":"Clear Brain Lab Review: Six Free Tools That Tell You What They Cannot Measure"},"content":{"rendered":"

The most interesting thing about Clear Brain Lab is not what its six tools calculate. It is that every one of them publishes a block explaining what it cannot tell you, including an explicit statement that it does not measure cognitive performance.<\/strong><\/p>\n

A free tool volunteering that limitation is giving up the exact claim that would make it sound more impressive. That is rare enough to be the reason this review exists.<\/p>\n

Disclosure first, because a review that buries this is not a review. These tools arrived as an unsolicited email submission on 16 August 2026, from a company called Portfolio Studio, which stated explicitly that no paid placement was requested. None was made. No money changed hands in either direction.<\/p>\n

How this reached us, and what we did and did not check<\/h2>\n

The submission proposed six browser-based tools for editorial consideration, named three of them, and said screenshots and production metadata were available from the live pages. It described the suite as requiring no account, processing inputs client-side, and explaining each calculation and limitation.<\/p>\n

Those are testable claims rather than adjectives, which is the main reason we took the submission seriously enough to spend time on it.<\/p>\n

What we did: fetched every page in the suite that was named, plus the company’s own site, plus six comparable tools and guides that rank for this category. Read the markup of one tool page directly to check the client-side claim rather than repeat it.<\/p>\n

What we did not do: run the tools against real calendar data, compare their outputs against other calculators on identical inputs, or verify that the arithmetic inside them is correct. This is a review of what the product publishes and what its code does. It is not a validation of its numbers, and the section near the end says so again.<\/p>\n

What Clear Brain Lab actually is<\/h2>\n

Six browser-based instruments, which the site groups into Measure, Understand and Improve, each carrying an identifier from CBL-001 to CBL-006.<\/p>\n

They are the Workday Fragmentation Analyzer, the Notification Load Audit, the Communication Overload Analyzer, the Attention Residue and Switch Planner, the Meeting Consolidation Simulator, and the Browser Workspace Fragmentation Analyzer.<\/p>\n

The suite is published at clearbrainlab.com<\/a>. The input model is the same throughout and it is worth understanding before anything else, because it determines what the outputs can mean. You type estimates. The tool performs arithmetic on them and returns a structured view of your current pattern plus a before-and-after scenario for a practical alternative. Nothing is imported and nothing is measured for you.<\/p>\n

The site is direct about this in its own words: no accounts, no imported calendars, no browser history, and no private message content. What you get out is a function of what you type in, which is both the limitation and, as the next section argues, the entire point.<\/p>\n

The choice nobody in this category explains<\/h2>\n

Every tool that measures workday fragmentation sits on one side of a single line, and no page in this category presents that line as a decision the reader gets to make.<\/p>\n

On one side is integration. Worklytics, Multitudes and Flowtrace measure your actual calendar, and to do that they need access to it. Multitudes states the requirement outright in its documentation: you need to integrate with Google. What you get back is real data about real meetings, because the tool read them.<\/p>\n

On the other side is estimation. The free calculators, including this one and the comparators named later, ask you to type what you think your week looks like. Nothing connects to anything.<\/p>\n

The trade is exact and it goes both ways. Integration buys accuracy and costs calendar access. Estimation buys privacy and costs precision.<\/strong><\/p>\n

Which one is right depends entirely on why you are asking. Someone building a case to their manager about team meeting load needs data their manager will accept, and typed estimates will not survive that conversation. Someone privately working out whether their own week is as broken as it feels does not need calendar-grade accuracy and may strongly prefer not to authorise a third party to read six months of meeting titles.<\/p>\n

We checked the privacy claim against the code<\/h2>\n

Every free tool in this category asserts that your data is safe. None of the comparators checks anyone’s claim, including its own. So we read the page source, which is a narrower thing than running the tool and is described precisely below.<\/p>\n

On 17 August 2026 we fetched the Workday Fragmentation Analyzer page and examined its markup. The findings were consistent and easy to state.<\/p>\n

The form on the page carries no action attribute<\/strong>, which means it has no destination to submit to. There are zero fetch calls<\/strong> and zero XMLHttpRequest references<\/strong> anywhere in the page or in the payload underneath it. Seven JavaScript bundles load, all from the site’s own domain.<\/p>\n

In plain terms: there is no mechanism present on that page to send what you type anywhere. That is the strongest support a claim of this kind can get short of watching network traffic during a session, and it is more than any comparator offers about itself.<\/p>\n

There is one thing the submission did not mention, and a reader should have it. The site loads Plausible Analytics<\/strong>, from plausible.io. It is the only external host the page references, aside from a schema vocabulary URL that is not a request at all.<\/p>\n

Being fair about what that means: Plausible is a cookieless, privacy-focused analytics product that does not collect personal data, and its presence does not contradict the claim that your inputs are processed in your browser. Those inputs still are. But somebody told that a tool “processes inputs client-side” would reasonably infer no third parties at all, and that inference would be slightly wrong, so it is stated here.<\/p>\n

The six tools<\/h2>\n

All six share an input model, a methodology block and a before-and-after structure, so the differences between them are about what they choose to count rather than about how they work.<\/p>\n

What this section cannot tell you is whether any of the numbers are accurate, which is dealt with near the end.<\/p>\n

Workday Fragmentation Analyzer (CBL-001)<\/h3>\n

You enter meetings, communication load and context boundaries, and it returns how much genuinely available focus time your day contains.<\/p>\n

Fragmentation rather than total meeting hours is the right frame here, and Multitudes supplies the concrete threshold that makes it legible. In its documentation, focus time is a block of two hours or more, and a gap between meetings shorter than that counts as fragmented time rather than as focus time.<\/p>\n

Apply that and the arithmetic becomes obvious. Two hours of meetings placed badly, one at 10am and one at 2pm, can leave a day with no qualifying focus block at all. Three hours of meetings stacked back to back can leave a clean four-hour afternoon. The total is identical and the usable output is not remotely.<\/p>\n

The tool describes schedule structure and says so, disclaiming any measurement of cognitive performance. It is telling you the shape of your day, not how well your brain worked in it.<\/p>\n

Best for someone whose calendar looks survivable when totalled and does not feel survivable when lived. The limitation is inherent to estimation: if you misremember your meeting pattern, you get a precise answer about a week you did not have.<\/p>\n

Notification Load Audit (CBL-002)<\/h3>\n

This one measures interruption volume across your channels and then lets you model practical notification-reduction scenarios against that baseline, rather than simply reporting the total back to you.<\/p>\n

The scenario half is worth more than the measurement half, and that is not a criticism. Knowing you receive a great many notifications is not information; you already knew. Seeing what happens to the total when you turn off one specific channel is a decision aid, because it converts a vague sense of being overwhelmed into a comparison between two options.<\/p>\n

Be honest about the input problem, because this is the tool where it bites hardest. Notification counts are the least reliable thing on this list to estimate from memory. People routinely underestimate the small ones and overestimate the annoying ones, and nothing in the tool corrects for that.<\/p>\n

Its own limitations block concedes the general version of this: self-reported approximations cannot capture urgency or task difficulty. A notification that matters and one that does not are counted identically.<\/p>\n

Best for someone deciding which channel to switch off first. Considerably less useful for quantifying a problem you already feel, where the number you produce will mostly reflect the mood you were in when you typed it.<\/p>\n

Communication Overload Analyzer (CBL-003)<\/h3>\n

This maps the number and complexity of the systems that continuously require your monitoring.<\/p>\n

Counting systems rather than message volume is a better proxy than it first appears. Each additional tool carries a checking habit, and that habit exists whether or not the tool is carrying traffic that day. Five quiet systems still cost five checks, and the checking is the interruption.<\/p>\n

It sits close to the Browser Workspace analyzer and the two are best read together, since they measure adjacent things from different angles: one counts the systems you are responsible for, the other counts the contexts currently open in front of you.<\/p>\n

Best for teams that have accumulated tools faster than they have retired them, which is most teams, and for anyone building a case that consolidation is worth the migration pain.<\/p>\n

The limitation is weighting. A system checked twice a day and one checked twice a month contribute similarly unless the person typing reflects that difference in their own estimates, and the tool does not prompt for it. That matters most for the organisations this tool suits best, since a long tail of rarely-touched systems is exactly what accumulates when nothing is ever retired.<\/p>\n

Attention Residue \/ Switch Planner (CBL-004)<\/h3>\n

This one has a name that makes a claim, so it deserves the most careful handling of the six.<\/p>\n

What it does is concrete: it turns unfinished contexts into explicit closure and resumption cues before you switch away from them. You describe the switch, and it produces the structure of a handover to your future self.<\/p>\n

The underlying idea, stated plainly and without overclaiming, is that leaving a task unfinished leaves something behind that makes the next task harder to start, and that the practical response is writing a deliberate note about where you stopped and what happens next, rather than trusting recall.<\/p>\n

What the tool does not assert is as important as what it does. Its methodology block explicitly disclaims measuring cognitive performance, and describes its outputs as schedule structure and its labels as fixed thresholds rather than diagnoses or population norms. A tool named after a cognitive phenomenon declining to claim it measures one is unusual and is to its credit.<\/p>\n

Best for people who switch contexts on someone else’s schedule rather than their own, where the switch is not a choice and the only controllable part is the handover.<\/p>\n

Meeting Consolidation Simulator (CBL-005)<\/h3>\n

This tests what happens if meetings are grouped rather than scattered across the week.<\/p>\n

Flowtrace supplies the sharpest caution in the entire comparator set, and it applies directly here: a meeting-free day can look like a success while the meetings simply move to other days, leaving the weekly total untouched and the other days denser. The measure that matters is the shape of the whole week, not the count on the protected day.<\/p>\n

A consolidation simulator is precisely the tool that can expose that displacement, provided the person using it models the entire week rather than only the day they are hoping to protect. Used on a single day it will tell you what you wanted to hear.<\/p>\n

Best for anyone about to propose a no-meeting Wednesday, and worth running before the proposal rather than after, since the version that survives contact with colleagues is the one that shows where the meetings go instead.<\/p>\n

The limitation is that it models schedule shape and cannot model endurance. Five consolidated meetings in one block and five scattered meetings occupy the same hours, and they are not the same day to sit through.<\/p>\n

Browser Workspace Fragmentation Analyzer (CBL-006)<\/h3>\n

This measures the work contexts and open loops represented by your current browser workspace.<\/p>\n

It is the most immediately legible of the six, and for a reason that solves the problem the other five have. Tab count is not an estimate. It is a number you can read off your own screen right now, which removes the recall guesswork entirely and makes this the honest place to start with the suite.<\/p>\n

It also frames tabs correctly. They are treated as proxies for open loops, unfinished contexts you have not closed, rather than as clutter to be ashamed of. That is a considerably more useful reading than tab-count shaming, and it connects the measurement to the same closure idea the Switch Planner is built on.<\/p>\n

Best for a quick and honest reading with the least guesswork involved, and a sensible first tool to try before deciding whether the estimate-based ones are worth your time.<\/p>\n

The limitation is that a tab is a weak proxy. Twenty tabs belonging to one research task is a completely different state from twenty tabs belonging to twenty tasks, and the count alone cannot distinguish them.<\/p>\n

The best thing about it is a disclaimer<\/h2>\n

Every tool page carries an identical block headed “Transparent by design”, separating direct inputs, derived outputs, qualitative labels and limitations.<\/p>\n

The content of that block is the reason this review is favourable. Estimated block sizes, it says, “describe schedule structure, not cognitive performance”. The qualitative labels are “documented fixed thresholds used only to make relative load easier to scan” and are “not diagnoses, performance ratings, or population norms”. And the limitations are stated rather than implied: self-reported approximations “cannot capture urgency, task difficulty, individual preferences, or the quality of a meeting or communication”.<\/p>\n

Consider what is being given up there. A tool in this category could very easily imply that it measures your focus, your productivity or your cognitive load, and many adjacent products do exactly that. This one explicitly declines the strongest available claim about itself, in the same visual weight as its results.<\/p>\n

Now the qualification, because a review that only praises is an advertisement.<\/p>\n

That block is identical, word for word, on all three tool pages examined.<\/strong> It is a suite-level disclosure rather than a per-tool methodology. The submission described the suite as explaining “each calculation and limitation”, and what is actually published is one general statement of limitations repeated six times.<\/p>\n

That overstates it. The disclosure is still better than the category norm by a wide margin, and it would be better again if the Notification Load Audit named the specific weakness of recalled notification counts, or the Browser Workspace analyzer named the twenty-tabs-one-task problem, instead of both pointing at the same generic paragraph.<\/p>\n

Who is behind it<\/h2>\n

The tools were submitted to us by Portfolio Studio, which is also the company that publishes them, and that relationship is worth setting out plainly rather than leaving in a footer.<\/p>\n

The same company sells a separate paid service: an AI Visibility Checkup at a published price of $485 per business, delivered within five business days. That is a different product on a different domain, and it is not what this review covers.<\/p>\n

Stated without insinuation, because there is nothing improper here: the tools reviewed on this page are free, require no account, and the company that publishes them has a commercial product elsewhere. Somebody deciding whether to type estimates about their working week into a free tool is entitled to know who publishes it and what else that publisher sells.<\/p>\n

The alternatives<\/h2>\n

These are named without being ranked, because we ran no head-to-head comparison and any ordering here would be a preference presented as a finding.<\/p>\n

In the estimation half of the category, alongside this one: em-tools.io publishes a focus time calculator aimed at engineering managers, ucals.com publishes a focus time audit, and meetingtoll.com publishes a meeting productivity calculator. Reclaim.ai publishes a meeting cost calculator, which is a lead magnet for its scheduling product, and that is context rather than criticism.<\/p>\n

In the integration half: Worklytics, Multitudes and Flowtrace, all of which measure real calendar data and all of which require access to it.<\/p>\n

The useful way to choose between any of them is not a feature comparison. It is the question in the earlier section: do you need numbers that will survive being shown to someone else, or do you need an honest private reading without authorising anything to read your calendar? That answer eliminates half this list immediately.<\/p>\n

What this review cannot tell you<\/h2>\n

Whether the numbers are right, which is the question a reader most wants answered and the one this review is least able to settle.<\/p>\n

We did not run the tools against real calendar data, did not put identical inputs through several tools to compare their outputs, and did not check the arithmetic inside any of them.<\/p>\n

It is worth being clear that this is a gap in the whole category rather than in this product. No tool examined for this review, including every comparator named above, publishes a validation study.<\/strong> Nobody in this space has demonstrated that their fragmentation figure corresponds to anything measurable about a real working week. That is a striking absence in a category built entirely on producing numbers.<\/p>\n

What would change it is not complicated: the same week run through several of these tools, or a comparison of one tool’s output against a real calendar export. Neither exists publicly and neither was done here.<\/p>\n

How this review was built<\/h2>\n

Eleven pages were extracted on 17 August 2026 with no failures: five belonging to the product and its publisher, and six comparators drawn from the search results for this category. One tool page had its markup inspected directly to test the client-side claim. Keyword research was run against Google’s autocomplete, which publishes no search volume, and none is quoted here.<\/p>\n

One correction is worth recording, because it nearly became a published error and it is the reason this review mentions Plausible at all.<\/p>\n

The first inspection used a crude pattern match and reported that the page loaded no external JavaScript and referenced no third parties. It also flagged two words as possible analytics tools. Both readings were wrong. The scripts on this site are injected through an escaped payload rather than written as ordinary script tags, so the pattern missed them entirely, and one of the two flags was a false positive caused by internal framework naming.<\/p>\n

Only unescaping that payload produced the true list of external hosts, which contained exactly one: plausible.io. Had the first result been trusted, this review would have told you the page contacts nobody, and that would have been false.<\/p>\n

Frequently asked questions<\/h2>\n

These are the questions people search about tools in this category, answered from the product’s own pages and from the comparators named above.<\/p>\n

What is Clear Brain Lab?<\/h3>\n

A free set of six browser-based tools for examining workday fragmentation, notification load, communication burden, attention switching, meeting concentration and browser workspace fragmentation. You type estimates and it returns arithmetic and a before-and-after scenario. No account is required.<\/p>\n

Does it need access to my calendar?<\/h3>\n

No. It imports nothing: no calendar, no browser history, no message content. That is the trade this category is built on, and it means you get privacy at the cost of the precision that comes from a tool reading your real meetings.<\/p>\n

Does it send my data anywhere?<\/h3>\n

We found no mechanism on the tool page to do so: no form destination, no fetch calls, no XMLHttpRequest. The page does load Plausible Analytics, a cookieless analytics product, which the submission did not mention and which does not affect how your inputs are handled.<\/p>\n

What actually counts as a focus block?<\/h3>\n

Multitudes defines it as two hours or more, with any meeting-free gap shorter than that counting as fragmented time instead. That threshold is why meeting placement matters more than meeting totals, and it is the clearest published definition found in this category.<\/p>\n

Who publishes these tools?<\/h3>\n

Portfolio Studio, which submitted them for editorial consideration and stated that no paid placement was requested. The same company sells a separate paid assessment service at a published $485. The tools themselves are free and require no account.<\/p>\n

Are the numbers accurate?<\/h3>\n

Unknown, and not only for this tool. No product examined for this review publishes a validation study showing its output corresponds to a real working week. Treat any figure from any tool in this category as a structured way to think, not as a measurement.<\/p>\n","protected":false},"excerpt":{"rendered":"

The most interesting thing about Clear Brain Lab is not what its six tools calculate. It is that every one of them publishes a block explaining what it cannot tell you, including an explicit statement that it does not measure cognitive performance. A free tool volunteering that limitation is giving up the exact claim that […]<\/p>\n","protected":false},"author":1,"featured_media":407,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-405","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business"],"_links":{"self":[{"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/posts\/405","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/comments?post=405"}],"version-history":[{"count":1,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/posts\/405\/revisions"}],"predecessor-version":[{"id":406,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/posts\/405\/revisions\/406"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/media\/407"}],"wp:attachment":[{"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/media?parent=405"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/categories?post=405"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/texttoolz.com\/blog\/wp-json\/wp\/v2\/tags?post=405"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}