Narrative, assumptions, a lag register and a health check against common thresholds accompany the baseline network in the MT381 Unit 10 submittal to an owner's representative. Searches like "mt 381 unit 10 assignment example", "mt381 unit 10 sample" and "mt381 unit 10 example" land here.
What a finished MT381 Unit 10 baseline schedule submittal looks like
A transmittal letter references 01 32 16, the specification section governing the progress schedule, and lists the enclosures. The narrative runs six pages: scope and sequence, the critical path from steel submittals to punch list, the near-critical power chain, calendars, weather assumptions, procurement lead times, submittal review at the ten working days Section 01 33 00 allows, and the treatment of the seven days between December 15 and December 27. An assumptions and exclusions list follows. The schedule itself arrives as a predecessor-successor report, a logic diagram and a bar chart sorted by area. The final pages hold a health check modeled on the Defense Contract Management Agency's fourteen-point assessment: open ends, leads, lags, relationship types, constraints, high float and high duration, each with a count, a percentage and a comment.
How a MT381 Unit 10 example is structured
Everything a reviewer needs to reproduce the dates appears before the dates themselves, so the narrative leads and the reports follow. The standard calendar works five days with nine holidays; the exterior calendar removes 28 anticipated lost days through the contract date, month by month, and the paper names the seventeen activities assigned to it. The early finish is addressed directly: the narrative labels the seven days project float, cites the float clause, and requests no compensation for finishing early. In the health check, finish-to-start ties make up 71.6 percent of the logic against a common 90 percent guide, and 32.1 percent carry lags against a 5 percent guide, because overlapping trades are modeled with paired start and finish ties that the lag register justifies. High-float and long-duration counts come almost entirely from procurement, which the narrative separates from field work.
Transmittal and enclosures
The letter cites Section 01 32 16, names the data date and the scheduling software used, and lists five enclosures so the reviewer can confirm nothing is missing before reading further.
Two calendars, month by month
The standard calendar has a five-day week and nine holidays. The exterior calendar removes four anticipated lost days in each of March, April and December, fewer in summer, 28 in all.
The early finish, labeled project float
Finishing on December 15, twelve calendar days before the contract's December 27, is stated plainly. The narrative treats the gap as shared project float under the contract's clause and asks nothing for it.
Departures from the health check, explained
Finish-to-start ties at 71.6 percent and lags on 32.1 percent miss common guides. Paired start and finish ties model overlapping trades, and the lag register gives each one a physical reason.
Procurement kept apart
Four procurement lines exceed 44 working days, and five activities hold more than 44 days of float, rooftop unit setting among them. Separating supplier time from field work keeps those counts from reading as padding.
Assumptions a reviewer can challenge
Crew sizes, production rates, submittal review periods, utility energizing time and the weather source are listed with their bases, so the owner's representative can dispute a premise rather than a date.
Where marks go in MT381 Unit 10
An owner's representative cannot accept dates without the assumptions behind them, so a bar chart sent with no narrative is the submittal most often returned in this unit. Expect scrutiny of calendars, weather treatment, procurement durations and submittal review periods stated in writing, each traceable to the specification or the scenario. An early-finish schedule presented without comment invites a later dispute over who owns the gap, so addressing it earns credit. Constraints standing in for logic, open ends and unexplained lags are the defects reviewers commonly screen for first. A health check reported only where it passes suggests selective reading; departures explained honestly score better than numbers massaged to fit. A submittal that cannot be reproduced from its own reports and settings invites rejection on procedure alone.
Get a MT381 Unit 10 example written to your instructions
A baseline submittal needs the finished network, or the scope your Unit 10 prompt defines, plus the contract dates, any specification language it quotes and the rubric. From those, the first submittal is prepared free within 24-48h, transmittal through health check, with each departure from common thresholds explained instead of hidden.
MT381 Unit 10 questions, answered
Can a baseline show completion before the contract date?
It can, but it should say so and explain how the gap is treated. Some owners reject early-finish baselines, fearing claims for delay to an early date; others accept them if the gap is labeled as shared float. Check your contract's language, then state your position in the narrative rather than leaving the reviewer to guess.
What is the DCMA fourteen-point assessment?
A set of schedule health checks developed by the Defense Contract Management Agency, covering logic, leads, lags, relationship types, hard constraints, high float, negative float, high duration, invalid dates, resources, missed tasks, a critical path test and two performance indexes. Construction networks often depart from some thresholds for good reason; explain each departure.
What belongs in the schedule narrative?
Enough for a reviewer to reproduce and judge the dates: sequence, critical and near-critical paths, calendars, weather assumptions, procurement lead times, submittal review periods, crew assumptions and any constraints. Many specifications list required narrative contents, so follow yours first. A narrative that merely repeats the bar chart in words adds nothing.