# Building contractor: one dashboard instead of five spreadsheets URL: https://up2.digital/examples/builder-job-tracking-dashboard > An example of a typical project for a building contractor running several jobs at once: bringing scattered spreadsheets together into one dashboard the whole team can see. ## The situation Meet Priya, an illustrative example: she runs a building contracting firm with six people, juggling four or five jobs at once: an extension here, a loft conversion there, a kitchen fit due to start next month. Each job has its own spreadsheet, built up over time by whoever started it, so one has a materials list, another has a day-rate tracker, and a third has nothing beyond a date and a client name. Nobody has a single view of what's actually happening. The office manager checks five tabs to answer a simple question like "are we on budget on this job." A site manager texts over material costs that get copied into the wrong sheet, or forgotten until invoicing day. Job sheets and variation paperwork get typed from scratch for every project, even when most of the content is the same each time. *"Jobs, certificates and staff for six people live across five spreadsheets that never quite agree,"* says Priya. *"I want one place to see every job and its paperwork."* It isn't that anyone's bad at their job. It's that Priya's firm has grown past what a spreadsheet, however well kept, can hold on its own. ## What we'd set up - **[Importing existing jobs and contacts](/services/crm)** from the current spreadsheets, so nothing gets lost or retyped by hand during the move. - **[A CRM set up around how the firm already works](/services/crm)**, holding clients, suppliers and job history in one place rather than scattered across files. - **[An internal dashboard](/services/custom-apps)** built specifically around this contractor's jobs: live budgets, material costs, timelines and who's working where, all in one screen. - **[Document automation](/services/automation)** for job sheets and variation paperwork, generated from information already in the system instead of typed out fresh for every job. ## How the project would run **Weeks 1-2**: a discovery call and a proper look at the existing spreadsheets, working out what's genuinely useful and what's just habit. Contacts and job history get imported, and the CRM structure is set up around real job types. **Weeks 3-5**: the dashboard itself gets built: live views of budget against actual spend, material costs per job, and who's on which site, tested against two or three real, current jobs rather than dummy data. **Week 6**: job sheet and variation document automation is wired in, pulling from the same data already sitting in the dashboard rather than a separate system. **Weeks 7-8**: the dashboard runs alongside the old spreadsheets for a short overlap, so the team can trust it before switching fully, followed by training for the office and site managers and a written guide to the whole setup. ## What changes day to day A question like "are we over budget on this job" gets answered by opening one screen instead of checking several spreadsheets and hoping they agree. Material costs logged by a site manager on their phone show up in the same dashboard the office manager is already looking at, rather than arriving by text and waiting to be copied in. A variation to the contract gets generated from the job's existing details in minutes rather than typed from a blank page. The business doesn't get bigger. It gets easier to see clearly, which tends to matter more. ## What you get back The office manager stops losing half a morning reconciling five spreadsheets that don't agree, because budgets, materials and timelines live in one screen everyone trusts. A site manager's material costs stop needing to be texted over and copied in by hand, because they're logged straight into the same dashboard the office is already looking at. Variation paperwork stops being typed from a blank page for every job, because it's generated from details already sitting in the system. If this sounds familiar, [start my project like this](/start?goal=app). ## Tools involved A project like this typically sits alongside whatever accounting software Priya's firm already uses, such as Xero or QuickBooks, and can pull in data from existing tools like Tradify or a simple shared spreadsheet during the transition. The dashboard itself is built specifically for Priya's firm rather than being an off-the-shelf product, which is what lets it match how jobs actually run rather than forcing a generic structure onto them. ## Related If this sounds familiar, see [The business runs on a spreadsheet that's creaking](/solutions/spreadsheet-chaos) and [Admin eats our evenings and weekends](/solutions/drowning-in-admin). Further reading: [7 signs your business has outgrown spreadsheets](/guides/outgrown-spreadsheets) and [10 admin tasks small businesses can automate this month](/guides/admin-tasks-to-automate). For the wider picture on this sector, see [websites and job management for trades](/industries/trades). ## Frequently asked questions ### Why build a custom dashboard instead of buying existing job management software? Off-the-shelf software is often the right answer, and we'll say so if it fits. A custom dashboard tends to make sense when a business has outgrown generic templates and needs its own job types, budgets and paperwork built in exactly as they work, without bending the business to fit the software. ### How long does something like this usually take? A dashboard like this typically takes four to eight weeks to build, depending on how many job types and data sources it needs to bring together, plus time for importing existing data and training the team. ### What happens to our existing spreadsheets? Nothing gets deleted until you're confident the new system covers everything. Data gets imported across, and the spreadsheets can sit untouched as a backup for as long as you want them to. ### Can site staff update it from their phones? Yes. A dashboard like this is normally built to work on a phone or tablet as well as a desktop, so updates from site don't have to wait until someone's back at a computer.