A Massachusetts lien takes three filings: a notice of contract (60 or 90 days), a statement of account (90 or 120 days), and a lawsuit within 90 days after the statement. The earliest triggering event controls each deadline.
Review invoices, committed costs, and cash timing together before making project decisions. AI-generated illustration.
Massachusetts General Laws Chapter 254 builds a mechanics lien in three steps, each with its own clock. First, record a notice of contract at the registry of deeds. Second, record a statement of account showing what is owed. Third, file a civil action to enforce within 90 days after the statement. Each filing deadline is the earliest of several dates, and the owner can shorten your time by recording a notice of substantial completion or termination.
Massachusetts lien deadlines at a glance (M.G.L. c. 254, sections 2, 4, 8, 11)
Step
Deadline (earliest of)
Where
Notice of contract
60 days after notice of substantial completion is recorded; 90 days after notice of termination; 90 days after your last labor or materials
Registry of deeds where the land lies
Statement of account
90 days after notice of substantial completion; 120 days after notice of termination; 120 days after your last labor or materials
Registry of deeds where the land lies
Civil action to enforce
90 days after filing the statement of account
Court
Notice of identification (optional, lower tiers)
Within 30 days of starting work, certified mail to the original contractor
Sent, not recorded
Who has lien rights in Massachusetts
Section 2 covers anyone with a written contract with the owner (or someone acting for or with the owner's consent) for labor, including construction management and general contractor services, or for materials, rental equipment, appliances, or tools. Section 4 extends rights to anyone working under a written contract with the contractor or with a subcontractor of the contractor, which reaches subs, sub-subs, and suppliers. Section 4 also covers people who perform professional services under those contracts.
The phrase written contract does real work here. A supplier selling on a phone order with no written terms has a weaker position. Get a signed credit application, PO acceptance, or subcontract on file before the first delivery.
Step one: the notice of contract
You can record a notice of contract any time after the written contract is signed, even before work starts. That is the smart move on large jobs, because the lien does not exist until the notice is recorded and, for subs, until the owner gets actual notice of the filing. The outside deadline is the earliest of 60 days after the owner records a notice of substantial completion, 90 days after a notice of termination, or 90 days after your last day of work or supply.
A sub's lien is capped at what is due or will become due under the original contract on the date the sub notifies the owner of its filing. A lower-tier claimant without a contract with the original contractor is generally capped at the balance under the subcontract that includes its work, as of when it files. That second cap falls away if the claimant sent the original contractor a written notice of identification by certified mail, return receipt requested, within 30 days of starting work. It is optional, but it is the closest thing Massachusetts has to a preliminary notice, and it is cheap insurance for a sub-sub or supplier.
Step two: the statement of account
Under section 8, the lien dissolves unless you record a statement of account by the earliest of 90 days after the notice of substantial completion, 120 days after the notice of termination, or 120 days after your last labor or materials. The statement must give a just and true account of the amount due or to become due, with all just credits, a brief property description, and the owners' names as set out in the notice of contract. It can be filed before the owner's notices.
Example: a mechanical sub on a $2.3 million Worcester lab fit-out last works on May 1. The owner records a notice of substantial completion on May 20. The notice of contract is due by July 19 (60 days after May 20, which beats 90 days after May 1). The statement of account is due by August 18 (90 days after May 20). Most subs assume 90 and 120 days from their last day and miss both.
Step three: suit within 90 days
Section 11 dissolves the lien unless a civil action to enforce it is commenced within 90 days after the statement of account is filed. That is a short window. Line up counsel when you record the statement, not after.
Lien waivers in Massachusetts
Section 32 voids contract terms that bar filing a notice of contract, bar enforcing a lien, or subordinate lien rights. The exceptions include a Partial Waiver and Subordination of Lien, which must be substantially in the statutory form with no material deviation. It waives rights for work through the payment period on receipt of the stated payment, excluding retainage, unpaid change orders, and disputed claims, and subordinates rights to the lender's advances through the 25th day after the period. It is signed under penalties of perjury. A GC handing subs a custom lien waiver that waives more than the statute allows is creating an unenforceable document.
Residential work
The Chapter 254 sections covered here apply the same notice of contract and statement of account steps to residential and commercial work, with no separate homeowner track in their text. The practical protection for homeowners is the cap tied to the amount still owed under the original contract when the sub gives notice. Check the full chapter and the owner's situation before filing against an owner-occupied home.
Public projects use payment bonds
Public property cannot be liened. Under M.G.L. c. 149, section 29, public construction contracts over $25,000 require a payment bond of at least 50 percent of the contract price. A claimant with no direct contract with the bond principal must send written notice by registered or certified mail within 65 days after last furnishing labor or materials, and must file suit within one year after its last work.
How long do I have to file a mechanics lien in Massachusetts?+
The notice of contract must be recorded by the earliest of 60 days after a notice of substantial completion, 90 days after a notice of termination, or 90 days after your last work. The statement of account follows by the earliest of 90, 120, or 120 days from those same events.
Does Massachusetts require a preliminary notice?+
No preliminary notice is required to have a lien. Lower-tier claimants can send an optional notice of identification to the original contractor within 30 days of starting work, which removes a cap on their lien amount.
How long does a Massachusetts lien last?+
The lien dissolves unless a civil action is filed within 90 days after the statement of account is recorded.
Can a subcontract waive my Massachusetts lien rights?+
Generally no. Section 32 voids advance waivers and subordinations, except for listed items such as the statutory Partial Waiver and Subordination of Lien given with a payment.
What is the payment bond claim deadline on Massachusetts public jobs?+
Claimants without a direct contract with the bond principal give written notice within 65 days after last furnishing labor or materials and sue within one year after their last work.
Laws and rates change. Confirm current requirements with the state agency before you bid, file, or pay. This page is general information, not legal advice.
Revenue can rise while cash, margin, and field control deteriorate. This Season 3 premiere builds a five-number Monday control room for construction decision-makers: 13-week projected cash coverage, margin fade, billing position, cost incurred on unapproved changes, and labor-hour variance.
The briefing maps the inputs, formulas, meeting cadence, red flags, human approvals, and automation workflow required to turn delayed reports into management alerts.
Starts muted when the player comes into view.
Read the full episode transcript
Published transcript from Scaling Legends. It may contain transcription errors. View the source transcript.
Welcome to this AI -assisted Scaling Legends decision briefing. We're bypassing the usual pleasantries today because, well, the financial data we're examining demands immediate attention. Yeah. On July 6, 2026, the Construction Financial Management Association documented a highly revealing operational scenario that, well, every executive needs to hear. Right. Consider a contractor holding a $2 million contract. They incurred $960 ,000 in costs. And they generate billings of $1 .3 million. Okay. So on the surface, that results, it looks like a pretty healthy $184 ,000 overbilling position. Right. Which, I mean, it feels like a comfortable place to be when you just look
at the cash in the bank, you see a positive position, and you assume the project is performing well. Yeah, it feels comfortable until you measure the consequence of what is actually happening in the field. So in this documented case, the revised cost to complete the project actually jumped to $1 .72 million. Oh, wow. Yeah, because of that hidden increase in cost, the project's margin faded by six full percentage points. And that structural blind spot is the core issue we are targeting today. So this briefing is produced by Smart Business Automator, a company that designs AI and automation systems for construction companies. We are directing this specifically to construction company owners, CEOs, COOs, CFOs, project executives, pre -construction leaders, and technology leaders. And please note, this session is for educational and informational purposes and does not constitute
professional, legal, or financial advice. Our mission today is to build a five -number Monday control room that turns delayed historical reports into forward -looking management alerts. And we need to assign that problem to the decision makers who actually own it. The responsibility for cash work in progress, project performance, and executive visibility, it rests squarely on the shoulders of the owners, the chief financial officers, and the chief operating officers. If those leaders are getting blindsided by a 6 % margin fade, well, we have to look at the manual process failure happening behind the scenes. In most operations, disconnected data creates the failure. Cash sits in the accounting software. Percent Complete lives in some static work -in -progress spreadsheet that gets updated maybe
once a month. If they're lucky. Yeah, right? Billings are locked in separate pay applications. Pending changes get lost in email threads or project management software. And the explanations for all of this are buried in text messages from the field. The information exists to prevent that margin fade, but it is entirely fragmented. And let us be honest about those text messages. They usually just say something vague like weather was bad or waiting on materials followed by a thumbs up emoji. That does not help a CFO figure out how to pay the bank. Think of it like trying to drive a heavy -duty truck, where the speedometer, the fuel gauge, and the check engine light are all located in different zip codes. By the time the owner learns about a margin fade or labor burn, the company has already funded the problem. The money is gone before the report is even generated.
Which brings us to the systematic exception management layer required to fix it. We aren't talking about replacing your accounting system or firing your controller. We're talking about connecting your existing data to isolate five specific numbers. So how do we fix the dashboard on this truck? We have to start with survival, which means securing the fuel tank. That is number one, your 13 -week projected cash coverage. Right. The U .S. Small Business Administration formally recommends disciplined cash flow projections as a fundamental part of managing a business. The calculation we use here is a specific formula. You take your lowest projected unrestricted cash during the next 13 weeks, and you divide that by your average weekly unavoidable cash outflow. So from a system's perspective, we map that into an automated workflow by connecting
specific inputs. The system needs to pull accounts' receivable aging expected payment dates, payroll calendars, recurring obligations, and purchase commitments. Okay. And then the rule engine updates this 13 -week view on a strict schedule. It flags any missing dates, identifies the specific week where cash dips to its lowest point, and compares that forecast to the prior week. And it is critical to define unavoidable cash outflow accurately here. This is not your operational wish list. It represents the absolute hard costs of keeping the doors open. We are talking about payroll and taxes because, well, you cannot skip paying your crews or the government. We are talking about debt service and equipment payments because the bank will repossess your fleet. And we must include committed materials because those purchase orders are already signed. I want to push back
on this calculation for a moment just to understand the logic. Why do we need the system to calculate a dynamic 13 -week ratio? Why not just set a universal safe cash threshold in the system, like trigger an alert when the bank account drops below $500 ,000? Because a static number provides zero context. A universal safe threshold simply does not exist in construction. Company -sized current credit facilities, the amount of retainage held by owners, your customer mix, and bonding requirements all change the answer. Oh, I see. Yeah. A million dollars in cash looks great on paper, but it is dangerously low if you have a $2 million payroll hitting in week three. The useful signals of the specific date of the lowest projected balance, whether the coverage ratio
is rising or falling over time, and identifying which specific delayed receipts or upcoming expenses are driving that low point. That makes total sense. Context is everything. So the automation route's an exception alert if a major customer payment slips by even a few days, or if a material commitment moves forward and unexpectedly compresses that ratio. The human action here is that the CFO or the owner must approve a specific response, whether that is a collections escalation, a billing correction, or a shift in expenditure timing. Spot on. Once survival is secured and your cash floor is established, the immediate next question for the leadership team is whether the jobs are actually generating the profit promised to the bank. Which brings us to the second number, projected margin fade. This is your financial GPS telling you if you are veering off course. Yeah, the
Construction Financial Management Association identifies the work -in -progress schedule as a vital view into projected job profitability. The formula for this second number is straightforward. Its original estimated gross margin percentage minus the current estimated gross margin percentage. From an automation standpoint, the system requires the original estimate, the current cost to complete forecast committed costs, actual costs, and approved changes. It recalculates the projected margin on a defined cadence and flags an exception if the margin falls beyond a company -defined tolerance. But let's break down the logic of how we view this. Why does the control room need to rank these jobs by gross profit dollars lost rather than just the percentage? Because percentages can be highly deceptive when comparing projects of different scales. Right. A CFO looking at
a spreadsheet might see a 1 % variance and think the company is safe completely ignoring the scale of the contract. A small percentage shift on a large contract creates far more financial risk than a large percentage shift on a tiny job. A 1 % fade on a $50 million project removes $500 ,000 in gross profit. A 10 % fade on a $100 ,000 project only removes $10 ,000. The control room must focus executive attention on the total dollars disappearing from the bottom line, not the ratios. So the system flags the largest dollar value, fades, and routes that exception directly to the project executive. The executive is then required to confirm the root cause within the system. They have to specify if it was reworked schedule compression, missed scope, or material
price escalation, and then document the recovery action. So if cash is clear and the projected margin is theoretically stable, we have to investigate how the cash is actually flowing in. The third number requires looking at the billing position. Under the cost -to -cost method, which aligns with the CFMA example we opened with, earned revenue equals the percent complete multiplied by the contract price. Hold on. Let's ground that math before we move forward. If my company is 50 % done with a $10 million job, I should have $5 million in earned revenue. If I have only billed $4 million to date, I am underbilled by $1 million. Is that the mechanism? That is correct. The billing position is simply the amount billed to date minus that earned revenue. A positive result is overbilling. A negative result is underbilling.
Automating this requires the contract value, the revised estimated costs incurred, and bill -to -date figures. The system calculates both the individual job and the overall portfolio positions, tracking the movement from the prior period. What is critical to understand here is that neither status is automatically healthy. Really? Yeah. Underbilling might reflect missed billing opportunities, slow pay application preparation, disputed quantities in the field, or changed work that is awaiting approval. Overbilling, while it improves working capital in the short term, might conceal margin fade or create severe future cash pressure if the management team treats that overbilled money. And we have to ask what typically causes those disputed quantities and delayed billings in the first place. That leads us directly to the fourth number cost incurred
on unapproved changes. The Associated General Contractors of America explicitly notes that delayed change orders significantly interrupt contractor cash flow. We must track changed work in three distinct buckets. Okay, what are the buckets? Priced and approved, priced and pending, and performed but not fully priced. The exposure number you review on Monday is the estimated cost already incurred in buckets two and three. The automation map for this is critical because it relies on highly time -sensitive data. We pull inputs from field instructions, requests for information, daily reports, cost entries, and the change log. The system creates the change record and begins calculating its age. More importantly, it watches the contractual notice deadlines. That is the pivotal function right there. Every pending item must contain the job identifier,
the amount incurred its age. the contractual notice deadline, the last documented communication, the decision owner, and the next action. You cannot count hoped -for markup as cash. You must track the actual cost your company is floating to finance the owner's design changes. If work starts without authorization in the system, or if a contractual notice date approaches without a formal submittal, the system generates an exception. The project executive or contract administrator receives an alert demanding a determination of the contractual response before the right to claim that cost expires. And if it's not an unapproved scope change draining the margin, the issue usually stems from the field execution itself. The fifth and final number is the labor hour variance. This is the check engine light flashing before the vehicle stalls. For self -performed work,
the formula is the budgeted hours for the completed quantity minus the actual paid hours for that completed quantity. A negative value means the actual hours exceeded the estimate for the amount of work put in place. Let's use a concrete example to translate that. Imagine a crew is pouring a foundation. The original estimate gave them 40 hours to complete that specific pour. They finished the pour, but the timesheets show it took 60 hours. From a financial perspective, it is vital to convert that 20 -hour variance using the company's burdened labor costs, not just the base wage. The financial impact must include taxes, benefits, and insurance to reflect the true cash burn. However, the purpose of tracking this variance is diagnosis. not automatic blame. That is a crucial distinction for the automation
workflow. If you just look at the timesheet, your first instinct might be to yell at the foreman. But if you dig into the why, the picture changes. If the variance exceeds a tolerance, or if the same constraint repeats across multiple days, the system flags it. The human action is for operations to investigate the root cause. Was there an estimating miss? Was the work area unavailable because a preceding trade was behind schedule? Was there a material delay, a supervision change, or an unrelated production target. Operations must actively identify and remove the constraint and then monitor the system to check if that intervention actually changes the variance in the following week. Now that we have detailed the five numbers, 13 -week cash coverage, margin fade billing position, unapproved change exposure, and labor variance, we have to implement a strict
meeting cadence to review them. This is the 30 -minute Monday control room meeting. We map this meeting schedule down to the minute to ensure it remains an exception management process rather than a generalized rambling status recital where everyone just says their projects are going fine. Minutes zero through five are dedicated solely to projected cash coverage and identifying the lowest cash week. Minutes 5 through 12 cover the three largest projected gross profit fades across the portfolio measured in dollars. Minutes 12 through 18 address the billing position and any assigned collection actions. Minutes 18 through 24 focus on unapproved change exposure and approaching contractual notice deadlines. Finally, minutes 24 through 28 review labor variance. And the final two minutes, minutes 28 through 30, are reserved for confirming an owner an action, a
due date, and a measurable success metric for every red item identified. This workflow requires three concrete actions to be completed after the meeting. First, the CFO or owner must approve a specific collections escalation or expenditure timing shift before cash coverage reaches a critical state. Second, the project executive must assign a specific contractual response for unapproved work before a notice deadline hits. Third, operations must actively remove one specific constraint causing labor variance and report back on whether it altered the data. The operating principle here is entirely based on exception management. Yeah. You show it changed, you demonstrate why it matters financially, you identify who owns it, and you dictate what happens next. Before a company can run this meeting, though, we have to address the reality of their data infrastructure.
There is one primary implementation risk that derails this entire process. It is the failure to normalize identifiers across different platforms. We frequently see companies where the timekeeping application, the product management software, and the accounting system all speak completely different languages. Oh, yeah. The job numbers do not match. The cost codes are structured differently, and the customer names are abbreviated in varying formats. If the timekeeping application says cost code 100, but the accounting software categorizes that exact same work as phase one concrete, the automation map breaks. The rules engine cannot compare the earned hours in the project software against the actual paid hours in their accounting ledger if the cost codes are misaligned. When the data fails to sync, the exceptions cannot
be routed to the responsible decision maker. Building this control room requires establishing a single source of truth for your data architecture first. Which brings us to the immediate action required from the leadership team. The move for the decision maker listening right now is to copy the companion scorecard provided with this briefing. Before your next leadership meeting, you must attempt to populate these five current values for your company. And if you find that a value is unavailable, or if it takes three days of emailing different departments to calculate it, I want you to physically mark that box not measured. then assign the name of the person responsible for producing it. The missing data is in itself a critical operating signal. It tells you exactly where your visibility is compromised. You cannot manage an exception if your reporting structure is incapable of identifying it in the
first place. Understanding your financial exposure on a delay of 30 days is simply documenting history. True control requires looking forward. We have a specific request for you regarding this material. Please send this briefing and the companion scorecard directly to the person who owns your company's Monday operating meeting. If you are the owner, COO, or CFO of a construction company and your team cannot assemble these five numbers without chasing spreadsheets and inboxes, Smart Business Automator can map the reporting and approval workflow with you. Request an executive reporting and workflow assessment at smartbusinessautomator .com. Again, that is smartbusinessautomator .com. The technical mechanics of building this dashboard are solvable, but the human element is what truly dictates success. Which leaves us with this final
thought to consider as AI and automation begin to calculate these five numbers flawlessly, the ultimate competitive advantage in construction will not be data collection anymore. It will be the psychological safety of your Monday meetings. If your project executives are still too afraid to report a margin fade in a room full of their peers, the best automated control room in the world will not save you. The system can only highlight the truth. Your culture has to be brave enough to act on it.
