The structure everything else hangs on, and the plan the progress bars are a percentage of.
Projects, sections, structures, piers
A project is a site — its client, consultant, contractor, location, and the programme start and finish dates. A project is divided into sections, a section holds structures (the bridges: KM 54, KM 60), and a structure holds piers. Every pile belongs to a structure, and every report belongs to a project.
Getting this right early matters because it is what the board slices by. The commonest mistake is entering bridges under the wrong project, so every administration screen names the project it is editing, and a board with no data offers to switch you to the project the bridges are actually under.
The pile register (Administration → Pile register)
Upload the client's pile schedule as a spreadsheet. Columns are matched by their headings, so the file does not have to be rearranged: pile number, pier, chainage, diameter, design depth, cut-off level, tip level, concrete volume, cage length.
You see what it read — how many piles, under which piers, and anything it could not make sense of — before it is imported. Importing again later updates what changed and adds what is new; it does not duplicate.
Piles that were built before you started
A contractor does not buy a system on the morning work begins. Piles are already in the ground, nobody is going to fill in six months of daily sheets for them, and a progress bar that ignores them says 8 piles when 208 are done — which no client will accept.
Put a Completed column on the plan sheet (also read as Completion Date, Finished, Tamamlanma, Bitiş Tarihi). A date in it is the day the pile was finished; a word such as Done means finished on a day nobody wrote down; blank means still to do. Nothing is guessed from a blank cell, because that would be reporting work that has not happened.
A date is worth more than a word: it puts the pile somewhere in time, so it counts in the S-curve and in "how many were done in March". An approximate date is not an invented one — the middle of the month you know it was finished is a real answer.
Commencement Date is a different question. It says when a pile started, which is not a claim that it finished — and if your plan carries future start dates, one column for both would turn every pile on the job into a completed one overnight.
Carried-over piles count towards progress, are not offered when a new record is started, and appear in their own Carried column so that you can say why no daily sheet exists behind them.
Correcting the register
The plan comes off somebody else's spreadsheet, so it sometimes goes in wrong — a column read as the pile number when it was the diameter, the wrong sheet, the right sheet against the wrong bridge.
- One pile: the × at the end of its row takes it off the plan.
- The whole bridge: Clear this bridge's plan empties it, and asks you to
type the bridge's own code first. A tick box gets clicked past; a code read off the screen and typed does not.
- A pile that has a record filed against it is never deleted either way. The
record is what somebody actually did that day; the plan line is only the intention to do it. The screen says how many were kept for that reason.
Clearing a bridge touches nothing else: the bridge, its section and every daily report stay where they are. Upload the corrected sheet afterwards.
What the register buys you
- Every daily pile log can be tied to its planned pile, so the design figures come with it and nothing is typed twice.
- Progress is a percentage of something real — completed against planned, per bridge and per section.
- The S-curve works: planned against actual, month by month, needing only the programme dates on the project.
- Nothing gets logged twice: one report per planned pile.