Documentation

In this tutorial you design one isolated footing for a 400 × 400 mm column, save it into a project and download its calculation report. You need an email address and nothing else — no card, no installation.

1. 1Go to Sign up and fill in Full Name, Email Address, Password and Confirm Password.
2. 2Select Create Account.
3. 3Open the verification email and follow its link. Design tools stay locked until your email is verified.

A project groups every design for one building and gives them one title block and one submission pack.

1. 1Open My Projects.
2. 2Type a name in New project name — for example Tutorial house — and select New project. The project hub opens.
3. 3In Project details, fill in the client, site address, engineer, checker and revision, then select Save details. These print on the report covers in the project.

1. 1On the hub, under 3 Foundation design, select Start new: Single footing. Foundation Design opens on the Single Column tab, with a chip showing that saves go to your project.
2. 2In the Design basis bar, choose IS 456, enter the SBC as 200 kN/m² with the basis net (report), set Founding to 1.5 m, and pick M25 concrete and Fe500 steel.
3. 3Under 1 Footing and task, select Design a footing and Isolated — best of pad or sloped.
4. 4Under 2 Column, enter Width b (along X) 400 and Depth h (along Y) 400.
5. 5Under 3 Loads, enter the Dead case P as 800 kN. Select + Imposed and enter its P as 400 kN. Loads are unfactored, at the top of the footing.
6. 6Select Run Design (or press Ctrl/⌘+Enter).

Code IS 456 · SBC 200 kN/m² (net) · founding depth 1.5 m · M25 / Fe500
Column 400 × 400 mm
Dead P = 800 kN · Imposed P = 400 kN

The result shows the chosen plan size, depth and bars, and every check as demand ÷ capacity with its load combination and code clause. A check passes at 1.00 or below; the footing passes only when every check does.

1. 1Select Save in the toolbar under the design basis bar.
2. 2Go back to the project hub. The footing is listed under 3 Foundation design, and the stage shows its status.

1. 1In the result header, select PDF. The calculation report downloads with every check’s working, a soil-pressure plan, shear and moment diagrams, and the bar schedule.
2. 2To issue everything in the project at once, go to the hub and select Generate submission pack under 6 Submission pack. You get a ZIP with a cover sheet and one PDF per design.

• Run a site planDesign every footing on a plot in one pass.
• Export DXF drawingsTrue-scale drawings with a title block.
• How checks workWhat demand ÷ capacity means here.
• Foundation Design referenceEvery footing type, code and limit.

1. 1Open Foundation Design and select the Single Column tab.
2. 2In the Design basis bar, choose the code (IS 456, ACI 318, Eurocode 2, AS 3600 or CSA A23.3), the SBC and whether it is net (report) or gross / presumed, the founding depth, concrete, steel and cover.
3. 3Under 1 Footing and task, select Design a footing and a type: Isolated — best of pad or sloped, Pad, Sloped or Strip under a wall.
4. 4Under 2 Column, enter Width b (along X) and Depth h (along Y). For an edge column, open Column off the centre, and its bars and enter Offset along X and Offset along Y.
5. 5Under 3 Loads, enter the unfactored Dead case (P, Mx, My, Hx, Hy). Add + Imposed, + Snow, + Wind or + Earthquake cases as needed. Mx moves the load along X.
6. 6Optional: under Your own combinations, select Add a combination to design for your own combinations alongside the code’s.
7. 7Under 4 Soil, check the soil unit weight, water table, base friction μ and the SBC increase for wind or earthquake.
8. 8Under 5 Size and bars, leave the size blank to let the search design it, or fix any dimension.
9. 9Select Run Design (Ctrl/⌘+Enter).
10. 10Read the checks: each shows demand ÷ capacity, the governing combination and the clause. Select PDF to download the calculation report.

See also: Foundation Design for combined footings, pile caps and the other footing types.

1. 1Open Foundation Design on the Single Column tab.
2. 2Under 1 Footing and task, select Check a footing I have and the footing type.
3. 3Enter the column, the load cases and the soil as for a design.
4. 4Under 5 The footing and its bars, enter the plan size, depth and bars exactly as drawn.
5. 5Select Run Design. The result lists every check with its ratio; anything above 1.00 fails and names the clause.

1. 1Open Foundation Design and select the Site Plan tab.
2. 2Bring in the columns: Import Model (ETABS .e2k or CSV), Import Loads (a support-reactions table), or Templates for a sample project.
3. 3Set the plot boundary. Auto builds one from the column positions — convex hull, rectangular, uniform padding, or grid plus padding.
4. 4Set the SBC and design parameters. If you have SPT N-values, SPT estimates the SBC from them.
5. 5Select Run Site Optimization, or click outside the fields and press Ctrl/⌘+Enter.
6. 6Review the plan view, the 3D view and the results table. Select a column to open its checks. Columns that fail list the reason and the remedy tried.
7. 7Open Export to download reports, schedules, IFC or DXF drawings.

See also: The site plan engine for how each placed footing is checked again where it ends up.

1. 1In your analysis program, export the Joint Reactions (ETABS, SAFE, SAP2000) or Support Reactions (STAAD.Pro) table to Excel or CSV.
2. 2In Foundation Design, open Site Plan and select Import Loads, or open the Footing Schedule tab.
3. 3Choose the file. For STAAD, add the .std file as the coordinates file if you want joint positions and load types.
4. 4Check the vertical axis — Z up (CSI) or Y up (STAAD) — and the units the importer found.
5. 5Under Load cases, check each case’s type. Under Joints → columns, match each joint to a column or create a New column.
6. 6Select Import.

.xlsx  .xlsm  .csv  .txt  .tsv  (+ STAAD .std for coordinates)
Template: /templates/civiltech-load-import-template.csv

The conversion from reactions to foundation loads is listed under Load import formats.

1. 1Open Retaining Wall Designer.
2. 2Under Code & safety factors, pick the Design code / country. For IS 456 and ACI 318 you can override the Overturning FoS and Sliding FoS; Eurocode 2 uses EN 1997 partial factors instead.
3. 3Under Geometry, enter Total height H (underside of base to top of ground), the stem thicknesses, Base thickness, Toe length (0 = L-shaped) and Heel length (0 = reversed L).
4. 4Under Backfill, enter the unit weight, Friction angle φ', Surcharge q, the ground slope and any water level behind the wall.
5. 5Under Foundation soil, enter the Allowable bearing pressure and base friction. Add a shear key or passive resistance under Sliding resistance if you rely on them.
6. 6Under Reinforcement, choose Design bars for me, or Check my bars to enter your own.
7. 7Select Run Design, or leave Live on to recompute as you type.
8. 8To size the wall automatically, select Size it for me. Pick a wall from the alternatives plotted by cost and governing ratio.
9. 9Open the Exports tab: PDF or Excel for the report, DXF section for the drawing.

Every DXF is drawn at its stated scale, with real CAD dimensions, standard layers and lineweights, and one title block on every sheet. Values come from the design; anything missing prints as "as specified" or "not supplied".

1. 1Run a site plan (see Run a site plan).
2. 2Open Export and, under CAD / BIM, choose a sheet: Foundation Plan, Column Layout, Footing Sections, Rebar Details, General Notes, Excavation Plan, 3D Wireframe or Complete Set (ZIP).
3. 3In the dialog, choose the Paper Size, Scale and Unit System, then select Export DXF. The foundation plan, column layout and excavation plan ignore the scale you pick: they print at the largest standard scale that fits the whole site on the sheet.

1. 1Save the design first.
2. 2Open your profile and the Projects tab.
3. 3On the design’s row, select the Share with a teammate icon.
4. 4Under Invite a teammate by email, enter their email, choose Can edit or Can view, and select Share.

The teammate needs a CivilTech Studio account. A viewer can open and inspect the design; an editor can also save changes, but cannot re-share or delete it. The same dialog lists People with access and removes them.

1. 1In the module, select Share in the design toolbar, next to Export, Import and Restore last. In Foundation Design, Share sits in the result header.
2. 2A link with the current inputs is copied to your clipboard.
3. 3Send the link. Opening it restores the inputs; the recipient runs the design under their own account.

To discuss the design with the people you shared it with, see Comment on a design.

1. 1Save the design. Comments belong to a saved design, so everyone it is shared with sees the same threads.
2. 2Select Comments in the module toolbar, next to Collaborate. The number on the button counts open threads.
3. 3Under About, choose what the comment is about — the whole design, one of the inputs, or the result you picked with Add comment here.
4. 4Write the comment. Type @ to mention someone who can open the design; pick them from the list.
5. 5Select Comment, or press Ctrl/⌘+Enter.

• Reply answers inside a thread. Everyone who has written in the thread is notified.
• Resolve closes a thread once it is settled; Reopen brings it back. The owner and editors can resolve any thread; a viewer can resolve the threads they started.
• Show Open, Resolved, Mine (threads you wrote in) or Mentions (threads that mention you).
• You can edit or delete only your own comments.
• A thread marked on an older version was written before the design was last saved.

Anyone who can open the design comments on it: its owner, editors and viewers. A client or architect you add as a viewer can comment without being able to change the design. People you mention get an in-app notification that opens the design with the thread highlighted, and an email saying who mentioned them on which design — at most one per design an hour. A new thread notifies the design’s owner. To stop mention emails, use the link in one, or turn off When someone @mentions me in My practice.

1. 1Save the design. A review covers the saved version — save your latest changes before you submit.
2. 2Share the design with your checker (and approver, if you use one). An external reviewer can be a viewer: they can check and approve without being able to change any input.
3. 3Select Review in the module toolbar. As the owner, pick the Checker and, optionally, the Approver, then select Save assignment. You can also Share as viewer by email from the panel.
4. 4The designer (the owner or an editor) selects Submit for checking. The checker is notified.
5. 5The checker opens the design from the notification and selects Mark as checked, or Request changes… with a note (optionally opening a comment thread on the design).
6. 6If an approver is assigned, they select Approve (or request changes). Without an approver, the check is the final sign-off.

• Draft — being designed. Edits save normally.
• In review — submitted to the named checker. Inputs are locked; the designer can Withdraw from review.
• Checked — the checker passed it. Inputs are locked; the approver (if any) approves or requests changes.
• Approved — signed off. Inputs are locked until someone selects Revise (unlock).
• Changes requested — back with the designer, with the reviewer’s note. Edit, save and submit again.

• Only the owner assigns the checker and approver, from the people the design is shared with.
• Only the assigned checker checks, and only the assigned approver approves.
• Nobody checks or approves their own work: whoever submitted it, and anyone who saved changes to its inputs since the last approval, cannot be its checker or approver, and the checker cannot also approve. Working alone? The owner can tick Allow self-check — it is recorded in the audit trail, and the report says “(self-checked)”.
• The owner or an editor submits, withdraws and revises.

While a design is in review, checked or approved, the server refuses any change to its inputs or results — from any device — with a message saying why. Renaming it, its notes and its project status still save. Revise (unlock) returns it to Draft for the next round; the audit trail and the last approved revision are kept. A sign-off is bound to the exact saved revision it was given for: if the content ever changes, that sign-off no longer applies and the design must be submitted again.

Every step — who, when, which revision and round, and the note — is recorded by the server in the Audit trail at the bottom of the panel.

Calculation reports of a saved design carry its review status on every page: “Review: Checked by … on … (rev n)”, “Review: Approved by … on … (rev n)”, or “Review: Not reviewed”. The line comes from the server, so it always matches the review record — and only a report made from exactly the reviewed inputs shows a clean approval. A report whose inputs differ says so; where a report’s inputs can’t be matched to the saved design, it says the inputs were not verified.

Review steps always appear in your notifications. You also get at most one email per design an hour; turn review emails off in Profile → My practice.

When a saved design is shared and someone else has it open, their initials appear next to My Designs in the design toolbar. Hover or focus an initial for the name and role. The person who is editing has a ring and a pencil.

1. 1The first person to change an input becomes the editor. Everyone else who can edit sees a banner such as Ananya is editing — your changes may conflict.
2. 2By default you are on View only: inputs are read-only until they stop editing (a minute or two after their last change, or as soon as they close the design).
3. 3To make changes anyway, select Edit anyway. If they save first, your Save is refused and you can select Save as a copy to keep your work.
4. 4If you own the design, Take over makes you the editor. The previous editor is told on their next update.

You see a banner such as Ananya saved a new version. Select Reload to load their version. Unsaved changes on your page are replaced, so save a copy first if you need them.

1. 1Sign in and open Verify your status.
2. 2Choose Starter — student / freelancer or Academic — professor / researcher.
3. 3Upload your college ID card (Starter) or faculty credentials (Academic) — JPEG, PNG, WebP or PDF, up to 5 MB, with your name and institution visible.
4. 4For Academic, enter your Institutional email (.edu, .ac.in, .ac.uk and similar).
5. 5Select Submit for review. The page shows Under review until a reviewer decides.
6. 6When it shows Approved, select Continue to checkout to subscribe at the discounted rate. If it shows Not approved, read the reviewer’s notes and upload a new document.

1. 1Open the RC Building Estimator. It works without signing in; sign in to save to the cloud.
2. 2Start one of three ways: fill in Describe the building — the estimate builds itself (Built-up area per floor (m²), Floors (ground + upper), Building, Where, Specification) and select Build my estimate; select Import IFC to take members from a model; or start from a template.
3. 3Check the member tables. Each row is a wall, column, beam, slab or footing with a count × floors multiplier and its bars. Paste rows from a spreadsheet if you have them.
4. 4Set rates, finishes and detailing factors under Settings.
5. 5Select Generate estimate (Ctrl/⌘+Enter).
6. 6Read the results: concrete by mix and level, the bar-bending schedule, rebar by diameter, the priced bill and the cost by trade, with a per-sq-ft back-check.
7. 7Open Export for the estimate PDF, the full Excel workbook, the tender BOQ, the bar-bending schedule (PDF or CSV), the measurement book, the programme or the Submission pack — ZIP.

1. 1Generate the estimate. Review steps need a current result — regenerate after any change.
2. 2In the review bar, select Submit for checking.
3. 3The checker comments on items of the bill and selects Mark checked, or Send back with comments.
4. 4The approver selects Approve. An approved estimate is locked; select Revise to change it.

Every step is written to the estimate’s log with who took it. Signed-in steps carry the account; steps taken at a shared desk carry the typed name and are marked as such.

1. 1Open the BIM workspace.
2. 2Select New project, Quick open IFC, Sample project or Import project (a .ctsa package).
3. 3In Model Viewer, add more IFC files from the Model panel to federate them. Use Section for section planes and Plans for storey floor plans.
4. 4Select an element to read its properties. Press H to hide it, I to isolate it, F to fit the view.
5. 5Select Add Issue to raise a BCF issue with a snapshot. Manage issues under Issues; see totals under Dashboard.
6. 6Open BOQ for quantities taken from the IFC.
7. 7Use Paint and Sun to recolour finishes and study daylight; Export image or video saves a PNG or a video.
8. 8To share, open Project actions → Share with client, pick the model, a link expiry (7, 30, 90 or 365 days) and an optional watermark, then select Create client link.

For a report, select Issue report on the Dashboard or Report on Issues, choose PDF document or Excel workbook, group the issues and download. Project actions → Export project package saves the whole project as one .ctsa file, optionally password-protected.

1. 1Open Building Bye-laws Compliance. It works without signing in.
2. 2Choose the state: Bihar, Jharkhand, Uttar Pradesh or Delhi.
3. 3Enter the plot: the four side lengths, the compass direction each side runs (N = 0, E = 90, S = 180, W = 270), and the width of every road it faces.
4. 4Enter the building you intend: floors, height, use and the elements free of FAR such as stilt or basement. Declare any site constraints.
5. 5Select Check compliance, or leave Live on.
6. 6Read each rule with its clause. Rules not transcribed for your state are listed as not checked.
7. 7Download the DXF setback plan or the PDF report.

For a building that already stands, switch to As built to see whether the deviations can be regularised and, where the rules allow it, the compounding fee.

1. 1Open the project from My Projects.
2. 2Fill in Project details and select Save details. The revision goes into the file name.
3. 3Add designs stage by stage: Start new opens a module with the project as its save target; Add existing design links one you already saved.
4. 4Use the hand-offs: Hand SBC to Foundation on a geotechnical design, Send footings to Estimator on a foundation design.
5. 5Under 6 Submission pack, select Generate submission pack.

The ZIP holds 0-cover-sheet.pdf — contents, hand-offs and a reason for anything left out — and one PDF per design, each made by that module’s own report. Cube-test registers have no report, and designs saved in the older foundation store are listed as not included.

Each module also has a public landing page at its folder — for example /civiltechstudio/slab-design — with a worked overview and FAQs. The tool itself needs a signed-in account with a verified email, except the RC Building Estimator and Building Bye-laws Compliance, which work signed out.

Single Column designs or checks pads, sloped pads, strips under walls, plain concrete pads, combined footings and mats under 2–6 columns, and pile caps on 1–9 piles. Footing Schedule designs a list of columns at once. Site Plan places and designs every footing on a plot.

Open it at /civiltechstudio/foundation-design/app. Status: live.

• IS 456:2000, ACI 318-19 and EN 1992-1-1 (Eurocode 2) — every footing type and mode.
• AS 3600:2018 (with AS/NZS 1170.0) and CSA A23.3-19 (with NBCC 2020) — reinforced pads, sloped pads, strips, combined footings and pile caps, on the Single Column tab only.
• Load combinations per IS 875 / IS 456, ASCE 7-16 and EN 1990, in three families: service (soil), strength (concrete) and stability.

• Design basis: code, SBC and its basis (net or gross), founding depth, concrete, steel, cover.
• Column or wall size, and offsets for an edge column.
• Load cases Dead, Imposed, Snow, Wind and Earthquake, each with P, Mx, My, Hx, Hy — unfactored, at the top of the footing.
• Optional: your own combinations, soil unit weight, water table, base friction, passive resistance, crack-width limit, cost rates, plan grid step and longest L:B.
• Pile caps: pile diameter, safe compression, uplift and lateral loads, spacing and edge distance.

• Every check as demand ÷ capacity, with the combination, the clause and the working.
• Soil pressure from a tensionless biaxial solution; 3D model; strip shear and moment diagrams for any strength combination.
• Options explorer: up to 12 plans weighed, plotted by cost against governing ratio.
• FEM cross-check of the designed footing — a plate on soil springs, or a beam on springs for a strip — beside the rigid result and flagged when they disagree (for review; never changes pass or fail).
• Deep pile caps: a Strut-and-tie (deep cap) result group (struts, nodes, ties, anchorage). Under AS 3600 it governs; under the other codes it is shown beside the sectional check. 3-pile caps use the sectional checks.
• Bar-bending schedule (BBS tab), excavation, comparison and sensitivity tabs.
• Exports: calculation PDF, vector PDF, executive summary PDF, Excel, JSON; pile-cap DXF. Site Plan adds CSV, Excel, IFC, an FEM calculation report and DXF drawing sheets.

• AS 3600 and CSA A23.3 do not cover plain pads, the Other types, the Footing Schedule or Site Plan.
• Strap and raft foundations use the earlier cascade engine (Other types) with one service load.
• Not modelled: trapezoidal combined footings, pile-group efficiency.
• Site Plan: a corner column flush with two boundaries needs a two-way strap or tie-beam grid, which is not designed — it fails with that remedy named.

Results are net SBC with the governing method named.

Open it at /civiltechstudio/geotechnical/app. Status: live.

• IS 6403, Terzaghi, Meyerhof and Bowles SPT correlations; settlement by Burland & Burbidge.
• Liquefaction screening per IS 1893-1 Annex F and the NCEER simplified procedure.
• Rock bearing per IS 12070 and Carter–Kulhawy.

• Soil profile: layers with SPT N-values, unit weights and the water table; footing width and depth.
• Boreholes from AGS files; CPT data.

• Tabs: Soil Profile, Results, Diagrams, Calculations, Correlations, Boreholes (AGS), CPT Data, Rock Bearing, Ground Improvement, Downdrag (NSF), Liquefaction Mitigation, Pile Lateral, Nonlinear Soil.
• Exports: PDF calculation report. In a project, Hand SBC to Foundation passes the governing SBC and its basis to Foundation Design.

• The SBC is net unless stated. Check that the basis matches what Foundation Design expects (net (report) or gross / presumed).

Open it at /civiltechstudio/retaining-wall-design/app. Status: live.

• IS 456 / IS 14458: practice factors of safety (overturning 2.0, sliding 1.5; 1.5 and 1.2 with earthquake) plus cl. 20.1 and 20.2.
• ACI 318-19: IBC 2021 §1807.2.3 (factor of safety 1.5, or 1.1 with 0.7E).
• EN 1992-1-1 with EN 1997-1: EQU for overturning, DA1 combinations for sliding and bearing.
• Earth pressure by Rankine or Coulomb; seismic by Mononobe–Okabe.

• Total height H from the underside of the base; stem thicknesses (tapered stem allowed), base thickness, toe and heel lengths (either may be 0).
• Backfill: unit weight, friction angle, wall friction, surcharge, ground slope, water levels behind and in front.
• Foundation soil, base friction, passive resistance, optional shear key; seismic kh and kv.
• Materials, exposure, and either Design bars for me or Check my bars.

• Overturning, sliding, bearing and global (Bishop) stability; member checks as demand ÷ capacity with clauses.
• To-scale stability diagram, member bending and shear diagrams, detailing and a bar schedule (S1–S4, B1–B5, K1–K2).
• Size it for me returns up to 15 alternatives.
• Exports: PDF and Excel report; DXF section.

• Bishop circles don’t model the shear key or the seismic case.
• No shrinkage curvature in deflection; water in front of the wall isn’t counted as resisting; no seismic increase on allowable bearing.
• Factor-of-safety overrides apply to IS 456 and ACI 318 only.

Open it at /civiltechstudio/basement-design/app. Status: live.

• IS 456 with IS 3370 crack-width limits
• ACI 318
• Eurocode 2

• Basement depth, plan length and width, wall and slab thicknesses.
• Wall support: Propped (by the slab above) or Cantilever.
• SBC, soil properties and water table; surcharge.

• Wall and base-slab moments and steel, crack width, uplift factor of safety.
• Exports: design calculation PDF, vector PDF, Excel, DXF, JSON.

• Waterproofing is checked as crack-width control on the concrete; membranes are drawn, not designed.

Open it at /civiltechstudio/slab-design/app. Status: live.

• IS 456:2000 (Annex D coefficients, Table 26)
• ACI 318-19
• EN 1992-1-1

• Two-way: short and long spans, panel type (nine edge-restraint cases).
• One-way: span and support condition. Flat slab: spans L1 and L2, column size.
• Loads, thickness, materials, cover.

• Design moments, steel areas, minimum-steel governance, deflection (span/depth), punching shear.
• Exports: PDF and Excel report.

• Annex D two-way coefficients apply to panels with ly/lx ≤ 2; a longer panel acts one-way, so design it as one.
• Flat slabs use the direct design method.

Open it at /civiltechstudio/section-design/app. Status: live.

• RC: IS 456:2000, ACI 318-19, Eurocode 2
• Timber: IS 883:2016, NDS 2024, Eurocode 5

• Member type, section size, cover, concrete and steel grades.
• Beams: Mu, Vu (and torsion). Columns: Pu, Mux, Muy, unsupported length.

• Flexure, shear, torsion, crack width; column P–M interaction and biaxial bending.
• Exports: PDF report.

• One section at a time; the member forces come from your own analysis.

Open it at /civiltechstudio/shear-wall/app. Status: live.

• IS 456 with IS 13920:2016
• ACI 318-19 §18.10
• EN 1992-1-1 with EN 1998-1

• Wall length and thickness, web steel (two curtains), boundary bars.
• Factored axial load, in-plane moment and shear; materials.

• P–M interaction envelope by strain compatibility, shear (Vc + Vs ≤ Vmax), boundary-element trigger and confinement, minimum steel.
• Exports: PDF and Excel report.

• In-plane actions only.

Open it at /civiltechstudio/masonry-design/app. Status: live.

• IS 1905 with IS 4326 and IS 13828 (seismic detailing)
• TMS 402
• EN 1996 (Eurocode 6)

• Wall height, length and thickness; masonry unit and mortar; loads; seismic zone.

• Slenderness, stress-reduction factors, permissible against actual stress; plinth, lintel and roof bands and vertical steel.
• Exports: PDF and Excel report.

• One wall at a time; the loads come from your own analysis.

Open it at /civiltechstudio/concrete-mix-design/app. Status: live.

• IS 10262:2019
• ACI 211.1
• BS 8500 / EN 206

• Grade, exposure, slump (25–200 mm), maximum aggregate size (10–40 mm), aggregate shape, grading zone, cement type.

• Proportions per m³, trial batches, grading and QC panels, optimisation and comparison.
• Exports: PDF and Excel report.

• Proportions are a starting point for trial mixes; confirm by trial batches.

Open it at /civiltechstudio/water-tank-design/app. Status: live.

• IS 3370 (working stress) with IS 1893-2 sloshing
• ACI 350-06
• EN 1992-3

• Shape, size, water depth, wall and base thickness, freeboard; soil and water table; materials.

• Hoop and vertical steel, permissible-stress and crack checks, flotation factor of safety, sloshing.
• Exports: report PDF and Excel, calculation report PDF, BoQ PDF, DXF. FEM analysis is metered.

• Circular and rectangular tanks only.

Open it at /civiltechstudio/septic-tank/app. Status: live.

• IS 2470 (Part 1) with CPHEEO per-capita flows. The country selector shows the matching US (EPA 625) and EU (EN 12566) references.

• Number of users, sewage per capita, detention time, sludge per capita, cleaning interval, liquid depth, length-to-width ratio, freeboard.

• Sewage flow, detention and sludge volumes, tank length, width, depth; compartment guidance.
• Exports: PDF and Excel report.

• The sizing is always to IS 2470; the country selector changes the cited references, not the numbers.

Open it at /civiltechstudio/rainwater-pit/app. Status: live.

• CGWB recharge guidance, IS 15797, rational method (Q = C·i·A)

• Roof area, rainfall, runoff coefficient, soil infiltration rate, pit depth, storage time, fill porosity.

• Annual harvestable volume, peak inflow, pit dimensions, infiltration check.
• Exports: PDF and Excel report.

• Sizing follows CGWB guidance whichever country is selected.

Open it at /civiltechstudio/cube-test-register. Status: beta.

• IS 456:2000 Cl 16 and Table 11 (individual and 4-group acceptance), Cl 15.3–15.4, Table 8; IS 516 test method

• Grade, pours with their 7- and 28-day cube results, quantity, and the site standard deviation once established.

• Individual-result and 4-consecutive-group acceptance, non-conformance flags, 7-day trend check.
• Save and JSON export; no PDF report.

• Acceptance is to IS 456; the country selector changes the cited references.

Open it at /civiltechstudio/rc-estimator. Status: beta. Works without signing in.

• Standard IS estimating practice; plaster measured to IS 1200.

• A quick-start brief (area per floor, floors, use, place, specification), an IFC model, a template, or member tables.
• Walls, columns, beams, slabs and footings, each with count × floors and its bars; rates, finishes, laps, hooks and wastage.

• Concrete by mix and level; cement, sand and aggregate; bar-bending schedule with real cutting lengths; rebar by diameter; priced BOQ; cost by trade; per-sq-ft back-check.
• Plan, tender and contract stages: cash flow, purchases, proposal, bids, RA bills, variations, cost report.
• Exports: estimate PDF, full Excel workbook, tender BOQ, BBS (PDF, CSV), measurement book, MS Project XML programme, IFC with the estimate, submission pack ZIP.

• Quick-start sizes are preliminary and rates indicative; the quick start goes to G+9.
• Built for non-engineered rural and semi-urban buildings.

Regularisation mode checks a building that already stands.

Open it at /civiltechstudio/bihar-bylaws. Status: beta. Works without signing in.

• Bihar (gazette-verified); Jharkhand, Uttar Pradesh and Delhi (draft — verify against gazette). See Bye-laws jurisdictions.

• Four side lengths, the compass direction of each side, the width of every road the plot faces; deed area, a corner angle or a diagonal for irregular plots.
• The building: floors, height, use, FAR-free elements (stilt, basement, service floor), site constraints.
• Optional: a site-plan DXF to check against the setback envelope.

• Setbacks, ground coverage, FAR, height, floor count, access road, plot size, parking, high-rise trigger — each with its clause.
• Rules not transcribed for the state, named as not checked; itemised sanction fees (unknown where unpublished); document checklist.
• Exports: DXF setback plan and PDF report.

• A pre-check, not a sanction. UP excludes NOIDA, Greater NOIDA and YEIDA.

Open it at /civiltechstudio/archviz/app. Status: beta.

• IFC models; BCF issues

• IFC files (.ifc), or a project package (.ctsa or .zip).

• Sections, storey plans, views, sets, notes, issues with snapshots, dashboards, quantities (BOQ).
• Exports: PNG image, turntable or recorded video, issue report (PDF or Excel), project package, client link (7–365 days).

• Measurements are metric.
• Signed out, projects stay in this browser; sign in to keep models in your cloud storage.

The full list, grouped by purpose, is on Free tools.

Every plan opens every module. Plans differ in monthly credits, saved projects, batch size and a few features. Credits pay for heavy compute and some exports; ordinary design runs are free.

Starter and Academic pricing need a verified student or academic ID — see Submit your student or academic ID. A new account gets one Professional trial per verified email.

Inputs are entered in metric. Where a module offers Export units, you can print the report in SI or Imperial.

Single-key shortcuts such as ?, F or H are ignored while you type in a field. Ctrl/⌘ shortcuts also work from inside a field in Single Column and the RC Building Estimator. In Site Plan, every shortcut waits until you leave the field.

Accepted files are .xlsx, .xlsm, .csv, .txt and .tsv. Legacy .xls is rejected, and so are member-force tables.

The engine works with the load the column puts on the foundation: P downward and compression-positive, Mx moving the resultant along +x (the footing length L, so ex = Mx / P), My moving it along +y (the width B). A reaction is the support’s force on the structure, so the importer negates it:

If at least 80 % of the non-zero dead and live P values are negative, the file holds loads on supports rather than reactions; every component is negated and you are warned. Units come from a units row, the header (FZ (kN)) or your override; forces in kN, N, MN, kip, lb, kgf and tonf are recognised. The output is always kN, kN·m and mm.

Bihar fees vary by local-body class. Jharkhand has per-ULB FAR caps for 42 named bodies. Uttar Pradesh covers Development Authority areas, not NOIDA, Greater NOIDA or YEIDA.

• Engineering glossaryTerms used across the modules, defined.
• Code Clause CompassFind the clause behind a check.
• Verification LibraryEngine output against published reference values, run live.
• ChangelogWhat changed, month by month.
• APIProgrammatic access on plans that include it.

A check compares what the structure must carry (the demand) with what the code allows it to carry (the capacity). The studio reports the ratio demand ÷ capacity, so every check reads the same way: 0.80 has 20 % in hand, 1.00 is exactly at the limit, and anything above 1.00 fails.

Next to each ratio you see the load combination that produced it, the clause it comes from and the working — the intermediate values a checker would want. The check with the highest ratio governs. A design passes only when every check does; there is no averaging and no partial pass.

• The footing FEM cross-check analyses the designed footing as a plate on tensionless springs, or a strip as a beam on springs. A plate’s moments usually come out 3–8 % above the rigid method because of the twisting term, so the result is shown for review, flagged when it disagrees, and never changes pass or fail — the codes design footings by the rigid method.
• In Site Plan, crack-width checks are review-only, and a footing whose worst ratio is between 1.00 and 1.05 is flagged as marginal for you to judge.
• Input hints flag unusual values in amber and impossible ones in red as you type. They explain; they never block a run.

You enter unfactored load cases at the top of the footing. The engine builds the code’s combinations from them in three families, because soil, concrete and stability are checked at different load levels:

Wind acts one case at a time, in both senses. Earthquake in X and Y is combined 100 / 30. Your own combinations are designed for alongside the code’s, never instead of them.

Most soil reports quote a net safe bearing capacity — the pressure the soil can take above what the excavated ground already applied. Presumed values from tables are often gross. Tell the design basis which one you have, so the bearing check compares like with like. The Geotechnical module reports net SBC, and its hand-off to Foundation Design carries the basis with it.

Throughout the studio, Mx moves the load along X: the eccentricity ex = Mx / P is measured against the footing length L, and My moves it along Y against the width B. The load importer converts ETABS, SAFE, SAP2000 and STAAD reactions to this convention, so the same physical reaction gives the same loads whichever program it came from.

Inputs are metric. Modules with a unit toggle display Imperial values, and reports offer an Export units choice of SI or Imperial.

When you leave a size blank, the engine searches rather than guesses. For an isolated footing it lays out up to twelve plans — equal overhangs and aspect ratios up to your longest L:B, on your size step — and for each finds the least depth that passes and the lightest bars that work. A crack-width failure is fixed with more bars before the footing is made deeper.

Pad against sloped is then decided on total cost: concrete, steel, shuttering, excavation, backfill and blinding, at rates you can change. A plan with equal overhangs is preferred when it costs within 3 % of the cheapest, because it is easier to set out and less likely to be built wrong.

Every passing option is returned, not just the winner. Checking any option as given reproduces exactly the governing ratio the search reported — the search and the check are the same engine.

• A pile cap takes the fewest piles that work, then the least depth, then the lightest bars. Its cost includes the piles.
• A retaining wall’s Size it for me varies the base width, the split between toe and heel, the base and stem thicknesses and an optional key, and keeps the cheapest wall with every check passing, plus up to 15 alternatives. Re-running the chosen wall through the design gives the same governing ratio.

Site Plan runs IntelliCascade™, CivilTech Studio’s patent-pending engine for designing the footings of a whole plot together. It works through the columns and footing types, places each footing within the boundary, and merges or reshapes footings that would clash.

Placement alone isn’t proof. A footing designed centred on its column and then pushed inward by the boundary carries the load off-centre; a footing that fits on its own may run into its neighbour. So every footing the optimiser places is checked again where it ends up, by the same engine as a single footing, with the column’s real offset and the bars the schedule actually gives it.

The final check tries remedies in order, keeping the first that passes:

1. 1Redesign the bars and depth in place, when the soil and stability checks already pass.
2. 2Strap the footing to a standing neighbour, or to the edge column facing it across the plot.
3. 3Refit the footing, centred, within the room it has.
4. 4Combine it with its neighbour into one footing.
5. 5Join nearby failing columns on a local mat.

No two passing footings may overlap. A remedy that would run into a standing footing is refused. Anything still failing is reported with its reason and the remedy that would be needed; if even a mat over the whole plot exceeds the bearing capacity, you are told no shallow foundation works and piles should be considered.

The Verification Library runs the production engine live against published and closed-form reference values — Das, Terzaghi, Taylor, Prandtl and exact theoretical identities — and shows computed against expected, the percentage error and a pass or fail for every case. Because it recomputes on every visit, a regression anywhere shows up there.

Behind it, the single-footing, combined-footing, pile-cap and retaining-wall engines are tested against hand calculations, and the browser tests check that the ratios on screen equal those hand values.

• Bye-laws results for Jharkhand, Uttar Pradesh and Delhi are labelled draft until checked against the printed gazettes. Rules not transcribed for a state are listed as not checked, and an unpublished fee is shown as unknown, never as zero.
• A few AS 3600 table values used by the footing engine are still to be confirmed against the published standard.
• Drawings print “as specified” or “not supplied” rather than inventing a value the design didn’t give.

Forms, input hints, diagrams and the 3D views run in your browser. Design checks run on CivilTech’s engines: a Python engine for the code checks and reports, a compiled C++ solver for finite-element analysis, and a .NET service that draws the DXF files. Every engine call goes through the website, which checks your sign-in, your plan and your credits first.

Saved designs belong to your account, and only you and the people you share them with can open them. A share link carries the inputs in the URL, not the design record. In the BIM workspace, models stay in your browser and, when you are signed in, are also kept privately in your cloud storage.