Every feature, a real use case, and where to find it

Seven roles, each with its own navigation and permissions: Owner, Admin, Project Engineer, Site Engineer, Labour, Client, and Marketplace accounts (Material Vendor / Manpower Contractor). On top of these, five additive permission grants (Project Manager, Quantity Surveyor, Billing Engineer, Accounts, Equipment Manager) unlock specific commercial actions without changing anyone's base role.

Use case: A Site Engineer also does the billing for one project. Instead of promoting them to Admin (which would expose payroll and every other project), you grant them "Quantity Surveyor" — now they can edit that project's BOQ and nothing else changes.

Find it: A member's role is set when they're added; grants are managed from Management → My Company → Members → BOQ Roles.

Two live registration paths: Construction Company (creates an organisation + Admin account, with a 28-day free trial on the plan you choose — Starter, Growth or Professional; Enterprise is set up with our team) and Client / House Owner (a standalone account with no organisation, used to track a build from the buyer's side). Both support signing up with Google. The company sign-up also asks what kind of work you do — that sets your starting organisation type, which you confirm later in your company settings. Manpower Contractor and Material Vendor self-registration exist behind the scenes but are marked Coming soon and not reachable from the sign-up screen yet.

Use case: A contracting firm's owner signs up as a Construction Company on a Friday evening, has their Admin account active immediately, and starts adding projects and staff the same night — no sales call, no waiting for setup.

Find it: The Sign Up button on the login screen.

Sub-projects require Professional or above.

Every project tracks location, budget, dates, documents, finances and progress in one place, and can carry up to 10 photos of the site or building — add them while creating the project or later; the first becomes the picture on the project's card in place of the default icon (your client sees it too), and every photo is encrypted at rest like any other upload. A large job can be split into sub-projects — full projects in their own right, each with its own budget, project engineer, site engineer, tasks, BOQ, DPR and materials — without consuming extra project slots on your plan. A sub-project inherits only its parent's client, branch and district; everything else about it runs independently. The parent shows a budget-allocation card — Total, Allocated (the sum of its sub-projects' own budgets) and Unallocated — so splitting a budget across sub-projects stays visible at a glance, and sub-projects can be dragged to reorder.

Use case: A 200-unit township is one contract but four site engineers each run one block. Splitting it into four sub-projects gives each engineer their own budget, materials and progress tracking — an ₹8 Cr total allocates ₹2 Cr to each block with nothing left unaccounted for — while the owner still sees the township roll up as a single project.

Find it: Photos: Add Project → Project Photos, or Project detail → Overview → Project Photos (Owner/Admin add and remove; everyone on the project can view). Sub-projects: Project detail → Overview tab → Sub projects toggle → Sub Projects tab → Add sub-project. Tapping any sub-project opens its own full project screen — the same tabs as a top-level project.

Drawn from the floors and sub-tasks your team logs in Progress — the more you log, the more accurate the building.

Every project card shows a small animated drawing of its building site, built floor by floor from the work your team has logged — no separate setup. Each floor named in your tasks becomes a storey, and each sub-task shows on it: columns rise with framing, the slab is poured, bricks fill in with masonry, pipes, wiring and tiles appear, paint creeps up the walls, and a floor gets a tick when it passes inspection. A crane carries what the busiest floor needs, workers do their trade where work is in progress, and a site board at the gate shows the % complete and spend against the estimate — red with the amount over when it goes over budget. A paused project freezes and greys out behind a barrier; a finished one stands at dusk with its lights on. Open the project for a larger view with every floor labelled and a line on what is happening where.

Use case: An owner with eight running sites opens the Projects screen and sees, without opening anything, that Anna Nagar Towers is still digging its foundation, Coimbatore Mall has bricks going up on three floors while the top floor is still being framed, and Erode Warehouse has been paused — before anyone has sent a report.

Find it: Projects — the banner on each project card. Larger view: Project detail → Overview, at the top. Follows your phone's reduce-motion setting.

Task/DPR integration requires Enterprise.

A contract's priced item list, tracked per project through a Draft → Active → Closed lifecycle. Items can be seeded from an estimate, and mix original contracted scope with post-award extra items. Setting up the first BOQ is now part of creating the project itself — import an estimate's line items or type them in manually — and stays fully editable from the BOQ tab afterwards exactly as before. Once a BOQ is active, updating a task can also record how much of a BOQ item that task built and what material it used, kept as its own number alongside contractor-measured quantities rather than merged into them. On Enterprise, a BOQ's status can additionally be updated straight from a task update, and every DPR carries a read-only BOQ status snapshot. Measuring and certifying work against BOQ items is covered separately under Subcontractor Commercials. Not yet built: RA billing — running bills against certified quantities.

Use case: A Quantity Surveyor adds 40 contracted line items to a BOQ, activates it once the contract is signed, and later raises three extra items for a client-approved scope change — all tracked in one list instead of a spreadsheet nobody else can see.

Find it: Project detail → BOQ tab.

Build a costed, line-by-line estimate before a project exists, or straight from within one. Estimates are always fully editable — add, price and remove line items any time, with net/GST/gross totals kept in sync automatically as you go. Attach a standalone estimate to a real project once the job is won, and its numbers become the numbers you build against — a project-attached estimate can also seed a BOQ directly. Export any estimate as a branded, watermarked PDF to send to a client. How many estimates you can keep depends on your plan.

Use case: A firm quotes five jobs in a month and wins two. All five are priced in CrewSense; the two that land get attached to new projects with their line items intact and exported as a clean PDF for the client's records, and the three that do not stay on file — still fully editable — to be reworked when the client comes back next season, instead of living in five different spreadsheets.

Find it: Admin console → Estimates, or the app's Admin hub → Estimates. Export PDF is in the top bar of any open estimate.

Tasks are grouped by floor into a connected "Site Timeline" — On Track / Due Soon / Overdue counts, then one waypoint per floor. Completing a task requires a proof photo, and overall project progress is the average of every task's completion. By default, a Site Engineer marking a task complete sends it to Pending Verification instead of straight to Completed — an Admin or Project Engineer has to approve it, or send it back for rework with a reason, before it counts. An org can turn this off in Configuration if every completion should be final immediately. Either way, a project itself can only be marked completed once every one of its tasks is.

Use case: A site engineer marks "3rd floor slab casting" complete and attaches a site photo. The floor's card updates instantly, and the project's overall progress percentage — visible to the owner and the client — moves with it.

Find it: Project detail → Progress tab, or the standalone Work Progress screen.

One report per project per day, auto-assembled from the day's tasks, attendance (staff + contractor, merged), material usage and site photos — there's no data-entry form. You only supply weather, and optionally issues and a site note. Goes through an approval workflow and generates a branded, shareable PDF. On Enterprise, a BOQ status section and an Equipment-on-site section are included automatically when relevant.

Use case: At 6 PM a site engineer taps "Generate today's DPR", picks "Sunny", and sends it — the report already has today's attendance, materials used and photos filled in. The client gets a branded PDF the moment it's approved, without anyone re-typing what happened on site.

Find it: Project detail → DPR tab → Generate today's DPR, or the Home screen's DPR card.

Upload building plans, floor plans, structural/electrical/plumbing drawings, elevations, approvals, contracts and more against a project, organised by category. Every document is encrypted at rest (see Data Security).

Use case: The architect revises the electrical plan mid-project. The admin uploads the new version under "Electrical Plan" so every site engineer opens the current drawing instead of working off a printed copy from three weeks ago.

Find it: Project detail → Documents section.

Pin a site's location (stand there and use your device's position, or paste a Google Maps link) and get a one-way, nearest-first route across every site you're assigned to that day. Sites with no pin are listed separately so you know what still needs one.

Use case: A project engineer supervising 6 sites opens "Plan Route" each morning and gets the nearest-first order for the day, instead of guessing which site to visit first and backtracking across town.

Find it: Project → Overview (pin a site); Home → Site Tools → Plan Route.

A per-floor layout canvas under each project, separate from the task-progress list — add a floor here to start drawing/positioning its layout. Marketed on pricing as "Plan Visualizer."

Use case: Before construction starts on a new floor, the engineer adds it here to lay out the plan visually, giving the team a shared reference beyond the printed architectural drawing.

Find it: Project detail → Building Plan tab.

Mark directly-employed workers Present/Absent/Half-day, log anonymous casual headcount by skill, and record the headcount a contractor supplied — each feeding straight into the matching Salary report. History is browsable by day, and exports to Excel/PDF or WhatsApp. No signal on site? Save anyway — new marks wait on the phone, a banner shows how many, and they send themselves once you are back online.

Use case: A site engineer marks 18 masons present each morning in under a minute. By month-end, that daily habit alone is what the Salary screen uses to calculate everyone's pay — no separate attendance register to reconcile.

Find it: Home → Site Tools → Attendance.

Android app, with internet at the moment of the scan. Fingerprint (USB scanner) is coming soon — face only for now.

Confirm a labourer is really the person being marked present with a quick face scan on the phone. Enrol a worker once (with their consent), then tap Verify on their card — a match marks them Present with a green check, and the saved record shows it was face-checked. For the morning and evening queues, Scan to mark — roll call scans first and names the worker: the first scan of the day checks them in and records their in time, the next checks them out. The hours between them suggest the day — 8 hours a full day, 6 a three-quarter day, 4 a half day, less a quarter day — and the site engineer can change it before saving; pay follows the day that is saved. Attendance cards then read "In 9:05 AM · Out 6:10 PM · 9h 05m". Times come from the server, not the phone's clock. A blink-and-turn check stops a printed photo from passing. Offline sites can still mark by hand; if the company requires a check, hand-marked records are flagged for review rather than refused.

Use case: On a 60-worker site, proxy attendance ("mark my brother too") quietly inflates the wage bill. With roll call, each worker faces the phone on the way in — the app names them, the engineer taps Present, and month-end salary is built only from people who actually turned up.

Find it: Enrol: My Company → Members → a labourer's ⋮ menu → Fingerprint & Face, or Enrol on their card in Attendance. Check: Attendance → Workers → Verify or Scan to mark — roll call. Require it: My Company → Configuration → Biometric Attendance.

Add a labour contractor, assign them to a project, and set per-skill agreed rates (defaulted from the district contract-labour wage table). Once assigned with rates, their supplied workforce is attendance-ready and their dues flow into payroll automatically.

Each contractor is marked with how they are paid: daily wages (headcount × day rate, through payroll — the default, and what most thekedars are), work package (paid per unit of measured output — see Subcontractor Commercials), or both, for a contractor who does some of each. The two never mix: work priced per day cannot be put on a measured contract, so the same work can never be paid for twice.

Use case: A masonry contractor supplies 12 masons to a site. The admin sets their per-mason day rate once; every day the site engineer logs "12 masons, full day" and the contractor's running dues update themselves.

Find it: Admin hub → Operations → Contractors.

For subcontractors paid per unit of what they build rather than per day. Award a share of a BOQ item to a subcontractor under a priced contract, record what gets built, and certify what actually passes — keeping awarded, executed and certified as three separate numbers instead of one vague balance. A package can be 46% executed and 31% certified at the same time, and the gap between them is money someone is expecting that you have not agreed to yet.

The contract carries its value, retention, advance and payment terms. Awarding more of a BOQ item than the BOQ actually contains — across every subcontractor, not just one — is refused rather than quietly accepted, and a measurement that over-claims is flagged while it is being typed. Certifying less than was claimed requires a reason, and prices the difference as you enter it. Not yet built: RA bills, retention release and payments against a subcontract.

Use case: A blockwork subcontractor is awarded 1,200 cum of a BOQ item at ₹650/cum. Site measures 550 cum over three weeks; the project engineer certifies 370 and cuts 30 for pointing that was not finished. The office sees ₹2,40,500 certified against ₹3,57,500 claimed — and knows exactly which 180 cum is still waiting on an engineer rather than discovering it in a payment dispute.

Find it: Admin console → Contractors → a work-package contractor → Commercial. Site measurement and certification are in the app under Contractors → Work packages & measurement.

Thumbprint receipts need Professional or above, and the Android app to take the scan.

Staff, Contractor and Casual payroll in one place, filterable by month/week/custom range, with per-worker gross/advances/net-payable drill-downs priced using the wage rate effective on each attendance date. Site engineers only ever see payroll for attendance they personally recorded.

Thumbprint receipts (Professional and above): turn them on and each labourer confirms they received a wage payment or an advance by scanning their thumb (or face) as the money is handed over. The scan is kept with the payment, and the Payments list shows "Receipt confirmed by thumbprint". Workers who haven't been enrolled are still paid — the payment just shows it was recorded without a scan.

Use case: Month-end arrives and the admin opens Salary, filters to the last 30 days, and sees exactly what's owed to every worker and contractor — including anyone who took an advance mid-month — without touching a calculator. When a worker later says they never got their advance, the payment shows their thumbprint confirming it.

Find it: Project detail → Finances tab → Manage → Salary. Thumbprint receipts: My Company → Configuration → Biometric Attendance → Thumbprint receipt for wages and advances.

Set per-district, per-skill daily wages for both directly-employed and contract labour — these auto-fill rates across Salary and new contractor setup.

Use case: A company running sites in two districts sets a mason's day rate once per district. Every new worker or contractor added in that district picks up the correct local rate automatically, instead of someone guessing what to enter.

Find it: Management → My Company → Skill Wages.

Admins, project engineers and site engineers can raise a leave request and track its approval; owners/admins review and approve or reject with a note. Separate from daily labour attendance — this is for the company's own salaried staff.

Use case: A project engineer requests 3 days of leave for a family event. The admin sees it in the Leave queue, approves it, and it's on record — no back-and-forth over WhatsApp about who's covering which site.

Find it: Leave section (Enterprise-only; hidden below that plan).

Per-project stock levels with low-stock badges, a usage log of what's been consumed, and material requests that route to an admin for approval.

Use case: Cement stock on a site drops below the threshold after a big pour. The Materials screen flags it with a low-stock badge before the site engineer even has to check manually.

Find it: Project → Overview → Materials.

The buying step between an approved material request and its stock/expense records — record the vendor, line items and any freight/misc charges. Depending on how far the purchase drifts from the approved request, a session auto-approves or is routed to review.

Use case: A site engineer buys the approved 200 bags of cement but the vendor charges a small delivery fee not in the original request. Because it's within the configured variance, the purchase auto-approves instead of sitting in a review queue.

Find it: Opens automatically from an approved material request.

Your organisation's own list of materials with a fixed unit per item, so "Cement", "cement" and "OPC 53" stop arriving as three different things nobody can total. Seeded with ~43 standard items on day one; edit, retire and restore your own copy — it never touches another org's list. On Starter, requests still work with free-text name and unit.

Use case: Before the catalogue, three site engineers requested "cement" three different ways and nobody could total company-wide cement spend. Now every request picks from the same list, so the number actually means something.

Find it: Management → My Company → Configuration → Materials.

A queue of pending material requests for an admin to approve or reject, with an optional note either way.

Use case: A site engineer requests 50 bags of cement. The admin sees it in the Approvals queue that evening, approves it with one tap, and the site can order first thing next morning.

Find it: Approvals tab → Material Requests.

Browse vendors with per-material rates, build a cart against a project, and send it for approval. Approved procurement orders are tracked through to delivery.

Use case: A site engineer compares two vendors' steel rates side by side in the Online Store, adds the cheaper one to cart against the right project, and sends it for approval — all before lunch.

Find it: Admin hub → Operations → Online Store.

A platform-wide, district-filtered directory of verified material vendors — raise a deal, negotiate a single counter-offer, and track the order through to delivery per line item, separate from your own organisation's material catalogue. The underlying deal/negotiation workflow exists, but the marketplace entry point in the app is currently shown as "Coming Soon" while the vendor network is built out.

Use case: (once live) A company new to a district browses the marketplace for a verified tile supplier, raises a deal for 500 boxes, accepts the vendor's counter-offer, and tracks delivery — without ever having called around for quotes.

Find it: Admin hub → Manage → Marketplace (currently marked Coming Soon).

A company-wide register of machinery — excavators, mixers, generators — with org-type-aware categories, ownership and depreciation tracking (book value computed on demand), and site allocation with full transfer history. A database-level guarantee means one machine can never be allocated to two sites at once. Currently a snapshot of what's on site, not per-day operating hours — daily usage logging is a future addition.

Use case: An excavator finishes at Site A and needs to move to Site B. The equipment manager taps "Transfer" — Site A's allocation ends and Site B's begins in one action, and the machine's full movement history stays intact for later reference.

Find it: Management → Operations → Equipment (hidden entirely below Enterprise).

Log site expenses by category (petty cash, transport, tools, fuel, food, other) with up to 3 receipt photos. A payment recorded as Other asks what it was for — "Crane rental", "Electricity bill" — and that name is what shows in the project's list of spends, instead of a row that just says "Other". Org-wide expense controls can auto-approve small amounts and require a photo above a set limit.

Use case: A site engineer buys ₹800 of diesel for the generator, snaps the receipt, and logs it under "Fuel" — since it's under the org's ₹1,000 auto-approve limit, it's added to spend instantly with no admin review needed.

Find it: Project → Finances → Project Spends → Add Payment, or Add Expense on the Petty Cash screen (Site Engineer).

Planned: client invoices with GSTIN details, the correct rate (5/12/18/28%), and automatic CGST+SGST vs IGST calculation depending on whether the sale is inter-state. Today, GSTIN format is validated at signup, and a vendor's own invoice can be attached to a purchase session as a file — but generating a GST invoice from within CrewSense isn't built yet.

Use case: (once live) An admin raises an invoice for a milestone payment, picks 18% GST, and the correct CGST+SGST split is calculated automatically because the client is in the same state — no manual tax lookup.

Find it: Not yet available in the app — a vendor invoice file can be attached under a project's Purchase Orders in the meantime.

A single summary of everything awaiting sign-off — material requests and procurement orders — with badge counts so nothing sits unnoticed.

Use case: An admin opens the Approvals tab once a day, sees a badge showing "4 items awaiting approval," and clears the whole queue in a couple of minutes instead of chasing separate screens.

Find it: Approvals tab (Admin/Project Engineer).

The org must enable it in Configuration.

A conversational AI over your organisation's own live data — not a single model call, but specialist agents (Project, Labour, Procurement, Finance, Commercial, Document, Planning, Knowledge, Reporting, Admin, Memory, and Help — which answers "where is that button?" from this guide) routed to by a question and merged into one answer. It can chart comparable figures inline, and a handful of tools can propose a change (update a task, raise a request) that only takes effect after you tap Confirm. Chat is Admin/Owner only. Each question spends one Advisor credit: Growth gets 15 a month, Professional 15 a day and Enterprise 25 a day, counted per organisation.

Use case: An owner asks "did we pay the cement vendor yet, and are we behind schedule on Riverside?" — the Advisor routes to Finance and Project agents, merges both answers into one reply, and even offers to update a task's status if that's what's actually needed.

Find it: Advisor tab (app) or Advisor page (admin console); enable it first at Management → My Company → Configuration.

The org must enable the Advisor in Configuration.

A proactive digest shown under the greeting on Home — "what needs your attention today" — generated once per day (plus up to 2 manual refreshes) by the same agent pipeline as the Advisor. Project Engineers and Site Engineers get it too, scoped strictly to their own assigned projects.

Use case: A site engineer opens the app in the morning and sees "Cement stock is low at Riverside Residency" already waiting on the Home screen — nobody had to ask the AI, it just flagged what mattered.

Find it: Automatically on the Home screen, right below the greeting.

A daily 11:00 AM job scans every active project for four kinds of genuine risk — task delay, material shortage, project delay, cost overrun — and raises a notification, deduplicated with a 4-day cooldown. Decision Memory lets the Advisor recall and search past logged decisions and project history.

Use case: A project quietly crosses 90% of its budget with work still incomplete. The next morning, admins get a push notification flagging the cost overrun — before it becomes a bigger surprise at month-end.

Find it: Notification bell; Advisor chat can also be asked about past decisions.

Owner role only.

Replaces the operations dashboard for the Owner with five screens answering: is the business making money, which projects are actually worth it, what does the team cost, is the business growing, and what needs attention right now?

• Company Health — revenue, cost and margin for a selected period, counting materials, labour and staff salary as cost (unlike every operational screen), plus a revenue-vs-cost trend and salary paid by role.
• Project P&L / Profit by project — for every project over its whole life: the estimate, what the client has paid, everything spent (materials, purchases, petty cash and salary) and the profit made, as a bar chart plus totals and a sortable table. Filter by project (one or several), district, project engineer or site engineer, and the chart and totals follow — so "how much did Karthik's sites make?" is one tap. A loss shows in red.
• People & Payroll — a standing monthly salary per salaried staff member, what's been paid this month vs outstanding, and a one-click way to record a payment.
• Growth — this period against the last one: money collected, material spend vs usage, labour and contractor wages, and new projects by contracted value — company-wide and by district.
• Needs Attention — budget risk, schedule slippage, leftover materials, unbilled cash flow, unrecorded payroll and spare capacity, computed straight from the ledgers rather than an AI model, so it keeps working even if the Advisor doesn't.

Use case: An owner opens Company Health on a Monday, sees margin has dipped, checks Project P&L to find which job is dragging it down, and Needs Attention has already flagged that same project as behind schedule — three clicks to a diagnosis instead of five separate project screens and doing the maths by hand.

Find it: Automatic landing screen for an Owner on Enterprise; the profit chart is Profit graph on the Project profitability section (admin console: Company / P&L / Attention / Growth in the bottom bar).

Custom reports require Professional or above.

Export payments, salary, materials (stock or usage log) and attendance as PDF or Excel, and share straight to WhatsApp. Every export carries a consistent branded header — your logo, GSTIN, project and site-team contacts — and documents that leave the company are watermarked. Project Estimates and Project Showcase each carry their own dedicated watermarked PDF export, built the same way.

Use case: An admin needs last month's attendance for a client meeting in ten minutes. They export it as a branded PDF straight from the Attendance screen and share it over WhatsApp on the way to the meeting.

Find it: The Export action on each relevant screen (Attendance, Salary, Materials, Finances); Export PDF on an open Estimate or Project Showcase.

The org must be on Growth or above to link a client; the client's own account is always free.

A client sees only the projects they're linked to as client on: status, budget, timeline, documents, payments, approved DPRs, and a "who to contact" card with a one-tap call button for the assigned site team. Once a project is completed, they can leave a star rating and review.

Use case: A house-owner wants a quick update at 9 PM. Instead of calling the site engineer, they open their project in the app and see today's approved DPR, complete with photos, already waiting for them.

Find it: My Projects tab on a client account.

A 4-step wizard (location, building size, quality tier, extras) that produces a low/high cost range with a 6-category breakdown — self-service, for anyone evaluating a build.

Use case: Someone planning a 2,000 sqft house picks their district, floor count and a "Standard" finish, and gets a low/high budget range in under a minute — before ever contacting a contractor.

Find it: Estimator tab on a client account.

Planned as a public, no-login directory of construction companies with ratings, years active and project counts — for prospective clients browsing, and for sharing a company's public profile link. The Companies tab exists on a client account today, but currently shows a "Coming Soon" placeholder while the directory is rebuilt.

Use case: (once live) A prospective client browses companies in their district, sorts by rating, and opens a showcased project's public brochure — all without creating an account first.

Find it: Companies tab on a client account (currently marked Coming Soon).

Client-side tiers — Basic is free, Advanced is ₹99/month — unrelated to the construction company's own plan.

Every client account is on Basic (free) or Advanced. Advanced unlocks reading full reviews, writing your own, and a company's work portfolio and project history. This is entirely separate from the construction company's own organisation plan.

Use case: A client shortlisting contractors upgrades to Advanced for ₹99 to read full reviews on three companies before picking one — a small cost against a multi-lakh decision.

Find it: Client profile avatar → Manage Plan.

Curate a marketing-ready gallery of your completed projects — reorderable photos, a cover image, and a public read-only view a client can browse without logging in. Cost, staff names and phone numbers are never sent to that public view. Exports as a watermarked PDF brochure.

Use case: A company finishes a villa project, curates the best 15 photos with a cover shot, and shares the public brochure link with a new prospect — who sees a polished portfolio, never the budget or who worked on it.

Find it: Management → Project Showcase.

Logo upload / white-label requires Enterprise.

Four tabs: Details (org profile, logo, force-logout-all-members), Members — add a new Admin, Project Engineer, Site Engineer or Labour with a name, phone and email; Admins, Project Engineers and Site Engineers are also assigned one or more districts, and salaried roles can optionally carry Aadhaar/PAN for the record. The same list is also where you reset a member's password, force them out of an active session, or grant one of the additive BOQ Roles. Skill Wages sets the direct + contract wage tables, and Configuration covers catalogues, expense controls, the Advisor toggle and task verification.

Use case: A new site engineer joins on Monday morning. The admin adds them from Members with just a name, phone number and district, and by lunch they're logged in on their own phone marking attendance for their crew — no separate onboarding call needed.

Find it: Management → My Company → Members → Add (also available as the Home screen's Add User quick action).

Equipment Manager grant requires Enterprise.

Five additive grants — Project Manager, Quantity Surveyor, Billing Engineer, Accounts, Equipment Manager — layered on top of a member's existing role rather than replacing it. Lets a Site Engineer edit a BOQ or allocate equipment without becoming an Admin.

Use case: A trusted Project Engineer needs to allocate equipment across sites but shouldn't see company-wide payroll. The admin grants them "Equipment Manager" only — nothing else about their access changes.

Find it: Management → My Company → Members → BOQ Roles tab.

Choosing your type works on every plan; editing the lists needs Growth or above.

Three lists your organisation works from: the stage sub-tasks offered when adding a floor, the labour-role/skill list used everywhere from attendance to wages, and the material catalogue. They start from your organisation type — Construction, Modification, or another kind of work CrewSense supports — each with its own standard lists.

• Choose it once. In Configuration, pick your type and confirm: its sub-tasks, labour roles and materials are copied into your lists. It is a one-time setting; to change it later, contact CrewSense support.
• Your copy is yours. Rename, retire or add items freely — your changes never alter the standard list, and changes to the standard list never overwrite yours. Add your own custom items alongside.
• What you had before stays if you used it. Items from your starting list that you edited or already used (on a worker, a wage, a floor or a purchase) are kept; unused ones are retired — hidden from pickers but still shown on old records.
• New items are offered, never pushed. When CrewSense adds to your type's standard list, Configuration and each list show "new for your organisation type" — tick what you want and add it.

Use case: A renovation company confirms "Modification" and gets sub-tasks like "Clearing" and "Wall Break" instead of a new-build company's "Framing" and "Roofing". They rename "Wall Break" to "Demolition", add "Waterproofing" of their own — and when CrewSense later adds "False Ceiling" to Modification, it appears as a suggestion they can take or leave.

Find it: Management → My Company → Configuration → Organization Type (choose once) and Catalogs (edit the lists).

Every organisation starts on a 28-day free trial of the plan chosen at signup, with that plan's features and limits. Upgrade via Razorpay checkout (one-time or auto-pay). Moving to a smaller plan needs your usage within its limits first — the app lists exactly which team members or projects are over. Once a trial or subscription lapses, admins are guided to renew and non-admins see a plain "ask your admin" message rather than a broken app. Invoices & receipts lists every payment you have made to CrewSense — pick a month, a quarter (financial-year quarters, so Q1 is April–June), a year or a financial year, and download one PDF for the whole period or any single invoice. It stays open even after a plan lapses.

Use case: A trial is about to end. The admin sees the trial banner, upgrades via Razorpay in under a minute, and the banner disappears immediately across the whole company — no restart, no waiting.

Find it: Profile → Subscription → Plans; invoices under Profile → Subscription → Invoices & receipts.

Event-driven pushes (approvals, salary, project assignment) arrive automatically; an admin can also broadcast a manual notification to the team. Correctly scoped per account even on a shared device — logging out unregisters that device from your account.

Use case: An admin needs to tell every site team about an early Saturday start. One broadcast from Send Notification reaches every active member instantly, instead of a WhatsApp forward that some people miss.

Find it: Admin hub → Send Notification.

Manually added events plus automatic task-deadline reminders, colour-coded by urgency, shown on every dashboard.

Use case: A task's due date quietly passes. The project engineer sees it flagged in red on their Home screen under Upcoming, without having to open the project and check every task manually.

Find it: The Upcoming section on Home; Add Event (Admin/Site Engineer).

A timestamped log of completed tasks across every project, credited to whoever actually marked it done, filterable by project.

Use case: An admin scrolls the Feeds tab on a Friday to see everything that got done across all projects that week, credited to the actual site engineer who closed each task.

Find it: Feeds tab (Admin/Site Engineer).

Always on for Owners and Admins; optional for everyone else.

After your password (or Google, or fingerprint quick-login), CrewSense emails a 6-digit code to your account's address and asks for it before signing you in. Owners and Admins always use it; anyone else can turn it on for themselves. On the phone app it is asked once per phone — tick "Don't ask again on this device" — while a browser asks every time. Codes last 10 minutes, a new one can be sent after 30 seconds, and five wrong tries start the sign-in again. The email has a Copy code button. Changing your password makes your other devices ask again.

Use case: Someone learns an admin's password. Without the code — which only ever goes to the admin's own inbox — they still can't get in, and the admin sees an unexpected code arrive as a warning.

Find it: Asked automatically at sign-in. Others turn it on in Profile → Two-step sign-in. Keep your email address current — there are no backup codes, so an Owner or Admin who loses access to their email needs it corrected to sign in. On Android, use the latest app version.

Passwords are bcrypt-hashed and never returned by any endpoint. Photos, documents, logos and generated PDFs use envelope encryption at rest (AES-256-GCM, wrapped by Cloud KMS) — the storage bucket holds only ciphertext. Aadhaar/PAN are encrypted at rest and only ever shown masked. Fingerprint and face checks never upload an image: a fingerprint is sent as the scanner's list of ridge points, and a face as 128 numbers the phone computes before deleting the photo. The server stores them encrypted — never sent back to any app, deleted for good when removed. Money isn't column-encrypted (it needs to stay summable/sortable in reports), so it's protected instead by tenant isolation and a database with no public IP. Everything in transit uses HTTPS.

Use case: Even if someone gained direct access to the storage bucket, every photo and document inside is unreadable ciphertext — the decryption key never leaves Cloud KMS, so a storage-level breach alone reveals nothing.

Find it: Applies automatically — nothing to turn on.