Closeout & Warranty Workspace

The end of the project is a record, not a verdict

Organize what was completed, what remains unresolved, and which records you should retain — without pretending ConcreteOwner inspected or approved the work.

Documentation and decision support. It is not an inspection, an engineering evaluation, a legal review, a warranty interpretation, a permit record, or an official completion document. Everything you enter stays in this browser.

Loading…

Why the last day of a project is worth an hour

On the day the crew leaves, you know more about your concrete than you ever will again. You know what the base looked like, what you were told about the mix, when you were asked not to drive on it, and which of your questions never quite got answered. Six months later almost none of that survives, and in five years, when something changes or you sell the house, none of it does.

An hour spent writing it down is not paperwork for its own sake. It is the difference between a warranty you can use and one you cannot find, and between a conversation about a crack that starts from a dated photograph and one that starts from two recollections.

Everything here keeps its source attached

This workspace uses 14 source layers, and every line it produces carries one. “The contractor told you the job is finished” and “the job is finished” are different statements, and only the first is one anybody here can record. The same applies to a warranty document, an inspector’s comment, a supplier’s data sheet and your own observation: each is written down as what it is, attributed to the kind of source it came from, with a plain statement of what it does not establish.

That is not caution for its own sake either. The moment a representation is printed as a fact, a homeowner has a document that says something nobody established — and it has our name on it.

What it covers

29 closeout topics across completion, scope reconciliation, observations, project records, warranty, care and future use, plus 20 neutral categories for things you can see. Only the topics that apply to your project are shown — a repair does not need a reinforcement record, and an interior slab does not need a de-icing conversation — and anything filtered out is counted nowhere.

What it will not do

  • It will not approve or reject the work, certify workmanship, or declare anything complete. Recording that somebody told you the job is finished is recorded as exactly that.
  • It will not diagnose. A crack, a patch of discolouration, water sitting after rain, or surface flaking are all things you can write down. What any of them means needs somebody appropriately qualified who has seen the actual slab.
  • It will not interpret a warranty or decide what is covered. It organises what you tell it a document says, and the document remains the thing that governs.
  • It will not determine code or permit compliance. Only the authority that issued a record says what it approved.
  • It will not tell you whether payment is due, direct you to pay or hold anything back, release retainage, or draft or interpret a waiver.
  • It will not decide who is at fault. There is nowhere here to record that, and that is deliberate — a closeout packet that assigns blame is not one you can hand to anybody.

If something is not safe

The first question this workspace asks is whether you are looking at something that is not a paperwork question at all. If you say yes, it stops: no packet, no checklist and no form. It restates what you reported, says plainly that nothing here has assessed it, and points you toward somebody appropriately qualified locally. ConcreteOwner is not an emergency service and does not provide one.