Run a project across every company on it.
A project has an owner, a PMC, a main contractor and a dozen subcontractors — and each one keeps its own version of the truth. SyteMarshal gives them one plan, one set of approvals, and one record of what actually happened.
In development. We're working with a small number of projects before opening it up.
The lifecycle
Planning to closure, without leaving the system.
Most tools cover one stage and hand off to email for the rest. The handoffs are where projects lose time.
Planning
Break the project into a WBS, assign each branch to a responsible organisation, set planned dates.
Execution
Activities carry sub-tasks with priority, assignment, comments and attachments. Progress rolls up automatically.
Inspection
The responsible firm raises an RFI; the owner-side inspector runs a checklist on site and records the outcome.
Approval
Configurable multi-step approval chains, with side effects — a sign-off can complete the task it approved.
Closure
Baseline versus actual, variance and forecast completion — so the record of what happened survives the project.
What it does
Built for the awkward part: other companies.
Single-company project tools are a solved problem. Coordinating firms that don't share a payroll is not.
Multi-organisation by design
The owner invites contractor firms by company code and controls exactly which modules each one can see — WBS, tasks, inspections, approvals, documents, reports, budget. A partner sees its own work, not the whole project.
Work breakdown & schedule
A nested WBS with weighted progress roll-up, finish-to-start dependencies with a cycle guard, planned versus actual dates, and derived health: On Track, At Risk, Delayed. When a predecessor slips, everything downstream is flagged for you.
Inspections and RFIs that close the loop
Passed, Correction Required, or Rejected — each with a defined path back. Checklist results feed the activity feed and can raise a sign-off approval automatically.
Governance, not free-for-all
Collaborating firms request member additions, role changes and module access; the owner org reviews and decides. Drafts need approval before entering the live schedule.
One audit trail
Every task, RFI, inspection, approval and document upload lands in a project activity feed, scoped so each firm sees what it is entitled to see.
Roles that match the site
Clone a permission template to author your own — Site Engineer, QA/QC Engineer, Planning Manager — instead of bending your org chart to fit ours.
Which one do I need?
KhataKro is about your money. SyteMarshal is about everyone's work.
One contractor, one khata. Labour, wages, materials, vendors and site profit. If your question is “what did this site cost me and what am I owed”, this is the one.
See KhataKroSeveral companies, one project. Scope, schedule, inspections and approvals across firms. If your question is “who is holding up the slab and who signed off on it”, this is the one.
Request early accessThey're separate products with separate accounts — using one doesn't sign you in to the other.