Construction management platform
One record for the work — office and field.
RFIs, observations, inspections, action plans, daily logs, photos, documents and drawings, with a project directory and role-based permissions tying it together. Sidratek at the desk, Sidratek Field in your pocket.
Ten permissioned tools. Two apps. Field capture that works with no signal.
Built for the way a project actually runs.
One system of record across the office and the site, with the permissions and the offline behaviour that construction work needs rather than the ones a generic tool ships with.
The record lives in one place
Every answered RFI, accepted observation, completed inspection, submitted log and uploaded photo attaches to the project — not to somebody's phone or somebody's inbox.
Built to work without signal
Sidratek Field captures offline, queues what you shoot, retries what failed and syncs the moment you're back in range.
Access decided per person, per tool
Ten permission templates, four levels per tool, per-person overrides — and private records only their own people can see.
Everything ties back to the sheet
Drop a pin on a drawing and link it to an RFI, a photo or a document. Revisions keep their history; the superseded copy stays findable.
The tools
Ten tools, one project record.
Every tool shares the same directory, the same permissions and the same history — so a photo taken on site, the RFI it answers and the sheet it is pinned to are all the same project's record.
RFIs
WebSidratek FieldAsk the question, log the answer.
Ball-in-court, assignees, distribution lists and due dates. Link the drawing, the spec section and the cost code; record the official response; let automated reminders chase what's overdue.
Observations
WebSidratek FieldCatch it, shoot it, send it.
Safety, quality and environmental findings captured camera-first from the phone. Seven categories and twenty-seven types you configure per project, hazard and contributing behaviour or condition, review-and-accept, and a separate send step so records exist before they're broadcast.
Inspections
WebSidratek FieldChecklists that finish on site.
Build a template once — sections, items, twelve response types from pass/fail to a signature — then run it from the phone. A failed item raises a linked observation without leaving the checklist.
Inspections are run in Sidratek Field. Templates, results and notification rules live on the web.
Action Plans
WebSidratek FieldCommissioning and QC, item by item.
Sections and items with acceptance criteria, references, verification method, assignees and due dates. Items move open → in progress → submitted → approved, with the approvers you name.
Daily Logs
WebSidratek FieldOne log a day, complete.
Fifteen section types — weather, manpower, equipment, deliveries, visitors, delays, waste and more — enabled per project, each field required, optional or hidden. Draft, submit, approve, reopen.
Photos
WebSidratek FieldEvery photo, findable.
Timeline by day, week or month; albums; markup; comments; full metadata. Each photo links to the RFI, observation, inspection or daily log it belongs to. Deleted photos wait 30 days in the recycle bin.
Documents
WebSidratek FieldDocument control, not a shared drive.
Nested folders with per-folder privacy and permission grants, revision history that marks the superseded copy, folder watching, drag-and-drop upload, and share links for people outside the project.
Drawings
WebSidratek FieldThe current sheet, and everything pinned to it.
Sets, sheets and revisions carrying discipline and publication status. Upload a multi-sheet PDF and it splits itself. The viewer adds a sheet rail, zoom, a revision picker, seven markup tools and typed pins to RFIs, photos, documents and notes.
Directory
WebSidratek FieldWho's on the job, and what they can touch.
People, companies, external contacts and distribution groups per project — per-person permission editing on the web, tap-to-call, text and email in the field.
Project Settings
WebConfigure it once, per project.
Turn modules on and set their defaults, manage templates and notification matrices, approve the companies joining the job, and invite the people who work on it.
Project configuration is a web-only surface.
Workflow
Status means something, because the tool enforces it.
No spreadsheet column pretending to be a workflow. Each record moves through states the module knows about, with the reviews, rejections and reminders that go with them.
An RFI
Overdue is derived from the due date, and reminders go out on their own.
An observation
A reviewer's rejection lands at Not accepted, and sending is its own step — records exist before they're broadcast.
A daily log
Reopenable, because the day is not always over when the log is filed.
Sidratek Field
One hand, no signal.
The crew's app. Capture-first, offline by default, and everything it takes hands straight to the office record — the same project, the same directory, the same permissions.
Log an observation
Camera first. Category and type, hazard and contributing condition, send when you're done.
Run an inspection
Pass or fail per item. A deficiency note and photo raise a linked observation without leaving the checklist. Sign, submit.
Submit a daily log
Weather pulled in, crew steppers, work-completed note, and only the sections that apply to your project.
The offline banner, the capture queue and the retry are the design — not a slide.
Who it's for
A general contractor's project, and everyone on it.
The people who build the job and the people who need to see it — each with the access their work needs and nothing wider.
Office
- Company Admin
- Creates projects, invites people, assigns templates
- Project Manager
- Admin on every tool and every module setting
- Assistant PM
- Admin on RFIs; standard on field tools, drawings, documents
Field
- Superintendent
- Admin on observations, inspections, daily logs and photos
- Field Engineer
- Standard on field tools and documents
- Foreman
- Field entry and photos; read-only on the office tools
Quality & safety
- QA/QC Engineer
- Admin on inspections; standard across RFIs and observations
- Safety Manager
- Admin on observations; standard on inspections and daily logs
Partners & owners
- Subcontractor
- Their own scope and what's assigned to them, nothing else
- Client / Owner
- Read-only across the project
- Platform Admin
- Approves companies and manages users across the platform
Access & control
Decided per person, per tool, per project.
- Four levels per tool — none, read only, standard, admin.
- Ten built-in permission templates, from project manager to read-only owner.
- Per-person overrides for when a template doesn't quite fit.
- Private records — RFIs, observations, inspections, action plans, folders — visible only to that tool's admins, the creator, the assignees, the signers and the distribution list.
- Per-folder privacy and permission grants in Documents.
| Tool | None | Read only | Standard | Admin |
|---|---|---|---|---|
| RFIs | ||||
| Observations | ||||
| Inspections | ||||
| Documents |
One level per tool, per person. An example — every project sets its own.
Traceability
Nothing disappears quietly.
Who changed what, when, and what it replaced — kept by the tool rather than reconstructed from memory six months later.
Change history on every record
Activity and comments on RFIs and observations
Revision history that keeps the superseded copy
30-day recycle bins
Share links are explicit, never implied
Notification rules per module, per event, per role
Put the field and the office on the same record.
Sidratek for the desk, Sidratek Field for the site. One project, one directory, one set of permissions.