Project facts
Keep the client, category, milestone and expected handover in one stable project header.
01
Project command centre
Project Overview
The Overview is the project’s working control surface, not a decorative dashboard. It places the project identity, milestone, today’s priorities, next reminder, latest note, active members, storage usage and section readiness in one view, so the team can understand what is happening and move directly to the record that needs attention without assembling a status report by hand.
What this area includes
Today's priorities
Bring assigned and team tasks together with urgency, due time and activity context.
Reminder and latest note
Surface the next commitment and the newest project knowledge beside the work.
Members and storage
Review the active team and controlled file usage without leaving the overview.
Section status
Move directly into engineering, execution, revisions, commercials or handover with a factual status.
02
Commercial control
Commercials
Commercials keeps the financial story beside the engineering and delivery record instead of in a disconnected spreadsheet. The overview combines contract value, receipts, actual and committed cost, forecast and payment progress; the underlying areas then cover budgets, collaborators, expenses, payments, commitments, commercial notes and modification requests under explicit permissions.
What this area includes
Overview
Read the approved budget, spending, receipts and open commitments in one summary.
Budget
Define project currency, budget categories and warning thresholds.
Collaborators
Track commercial shares and visibility for authorized collaborators.
Expenses
Record, import, review and approve costs with supporting evidence.
Payments
Follow expected and received client payments with dates and references.
Commitments
Keep purchase and contractual obligations visible before they become expenses.
Notes
Retain commercial decisions and context in a protected project notebook.
Modification requests
Connect technical change with schedule and cost impact without exposing restricted values.
03
Working project knowledge
Project Office
Project Office turns daily coordination into durable project knowledge. Reminders keep time-sensitive follow-ups visible, the Project Notebook preserves meetings, procedures, decisions and site observations in a searchable structure, and Project Tasks connect responsibility, priority, due date, discussion and evidence to the work that must be completed.
What this area includes
04
Structured engineering record
Engineering
Engineering replaces disconnected spreadsheets with project-scoped registers for equipment, software and firmware, I/O, industrial networks, network design and plant zones. Records remain searchable and reviewable, explainable validation identifies exact problems, and controlled import/export lets existing project data move in and out without losing structure or history.
What this area includes
05
Field execution
Execution & Commissioning
Execution uses the approved engineering record as the basis for field verification. Teams can complete I/O checkout, run versioned FAT/SAT and commissioning checklists, raise punch items with ownership and priority, and retain comments and attachments against the exact item so unfinished work and accepted evidence remain visible.
What this area includes
06
Controlled project files
Storage
Storage explains exactly how secure capacity is being used without exposing raw provider paths. It separates project files from reserved and available space, shows pending or failed transfers honestly, identifies the largest records and keeps every download behind the same project authorization and checksum-verification boundary.
What this area includes
Capacity
See used, reserved and available secure capacity before uploading more data.
Project files
Review files by source section without exposing remote storage paths.
Transfers
See pending, failed and completed remote transfers instead of receiving premature success.
Largest files
Identify the records consuming the most capacity while preserving authorization.
07
Immutable file history
Revision Vault
Revision Vault gives each controlled document a permanent, reviewable history. Immutable revisions, approval states, installed versions, Golden Copies and backup-verification records show which file was reviewed, what reached the field, what it replaced and whether the protected copy remains recoverable—without overwriting earlier evidence.
What this area includes
08
Governed change
Lifecycle
Lifecycle governs change from the first request to verified closure. The team records scope and reason, evaluates safety, production, technical, schedule and authorized cost effects, follows guarded review and approval states, and keeps every linked document, task, revision and execution result attached to the decision.
What this area includes
Modification request
State the scope, reason, proposed change, priority and responsible people.
Impact and risk
Assess safety, production, technical, schedule and authorized cost effects.
Controlled status
Use guarded transitions for review, approval, implementation and closure.
Linked evidence
Attach documents, revisions, tasks and execution records to the decision.
09
Purpose-built project views
Project Passports
Project Passports assemble a purpose-built view of the controlled project for a defined audience. Authorized users choose the included notebook, task, engineering, execution, storage and lifecycle records, decide between a live or frozen snapshot, apply access and expiry boundaries, and issue a revocable QR path with printable labels.
Open the live Sample Passport
This link opens the real read-only public output. It is not a mock-up or a marketing-only page.
What this area includes
10
Verified delivery
Handover
Handover measures readiness against the actual records rather than a manually maintained checklist. It evaluates engineering registers, revisions, installed state, backups, tests, punch work and As-Built evidence, then lets an authorized team select the accepted content and freeze a versioned package with a manifest, checksums and auditable source state.
What this area includes
Readiness
Evaluate registers, revisions, installed state, backups, tests, punch work and As-Built evidence.
Package builder
Start from a Project Passport or make a controlled section-by-section selection.
Immutable packages
Preserve version, source state, manifest, checksums and downloadable artifacts.
11
Accountable access
Project Members
Project Members makes access part of the controlled project record. Invitations follow an expiring acceptance flow, roles describe delivery responsibility, section permissions separate engineering, execution, commercial and member-management authority, and activity remains reviewable without exposing unrelated account information.
What this area includes
Invitations
Invite a known collaborator through a controlled, expiring decision flow.
Project roles
Assign ownership and delivery responsibility within the project.
Section permissions
Control engineering, execution, commercial and member-management capabilities separately.
Activity
Review member participation without exposing unrelated account data.
12
Relevant follow-up
Notifications
Notifications keeps actionable events reviewable without turning delivery channels into a data leak. The inbox separates project and personal context, filters and stable references make events findable, read state is isolated per recipient, and channel preferences control which categories may reach email, browser notifications or Telegram.
What this area includes
Project inbox
Keep project-specific events separate from personal global notifications.
Filter and references
Find events by status and stable public reference.
Read state
Mark individual or visible notifications as read without changing another recipient.
Delivery preferences
Control email, browser and Telegram categories from the authenticated account.
Get your next project on track.
Start with the included secure capacity. No card, no time limit and no feature gate.