Our New Data Protection Tools

We are pleased to announce the arrival of some new data protection tools that aim to help Solomon customers stay compliant with the General Data Protection Regulation.

Solomon users can now set the lawful basis for storing any personal data in the People table:

Screen Capture on 2018-06-04 at 15-43-35.gif

Under GDPR, there are six lawful bases for processing personal data. We have only included the four most relevant to our customers: legal obligation, contract, legitimate interest, and consent.

If consent is the basis, we have added a simple wizard to help you record key informaton and to get the subject to opt-in as required. If the data subject is with you - for example, you get consent during a visit to see them - you can let them review the policy and set their preferences themselves, after which a confirmation email is sent to their inbox:

Screen Capture on 2018-06-04 at 16-04-46.gif

If consent is given in another way - over the phone, for example - there is an alternative workflow. Here you record the consent but an opt-in email is sent to the subject. Only after they have clicked on the confirmation link will their consent be registered:

Screen Capture on 2018-06-04 at 16-06-19.gif

If you are seeking consent, or you have it but you are unsure of the individual's data processing preferences, there is a final workflow that generates a consent request email. This will allow the data subject to create their own consent online. Warning: you must have their permissions to send the request email or you will be in breach of GDPR.

Under GDRP, subjects have the right to withdraw consent at any time. We have created a public web page where data subjects can manage their processing preferences, and withdraw their consent. They enter their email address first:

Screen Capture on 2018-06-04 at 16-21-17.gif

This will generate an email containing a link to a secure page where they can update their consent:

Screen Capture on 2018-06-04 at 16-24-25.gif

And there you have it!

Last week we updated our own data protection documentation. This is now available for review on the data protection pages of this site. As a result of these new policies, we have introduced some "technical measures". For example, all users are now required to review and accept a Privacy Policy before they can access the software. Each acceptance is stored in the user's account, along with a copy of the policy at that time.

We've been working on getting GDPR ready for over a year. We hope these new tools and policies will help our customers with their own data protection agenda. We've tried to take pain out of the process by making things simple and fast. We look forward to hearing feedback from our users, and to continuing to make Solomon best-in-class for data protection.

Solomon Branding Pack

We're pleased to announce that we have launched a new pack that allows our customers to wrap their brand around the Solomon interface.

As well as being able to replace the Solomon logo, we can now update login pages, accent colours and the Timeline. Here is a gallery of screenshots from Sheffield BID:

Many thanks to the Sheffield BID team for allowing us to share the wonderful work they have been doing, curating local information into their dashboards. Using existing Solomon features, they have created a members-only website experience. Thanks to the branding pack, that experience fits seamlessly into the BID's visual identity and offer.

The branding pack is available to existing and new customers, for a one-off charge of £500.

If you would like to place an order, please contact Leonard Carey today.

GDPR: making our customers "compliant by default"

A huge thanks to Rebecca, our Privacy Sheriff.

A huge thanks to Rebecca, our Privacy Sheriff.

Since May of this year, our self-titled "Privacy Sheriff", Rebecca, has been cracking the whip on our efforts to understand and prepare for the General Data Protection Regulation (GDPR), which takes effect on 25th May 2018.

We've undertaken an information audit (an ongoing process), identified steps that we must take as an organisation to protect our data and that of own data subjects, and have made ourselves battle-ready. We have a few feet to cover before May but we're proud to report that Solomon, as an organisation, will meet all the demands of the new data protection laws.

That work covers our role as a Data Processor; a party who acts on data on behalf of our customers. But what about our customers, as owners of the data held in Solomon; what the Information Commissioner calls Data Controllers

On the one hand, our BID customers are in a good position because they have a "legitimate interests" in processing much of the data they hold. Going a step further, we would argue that there is a "legal obligation" to hold liable party information, to ensure a Ballot/Renewal is legitimate. When it comes to some other points of data that is personally identifiable - personal information about individuals the BID team communicate with day-to-day - GDRP includes some new rights for data subjects that BIDs, as Data Controllers, must take account of.

Today we are announcing that we plan to spend the first few months of 2018 adding some new features to Solomon that will provide tools to address these new rights, and to make all our customers "compliant by default."

Undertaking this work will mean pressing pause on the development of some new features but this is a major shift in the law that affects all BIDs, regardless of size and shape, and we what to do everything we can to help.

Three key areas require our attention:

  1. Consent and the right to unsubscribe: every data subject must give consent for their data to be processed, including email addresses used for electronic communication. Data Controllers must receive "positive, freely given, specific, informed and unambiguous" consent for their data to be processed. Controllers need to say how long they will hold data for, what they will do with the data, have clear procedures for deleting the data once any deadline passes, and outline the subject's rights. We want Solomon to incorporate a set of tools for managing consents.

  2. The right to access: upon request, any data subject can ask a Data Controller to provide, free of charge and in a commonly used electronic format, copies of any data held about that subject. We want Solomon to incorporate a "one-click" solution for our customers.

  3. The right to be forgotten: every data subject has the right to request that the Controller erase any personal data held concerning them. We want Solomon to incorporate tools that allow you to flag personally identifiable data, and destroy it on-demand. 

GDPR represents the biggest change in data protection rules in two decades. Delivering these new features will require a huge amount of effort from our team but it's essential to us that Solomon customers are compliant by default.

Say hello to Solomon V2


One of the three big challenges LeedsBID gave our team back in January 2017 when our journey into BID Land began was, "create a giant spreadsheet in the cloud."

With only a month to deliver something the team in Leeds could use to start organising their data, we had to be practical and pick something that already existed to work with. After some pretty intensive research we settled on AirTable; a new kid on the block and a spreadsheet-database hybrid with some awesome superpowers. For over a year, AirTable did the job but as more BIDs joined Solomon, and the volume of data they collected began to swell, cracks appeared. By the end of December 2016, we decided "enough is enough" and began planning something that would eventually replace AirTable, native to the Solomon platform and accessible within the same interface as our other great features. We decided to call it Directory

We also had a backlog of feature requests and suggested improvements that we wanted to deliver along side the launch of the Directory. 

In January 2017, our team of four engineers (Nate, Ste, Michal and Jack) and one designer (Joel) started work on what became our biggest development project so far. For nine months, they have poured everything they've got into their work and the result is Solomon V2, which we are pleased to be launching today.

It would be too much to list all the improvements we're rolling with V2, so I'm going to summarise some of the major changes:

New Layout


We pride ourselves on Solomon's usability and the new and better-organised layout makes it easier than ever for users to find their way around. 


The ultimate transparency tool: add activities to each business's timeline, giving them visibility on all the value you are adding.


Total control of your data, right inside Solomon. Manage, tag, sort, filter and export your data on-demand. Log everything you do to benefit your members. 

Votes and Ballot Insights

Our new Vote records mean you can track voting intentions and the Ballot Insights report helps you to forecast the outcome.

What next?

You'd think that, after nine-months working at full steam, we'd be ready for a long break. Wrong answer! We've got loads of ideas for great new features and we're diving right back in.

We're ALWAYS open to new ideas! Please use the live chat facility to feedback your suggestions and feature requests.

We'll spend the next fortnight reviewing all the options, and listening to our customers' priorities. After that, we will be publishing a public roadmap detailing what we're working on and when you should expect to see new features landing. Be sure to subscribe to our newsletter (below) for the latest news.

335 days to GDPR: the story so far

"29-page documents" have become something of a running joke in our office as we've waded through guidance emanating from the Information Commissioner's Office (ICO), trying to wrap our heads around the General Data Protection Regulation (GDPR).

We are 335 days out from its introduction and awareness is turning into a mild panic: "When the hell is something personal data, and when is it not?" "Really, I can't legally market to someone who gave me their business card at a trade event?" "What in Solomon's name is a 'double opt-in'?" 

Answers to the above and other questions will follow in the coming weeks. In the meantime, here's an update on our progress working through the 12 Steps of GDPR preparation suggested by the ICO, along with some tips that might help to save you time. 

Step 1, Awareness, is all about who needs to know and as far as we were concerned that's everyone in our team. In one way or another, everyone at Solomon is a "decision maker" and someone that needs to be "aware that the law is changing" and "to appreciate the impact this is likely to have."

Rebecca, who has been blessed(?) with the responsibility for leading us through this process prepared a summary of what the GDPR is and how it's likely to affect our people, our technology, and our customers. She presented this to the team along with a flow-chart describing the 12 steps and how we will approach them.

We used Step 1 as an opportunity to check our compliance under the current Data Protection Act arrangement. We thought it would be interesting to share one of the documents Rebecca prepared, which outlines the current responsibilities of Data Controllers (if you are a BID then you almost certainly are one) with regards to their use of cloud computing services like Solomon. I'm delighted to say that Solomon passes the test. If you are reading this and you are not a Solomon customer then I hope the document will provide some talking points you can use with your current supplier to ensure you're compliant too.

Step 2, Information you hold, is fundamental. The remaining 10 steps are pretty dependant on  getting this bit right. Here's what the ICO says:

You should document what personal data you hold, where it came from and who you share it with. You may need to organise an information audit.

We headed right over to the deep end and organised an information audit. We started this by defining some questions we wanted the audit to answer. Here's the list:

  1. Where is our electronic information stored and processed?
  2. What personally identifiable information do we hold in each of those places?
  3. What is the origin of that information?
  4. Why do we store that information - what's the business case?
  5. Is there a legal basis for storing that information?
  6. What is our responsibility for the information we hold - are we a Controller or a Processor?
  7. What are its "exit points" - when, how and why is it shared outside of our organisation?
  8. For each type of information we hold, how do we record consent from the data subject?
  9. How secure are each of the places where we store data - what are the risks of a breach?
  10. What steps are necessary to eliminate or mitigate those risks, and to identify and report breaches?

A tip from us is to start by getting your team in one room and generating a list of all the software and hardware everybody uses. Including computers, phones, external drives, cloud software tools and our own technologies, we identified 29 data stores that need auditing. 

The next time we post our progress report, we will have answered all of the questions listed above. We hope to have built a comprehensive picture of what we hold and why and will be armed with what we need to define processes and policies fit for the GDRP.

If you have any questions about what we've learned please feel free to contact me directly: simon@hebeworks.com. If you haven't done so already, please subscribe to our mailing list and we'll send future updates straight to your inbox.

Air Quality Unlocked

To celebrate National Clean Air Day, we're proud to announce a new Solomon Story that gives businesses real-time access to air quality information for each of their locations. 

The Story is powered by CleanSpace whose users help them to gather data by carrying a small sensor called a Tag. The Tag takes readings of all major pollutants and sends data to the cloud (presumably a very white one) via the user's mobile phone. The Solomon team, along with the LeedsBID street teams, are taking part and capturing data from across the BID area in central Leeds.

Like many towns and cities across the UK, Leeds has a poor history when it comes to the air we breathe.

According to our own research, there is a 4.5 year difference in life expectancy between the boroughs of Leeds that have the highest and lowest levels of Nitrogen Dioxide pollution. Unlocking air quality data for Business Improvement Districts means that business communities can better understand where the problem areas are and how they can work together to make places cleaner and greener for all.

Solomon has been designed to plug into data from any source on the web. Please take part in our poll on Twitter and let us know what other information you think BIDs want to see on their local intelligence dashboards.

The first global data protection law is coming.

In exactly a year from today, on 25th May 2018, EU regulations will bring into effect the biggest changes in Data Protection law for 20 years.

The GDPR (General Data Protection Regulations) will determine the use of personal data by placing rigorous obligations on organisations, like ourselves, who handle personal data. All companies worldwide, who process the data of EU citizens, will be obliged to take data privacy more seriously.

These new obligations will broaden the definition of ‘personal data’, meaning that genetic, mental, cultural, economic or social information will be considered such. There will be changes to the practices of how that data can be collected, stored and used. Additionally a new ‘right to be forgotten’ whereby individuals can request the permanent deletion of their data, which subsequently means process and technology systems may need to evolve. Finally, there will be new requirements surrounding data breaches and increased penalties for those who fail to comply.

Information Commissioner, Elizabeth Denham talks about how GDPR is an issue for the boardroom.

Here at Solomon, we are committed to handling data sensitively and ethically - data security is one of our key values after-all! We have already begun taking steps to ensure our compliance and over the coming months we’ll be keeping you up-to-date on this blog with a series of in-depth audits, reviews and policy changes which we have mapped out.

Please subscribe to our mailing list today and we’ll send updates to your inbox – no more than two emails each month, we promise.

A platform for collaboration - from #ACTMBIDS 2017

On 18th May 2017 the Solomon team landed in Birmingham for the inaugural #ATCMBIDS conference, held by the Association of Town Centre Management. What follows is a long-form version of the presentation we gave to delegates about our experience of collaboration between the public and private sector:

Born from collaboration

Solomon was born from collaboration between our team and a number of organisations and individuals from a variety of worlds. Our journey began in 2013 when we entered into a partnership with Leeds City Council, supported with funding from Innovate UK, DCLG, Nesta, Creative England and the Cabinet Office, with the aim of unlocking local data and promoting a deeper understanding of place. An 18-month long collaborative research project took place, that culminated in production of an open data portal for Leeds (now Data Mill North) and a civic dashboard that made open data — from the Data Mill but also many other sources from across the web — easy to digest and useful to citizens. Due to the open source nature of that project, our collaboration extended far beyond the partnership to include more than 700 web developers, worldwide, who contribute to Ember.js, the framework used to build Solomon. As an aside, Ember.js is used by the likes of Apple and LinkedIn, so we're in good company. 

Unlocking local data and promoting a deeper understanding of place.

As a technology, Solomon is made up of a number of "components" that can be composed in different ways to meet different needs: we often describe it to people as "web Lego". Two examples of projects that have benefited from this approach were delivered with teams at NHS England and Yorkshire Water. Both projects explored how Solomon could be used to share intelligence internally and externally. Unlike the civic dashboard, these projects required deep analysis and required more than just grabbing and presenting data —  they needed complex transformations to take place in between. This led to the formation of a Knowledge Transfer Partnership with University of Bradford and the creation of a Data Science team and a family of applications doing seriously clever stuff in the cloud.

Unsurprisingly, the nature of the projects described above required careful attention to security and data protection; user experience, especially in the context of a civic dashboard with general users of mixed technical ability; scale, with the potential for huge volumes of traffic; and portability, with users demanding access on computers, tablets and smartphones, from anywhere. All of these things required engaging or recruiting specialist skills to join our team, with collaboration being fundamental to our success.

Growing in collaboration with BIDs

In January 2016, we held our first requirements workshop with LeedsBID. We met with Andrew Cooper towards the end of 2015 to discuss Solomon, and the potential value our "web Lego" could offer to LeedsBID. Andrew, though, saw a bigger picture, and an opportunity for us to create value for BIDs right across the UK. In Andrew's experience, BIDs struggled to manage and make sense of the data they gathered and, as a result, struggled to articulate their impact to their members. We were hot off the back of being named as one of the UK's top 50 creative companies, and Andrew challenged our team to:

  1. "Create a 'giant spreadsheet in the cloud' that BID teams can share, and that is aware of changes to the National Non-domestic Rates record, as they occur"
  2. "Use Solomon to create a portal for business users, that lets them see what the BID is doing for them as well as helping them to get more from the BID"
  3. "Create a mobile application that the BID team can use, on any device and from any location, to capture and update data about the BIDs' relationships with their members" 

After an incredibly steep learning curve for the whole team, including understanding the dynamics of NNDR data, and learning to pronounce the word "hereditament", we launched Solomon for BIDs in September 2016. Andrew and his team were, and have remained, an invaluable partner, helping us to understand the intricacies of BIDs at all stages of development and delivery, while also helping us to shape features that deliver value by improving data quality, promoting efficiency and enhancing local knowledge.

At the time of writing, LeedsBID has been joined by Bristol City Centre BID and Liverpool BID Company, along with BIDs in York, Stockton, Shrewsbury, Otley, Keighley and, most recently, Basingstoke, in using Solomon. Each BID is unique and has brought new requirements that continue to shape the software. For example, the team in Bristol asked us if we could help them to track voting intentions, so we added Ballots and Votes to our database. This means BIDs can now track voting intention for any eligible business for any given ballot, and use tools and reporting dashboards to track progress and forecast results. We will be keeping our fingers tightly crossed for Bristol City Centre BID until we hear the outcome of next month's ballot.

A platform for collaboration

While Solomon has been driven by the core team of designers and developers within the Solomon team, the technology would not exist in the way it does today without the influences and contributions of others. Collaboration is central to how we work. Here are a few examples of how it happens:

Gathering Knowledge: we are always working with BIDs to unlock data and consolidate knowledge into their clouds. Sometimes this involves liaising with local authority partners or hunting and gathering data from across the web, and other times it's interacting with third-party data providers to overcome the technical challenges of moving data back and forth securely.

Sharing Knowledge: working with BIDs has been a steep learning curve for our team, but we have risen from this baptism with an intricate understanding of BIDs of all shapes and sizes. We're proactive about sharing that knowledge with early stage BIDs, as well as connecting them with more experienced practitioners we've met along the way. We aim to be a useful resource for BIDs who want to understand and make better use of technology. We are happy to offer our time to help BIDs assess their options — "should I use MailChimp or Campaign Monitor, and why?" — and to assist them with issues related to data protection and security.

Service Design: great software services start with the user and their needs. We run workshops with BID teams and businesses, listening to their evolving requirements and using what we learn to shape the roadmap for Solomon so that it delivers maximum value today and tomorrow.

Innovation: open innovation is in our DNA. We depend on the effort of more than 700 developers around the world who help to make Ember.js better, and we say "thank you" by sharing code, approaches and best practice back to the community. We are about to come to the end of our second Innovate UK funded collaborative research programme. Working with City of Bradford MDC and a group of engineers, we have developed a family of Internet-connected, environmental sensors that feed data back to Solomon in real-time. These promise value to BIDs and their members by boosting local intelligence. 

Integration: we are working with Springboard, The Welcome People, Sentrysis, Meerkat and more, to pull data from existing services and systems together in Solomon, eliminating the need for spreadsheets and making it easier for BIDs to generate reports and share success.

Storytelling: Solomon is a part of the Hebe Works group of companies and our sister company, The City Talking (TCT), is a media company with an award-winning approach to "destination marketing" that is delivered through high-quality storytelling. Like us, the TCT team aim to promote a deeper understanding of place by uncovering fascinating stories about the people who make our towns and cities light up. Examples of their work include a BBC backed documentary, Do You Want To Win?; working in partnership with LeedsBID to deliver the first Leeds International Festival (see video); and The City Talking: Air Quality, a collaboration with the Solomon team, using 48 million rows of open data to illustrate the impact of nitrogen dioxide on all our lives.

Solomon is more than software. It's a platform for collaboration, and a partner, that wants our towns and cities to thrive. At Solomon, we believe we achieve that best by making deep relationships between people and place. That has to start at a local level. 

Solving "the NNDR problem"

Business Improvement Districts, Town Centre Management teams and other people involved in place-making spend too much of their time managing data instead of doing.

Having access to quality data is key for place management teams. Often, that data comes from a number of sources which need to be synchronised on a regular basis.

Take National Non-domestic Rates (NNDR) for example. Each local authority maintains a list of hereditaments and the parties liable for paying business rates. As businesses move and change, and as new hereditaments are created, this data changes.

Today, most place managers maintain this data by wading through spreadsheets and manually updating records to ensure everything is in sync. It’s time-consuming work and as soon as it’s finished their data is already out-of-date.

We’ve solved this problem with Solomon. Our software incorporates a central database that allows place management teams to consolidate, store, share and get value from data.
Solomon can consume data from almost any source.

For example, NNDR data can be grabbed from the web or uploaded in spreadsheets; Solomon then automatically imports and updates the records. New hereditaments are created and flagged for the place manager’s attention. Existing records, including liable party details are updated. Finally, a link is created to a business record where all the information generated by a place management team is stored.

Less work for you and your team. More time for doing.

Andrew Cooper on why LeedsBID chose to support Solomon

It's almost exactly a year since we held our first workshop with the LeedsBID team to look at how Solomon could be used to help them to overcome some of the many challenges they face. In this short interview, Chief Executive Andrew Cooper explains why LeedsBID chose Solomon and gives an insight into the value it has created for his team and customers.

Solomon has been tailored, specifically, to meet the needs of how a Business Improvement District should be run from the start.
— Andrew Cooper - LeedsBID