Preconstruction checklist

Project checklist

The administrative things you want in hand before the crew turns up, and where each one has got to.

Readiness is a list, not a feeling

Almost every job that starts badly starts with somebody assuming somebody else had it. This is one list, with a name and a date against each line, that answers "are we ready" with items rather than opinions. What is outstanding, who it is sitting with, and when you wanted it.

It states no requirements

There is no published set of preconstruction prerequisites here, no permitting logic and no contract reading. The list is yours. That matters more than it sounds: a checklist that arrives pre-filled with items somebody else decided teaches people to tick rather than to think, and the ticks end up on a record.

What sits either side of it

Standing the site up is the site mobilization checklist. A question you need answered in writing is an RFI, and what a package includes is the subcontractor scope checklist.

An administrative checklist of items you chose. It states no legal, permitting or contractual prerequisite for starting construction, does not decide whether a job may begin, and is not advice. Everything runs on your device.

Questions people ask

Does this tell me what I am legally required to have before starting?
No. It publishes no list of legal, permitting or contractual prerequisites, because what a job needs depends on the jurisdiction, the contract and the work — and a free website printing a list of them would be guessing on your behalf. The items are the ones you type. Whether you are ready to start is your decision.
How is this different from the mobilization checklist?
This one is paperwork; that one is the physical site. Signed subcontracts, certificates of insurance, permits you have applied for and drawings you are working to belong here. Fencing, temporary power, the trailer and the dumpster belong on the mobilization checklist. Two lists because two different people chase them.
Can I keep a standard list and reuse it on the next job?
Every item is entered against one job by its id, so nothing is shared between jobs and nothing is overwritten when two jobs have similar lists. There is no template library: a starter list published by us would become a list somebody believes is required.
What happens when I file the checklist?
It becomes a dated record against that job, alongside everything else filed for it, and prints as one sheet. The items themselves stay live in the register — filing takes a snapshot, it does not close the list.