Digitize your Friday Pack
6 min read
If you run construction sites you know the Friday ritual: chasing signed toolbox talks, printing permits, scanning site diaries and stapling it all into a pack for the main contractor. OpsCores turns that afternoon into a single tap, because the pack is built from records your crew already captured during the week.
What goes into a Friday Pack
A typical weekly pack for one site pulls together:
- Daily site diaries, one per working day, supervisor-signed. See what a site diary should capture.
- Toolbox talks, the week's briefings, each with a signed attendance list. See toolbox talks explained.
- Permits to work for hot works, confined space and work at height, with photos attached. See permit to work.
- Inspections, including weekly PUWER equipment checks and LOLER lifting checks.
- Attendance, a geofenced check-in log showing who was on site and when.
Why the compiler can work unattended
Every record your crew completes on the mobile app auto-files into the folder
taxonomy Type / Year / Month / Week Ending DD-MM-YYYY. That filing happens at the
moment of capture, not at the end of the week, which is the whole reason the
compiler can run without anyone tidying up first.
Three things make the resulting pack trustworthy rather than merely tidy:
- It only contains what was actually recorded. Nothing is generated to fill a gap. If a check was missed, the pack shows it as missing.
- Evidence stays attached to the task it belongs to. Photos and signatures are fields inside the form, so they travel with the entry into the PDF rather than arriving as a separate folder of images.
- Failures become follow-ups during the week. A numeric reading outside its threshold raises a corrective task automatically, so gaps are fixed before Friday instead of discovered after.
What the check sheet actually proves
The auto-ticked check sheet compares the site's active recurring schedules against the submissions that arrived that week. A ticked line means a scheduled check was completed and the record is in the pack. An unticked line means it was not, and it stays unticked. That is deliberate: a pack that always looks complete tells a client nothing, and a pack that shows a real gap is what lets you fix it before the principal contractor finds it.
Working offline
Site coverage is unreliable, so capture does not depend on it. Forms, photos and check-ins recorded with no signal are stored on the device and sync when a connection returns. A crew working in a basement for two days still appears in Friday's pack once their phones reconnect.
Where it fits
The Friday Pack is one output of the wider compliance pack compiler, which draws on the same digital site diary and RAMS briefing records your team fills in day to day.
The result: the week's evidence in one client-ready PDF, with no printing, no scanning and no stapling, and an honest record of anything that was missed.
How to set up an automatic Friday Pack
- 1
Choose the Construction pack at signup
Pick the Construction template pack when you create your workspace. The form set, folder taxonomy and Friday Pack recipe are seeded for you, so you start with a working system rather than a blank one.
- 2
Assign your recurring inspections
Attach the weekly PUWER equipment checks and LOLER lifting checks to a role rather than a person. They then generate themselves on schedule and appear for whoever holds that role that week.
- 3
Let the week record itself
Operatives complete forms, capture photos and sign on their phones as they work. Records file themselves into Type, Year, Month and Week Ending folders as they arrive, so nothing needs sorting later.
- 4
Compile on Friday
Open Forms and then Friday Pack in the admin app and press Compile. The compiler assembles one dated PDF with an auto-ticked check sheet, ready to hand to the client or principal contractor.