Publish, Respond, and Close in Centerline

Centerline and the record it holds

Module 12 closes the async program with debriefing and continuous improvement. Onsite #2 proves the standard against real cases. This session sits between the two, at the point in the lifecycle where Centerline carries the most weight and where the responsibility matrix found the easiest wins available to the first cohort.

Centerline is Grace’s project platform and its system of record. It holds the project lifecycle document, the record that captures a project from setup through closeout. It holds the monthly progress reports. It holds the A3, the one-page story that pulls cost data from the lifecycle record and outputs to PDF or print for marketing. The course puts it in one line: where the story is built and where it lives.

The record is required in every phase, and the lifecycle map names each place. A project workspace is created in Centerline at initiation and planning. Consultants are added to Centerline through design and coordination. Drawings and specifications are published before construction administration. Construction management is set up in Centerline for that phase. The punchlist is created and completed in Centerline at closeout. Project emails are stored there, and the archive zip that formally closes the project is requested from there.

The responsibility matrix carries four Centerline items, drawn from 570 observations logged by 20 groups across five offices: publishing drawings and specs, responding to RFIs, archiving project records and emails, and requesting the archive zip. All four are recorded with a cause of BEHAVIOR rather than PROCESS or TRAINING. The matrix reads them as habits that have not formed rather than as procedures that were never written.

What does the lifecycle document ask, and who answers it?

The lifecycle document is a set of questions that, answered in order, tell the whole story of a project. It runs in eight question sets. Each set carries a citation naming where its answers come from, and those citations are the closest thing to field labels the course provides.

The division of work is stated. A project manager is the main source for the first five sets. The Storyteller gathers the last three. The Storyteller builds the record, and a project manager reviews it for accuracy. Module 4’s Storyteller field guide sets out the role, the three-layer governance, and every question in full. This session assumes that guide has been read rather than repeating it.

Three of the eight citations name a section letter: B for delivery and commercial, C for scale, scope, and the experience, and D for the schedule. Section A is never named anywhere in the course, sets 1, 2, 6, 7, and 8 carry no letter at all, and no page describes how the sections are ordered or what any one of them contains. The lettering that does exist implies a document structure the course has never shown, and the letters that are missing sit in the open items below.

Some fields populate themselves. Project name and number arrive automatically, as do the project manager and the project team. Cost fields pull from the record, which is what allows the A3 to assemble quickly at closeout. Which fields behave this way, and which require entry, the course does not document.

One instruction in the guide is a Centerline action with no mechanics behind it. Name a Storyteller and tag them in the Centerline lifecycle document so ownership is clear. The tagging step is named. The way to perform it is not.

What has to reach Centerline before Construction Administration begins?

Drawings and specifications are published to Centerline’s Publishing and Conforming Center before Construction Administration. The responsibility matrix ranks that item 10 of 44 at a priority of 33.6, the highest ranked Centerline item on the whole list.

The matrix item reads as one sentence: complete code analysis and specifications, publish drawings and specs to Centerline’s Publishing and Conforming Center before Construction Administration. The lifecycle map records the same event in three words, drawings and specs published, in the team stream of the Design and Coordination phase. Two tool links, Publishing Drawings and Publishing Specifications, sit in the same phase bar.

Conforming is the second half, and it runs for the length of construction. Issued ASIs and change orders are conformed into the published set, so the set on the platform matches the set the contractor is building from. The matrix ranks that item 37 of 44 at a priority of 6.8.

The distance between 33.6 and 6.8 is worth reading. Publishing is a single event with a phase behind it that cannot begin until the event happens. Conforming is a habit that runs every month with no date attached to it. The item that carries its own deadline was flagged by nearly every group. The item that carries none was flagged by almost no one.

What does the assigned Centerline responder owe, and by when?

A project manager assigned as the Centerline responder processes RFIs within about 3 business days, routes them to consultants, and reviews each one for cost and contract impact. The responsibility matrix ranks that item 18 of 44 at a priority of 26.7.

The three actions carry three different kinds of work. Routing is coordination, moving the question to the discipline that owns the answer. Reviewing for cost and contract impact is judgment, deciding whether the answer changes the scope, the fee, or the schedule. Responding inside the window is the discipline that keeps the first two from turning into a change order.

1. Receive and log the RFI in Centerline. Module 11 lists RFIs as a Construction Administration task, with the RFI log and form in Centerline.
2. Route to the discipline that owns the answer. The matrix names the routing step explicitly. A question sent to the wrong consultant is asked twice and answered late.
3. Review for cost impact. An answer that adds work carries a price. Pricing it at the response costs a conversation. Pricing it after the work is built costs a change order.
4. Review for contract impact. An answer that changes scope, schedule, or the terms of the agreement belongs in the change chain rather than in a response.
5. Respond inside about 3 business days. This is the only Centerline response standard the course states anywhere.

One contradiction has to be named before a cohort is asked to work to that standard. The 3 day window and the role title, assigned Centerline responder, exist in exactly one place on the site: a data array inside the participant feedback summary. Module 11’s Quick Reference lists RFIs as a Construction Administration task in Centerline and attaches no timing to them at all. A project manager reading the module that governs Construction Administration would never learn that a response window exists, would never learn that responding is a named assignment rather than a shared duty, and would never learn that either standard had been written down at all.

Submittals sit in the same table, in the same system, with an open question printed where an owner belongs. The column naming who leads reads: To discuss, role split not yet defined. The column naming who verifies reads: To discuss. The site states in its own words that the division of work between the project manager and the administrative role has not been settled.

Which system holds which document?

Grace runs four systems on a project. The course lists them in a single line with no explanation of the split: Project Server, Centerline, Milo, and BST. Module 11’s Quick Reference is the only page that assigns individual documents to individual systems, and it covers Construction Administration alone.

A pattern is visible in the table. Centerline holds the documents that describe the work and the changes to it. Project Server holds the pay applications and the two completion certificates. Whether that pattern is the rule, or whether it is an artifact of how one table was built, the course never says. The AIA documents are split between two systems with no stated principle governing the split, no page states which system governs a document the table does not list, and no page covers the documents produced in any phase other than Construction Administration.

One inconsistency runs through the same material. The course spells the system Centerline in seven files and CenterLine, with a capital L, in two: Module 11’s Quick Reference and the second Quick Reference in Module 4. This session uses Centerline throughout. A system of record carrying two spellings is a system that has to be searched two ways, and the inconsistency sits in the open items.

What formally closes a project?

Two responsibilities close a project in Centerline, and the matrix ranks them separately. Archive project records and store project emails in Centerline ranks 23 of 44 at a priority of 21.8. Request the Centerline archive zip to formally close the project, and validate deliverables against the original scope, ranks 29 at a priority of 17.6.

The lifecycle map records the same two events in the business stream of its Closeout and Growth phase: project emails stored in Centerline, and Centerline archive zip requested, with the project archived. Its leadership view compresses both into one clause. Archives and requests the close-out zip. The punchlist is created and completed in Centerline in the same phase, in the client experience stream.

1. Complete the punchlist in Centerline. The lifecycle map places punchlist creation and completion in Centerline, in the client experience stream at closeout.
2. Archive the project records. Matrix rank 23, priority 21.8.
3. Store the project emails in Centerline. The same matrix item. The course states it as the second half of one responsibility rather than as a separate task.
4. Validate the deliverables against the original scope. The comparison between what the agreement promised and what the project produced.
5. Request the Centerline archive zip. Matrix rank 29, priority 17.6. This is the step the course names as formally closing the project.
6. Finish the A3. Cost fields pull from the lifecycle record, photographs are added, and the output goes to PDF or print for marketing.

Validating the deliverables against the original scope is the substantive half of the second item. The archive zip is a request. The validation is a comparison, and it is the last moment at which the difference between what was promised and what was produced can be recorded while anyone still remembers the reason for it.

The Storyteller field guide asks three closeout housekeeping questions in the same breath. Pay apps filed. Drawings archived. Where the A3 process stands. It also states the failure mode that produces a thin record, and it states it as the first practice to avoid: waiting until closeout to capture the story. The record builds while the work happens. A story reconstructed at the end is thin, late, and misses the why.

Summary

Centerline holds the project record from setup through closeout. The lifecycle document runs in eight question sets, five sourced by the project manager and three gathered by the Storyteller. Drawings and specifications publish to the Publishing and Conforming Center before Construction Administration, and issued ASIs and change orders conform into the published set afterward. RFIs come back inside about 3 business days, routed to the owning discipline and reviewed for cost and contract impact. Project records and project emails go into Centerline at closeout, the archive zip is requested, and the deliverables are validated against the original scope.

The mechanics behind every one of those sentences sit in the open items below, and that list is longer than either BST session carries. The length is an accurate measure of how much of Centerline the course has written down. Naming each gap precisely is what allows Grace to close it, and a list of thirteen specific questions is a shorter piece of work than it looks.

Onsite #2 opens next and proves the standard against real cases from the cohort’s own projects. A project brought to the capstone with a complete Centerline record can be discussed on its evidence. A project brought without one can be discussed only on memory.

Come prepared

1. Bring one project currently in closeout, or the most recently closed project available.
2. Note whether that project has a named Storyteller, and bring the name or bring the fact that no one holds the role.
3. Open its Centerline lifecycle document and note which of the eight question sets carry answers.
4. Note whether the archive zip was ever requested, and if it was, note who requested it.
5. Read the Module 12 closeout checklist and mark every item on it that depends on Centerline.
6. Bring one question about Centerline that the course has never answered. It will go on the open items list.