Tests by type
Recent activity
| Test | Type | Project | Date | Status |
|---|
Open failures
| Test | Type | Project | Location | First failed | Open for | Why it failed | Retests |
|---|
A failed test stays open until a retest of it passes. Technicians pick the failed test when they enter the retest. Failures from before this page existed have no retest linked, so they show here until you link one (Link a retest, or open the later test and choose Mark as a retest of).
| Test | Type | Project | Location | Technician | Date | Photos | Status |
|---|
| Date | Project | Technician | Weather | Contractor activities |
|---|
Filed from the field app's "File daily report" button — one per project per day. Refiling the same project on the same date overwrites the earlier version here rather than adding a duplicate row.
Each photo is geotagged twice — once here in the database (for the pins and sorting above) and once written directly into the photo file's own EXIF data at the moment it's captured, so a downloaded photo carries its location the standard way a tool like Propeller expects. Individual photos open full-size in a new tab; "Download ZIP" bundles everything in the date range above (leave both blank for everything on file) for a batch upload.
Technicians keep their field notes private. A note only appears here when the technician taps Share with project manager on it — and it disappears again if they stop sharing.
| Delivered | Inventoried | Material | Manufacturer | Project | Rolls | Length (ft) | Area (sq ft) | Deployed | QC cert / sample | Technician |
|---|
Filed from the field app's Liner Inventory Log: one log per material per delivery day, with every roll on it (no limit). Click a log to see its rolls, edit it, or view its history. Pick a material above to list every roll of it from every day. The two Excel buttons open the Report builder: by material gives a summary plus one sheet per material with all days together; by day gives one sheet per material per day. The material is named in each sheet tab and across the top of each sheet.
| Sample | Project | Material | Location | Sampled | Sent | Tests (✓ back, amber waiting) | Waiting | Status |
|---|
Samples are entered here by the project manager. Pick the material and the usual tests are ticked for you; add several at once when a batch goes to the lab together; tick results off as they come back (“Mark results received” does a whole batch at once). Samples waiting longer than 14 days appear on Needs attention. The test list and material prefixes are set per project with “Test list”.
Download a backup
One ZIP with every project's test records, read straight from the database, in two forms: an Excel workbook you can open and read (a sheet per kind of test, plus the change log and the project list), and a data file that holds every record exactly as stored, which this page can use to restore tests that were lost. It covers test records, their change log and the project list for all projects (not the project picked at the top). Photos, daily reports, field notes, Proctors and spec settings are not in it. Keep the file somewhere private: it holds your clients' data.
Restore tests from a backup
Choose a backup ZIP (or its data file). This only adds back tests that are missing from the database. It never changes or deletes a test that is there, so it is safe to try: you see the numbers first and confirm before anything is written.
Import density tests from an Excel worksheet
For tests recorded before the project started in this app. Choose the firm's density summary worksheet (nuclear gauge, ASTM D-6938 layout), pick the sheet and the project, and press Preview. Nothing is saved until you press Import; the preview checks every result against the sheet's own compaction % and pass/fail. Tests already in the project are skipped, so it is safe to run again.
Every time a test is added, changed or deleted, the database records who did it, when, what changed, and the full record before and after. The log can't be edited or deleted from this app. A deleted test can be restored from here.
| When (Eastern) | Who | What | Test | Details |
|---|
| Project | Tests | Technicians who can see it | Tests available |
|---|
Project managers can always see every project. A technician only sees the projects ticked here, in the field app, and only after their phone refreshes (reopen the app or switch back to it).
| Proctor # | Project | Category | Source | Method | MDD (pcf) | OMC (%) | Curve | Report | Date | Tech |
|---|
MDD and optimum moisture entered here become available immediately to field techs on that project — when they open a soil compaction test and pick a Proctor #, these values autofill instead of being retyped by hand. Try it: add one below, then open the field app prototype and start a new soil compaction test on the same project. A Proctor with family curve points on file (2+) is also eligible to be auto-matched by a One-Point Proctor test — no manual selection needed there.
| Project | Test type | Spec values | CQA plan reference |
|---|
Soil categories
Split a project's soil testing into categories (structural fill, berm, compacted clay liner…), each with its own spec requirements. Once a project has any, field techs pick one on every soil test, the test is graded against that category's requirements, and the density reports summarize each category separately. A project with none behaves as before.
| Project | Category | Min. compaction | Moisture tolerance | Numbering | Tests |
|---|
Acceptance thresholds (spec %, moisture tolerance, required f'c, and similar) are only editable here, by a PM or engineer, sourced from the project's approved CQA plan. Field techs see these values locked on their device — they can't change what a test is graded against. Editing a spec only affects new tests going forward; tests already recorded keep the spec they were evaluated under.