§6B(l) makes MBI records public. §12(h) must actually exempt each record. Notes ¹²³⁴ below.
Lab note · Draft research tool · Under revision
This is dense working analysis kept here as a research artifact. The flowchart is being rewritten for general readers; until then, treat it as a working draft. The clean public-facing version of this question lives in the MassTech custodian spotlight.
MBI (§6B) administers BEAD broadband grants.
§6B(l) (exact text):
"Records pertaining to the activities of the institute shall be subject to section 10 of chapter 66, unless exempted under subsection (h) of section 12."
Default = public. §12(h) must actually exempt.
What entity does §12(h) cover?
"The corporation" in §12(h) = ?
"As used in this section:
(ii) 'Corporation' means the Massachusetts Centers of Excellence Corporation"
Not MTPC. Not MBI. Not "MassTech."
This is §12(h)'s own definition.
If MBI were a §12(e) center, why did the Legislature create §6B (St. 2008, c. 231)?
None of this is how §12(e) works.
Ross (Dec 23 p.2): MBI is "a division of MTC." But §6B(b) creates MBI by statute — own board (§6B(c)), own fund (§6C). Not a "division." A statutory entity.
Ross then quotes MBI's own website:
"the Massachusetts Broadband Institute (MBI) opened the...solicitation"
→ MBI opened it. Not MTC. Ross's own source contradicts "division of MTC."
Saubermann: 20 pages of redactions. Every one says "MassTech." Never "MBI." Never cites §6B. Never explains why MTC — not MBI — renders broadband assistance.
"The revenues and fund balances for each of the divisions are restricted for that division's programmatic purpose."
MassTech told the federal government — in a sworn $45.4M grant application — that MBI's funds are restricted to broadband. If broadband is a separate restricted program, it is not "assistance which [MCEC] is empowered to render."
MassTech made the same representations to NTIA in its BEAD Initial and Final Proposals — describing MBI as the entity administering BEAD, with its own board and restricted fund.
WHY THIS MATTERS — THE SHORT VERSION
§12(b): "a body politic and corporate...the Massachusetts Centers of Excellence Corporation"
§12(a)(i) defines "Center of Excellence":
"a collaborative effort between private industry and one or more educational or research institutions"
§12(e) names 4: Polymer · Biotech · Marine · Photovoltaics. All education/research partnerships.
BEAD grants ISPs to build infrastructure — no educational institution is involved.
§12(h) protects info re "assistance which the corporation is empowered to render"
§12(c)(13): "establish centers pursuant to the provisions of this section"
§12(c)(20): "purposes of this section"
MCEC's only mandate = Centers of Excellence.
§12(e) expansion clause requires:
BEAD = ISPs building broadband infrastructure. Not education. Not research. Not training. This test is impossible to satisfy.
§6B(b): MTPC "shall establish" MBI.
§6B(c): MBI has own board (9 members):
Sec. of A&F, Sec. of Econ Dev (chair), Telecom commissioner, MTPC exec dir, JAII chair, + 4 gubernatorial appointees.
§6C: MBI has own fund (Broadband Incentive).
§6B(d): MBI makes grants "subject to conditions established by the board."
MBI board — not MTPC — sets grant terms. MCEC has no role in broadband. Zero.
§3: creates MTPC — "body politic and corporate"
§12(b): creates MCEC — "body politic and corporate"
Two separate entities. Still in the statute.
No dissolution. No merger. No succession. "MassTech" is a trade name — not in the law.
§12(a)(ii) has never been amended.
§1(13): even MTPC's expansion requires "educational centers" for "other technologies."
Same educational prerequisite as §12(e).
PRODUCE.
§12(h) = MCEC
Centers only.
Not BEAD.
Does §4C(a) override the §12(a)(ii) definition?
Ross claims yes. Read §4C(a) →
§4C(a) extends §12(h) to MTPC/MassTech.
"The corporation" in §12(h) = MassTech.
Ross never cites §12(a)(ii). Never addresses MCEC definition. ³
"The provisions of section twelve (h) of this chapter shall be deemed to apply to any and all proprietary information received by the corporation"
✓ "Deemed to apply" = import as-is ¹
✗ Does NOT say "definitions amended" ²
✗ Does NOT say "corporation = MTPC" ²
"Corporation means the Massachusetts Centers of Excellence Corporation"
This IS the §12(h) definition. Unchanged.
§4C(a) never rewrites it. ³
PRODUCE.
Definition =
MCEC. Not
rewritten.
Even if remapped to MTPC — does §4C(a) reach broadband?
§4C(a) added ~1993 for semiconductor firms.
§6B (broadband) added 15 years later (2008).
§2 defines "participating business":
"research, development, design, production or assembly of semiconductor or microelectronics products"
ISPs applying for BEAD grants are not semiconductor/microelectronics firms.
PRODUCE.
Wrong program.
Is this "proprietary information"?
(§4C(a)'s own threshold)
BEAD BOB solicitation is a public document.
Templates designed by MBI (gov't forms).
Content mandated by federal BEAD rules.
9 of 11 applicants did NOT request confidentiality despite an explicit option in the solicitation to do so.
The remaining 2: MassTech has not produced the requests, not identified the applicants, not shown pre-submission timing, and not produced any written General Counsel determination — the solicitation's mandatory steps. No proof of perfection = no valid claim. Phipps Products Corp. v. MBTA, 387 Mass. 687 (1982); Datatrol Inc. v. State Purchasing Agent, 379 Mass. 679 (1980).
PRODUCE.
Not proprietary.
"Trade secrets"? (§12(h) prong 1)
Even if entity test is passed:
Requires "reasonable efforts to maintain secrecy." ⁴
9 of 11 applicants didn't request confidentiality. No effort = no secret.
The 2 who allegedly did: MassTech has never produced the requests, never identified which applicants filed them, never shown pre-submission timing, and never produced the required written General Counsel determination. The solicitation required all of these steps to perfect a confidentiality claim — MassTech has not proven any were completed.
Mandatory procurement procedures must be followed exactly. Phipps Products Corp. v. MBTA, 387 Mass. 687, 691-92 (1982); Datatrol Inc. v. State Purchasing Agent, 379 Mass. 679, 699 (1980). MassTech cannot retroactively manufacture confidentiality where the solicitation's own process was not followed.
PRODUCE.
No secrecy efforts.
"Commercial or financial info re: operation of any business"? (prong 2)
Even if entity test is passed — is this "commercial"?
CIR v. USDOL (9th Cir. 2025): "commercial" = bought/sold OR exchange for profit.
BEAD apps = proposed use of public funds. Not "operation of business."
§12(h) doesn't define "commercial." MA courts haven't either. Federal FOIA Exemption 4 uses identical language.
PRODUCE.
Not commercial.
"Competitive position of such applicant"? (prong 3)
Even if entity test is passed:
BEAD grant-award competition is over. Awards made.
Must show concrete post-award harm, not hypothetical market competition.
PRODUCE.
No concrete
harm shown.
"Each exemption to each portion"?
950 CMR 32.06
SOR ORDERED Dec 31:
"must clarify" how info = trade secrets or commercial.
Specific justification required for each exemption applied to each portion of each record.
WHAT MASTECH ACTUALLY DID (Jan 15):
Saubermann responded with the same templated formula for every file across all 11 applicants:
"financial information regarding the operation of a business by an applicant for any form of assistance which MassTech is empowered to render"
No per-portion analysis. No explanation of why specific content within each file qualifies. Entire files withheld where partial redaction was plainly possible.
The unit of analysis is the portion, not the document. Reinstein v. Police Comm'r of Boston, 378 Mass. 281, 289-90 (1979): "the statutory exemptions are narrowly construed and are not blanket in nature." G.L. c. 66 §10(a) requires an agency to "permit inspection of the non-exempt portion"; 950 CMR 32.06 defines the work as redacting exempt data from non-exempt material — element by element within the record, not record by record.
Copy-pasting one sentence across 500 files is not per-portion analysis. It is blanket withholding — exactly what Reinstein forbids.
PRODUCE.
Burden not met.
Records "made or received by" EOED? (c. 4 §7 cl. 26)
EOED = federal grantee (Ross Dec 23 p.2).
MassTech = EOED's "subrecipient."
EOED "made or received" these records as the responsible federal grantee. That is sufficient under c. 4 §7 cl. 26 and G.L. c. 66 §10(a)(ii), which extends the obligation to records in the agency's "possession, custody, or control" — physical custody by a subrecipient does not defeat it.
See PETA v. Dep't of Agric. Resources, 477 Mass. 280 (2017) (exemptions narrowly construed; custodian must produce record-specific justification, not blanket assertions) and Bougas v. Chief of Police of Lexington, 371 Mass. 59 (1976) (presumption of disclosure; burden on custodian).
§12(h) is MassTech's exemption, not EOED's. EOED has the records "in control" via its federal-grantee oversight authority and cannot invoke another entity's confidentiality statute. Request from EOED directly.
PRODUCE
via EOED.
"Non-exempt, segregable portions"?
c. 66 §10(b)(iv)
SOR ORDERED Dec 31:
"must explain whether records can be redacted so segregable portions can be provided."
Entire files withheld. Not done.
PRODUCE w/
redaction.
Overbroad.
Even if §12(h) applied (it doesn't — see Q1-Q4 above), MassTech's Jan 15 response fails the substance and process tests for each record category. The SOR Dec 31 order required specific justification per exemption type; Saubermann responded with the same templated formula for every file.
7 applicants. MassTech produced only a blank template.
These workbooks use a standardized format for BEAD grant compliance. Every applicant filled in the same categories of fields as part of a government grant application process.
MassTech withheld the entire workbook for every applicant. Producing a blank template with no content is not a response — it is a refusal. MassTech has not explained why any specific entry in any specific workbook qualifies for exemption. A single templated sentence applied to all 7 files is not the per-portion, per-exemption analysis that 950 CMR 32.06 and the SOR's Dec 31 order require.
Exemption claimed: §12(h)/4C(a) — "financial information regarding operation of business"
SpaceX confirmed no sensitive info — GIS files fully produced. This concession undermines the blanket §26(n) claim for all other applicants' GIS files.
MassTech claims Exemption (n) — "internal layout and structural elements...likely to jeopardize cyber security." But proposed fiber routes for unbuilt networks are not "internal layout" of existing infrastructure.
If SpaceX's satellite network design isn't sensitive, why are terrestrial fiber routes?
Exemption claimed: §4 cl. 26(n) — cybersecurity/infrastructure security
2 non-publicly-traded applicants submitted internal P&L/balance sheets (2022-2024). These are the applicant's own corporate financials — not BEAD grant data.
Distinguish: internal company operating statements (may have legitimate confidentiality interest) vs. BEAD project budgets (government-mandated grant compliance data). MassTech treats both identically.
Internal P&L may warrant protection — but must still segregate non-exempt portions (company name, submission date, time period covered are not confidential).
Exemption claimed: §12(h)/4C(a) — "highly confidential financial information for a non-publicly traded company"
8 files across multiple applicants. These are project subarea budgets — breakdowns of how public BEAD funds will be spent by geographic area.
PSA = Project Service Area. These budgets describe spending of public money allocated by formula. The format is government-mandated.
Proposed spending of public grant funds is not "operation of any business." It's a public accountability document.
Exemption claimed: §12(h)/4C(a) — "financial information"
Saubermann acknowledged: "While it seems unhelpful to provide a performance bond letter from a financial institution while redacting the institution's name, the amount of the bond, and the terms of payment..."
She redacted: bank name, bond amount, payment terms. The produced documents are effectively blank. Saubermann herself concedes they are "unhelpful."
A performance bond's purpose is to guarantee public accountability. Redacting the guarantor and amount defeats the purpose. These are grant compliance instruments.
Exemption claimed: §12(h)/4C(a) — "commercial information (who the applicant banks with)"
7 files. 3 budget columns redacted per file: Administration/Misc, Pre-Construction, Construction costs per CAI location.
CAI lists identify schools, libraries, and community institutions that will receive broadband. The locations themselves were produced; only budget-per-location columns were redacted.
Per-location costs for connecting public institutions with public money — this is the core transparency interest. Not "competitive position."
Exemption claimed: §12(h)/4C(a) — "financial information regarding competitive position"
Includes network design narratives, budget narratives, technical approach descriptions. Varies by applicant — some wholly withheld, some partially redacted.
These narratives describe how applicants propose to deploy broadband using public funds. They were written specifically for a government grant application on government-designed forms.
Comcast's Compliance Approach was fully produced after Comcast confirmed it was releasable — proving the initial withholding was wrong. Same logic applies to other narratives.
Exemption claimed: §12(h)/4C(a) — "commercial information regarding competitive position"
W-9 forms produced with the Employer Identification Number redacted. Company name, address, business type, and signature were released.
EINs are public business identifiers, not confidential financial data. They are not SSNs and the identity-theft framing does not apply to them.
The same EINs MassTech redacted are already public:
Even the EIN redaction has no statutory basis on this record. There is no defensible redaction in the production.
The strongest version of MassTech's case is that §6B(l) (added 2008) cleanly imports §12(h) into MBI, regardless of how §12(a)(ii) defines "the corporation." Steel-manning this for the moment: even if a reviewer accepts that path, the withholding still fails on three independent grounds — each sufficient on its own.
Independent defeat #1 — Procedural perfection failure (Phipps / Datatrol)
The BEAD solicitation imposed mandatory steps to perfect a confidentiality claim: applicants had to submit written requests, pre-submission, with a documented General Counsel determination. 9 of 11 applicants did not invoke the process. For the 2 alleged requests, MassTech has not produced the written requests, has not identified the applicants, has not shown pre-submission timing, and has not produced the required General Counsel determination. Phipps Products Corp. v. MBTA, 387 Mass. 687 (1982) and Datatrol, 379 Mass. 679 (1980) require strict compliance with mandatory procurement procedures. No proof of perfection = no valid claim, regardless of what §12(h) covers.
Independent defeat #2 — G.L. c. 4 §7 cl. 26(g) carveout
Even assuming §12(h) reaches MBI, the general PRL exemption for trade secrets and commercial information (cl. 26(g)) contains an explicit carveout: "this subclause shall not apply to information submitted as required by law or as a condition of receiving a governmental contract or other benefit." BEAD applications are paradigmatic governmental-benefit submissions. Read in pari materia, the Legislature's baseline rule — that grant-application information belongs to the public — controls. A 1985 special exemption for pre-commercial R&D research collaborations cannot be stretched to swallow the general statute's explicit carveout for federal infrastructure grants.
Independent defeat #3 — Per-portion segregability failure (Reinstein)
Even if §12(h) applies AND has been properly perfected AND survives the cl. 26(g) carveout, MassTech must still meet the segregability standard. Reinstein, 378 Mass. at 289-90: "the statutory exemptions are narrowly construed and are not blanket in nature." G.L. c. 66 §10(a) requires inspection of "the non-exempt portion." MassTech withheld 44+ entire files using one templated sentence across all 11 applicants. That is the same blanket-withholding posture the SOR rejected in SPR15/0596 for the structural twin statute (c. 23J §2(k)). Concession: some portions of some applications may genuinely qualify as commercial — internal vendor pricing structures, applicant-developed cost build-ups. That doesn't authorize withholding the federally-templated forms, the public-match commitments, the public-procurement metrics, the EINs already published on SAM.gov, and the 30+ other content categories MassTech withheld wholesale.
The structural argument (Q1–Q5) and these three independent defeats are alternative paths to the same outcome. To win, MassTech would have to defeat the structural argument AND prove perfection of confidentiality requests AND defeat the cl. 26(g) carveout AND show per-portion segregability work for every file. To lose, the SOR need only agree with one.
A common pushback: "the SOR has never struck down §12(h) for MassTech, so the agency must be right." That gets the empirical record backwards.
No prior SOR ruling exists on §12(h) for MBI.
A query of all 30,000+ SOR determinations finds exactly one order citing G.L. c. 40J §12(h): the Dec 31, 2025 order in SPR25/3719 — the case this site documents. There is no third-party SOR precedent affirming §12(h) for MassTech, MBI, or any broadband program. The application of §12(h) to BEAD is genuinely a question of first impression.
The closest analog goes the other way.
G.L. c. 23J §2(k) is the structural twin of §12(h) — the same quasi-public confidentiality language, written for the Massachusetts Clean Energy Center instead of the Massachusetts Centers of Excellence Corporation. c. 23J §2(k) protects "trade secrets or commercial or financial information regarding the operation of any business conducted by an applicant for any form of assistance which the center is empowered to render" — verbatim the same construction as §12(h).
SPR15/0596 (Oct 6, 2015) — the Supervisor of Records rejected blanket withholding under §2(k):
"I find that the Center failed to satisfy its burden of explaining with specificity how the withheld documents, in their entirety, are exempt from disclosure under G. L. c. 23J, § 2(k). See Reinstein v. Police Comm'r of Boston, 378 Mass. 281, 289-90 (1979) (the statutory exemptions are narrowly construed and are not blanket in nature). Any non-exempt, segregable portion of a public record is subject to mandatory disclosure. G. L. c. 66, § 10(a)."
Same statutory architecture, same blanket-withholding posture, same Reinstein analysis. The same outcome should follow here.
No "quasi-public deference" doctrine.
The same SOR database contains only three orders that even use the phrase "quasi-public" — none of them establish a deference doctrine. The pattern across the records is the opposite: the SOR applies Reinstein narrow construction and requires per-portion specificity from quasi-public custodians on the same terms as anyone else.
Source: full-text query against the public SOR determinations corpus, 30,000+ orders. Methodology: case-insensitive regex match for "12(h)", "4C(a)", "23J", "quasi-public" combined with custodian filter for MassTech / MBI / MTC / MTPC / Massachusetts Clean Energy Center.
Beyond the substantive withholding, MassTech and outside counsel have run a parallel track of procedural pressure designed to make pursuing these records as expensive and time-consuming as possible.
1. Wiretapping accusation against the requester (Feb 12, 2026)
After the Dec 10, 2025 MassTech board meeting, board counsel sent written correspondence warning that if McCarter "did in fact record" the meeting, the wiretap statute (G.L. c. 272 §99) prescribes civil penalties.
Defeated by the open meeting law itself.
G.L. c. 30A §20(f) expressly permits any person to make an audio or video recording of an open meeting, subject only to written or oral notice to the chair at the start of the meeting. McCarter provided that notice. The wiretap statute does not reach activity the open meeting law expressly authorizes. AG OML determination 2025-112 (Rockland ZBA) confirms that identity cannot be a prerequisite for exercising §20(f) recording rights.
2. "Harassing" and "frivolous" labels in the fee and time-extension appeals
In the parallel fee and time-extension appeals (SPR25/3719, SPR26/0172, SPR26/0234), MassTech asked the SOR to find the underlying records requests harassing or frivolous and to relieve it of the obligation to produce.
SOR rejected every one.
The SOR rejected the harassment claim in the BEAD fee appeal; rejected claims that the requests were frivolous or harassing in SPR26/0172 (expanded BEAD fee appeal); and rejected the same theory in SPR26/0234 (GAP fee appeal), denying relief from the obligation to produce. After the harassment claim was dismissed, MassTech's outside counsel rate dropped from $750/hr to $25/hr.
The procedural cost is the point: SOR appeal orders run on a 5-business-day response clock. Each "harassment" filing forced an additional unscheduled response, often within 2-3 business days, derailing days of substantive work on each cycle.
3. Escalating fee demands
The fee estimate escalated from approximately $30,000 to $100,000 and then to $130,000 before the SOR capped it. Each escalation triggered a new appeal cycle.
4. Minutes that omit the dispute they are evidence of
The Dec 10, 2025 meeting minutes were approved on March 11, 2026 — three months after McCarter formally noticed (Jan 14, 2026 OML complaint) that they omitted the recording-notice exchange and the chair's attempt to bar him. The board approved them anyway, without correction.
5. Boilerplate withholding template — see Q10
The same single sentence — "financial information regarding the operation of a business by an applicant for any form of assistance which MassTech is empowered to render" — appears as the entire stated basis for hundreds of withholdings across all 11 applicants. That is not segregability analysis; it is a stamp.
Sources: MassTech board correspondence Feb 12, 2026; SOR orders in SPR25/3719, SPR26/0172, SPR26/0234; OML complaint filed Jan 14, 2026; OML supplement filed March 11, 2026; Saubermann redaction log (Jan 15, 2026).
The SOR's Dec 31 order required MassTech to explain whether records withheld in their entirety could be redacted to release segregable portions. The order cites Reinstein, 378 Mass. at 289-90: "the statutory exemptions are narrowly construed and are not blanket in nature." The separate fee and time-extension appeals are distinct proceedings — the SOR rejected the excess fee but the segregability obligation stands independently.
Saubermann's Jan 15 response fails this test across every category except W-9s: