PPlatform
One governed record for every project
BuildEase is a multi-company, multi-project platform. Each company works in its own workspace; each project is its own boundary; every action goes through one command that checks authority and writes the history.
| Reference | Discipline | Status · code | With | Due · time left | Rev. |
|---|---|---|---|---|---|
| SD-ARC-0142Level 3 façade shop drawing | Architectural | Under review | Consultant | 3 d left | B |
| MS-STR-0031Post-tensioning method statement | Structural | ApprovedA | — | — | A |
| SD-MEP-0217Chilled-water riser shop drawing | MEP | Under review | Consultant | 23 d over | A |
| MS-ARC-0044Façade installation method statement | Architectural | Awaiting resubmissionC | Contractor | 26 d over | A |
| DS-MEP-0088Switchgear design submission | MEP | ApprovedB | — | — | B |
| SD-CIV-0012Storm drainage shop drawing | Civil | Under review | Consultant | 6 d left | A |
| MOS-STR-0007Precast erection method | Structural | Awaiting resubmissionC | Contractor | 4 d left | A |
| SD-ARC-0151Lobby ceiling shop drawing | Architectural | Draft | Contractor | Not submitted | A |
Tracking line · SD-ARC-0142
- Draft
- Contractor PM approval
- Consultant receipt
- Discipline review
- PM approval
- Resubmission
- Closed
Reference · revision · latest code · who has it · time left: one source behind the register, My tasks and Document detail.
In BuildEase todayDocument registerDocument detailMy tasks
Illustrative data
How it is organised
- Company workspace
- Project
- Organisation in its capacity
- Role, discipline and stage
- Company workspaceA customer's own workspace, with its company administrators, people, organisations and storage. Nothing crosses to another company.
- ProjectsCreated through one controlled set-up. A person can belong to several projects with a different role on each; authority on one project gives nothing on another.
- Organisations in their capacityOwner, developer, PMC, consultant, designer, contractor, subcontractor, supplier: registered per project. Permissions follow the capacity on that project.
- Roles and scopeOrganisation, project, role, discipline, document type, workflow stage and action authority are checked separately, scoped to phase, package and location.
The record engine underneath
Documents, inspections, payment certificates and site records share one engine, so every module behaves the same way.
- BrowserUntrusted
- ServerChecks the request
- DatabaseChecks the person
- One commandAuthorise, validate, write
- Audit historyRecorded and sealed
Illustration, not a screenshot
One command per change
Each change is one database command that authorises, validates, writes and records the history in one transaction.
Originals are never changed
Submitted files and records are immutable. A correction is a new revision; nothing submitted is deleted.
Configuration with four eyes
Numbering, forms, workflows and review periods are project settings. Publishing a change needs a second person.
Delegation with an end date
Acting for someone else is time-limited, inside the original scope and the same organisation, and cannot be passed on.
Configured per project, not coded per customer
Review periods, working calendars, document numbering, forms and workflows, disciplines and roles are each project's settings. The product holds no customer's rules.