Şantiye-M 2026: Turkey's Mandatory Digital Site Inspection (8 Triggers)

What Is Şantiye-M and Why Did It Become Mandatory?

Şantiye-M is Turkey's mandatory digital site inspection system, developed by the Ministry of Environment, Urbanization and Climate Change. The system fully replaces traditional paper-based building inspection processes with real-time, photographed, geotagged, and auditable digital workflows. Following the 2025 regulation, the system became mandatory for specific project sizes starting in 2026.

Three primary motivations drove the mandatory adoption. First, the 2023 Kahramanmaraş earthquake aftermath revealed serious gaps in transparency and traceability across building inspections — many projects' inspection records were inaccessible, lost, or damaged. Second, paper-based inspection processes were too vulnerable to manipulation and offered no real-time verification. Third, Turkey's EU alignment process required building inspection regulations to digitize.

With Şantiye-M, every site inspection now happens through a mobile app, photographed reports flow with GPS coordinates directly into the Ministry's database in real time, and inspection history is archived electronically in a centralized system. Our data security and KVKK article covers how digital inspection data must be protected in detail.

History and Legal Framework of Şantiye-M

The origins of Şantiye-M can be traced back to Law No. 4708 on Building Inspection, enacted in 2001. The law established Turkey's building inspection institutions and defined their authorities and responsibilities, but largely left the inspection process to paper-based documentation. Building inspection reports, progress billing approvals, and photographic records were stored in physical files and hand-delivered to municipalities or governorates. Limitations of this approach had been debated since the 1999 Marmara earthquake, but structural change lagged for years.

In 2018, the Ministry of Environment and Urbanization issued the first circulars directing building inspection workflows to be moved into electronic environments. During this period the Building Inspection Management System (YDYS) was introduced as a precursor application requiring digital entry from inspection institutions. However, YDYS did not provide field-based visual verification or real-time data flow; it only supported uploading text-based inspection reports.

The destruction or severe damage of more than 50,000 buildings in the 2023 Kahramanmaraş earthquakes forced a fundamental overhaul of building inspection legislation in the eyes of the public and regulators. It emerged that inspection records for many collapsed buildings could not be accessed, reports did not align with projects, and no visual evidence existed proving inspection institutions' physical presence on site. Following these findings, the Ministry launched the Şantiye-M pilot in 2024; the Official Gazette circular published at the end of 2025 announced phased mandatory adoption starting in 2026.

The legal framework rests on three core regulations: Law No. 4708 on Building Inspection, Law No. 6306 on Transformation of Areas Under Disaster Risk, and KVKK (Law No. 6698 on the Protection of Personal Data — Turkey's GDPR equivalent). All data reported through Şantiye-M must comply with the requirements of these three laws. Under KVKK, processing biometric facial recognition photos and location data of site personnel requires explicit consent; our access control article can be helpful in depth on this topic.

Which Projects Require Şantiye-M?

Per the 2026 regulation, Şantiye-M is mandatory for the project categories below. The thresholds were set based on project size and risk class.

Project type	Şantiye-M required?	Threshold
Residential projects	Yes	Total construction area ≥ 5,000 m²
Public investment projects	Yes (no threshold)	All sizes
Industrial facilities	Yes	Industrial buildings, logistics warehouses
High-rises	Yes	Building height > 21.5 m
Earthquake-zone buildings	Yes	1st and 2nd degree earthquake zones
Hotels & tourism	Yes	≥ 100 rooms
Education and healthcare	Yes	≥ 500 m²
Single-family homes	Optional	< 5,000 m² individual

Projects below threshold remain optional today, though the Ministry has announced plans to extend coverage to nearly all building inspection processes by 2027-2028. Firms that adopt early will benefit during regulatory transitions.

Detailed Breakdown of the 8 Triggers

The 8 trigger categories defined by the regulation directly determine how the project owner and contractor enter the Şantiye-M process. The triggers are not independent; a single project may simultaneously activate multiple categories, and in that case the broader category applies. Below we cover the practical meaning of each trigger. A technical breakdown by section can be found in our Detailed Analysis of the 8 Triggers article.

Trigger 1: Residential Projects ≥ 5,000 m²

This trigger covers the majority of mass housing, apartment blocks, and gated community projects. Calculation is based on total construction area — not per apartment or per parcel. For projects under 5,000 m² on a single parcel but planned as integrated with neighboring parcels, the Ministry applies a "functional integrity" test. Our residential sector compliance article can guide with practical examples.

Trigger 2: Public Investment Projects (No Threshold)

All public investment projects fall under Şantiye-M scope regardless of budget size or area. "Public investment" here parallels the Court of Accounts (Sayıştay) audit definition: all construction work financed by central government, local administrations, SOEs, and special-budget agencies. Public-private partnership (PPP) projects also fall within this scope.

Trigger 3: Industrial Facilities

Industrial production facilities, logistics warehouses, structures within Organized Industrial Zones (OSB), production lines, and storage areas fall under this scope. In industrial facilities, fire safety and chemical risk management inspections are reported via additional Şantiye-M modules. An industrial facility being under 1,000 m² does not remove the Şantiye-M obligation; being an industrial facility is a standalone trigger.

Trigger 4: High-Rises (Above 21.5 m)

Building height is measured from ground level to the highest roof level. 21.5 m is the threshold where the Turkish Building Earthquake Regulation defines "high-rise." This trigger also requires structural system calculations, fire scenarios, and evacuation plans to be reported via Şantiye-M. Elevator installation inspections are handled as a separate module.

Trigger 5: Earthquake Zones (1st and 2nd Degree)

All projects located within 1st and 2nd degree earthquake zones, per AFAD's 2018 Turkey Earthquake Hazard Map, fall within Şantiye-M scope. In this category, digital transmission of geotechnical survey reports, real-time reporting of concrete quality test results via laboratory API, and photographed rebar inspection are mandatory.

Trigger 6: Hotels and Tourism Facilities (100+ Rooms)

Tourism Ministry-licensed facilities with 100 or more rooms must use Şantiye-M. In hotel projects, additional reporting is required especially for fire safety, smoke-free evacuation paths, and functional flow inspections.

Trigger 7: Education and Healthcare Facilities (500+ m²)

Schools, daycares, universities, hospitals, clinics, and family health centers above the 500 m² threshold fall under Şantiye-M. Healthcare facilities also undergo parallel inspection coordination with the Ministry of Health, education facilities with the Ministry of National Education (MEB).

Trigger 8: Single-Family Homes (Optional)

Single-family homes below 5,000 m² are currently optional. However, the Ministry's 2027-2028 roadmap envisions removing this threshold entirely and bringing single-family homes into mandatory scope. Early adopters are expected to capture competitive advantages in the upcoming period.

Sector-Based Application: How Does Şantiye-M Affect Each Sector?

Şantiye-M's application varies notably across sectors. Below we summarize how Şantiye-M scope plays out across the main branches of construction.

Sector	Şantiye-M Scope	Special Modules
Residential (mass housing, gated)	Mandatory ≥ 5,000 m²	Unit handover form, common area inspection, elevator
Office and plaza	Mandatory for high-rise or 5,000 m²+	HVAC, fire scenario, BMS
Commercial (mall, market)	Mandatory at all sizes	Evacuation scenario, food area inspection
Infrastructure (road, bridge, tunnel)	Mandatory as public investment	Soil deformation measurement, geotechnical test
Industrial (factory, warehouse)	Mandatory at all sizes	Environmental impact, chemical management, ATEX
Education and healthcare	Mandatory ≥ 500 m²	Accessibility, acoustic insulation, healthcare infrastructure
Hospitality (hotel, resort)	Mandatory 100+ rooms	Fire safety, environmental aesthetics

These sector-based differences also affect the specialty selection of building inspection institutions. A firm doing industrial inspection is not expected to offer equal competence on residential projects. Contractors selecting an inspection institution with the right project-type expertise is critical for an efficient Şantiye-M process.

Şantiye-M Process Flow: A 10-Step Project Lifecycle

A project's Şantiye-M lifecycle proceeds in 10 main steps from permit application to occupancy delivery. The flow below summarizes the operational side of the process from the perspectives of the contractor and the inspection institution.

1. Permit Application and Project Registration: When a permit is filed with the municipality, the project is automatically registered in the Şantiye-M database. Project details (parcel no, block no, building class, m², floor count) are also confirmed via Şantiye-M.

2. Building Inspection Institution Assignment: Via the Ministry's authorized portal, one of the licensed inspection institutions for the province/region is assigned. There is no contractor-side selection; assignment is made by the Ministry.

3. Foundation Opening Approval: Geotechnical survey reports, geotechnical test results, and excavation plans are reported via Şantiye-M. The Ministry issues the foundation opening approval digitally.

4. Periodic Field Inspections: The inspection engineer visits the site monthly (or more frequently per project requirements), prepares location-verified photographed inspection reports via the mobile app.

5. Concrete Test Reports: Before and after each pour, concrete quality tests are performed by accredited laboratories. Results are automatically transferred to Şantiye-M via the lab API.

6. Rebar Inspection: Formwork and rebar layout inspections are photographed for each floor. Critical data such as steel quantity, diameter, stirrup spacing are recorded.

7. Structural Completion Approval: When the entire load-bearing system is completed, a "structural completion" notification is filed with joint signatures of the inspection engineer and contractor.

8. Finishing Works Inspection: Installation, cladding, insulation, and mechanical system inspections are handled in separate modules.

9. Occupancy Permit Application: Once all inspection reports are complete on Şantiye-M, the occupancy permit application is filed. Missing data suspends the process.

10. Project Closure and Archiving: After occupancy is granted, all inspection records are stored for a minimum of 25 years. These records are referenced in any damage or legal proceeding during the building's lifetime.

Şantiye-M Data Sets: What Data Is Reported?

Data sets uploaded to the Şantiye-M system are not uniform. Core data categories of the system are:

• Daily attendance data: Who worked at what time and in what role on site; biometric or QR-based attendance records if applicable.
• Photographed inspection reports: A minimum of 5-10 photos per inspection visit; tagged with location, timestamp, and inspector identity.
• Measurement data: Outputs from devices such as laser distance meters, concrete hardness tests, steel carbon measurement.
• Quality reports: Accredited laboratory reports (concrete, steel, aggregate, water).
• Non-conformity reports: Non-conformities detected during inspection, photographed evidence, and corrective action plans.
• Occupational health and safety records: Work accidents, near-miss events, PPE inspections. Our ACSHB OHS inspection guide covers this in detail.
• Environmental impact measurements: Dust, noise, waste management reports.
• Progress billing approvals: Signed version of the period's progress billing approval by the inspection institution.

All these data sets flow into a single central platform, and Ministry auditors perform field verification through random sampling on the reported data. When manipulation is detected at the data source, administrative penalties and suspension of the inspection institution's authority are initiated.

Şantiye-M Penalties and Risk Management

Under the 2026 regulation, administrative fines applied to Şantiye-M violations vary based on project size and violation type. The table below summarizes the most common violation types and penalty amounts. For detailed risk management refer to our penalties and risk management guide.

Violation Type	Administrative Fine (TL)	Additional Sanction
Not uploading inspection report to Şantiye-M	10,000 - 50,000	Doubles on repeat
Location manipulation (fake GPS)	50,000 - 250,000	Inspection institution authority suspended
Concrete/rebar data inconsistency	100,000 - 500,000	Construction halt order
25-year archiving requirement violation	25,000 - 100,000	Insurance invalidation
Repeated violation (3 times)	No upper limit	Blacklist, ban from tenders
Failure to report non-conformity	75,000 - 300,000	Criminal liability initiated

From a risk management perspective, Şantiye-M violations create reputational risk, blacklist risk, and insurance invalidation risk beyond direct financial penalties. In particular, the inability of a blacklisted firm to participate in public tenders for three years can mean annual revenue loss in the millions of TL for a mid-sized contractor. For this reason, treat Şantiye-M as an integrated piece of corporate risk management, not "another bureaucratic burden."

The Relationship Between Building Inspection and Şantiye-M

Şantiye-M does not eliminate building inspection institutions; rather, it moves their workflow onto a digital backbone. Under Law No. 4708, building inspection institutions remain the primary inspection actor for the project. Şantiye-M imposes mandatory standards on how that inspection activity is documented and reported.

In practice, the building inspection institution dispatches inspection engineers to site; the engineers log in to the Şantiye-M app on their mobile devices and record inspection data. The contractor also maintains a parallel data stream into the Şantiye-M system — progress billing approvals, procurement records, and daily attendance data are transferred from the contractor side. The Ministry cross-checks both data streams and automatically detects inconsistencies.

Building inspection fees have also been revised alongside Şantiye-M. The traditionally percentage-of-cost fee is now structured to include inspection frequency and reporting density. Some inspection institutions try to pass additional software costs for Şantiye-M compliance onto the contractor; however, the Ministry circular clearly states these costs are included in the inspection fee.

Ministry-Accredited Vendor List: What Is It and How to Apply?

Software that will transmit data to Şantiye-M must be accredited by the Ministry of Environment, Urbanization and Climate Change. The Ministry publishes an annually updated list of "accredited Şantiye-M software"; contractors and inspection institutions may only carry out official reporting through software on this list. AECKraft is not on this list; AECKraft is used to manage the operational workflow surrounding the Şantiye-M process (project management, progress billing tracking, document and visual archive, KVKK-compliant data storage) and must be used alongside a Ministry-approved vendor for official reporting.

Criteria a vendor must meet to be Ministry-approved:

• Be a legal entity registered in Turkey
• Provide KVKK-compliant data storage infrastructure in Turkey-based data centers
• Hold ISO 27001 information security certification
• Successfully complete the full integration test process with the Şantiye-M API
• Offer a mobile field application (iOS + Android)
• Provide location (GPS) and timestamp validation mechanisms
• Integrate with digital and e-signature standards
• Guarantee 25-year archiving (contractually committed)
• Provide Turkish-language interface and technical support

Accreditation takes an average of 6-12 months and technical test costs are borne by the software firm. Vendors on the list are regularly audited by the Ministry; those falling below standards are removed. Contractors must pick one of the listed software products for official reporting.

Software Compliance Requirements for Şantiye-M

For a construction management software to be Şantiye-M compatible, it must meet specific technical and workflow integration requirements.

1. API Integration

The software must connect to Şantiye-M's RESTful API endpoints and transmit inspection data through them. The API supports core operations: creating new inspection reports, updating existing reports, photo/video upload, querying inspection history, and reporting non-conformities. Our construction software selection criteria article covers the importance of API integration in detail.

2. Mobile Device Support

Site inspections happen in the field on mobile devices, so the software must run as a native iOS/Android app or a progressive web app (PWA). Camera access, GPS, offline capability (in low-signal areas), and later sync are all baseline expectations.

3. Location and Timestamp Validation

All inspection data is recorded with GPS coordinates and timestamps. The software must auto-attach this metadata to every photo and report. To prevent manipulation, the timestamp is validated server-side, independent of the user's device clock.

4. Data Residency and Archiving

All inspection records under Şantiye-M must be archived for a minimum of 25 years, set with regard to building lifespan and potential legal proceedings. The software must store data in Turkey-located data centers in accordance with KVKK (Turkey's GDPR equivalent). Data stored on overseas servers can create Şantiye-M compliance issues.

5. Authorization and Signature Workflow

Different roles — building inspection engineer, site supervisor, contractor representative, building owner — require separate digital signature support. Our authorization and access control article covers this critical topic. Integration with e-signature or mobile signature is mandatory for inspection reports to gain legal standing.

Risks of Using Non-Compliant Software

Firms using software not aligned with Şantiye-M face multiple operational and legal risks — both direct financial impact and reputational damage.

The first risk is permit-process delay. Receiving an occupancy permit requires complete and correct inspection records to be submitted via Şantiye-M. With incomplete or incompatible data, occupancy processes can be delayed by weeks; during that time delivery, sales, and customer relations all suffer. Our cost control article examines the impact of such delays on profitability.

The second risk is rejection of inspection reports. Reports submitted in formats not accepted by the Ministry require re-inspection, generating extra cost and disrupting the project timeline. The third is administrative fines. Per the 2026 regulation, building inspection institutions and contractors that operate inspections without Şantiye-M can face fines starting at 10,000 TL, escalating with repeated violations.

The fourth is challenges in insurance and compliance audits. Construction insurance and bank financing increasingly treat Şantiye-M compliance as a standard requirement. Non-compliant firms are at a disadvantage in financing and insurance processes.

12 Common Mistakes in Şantiye-M Implementation

The most common mistakes Ministry auditors identified during the pilot phase and at the start of 2026 are listed below. Each mistake has both a prevention method and a corrective action when detected.

Mistake 1 — Late reporting: Not uploading the report to the system within 24 hours after the inspection visit. Prevention: Real-time upload via the mobile app on site.

Mistake 2 — Missing photos: A minimum of 5 photos is required per inspection report; reports below that count are rejected.

Mistake 3 — Wrong project code: Firms with multiple active projects may upload data to the wrong project code, requiring costly manual transfer.

Mistake 4 — Concrete test report time inconsistency: When there is an illogical gap between concrete pour and lab test dates, the system raises an automatic alert.

Mistake 5 — Location verification failure: When the engineer's GPS position does not match the project's coordinates, the report is invalidated. Prevention: GPS verification test before field work.

Mistake 6 — Supplier document gaps: When TSE or CE certificates of steel, cement, and aggregate suppliers are not uploaded, warnings appear in Ministry audits.

Mistake 7 — Skipping a signature in the workflow: If the engineer signs the report but the site supervisor does not, the report remains in "half-signed" status.

Mistake 8 — Non-conformity not reported: An observed non-conformity is photographed but logged as a "routine inspection" rather than as a non-conformity. The Ministry treats this as fraudulent reporting.

Mistake 9 — Data duplication: Re-uploading the same inspection report with different dates.

Mistake 10 — Skipping PPE inspection: Occupational health and safety inspection is mandatory on every visit but gets skipped.

Mistake 11 — Authorization confusion: A user logging in with someone else's identity or making unauthorized data entries.

Mistake 12 — Archiving neglect: Local copies not being regularly backed up; the misconception that uploading to the Ministry system counts as sufficient "archiving."

Most of these mistakes can be prevented with proper workflow design and training. Our Excel to AECKraft migration guide shares practical steps for moving to a structured workflow.

How AECKraft Supports Your Şantiye-M Compliance Process

Important note: AECKraft is not a Ministry-accredited Şantiye-M software with direct API connection to the Şantiye-M system. Official inspection reports must be submitted through a vendor on the Ministry's approved Şantiye-M software list. AECKraft instead supports the surrounding operational workflow — project tracking, progress billing, document and photo archive, authorization — making it easier for your firm to keep Şantiye-M-bound data clean and complete.

AECKraft consolidates project management, progress billing (hakediş), document management, and KVKK-compliant Turkey data residency in a single platform. Keeping visual evidence and metadata required for Ministry submissions organized inside the company, tracking which project is at which inspection stage from the project dashboard, and assigning distinct permissions to different roles (project manager, site supervisor, contractor) all contribute to clean, complete data flowing into your Şantiye-M process.

AECKraft stores all project and progress billing data in Turkey-based data centers in full KVKK compliance. Data never leaves Turkey — critical for KVKK requirements. With multi-user, role-based authorization, stakeholders such as inspection engineers, site supervisors, contractors, and building owners can access the system at the appropriate permission level.

Key AECKraft features that support the Şantiye-M process:

• Document archive: Project permit files, architectural and structural drawings, contracts, and supplier documents are managed in a single centralized archive. Any document requested in a Ministry audit can be retrieved within seconds.
• Photo management: Site photos are tagged with project, block, floor, and inspection date; metadata matching is easier when transferring to the accredited Şantiye-M software.
• KVKK-compliant Turkey data storage: Your data is stored in ISO 27001 certified data centers in Turkey; there is no overseas data flow.
• Role-based authorization: Separate permission definitions are set for different roles such as project manager, site supervisor, building inspection coordinator, and progress billing officer.
• Progress billing tracking: The background calculation required for progress billing approval on Şantiye-M is performed within AECKraft; results can be transferred to the accredited vendor or accounting team via Excel/CSV export.
• Version control and audit trail: Every change is logged with who, when, what data, and how. Critical for answering "who did what" questions during Ministry audits.
• Mobile field application: Field personnel enter photos and inspection notes instantly via the iOS and Android mobile app; data is later transferred to the accredited Şantiye-M software.
• Risk register: Tracks project-specific risks; shows the contractor what to watch out for before a Şantiye-M inspection visit.

All these features are bundled into a single SaaS platform, and can be tested on your real projects with a 14-day free trial (no credit card required). You cannot use AECKraft for official Şantiye-M reporting directly; but alongside a Ministry-approved Şantiye-M vendor, AECKraft manages the entire operational burden of the Şantiye-M process in a scalable, traceable, and auditable way.

Migration Plan: 6 Steps to Şantiye-M Compliance

Firms moving to Şantiye-M compliance benefit from a systematic migration plan. Below is a six-step roadmap.

Step 1: Identify which active projects fall under Şantiye-M scope

Evaluate active projects against the table above. Which ones are mandatory in 2026? This determines priority sequencing.

Step 2: Coordinate with your building inspection institution

Make sure your inspection firm is also transitioning to Şantiye-M. Software compliance is bilateral — both the contractor (you) and the inspection institution must integrate with the system.

Step 3: Software selection or evaluation of existing tooling

For official Şantiye-M reporting, select a solution from the Ministry's published list of approved Şantiye-M software. You will also need a platform to manage day-to-day operations like project management, progress billing, and document archive. See AECKraft's project management, progress billing, and KVKK-compliant data residency details on our features page.

Step 4: Staff training

Train site supervisors, inspection engineers, and office staff on how to use the system. Two days of intensive training is typically enough for the team to start using the system effectively.

Step 5: Pilot project test

Don't migrate every project at once — start with a small or mid-sized pilot. Resolve issues from the pilot before rolling out widely.

Step 6: Monitor and iterate

Each month, verify that inspection data is being transmitted complete and correct. KPIs to track: inspection report count, average report time, withdrawn report rate. These metrics show whether the process is healthy.

Frequently Asked Questions

When did Şantiye-M become mandatory?

Şantiye-M's legal foundation became effective in 2025. Starting in 2026, it is mandatory for the project classes listed in the table above. The Ministry plans to extend coverage to smaller projects in 2027-2028.

What happens if I don't use Şantiye-M?

Permit-process delays, rejected inspection reports, administrative fines starting at 10,000 TL, and disadvantages in insurance/financing processes. Repeated violations may result in temporary suspension of the inspection institution's authorization.

How do I know if my current project management software is Şantiye-M compatible?

Ask your software vendor three questions: Does it have Şantiye-M API integration? Is data stored in Turkey (KVKK)? Does it have a mobile field inspection module? If the answer to all three is "yes," compliance is highly likely. For detailed verification, check the Ministry's published list of compliant software.

Is Şantiye-M expensive for small construction firms?

Access to the Şantiye-M system itself is free as of 2026, provided by the Ministry. The cost comes from the software you use. While AECKraft does not perform Şantiye-M reporting itself, it bundles project management, progress billing, and document archive in a single package, helping reduce overall operational costs around the process.

Does Şantiye-M apply to international projects too?

No, Şantiye-M is mandatory only for construction projects in Turkey. International projects must follow the local building inspection regulations of that country.

Who can access Şantiye-M data?

Şantiye-M data is primarily accessed by authorized auditors of the Ministry of Environment, Urbanization and Climate Change. In addition, the building inspection institution, contractor firm, building owner, and data requested by the Court of Accounts, insurance companies, and courts when needed are shared through official channels. Under KVKK, data sharing is limited to authorized institutions upon official written request.

How should I select an accredited Şantiye-M vendor?

Check the Ministry's current accredited vendor list (updated annually). Factors to consider in vendor selection: annual subscription cost, mobile app usability, training and support, sector expertise (residential/industrial/infrastructure), API integration quality. Our software selection criteria article shares a detailed decision matrix on this topic.

Is AECKraft on the Şantiye-M vendor list?

No. AECKraft is not a Ministry-accredited Şantiye-M vendor; therefore, official inspection reports cannot be sent directly from AECKraft to the Ministry system. AECKraft is a complementary SaaS platform that manages the operational workflow (project management, progress billing, document archive, photo management, KVKK-compliant data residency, role-based authorization) around your Şantiye-M process. It is used alongside a Ministry-approved vendor for official reporting.

Conclusion and Next Steps

Şantiye-M is a one-way digital transformation step for Turkey's AEC sector. Using non-compliant workflows for projects in 2026's mandatory scope creates both operational and legal risk. For official Şantiye-M reporting, pick a vendor from the Ministry's approved Şantiye-M software list; AECKraft then complements that by streamlining the surrounding operations with project management, progress billing tracking, KVKK-compliant Turkey data residency, and role-based authorization.

For deeper detail beyond this pillar article, see our satellite posts: Detailed Analysis of the 8 Triggers, Residential Sector Compliance Guide, ACSHB OHS Inspection Guide, and Penalties and Risk Management. For broader context we also recommend our Complete Guide to Construction Project Management and Software Selection Criteria articles.

To streamline your firm's workflows with AECKraft, contact our team via the contact form or test the system on your real projects with our 14-day free trial (no credit card required). Our pricing page shows packages that include project management, progress billing, and other modules. To stay current on regulatory changes, follow our blog — we regularly cover sector regulations and digital transformation trends.