Drawings on the site
What engineers can open now. Updated every time you come back to this tab.
| Drawing | Status | Revision | Items | Review items | Last change |
|---|
Load drawings
Add new drawings, or new revisions of drawings already on the site. Nothing changes until you press a green or orange button in step 3.
The .json files you received. You can select all of them at once.
Baseline programme
Load the Primavera P6 export (.xer). The tool reads the construction activities, links each one to a drawing and a construction stage, and can then show where work is planned for any month. The programme structure is indicative, so links are made by area: drawing + stage + phase + road / junction.
Saved programme
Clean-up of test records
Delete WIRs, Blocked-work items and drawing comments that were created by mistake or for testing. This cannot be undone. (To keep a record instead, engineers can Cancel a WIR or Remove a comment or obstruction — it stays in the register as cancelled/removed.) Progress marks are not touched here.
WIRs
Blocked work
Drawing comments
WIR log
Choose your own WIR log (Excel) once. The tool reads the earlier WIRs with their codes, keeps your file as the master that QA/QC download (with new WIRs added in your own format), and continues the numbering after the highest number in it. Repeat whenever you want to refresh it from your file.
Numbering and work done before the tool
Inspected on paper
Work marked on or before this date was inspected on paper (its WIRs are in the log), so the tool does not offer it for a new WIR. Leave empty to offer everything; engineers can also link single items to an earlier WIR.
WIR coverage index
Stops two engineers raising WIRs over the same work at the same moment. It is kept up to date automatically; rebuild it once after updating to this version (and whenever you suspect it is out of step).
Storage
Largest shop drawing file
QA/QC can upload approved shop drawings up to this size. Bigger files use more of the free 1 GB (a file takes about 1.3× its size) and take longer to attach to a WIR.
Forgotten password
The “Reset” e-mail comes from Firebase (noreply@…firebaseapp.com) and is often filtered by company mail — ask the user to look in Junk / Spam / Quarantine and to search for “firebaseapp”. If it still does not arrive, use one of the two tools below. They run through your Google mail relay (set-up steps are in 9-Email-notification/Code.gs and the guide) and are checked by a separate admin secret that only you know; the secret is kept in this browser tab only.
WIR process: QA/QC → QS → document controller
The WIR detail shows who the WIR is waiting for (site engineer, QA/QC, QS, document controller, Engineer). When the switch below is on, a WIR can only be submitted to the Engineer after QA/QC has compiled it and QS has confirmed the BOQ codes; the document controller then records the official submission. Off (default): the old direct submission still works and the steps are optional. The planner can always override. This is enforced by the screens; the security rules enforce the order of the three steps themselves.
Draftsman e-mail notification
Sends an e-mail to the draftsman whenever a drawing comment is raised or reopened, takes it off the list when it is fixed or closed, and e-mails a reminder of everything still open every morning. It uses a free Google Apps Script relay (Code.gs in the folder 9-Email-notification; set-up steps are at the top of that file and in the guide). Recipients are fixed inside the script.
Users and permissions
Everyone with a company email who signs up appears here as a Site engineer. You decide what each person can do. Changes apply the next time they open the app. The first planner (set in the site settings) can never be locked out.
| Person | Role | Account | Last opened the app | |
|---|---|---|---|---|
| Loading… | ||||
What each role can do
Review inbox
Work that could not follow its line after a drawing update, and changes sent late by phones. Nothing is lost — you decide where each piece belongs. Most drawing updates create none.
QS records — inventory
Read-only. Shows which QS / valuation records exist, how many documents each holds, and whether they are active, reserved or historical (from the previous QS screens). Nothing is changed.
Backup
Downloads everything on the server (drawings, all revisions, every mark, history, review items) into one file. Keep it on the project drive. Do it every week and before any change.
Application data (WIRs, QS, QA/QC, programme, obstructions, comments)
The backup above holds the drawings and marks. This one holds everything else the tool owns: WIRs and their numbers, the WIR log and your Excel master, shop-drawing files, BOQ with links and assignments, rates, programme, obstructions and drawing comments. It lists the count of every collection and a checksum. Take both, together, every week. User accounts and sign-in are held by Firebase and are not in either file.
Restore application data
Writes the documents of an application-data file back (it checks the file’s checksum and counts first). Use it on an empty or test project, or to recover deleted records; existing documents with the same name are overwritten.
Security rules
Only needed when a new version of this tool says so (for example to allow renaming drawings). Copy the rules, open Firebase → Firestore Database → Rules, replace everything, press Publish.
Start fresh
Removes all drawings, marks, history and review items from the server. Engineers' accounts stay — nobody has to register again. Use this once before the pilot to clear test data.