Modules — Jig by SideKick

One platform

The office, the field and the money — on the same job.

Built around how a contractor actually works, not around a generic task list. Hover or tap any item to see what Jig does with it.

Twelve modules, one thread: the budget says what the work costs, the billing side says what you are owed. A change order lands on the budget line and on the next application in the same move; the application carries its own retainage and its previous certificate; the waivers and the draw follow behind it. Nothing here is a spreadsheet kept alongside the job — it is the job, added up.

The money

From schedule of values to certified payroll.

Pay applicationsEach application carries its own period, retainage and status. Jig totals this period from the line values you enter, carries the previous certificate forward, and moves the application from draft to submitted to paid. Continuation sheetsThe summary and the continuation sheet, in the layout owners and lenders expect, printed from the same record you just worked in — never a second spreadsheet to keep in step, and never a total that disagrees with the sheet behind it. BudgetLine items with budget, committed and paid, grouped by CSI division. Variance and balance are calculated, never typed, and each line can be tied to a schedule activity and a draw. Change ordersRaise it, price it, give it days. On approval Jig moves the contract sum, the cost line it belongs to and the activity duration in one step — approval is the only thing you do twice, because nothing downstream has to be told. Draw scheduleMilestone draws with what is funded and what is paid. Budget lines and vendor invoices are tagged to a draw number, so each draw reconciles against the work it paid for. Lien waiversConditional and unconditional, tracked per application and per company. Jig raises it as critical when an application was paid with waivers still outstanding — the exposure nobody notices until closeout. Certified payrollWeekly filings per worker per company for prevailing-wage and Davis-Bacon jobs. A short payment or a week nobody filed is flagged before the owner's compliance officer finds it. Client invoicesMoney in. Invoices raised against a work order, line by line, with what has been billed and what is still receivable. Overdue ones count up in the sidebar. Vendor invoicesMoney out. A subcontractor or supplier invoice tied to the budget line it draws against and the draw it belongs to, with received, approved, paid, disputed and void as its own states. Time & materialsA line per person per day — hours, rate class, what was done, signed ticket attached. Jig shows hours logged, value not yet billed, and how much of the T&M ceiling has been drawn. Cost-loaded scheduleCost carried on the activity, so the schedule answers money questions: earned value, cost to date, and where the job lands if it carries on at this rate. Cost by divisionThe whole budget rolled up to CSI division — budget, committed, paid and variance — with a bar chart you can read across in one pass. Divisions over budget go red.

The paperwork that decides who is right when a job goes wrong. RFIs, submittals, specifications and transmittals, each dated, numbered and tied to the thing it affects, plus the schedule that governs them and the pipeline that won the work in the first place. Overdue items surface on the job rather than waiting to be noticed.

The office

Every register a job is judged on.

RFIsNumbered, dated, with the answer and the cost and time it carried. An overdue RFI surfaces on the job's attention list, and an answer with a price behind it becomes a change order. SubmittalsEach one checked against its spec section, with the package that went out and the stamped copy that came back. Revise-and-resubmit reopens the cycle rather than closing the row. SpecificationsThe sections the job is built to. A submittal points at its section, so reviewing one means reading the other — no hunting through a 400-page book for the right paragraph. TransmittalsWhat was sent, to whom, on what date, and what came back. Overdue returns and rejected packages are flagged, so nothing sits with the architect unnoticed. ScheduleGantt with predecessors, float, critical path and milestones — plus baseline, variance and as-built views beside the plan. The program comes across from the planning tool that produced it, three interchange formats in. LookaheadThree weeks out, on one job or across the whole portfolio: what starts, what finishes, and what has nobody assigned to it yet. EstimatesPriced by the line, with status and win rate across the pipeline. A won estimate becomes a project, a work order or budget lines — carried across, not retyped. Work ordersThe smaller work that never justified a project: who it is for, who it is assigned to, value, margin, and whether it has been billed yet. CRMThe pipeline before it is a job — clients, contacts and what is out for decision, with estimates, work orders and invoices hanging off the client rather than living in a separate system. ClientsContact, address and terms, with every project, estimate, work order and invoice that belongs to them on the one record. SubcontractorsTrade partners with their insurance certificate, license and W-9. Jig chases the expiry date before it bites — an expired COI shows as a paperwork gap in the sidebar, not on the day of the loss. Handover packageOne download at the end: every report, the project record, the uploaded documents, the punch photos and a spreadsheet of the registers. The job can be closed without losing anything.

Written on site, on a phone, on the day. Daily logs that become the evidence a delay claim is argued from, punch items that carry the photograph proving they were closed, and the crews and equipment booked across every job at once so two supers are never promised the same machine. It is the half of the record that is hardest to reconstruct afterwards — so it is never reconstructed.

The field

What actually happened, logged where it happened.

Daily logsCrews on site, weather, work performed, issues, visitors and inspections — one entry a day. It is the evidence every delay claim is argued from, and it prints as its own report. Punch listBy area, trade and responsible company, with priority and a closing date. Photos live on the item, so proof of completion travels with it into the handover pack. PhotosTaken on the phone camera and attached to the row they belong to — a punch item, a log, a submittal. Thumbnails on the grid, full size on tap, and they carry into the printed report. EquipmentWhat you own, where it is, and which job it is booked to. A machine promised to two jobs in the same week shows as a clash before either super turns up expecting it. Hired-in plantRented kit with its supplier, dates and cost. Anything still to arrange stays visible until it is booked — with the days of lead time left counted down for you. Rental catalogYour hire companies and their day and week rates, kept once and shared across every job — so booking a machine is picking one, not phoning round for a price. Crew allocationWho is on which job, which week, over every job at once. Over-allocation is flagged on the board rather than discovered on Monday morning. TimesheetsHours booked against the job and the activity that used them. The same entry feeds T&M billing and the cost line, so an hour is written down once and counted once. Rate classesThe roles you bill and the hourly rate for each. Picking a role fills its rate automatically, and the rate stays editable on the individual entry when the job was negotiated differently. DrawingsPlans and drawings have their own category, apart from contracts and photos, and every upload keeps its revision history — the current sheet is obvious and the superseded one is still there. FilesDocuments filed by category, tied to the record that needed them, and twenty-nine file types open in place rather than downloading. Removing one from a screen does not destroy it — the file survives the click, deliberately. ReportsFifteen printed reports — status, schedule and Gantt, budget and draws, punch, RFIs, daily log, T&M and the partner directory, plus portfolio-wide ones across every job. Built to be handed over, not screenshotted.

Billing

The whole cycle, in the order it happens.

Approve the change order and it lands on this month's pay application. Certify it and the waivers follow. Submit the draw and it reconciles. One tab, top to bottom.

Summary and continuation sheets, print-ready, straight from the screen
Retainage per line, at its own rate on work and on stored materials
Previous certificates that carry forward correctly
Conditional and unconditional lien waivers
Weekly certified payroll for prevailing-wage work

Cost to date16-week fit-out · week 16

Earned to date—

This week—

Against baseline—

Week 16 of 16

━ Earned · ╌ Baseline · ╌ Contract sum · rings are certified applications

Daily logWeek 9 · Thursday

On site279 trades

Punch closed14this week

Inspections1passed

Work performed
Lead-lined board complete, Imaging 1 and 2. Med-gas rough-in pressure tested.

Issues
RFI-014 answeredThis is the line that starts the chain in the tour above: the answer carried a price, so it became CO-003, which moved the contract sum and appeared on application 3. — panoramic unit added to Imaging 2. Change order raised.

Inspections
AHJ rough-in electrical — passed.

In the field

The day gets logged once, and everything downstream uses it.

A daily log that becomes evidence. Punch items that carry photos. An RFI that turns into a change order and lands on the next pay application without anybody retyping it. Your first five field seats are free, then $3.99 a head — and it sees everything except the money.

Written on a phone, on site, without a second trip to the trailer
Photos attach to the row, not to a shared drive nobody opens
Equipment and crews booked across jobs, with clashes flagged
Timesheets and rate classes, exportable to payroll
Every register exports to a spreadsheet, or prints as a laid-out report

No migration pain

Bring the job you already have.

The schedule arrives in the format your planner already exports. Sixteen registers import from a spreadsheet file, each with a template you download first — so starting a job in Jig is a mapping exercise, not a fortnight of retyping.

3 scheduling interchange formats in 16 registers from a spreadsheet 29 file types opened in place 15 printed reports out 1 handover package 1 file for the whole portfolio

By invitation

Tell us what you build, and we'll show you the job.

Access is by invitation while the pilot runs. It takes a minute, and a person reads every one.

Sign-in opens with your account. Request access and we will send you the link.