Title 5 PDF Binary Requirements: What MA Boards of Health Look at Before Logging the Submission

By The Complos Team. Last reviewed 2026-05-14.

TL;DR. What the BOH actually checks in your Title 5 PDF before it gets logged: page count, signature embedding, attachment ordering, font embedding, PDF/A conformance. Inspector-level detail on why structural mistakes get reports bounced before the agent reads a word.

Before a MA Board of Health agent reads a single inspection finding, the PDF has to clear a structural check. The check is informal in most towns — the agent eyeballs the file in their reader, not a software validator — but the failure modes are consistent and they bounce reports more often than missing watershed notices do in the towns that have professionalized the most (Boston ISD, Cambridge, Worcester, Newton, Brookline).

This is the structural specification I run my own packets against. None of it is in 310 CMR 15.000 explicitly. All of it is what the receiving agent expects to see when they open your file.

Part of the MA Title 5 Inspection Complete Guide guide.

Page Count and Section Order

Title 5 inspection report is a 7-page document in the current MassDEP fillable revision (page 1 cover and certification, pages 2 to 6 system details, page 7 optional notes/continuation). A submission missing pages — typically because someone exported only the filled-in pages and skipped pages that look blank — gets bounced by any agent who knows the form.

The full packet, in order, is:

1. pages 1 to 7 of the Title 5 inspection report as the leading section, in order, no pages dropped even if they look empty.
2. Photo addendum with each photo labeled by component (Tank Top, Tank Inlet, Tank Outlet, D-Box Interior, SAS Surface at minimum).
3. Watershed compliance notice if the parcel is inside a Nitrogen Sensitive Area under 310 CMR 15.215. This is the document that gets forgotten most often.
4. Local bylaw addendum if the town has Article 51, a coastal-bylaw overlay, or other supplemental requirements (Falmouth, Wellfleet, Provincetown, Chatham, Truro all have these).
5. As-built drawing or sketch if available or required for the property class.

Out-of-order packets confuse agents who archive by section. Some towns paginate the archive and a misordered packet means the cover sheet shows up in the photo section, which gets flagged for re-submission.

Signature Embedding

The MassDEP attestation block on page 6 wants a real signature. Three things qualify:

• A flattened PNG of a hand-drawn signature, scanned or tablet-captured, embedded as an image in the form field.
• A digital signature with a visible appearance (Adobe Sign, DocuSign, Acrobat self-signed) where the certificate flattens into the PDF.
• A wet signature on paper, scanned at 300 DPI minimum, with the rest of the form filled digitally and merged.

Three things do not qualify:

• A typed name in a font that resembles a signature. Some inspectors do this and it gets flagged in maybe 1 in 5 towns.
• A signature on a separate cover sheet but blank on Title 5 inspection report. page 6 of the Title 5 inspection report needs the signature; the cover sheet is supplemental.
• An editable signature field that the agent can click and modify. Flatten the form before sending.

Font Embedding and PDF/A Conformance

Cambridge ePermits and Boston ISD prefer PDF/A-2 conformance. The MassDEP fillable form is not PDF/A by default. When it gets exported through standard "Save As" the fonts are usually but not always embedded.

The failure mode: agent opens the PDF on a city workstation that does not have the same font set, and the SAS notes field renders in a substitute font that overruns the cell or shows as boxes. Agent flags as "illegible" and bounces the report.

The fix is a one-click conversion in any modern PDF tool — Acrobat has "Save As Other > PDF/A," qpdf has --linearize and font-embedding flags, and most renderers default to embedded fonts now. If you are exporting through a generation pipeline, set font embedding to "all fonts always" not "subset on demand."

File Size and Compression

Most municipal mail servers cap inbound attachments at 25 MB. A Title 5 inspection report with embedded native-resolution iPhone photos can hit 35 to 50 MB. The mail bounces silently in some setups; the inspector ships and assumes delivery and the BOH never received the file.

Two safe practices:

• Compress embedded photos to 1500 px on the long side before embedding. The PDF size drops to 5 to 12 MB and the photos are still legible at the resolution the agent is reviewing.
• For portal submissions, keep the file under each portal's stated cap (Cambridge ePermits is 20 MB per file; Boston ISD is 50 MB total per packet split across files).

What the Agent Actually Opens On

This matters because it shapes what renders correctly. Most MA municipal workstations in 2026 are Windows 11 with Adobe Acrobat Reader DC or Microsoft Edge's built-in PDF viewer. A handful of towns are on macOS with Preview. None are using Linux pdf readers.

Edge's PDF viewer is the most fragile of the three for Title 5 inspection report. It sometimes drops form-field content if the PDF was generated by a non-Adobe pipeline. If you use a custom PDF generator (ReportLab, Prawn, wkhtmltopdf, anything that is not Adobe), test the output in Edge before shipping. Open it on a Windows machine and confirm every field renders.

Failure Mode I See Most Often

The the inspection report's SAS construction-and-condition field truncates silently at roughly 240 characters total when typed directly into the MassDEP fillable. Inspectors paste in a paragraph, the form accepts it visually, then on save-and-reopen the second half is gone. The agent reads a half-sentence and rejects for incomplete narrative.

Either type directly and proofread after saving and closing, or use a generation pipeline that flows the full string into a continuation page. Do not assume what you typed is what got archived.

Frequently asked questions

What's the short answer to "Title 5 PDF Binary Requirements: What MA Boards of Health Look at Before Logging the Submission"?

What the BOH actually checks in your Title 5 PDF before it gets logged: page count, signature embedding, attachment ordering, font embedding, PDF/A conformance. Inspector-level detail on why structural mistakes get reports bounced before the agent reads a word.

Who does this apply to?

NEIWPCC-certified Title 5 system inspectors in Massachusetts, FDEP-licensed septic contractors in Florida, SCDHS-permitted designers in Suffolk County NY, and the property owners these professionals serve.

Where can I read the underlying regulation?

Every Complos guide links to the source statute or rule in the body. MA Title 5: 310 CMR 15.000. FL HB 1379 / HB 1417. NY: Suffolk County Sanitary Code Article 19. Always confirm with mass.gov / flsenate.gov / suffolkcountyny.gov before acting.

How does Complos help with this?

Complos generates the regulator's exact PDF, validates the inspection against the local overlay, and tracks per-town submission methods so you don't ship the report into a black hole. Start a 14-day trial at complos.ai/signup.

How Complos helps

Complos generates Title 5 inspection report against the MassDEP fillable layout byte-for-byte where it matters: page count, section order, font embedding, PDF/A-2 conformance by default, and continuation flow for long SAS narratives. Photos are automatically resampled to 1500 px and the watershed notice is auto-attached when the parcel falls inside a nitrogen-sensitive zone. Run the Title 5 compliance checker to validate a packet's structure before submission, or look up your receiving BOH's PDF preferences by parcel.

Join our list for MA Title 5 inspection report format updates.