Time tracking that pays for itself
From timesheet to invoice in one click.
Weekly timesheets, on-site attendance, and billable-hour conversion into invoices. Unique constraints guarantee one timesheet per user per week and one attendance record per user-project-day.
Weekly timesheets, not chaos
Every user gets one timesheet per ISO-week — enforced by a database-level unique constraint. Inside the sheet, time entries record:
startTimeandendTime(timestamps, not durations).breakMinutesandtotalHours(computed).entryType: regular, overtime, site visit.activityType: site work, design, supervision, inspection, travel, admin, meeting, other.billable,billingRate,amount, andinvoicedflag.
Submit to PM → approve → done. No spreadsheet round-trips.
On-site attendance
Separate from timesheets, attendance tracks physical presence per project per day. One record per (user, project, date) — enforced by unique index. Useful for contractor contracts that settle on daily presence rather than billable hours.
status: present, absent, half-day, leave, holiday.checkInTime,checkOutTime(optional).
Timesheet → invoice
This is the trick: approved billable entries can be converted to a draft invoice in one action. Blueprint groups by project and line-items the description. Your finance team then adds GST/TDS rows and issues.
For architecture practices billing hourly, this collapses a week of reconciliation into minutes.
Mobile-ready
The mobile app supports timesheet entry, check-in / check-out, and attendance marking — with geotags for on-site work. Offline-capable; syncs when connectivity returns.
Who this is for
- Hourly-billing architecture practices.
- Contractors managing daily-rate labour.
- Consulting engineers who bill site visits by the hour.
Yes. Every invoice captures supplier + buyer GSTIN, state codes, and auto-splits CGST+SGST (intrastate) vs IGST (interstate). Invoices are numbered sequentially within the financial year (April–March) and include all mandatory GSTR-1 fields. TDS under Section 194C is computed automatically.
RA bills carry cumulative and previous-cumulative amounts, reference the previous RA bill, and maintain a sequential RA number per project. This is a first-class invoice type — not a workaround on top of standard invoices.
Yes. Most teams onboard a pilot project in under an hour and run Blueprint alongside existing tools for a month. Bulk imports for vendors, BOQ items, and historical invoices are available on Studio and Enterprise plans.
Data lives on Neon Postgres in India-adjacent regions, with files in AWS S3 / Cloudflare R2. Enterprise plans can pin data residency to a specific region or deploy into your own VPC.