Learn how our community members use Morta to drive their project performance.
25 stories
Colin Bell & Tom Crossley
Kier extended an information delivery planning approach from Ministry of Justice pathfinder projects into its regional construction business, using a controlled template, project-agreed responsibilities and connected reporting from project to business level.
Ashley Dawson & Tom Crossley
Kier connected information delivery plans, Viewpoint records and role-specific workflows inside its IM Excellence programme. The work removed weekly spreadsheet consolidation, reused one reporting pattern across seven custodial projects and left wider connections unfinished.
Andy Boutle
ALEC extended connected information management resources into labour onboarding, newsletter production and software requests. Controlled views let departments maintain their own records, while the labour tracker ran without Andy Boutle's day-to-day involvement.
Andy Boutle
ALEC connected reusable templates and a BIM 360 model tracker in Morta. On one project, a weekly metadata refresh replaced manual checks and entry, while permissions, peer review and wider adoption still required work.
Abdelrhman Negm
ALEC connected package identity, planned dates, onboarding and Aconex drawing data in one matrix. Restricted working tables fed shared Morta and Power BI views, while the demonstrated Aconex refresh was inactive.
Mariano Amoedo & Samuel Soh
Mott MacDonald moved a plan for more than 10,000 expected deliverables from Excel into connected Morta tables. Shared document numbers linked planning with SharePoint and Aconex status, while reviewers retained control of submission.
Christian Thomas
AJ Digital gave operations and maintenance packages a common, configurable structure. Combined maintenance data, staged technical review and role-specific readiness views helped teams find information and track what was needed for practical completion.
William Baker-Jones
William Baker-Jones explains proactive information management by linking requirements and delivery dates to the activities they enable. His Babcock examples show why information value, access and security form part of the same business conversation.
William Baker-Jones
Babcock connected requirements held in Morta to Python and IfcOpenShell for repeated IFC checks. William Baker-Jones's comparison reduced processing for 404 model files from 128 hours to 13.4 hours, with some reporting steps still in development.
Thibaud Guerrero & Ioan Evans
Bouygues TP Murphy JV and Arup Mott MacDonald JV used Morta as a common starting point for deliverables across Asite and ProjectWise, then extended the shared structure into programme reporting, consents and procurement.
Helen Luhaäär
Bouygues UK connected delivery and hoist booking choices to the limits of a restricted construction site. The workflow checked notice periods and permitted combinations while keeping approval, rejection and urgent exceptions with the logistics team.
Pawel Kudosz
Digital Guerrilla sent selected Revit schedules into prepared Morta tables for checking. Configured rules, supplementary Python checks and a navigable summary helped reviewers find the information design teams needed to correct in Revit.
Kasia Russek
Kane Group connected its drawing release schedule to client information and created views for different responsibilities. Document controllers could check issues and responses, while designers could find drawings requiring issue, revision or follow-up.
Jamile Tuma & Alessandro Napoli
Mace Consult created a consistent review route across contractors' different common data environments. Discipline assignments linked reviewers to current files, while an overview of their votes helped the lead technical adviser direct follow-up.
Glenn McCaffrey, Geri Gardner and 1 other
McLaughlin & Harvey connected delivery plans to actual submissions, shared model-check results with delivery teams and collected supplier data in asset registers. Agreed responsibilities and linked records showed what arrived, what needed correction and who needed support.
Matthew Scard, Jeannine Gavaghan and 2 others
The Ministry of Justice connected delivery information, shared requirements and technical standards for different prison categories. Digitising derogation information at receipt supported internal review while suppliers changed incrementally, with further connections still planned.
Allan Binns
Project Four separated building regulations evidence selection from plan review. Designers selected evidence in the CDE, Morta organised regulation-specific references, and the plan checker recorded applicability, decisions and comments in a separate tracker.
Rob Jackson
RLB Digital built a reusable template linking requirements, delivery plans and checks. Shared directory details and classification values reduced repeated entry, while client documents, project adaptation and further connection testing remained part of the work.
Rob Jackson
Rob Jackson explains how shared text, linked code lists and reusable templates connect information otherwise maintained in separate files. His practical starting point was one defined process, considered with its wider relationships from the outset.
Allan Binns
Ryder Architecture was developing a tracker connecting building regulations requirements with responsibilities, workstages and evidence. The structure gave principal designers a way to plan contributions, follow supporting documents and review each design response.
Javier Lopez, James Bishop CMgr and 2 others
SES Engineering Services connected planned deliverables with documents arriving in Dalux, then brought setup requests, licences, training and feedback into a governance hub so its digital team could identify rollout and support needs.
Mark Harrison & Josh Barnsley
Sir Robert McAlpine paired information delivery planning and shared data workflows with four review gates, configurable templates, training and project support. The process allowed an alternative tool or a useful project-only build where appropriate.
Dexter Robinson
Sphere's construction-data team reconciled invoices, attendance records and timecards before referring uncertain payment lines for human review. Shared definitions also supported handover comparisons and forecasts, while systems and future predictions still required judgement.
Jan Artemenko
Stantec's Buildings group connected project requests, individual workloads and resourcing reviews through weekly allocations. The same records fed Power BI views of utilisation and forecast fees, while people retained responsibility for staffing decisions.
Megan Hughes & Veronique Makhlouf
XD House used a structured Morta template to organise its appointed-party duties from tender response through model delivery. Connected team, plan, submission and RFI records supported selection and review without replacing human checks.
Get started