← Case Studies
04
Property & Real EstateFractional GIS Lead

Fractional GIS Lead Cover for a National Property Consultancy's Data Team

2-3 days/week Senior GIS capacity, extended into a second block
185+ layers Documented across 7 European markets
Project image coming soon

Snapshot

From October 2025 to February 2026, we worked as a Fractional GIS Lead (GIL) inside the central data team of a national property consultancy. The team runs the firm’s PostGIS spatial database and the ArcGIS Enterprise mapping platform used by its offices in the UK and across Europe. With one post waiting on a new starter and another colleague about to leave, it was turning work away. We took on consultancy projects the team had no capacity for, and we brought the platform’s data documentation, which had fallen around six months behind, up to date for every market it covers. The engagement ran at two to three days a week and was extended into the new year after the first block ended.

Challenge

This was a small team with a wide remit. A director handled most technical sign-off, a second director worked part-time on strategy, a manager looked after an offshore support team, and one engineer managed the spatial database along with every user login. Between them they supported fee-earning teams across several countries, whilst also carrying a large bid.

Two problems followed from that. Requests for consultancy work from elsewhere in the business were arriving faster than the team could take them on, so some were being left or delayed. Documentation had also slipped. The mapping platform serves web maps for the UK, Ireland, Poland, Spain, France, Italy and Portugal, each built from layers in the central database, and the records describing those layers were about six months out of date. Anyone trying to work out where a layer came from, or whether it was still current, had to ask the one person who knew.

A permanent hire would have taken months to recruit and longer to learn the platform, whereas the team needed someone who could start straight away.

Our approach

Taking on the project backlog

We already knew the platform well, so we were picking up work in the first week. We worked as part of the team, through the client’s own systems and channels, and took on consultancy projects that would otherwise have waited for the new starter. One was a custom retail occupancy map for a prime shopping street in a major European capital, mapped down to individual units, so the firm’s retail team could see occupancy shop by shop. The brief deliberately had no fixed deliverables, because the point was to absorb whatever came in. A senior lead was the main point of contact and a technician tracked incoming requests and their status. Everything was billed by the day against monthly timesheets.

Rebuilding the data documentation

We went through the platform market by market. For each country, we listed every web map and app, then traced each layer back to the database table or view behind it. Each entry records the layer’s source, which maps and apps it appears in, any known issues such as a dataset that hadn’t been refreshed since its first load, and links to the internal and external documentation. The UK platform alone holds several hundred layers, and that total changes as the team publishes new data; the six other markets added more than 180. The result is a single reference the team can use to answer data questions without going through one person.

Supporting the platform day to day

The engagement letter also covered support for the PostGIS server and onboarding for new joiners, so the incoming staff member learned the database and the platform from someone already working on both.

What we delivered

  • Consultancy projects for the wider business that the team would otherwise have had to turn down or delay, including a unit-level retail occupancy map for a prime European shopping street.
  • Up-to-date data documentation for the mapping platform across the UK, Ireland, Poland, Spain, France, Italy and Portugal, with every layer traced from the web map back to its source in the database.
  • Day-to-day support for the central PostGIS database and onboarding for new joiners.
  • Senior GIS capacity at two to three days a week, extended once when the workload continued into the new year.

Skills & tools we used

PostgreSQL and PostGIS, for database support and for tracing published layers back to their source tables and views.

ArcGIS Enterprise, for auditing and supporting the web maps and apps used by each country’s teams.

QGIS, for desktop analysis and checking data against the central database.

Data governance, covering lineage, source and currency recorded for each layer in a form the team can maintain.

Impact

The team kept taking on work for the rest of the business through a period when it would otherwise have been short-staffed, and the permanent staff could stay on their own priorities.

The documentation work closed a six-month gap across every market on the platform. Questions about where a layer comes from, which maps use it and whether it is still current now have a written answer, which matters most when the person who used to hold that knowledge leaves.

The client extended the engagement after the first block ended. Across both blocks they paid for two to three senior days a week, against the months it would have taken to recruit for a seat that was already being filled.

Ready to proceed?

Short-staffed in your GIS or data team?