<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>TradeYoke — Engineering</title>
    <link>https://tradeyoke.com/blog/tag/engineering</link>
    <description>How TradeYoke is built — architecture, decisions and trade-offs.</description>
    <language>en-gb</language>
    <atom:link href="https://tradeyoke.com/blog/tag/engineering/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The TradeYoke build timeline: every part of the build, in order</title>
      <link>https://tradeyoke.com/blog/the-tradeyoke-build-timeline</link>
      <guid>https://tradeyoke.com/blog/the-tradeyoke-build-timeline</guid>
      <pubDate>Wed, 14 Oct 2026 08:39:00 GMT</pubDate>
      <description>One page listing every part of Building TradeYoke in date order, from the idea in 2019 and the start in January 2024 to where the platform stands in October 2026.</description>
      <content:encoded><![CDATA[Part 39 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: From passwords to passkeys: how sign-in and trust grew with TradeYoke. See every part on the build timeline.

### Quick answer

Quick answer: Building TradeYoke is a month-by-month account of how the platform was built, from the start of development in January 2024 to October 2026, after an idea dating from around 2019. This page lists every part in date order, grouped by phase: the start, customers and jobs, invoicing, quoting, surveys and inspections, maps and directions, live monitoring, and the present.

### Key takeaways

Development started at the beginning of 2024; the idea dates from around 2019.The order was: customers and jobs, invoicing, quoting, surveys and inspections, maps and directions, then live monitoring. The document library began in July 2024 and spread across the system in March and April 2025.Every part below links to the full article.The most recent work is on the phone experience, sign-in and passkeys.

### How to read this page

The parts are in date order. Each phase has a one-line summary, and every entry links to the full article. If you only read one, start with the whole journey. For the same story by version and date, including the numbered releases from 0.2.2 to 0.3.45, see the release notes.

### The idea and the decision (2019 to January 2024)

Where the idea came from and why we began.

January 2024: Where TradeYoke began: an idea from helping run window cleaning roundsJanuary 2024: Five years of the same idea, and why we finally started building

### Designing the core (February to June 2024)

The problem, the round, the customer record, the repeating job, our terms and the early engineering decisions.

February 2024: Why window cleaning rounds drift, and what a good one looks likeMarch 2024: What is a round? Designing it in softwareApril 2024: The customer record a window cleaner actually needsMay 2024: Designing a job that repeats: every four weeks, for yearsJune 2024: Why we published our terms and privacy notice from the startJune 2024: One codebase and offline-first: the early engineering decisions

### Customers and jobs (July to September 2024)

Window cleaning customers and jobs working end to end, the document library for the paperwork, the diary, and getting a round in.

July 2024: July 2024: customers and jobs working end to end for window cleaningJuly 2024: July 2024: a library for the paperwork, filed where you will lookAugust 2024: August 2024: a diary that fills itself from the roundSeptember 2024: September 2024: getting an existing round in without retyping it

### Invoicing (October 2024 to January 2025)

Invoices, the ledger, part payments and Who owes me, and how customers pay.

October 2024: October 2024: why invoicing came next, and what it had to get rightNovember 2024: November 2024: a ledger that cannot be quietly editedDecember 2024: December 2024: part payments, receipts and knowing who owes youJanuary 2025: January 2025: how customers pay, with pay links, cards and Direct Debit

### Quoting and the document library everywhere (February to April 2025)

Guided quotes, the page customers accept on, what happens after a quote is sent, and the document library reaching every record, with search and expiry.

February 2025: February 2025: quotes that start from the customer record, not a blank pageMarch 2025: March 2025: the page a customer accepts a quote onMarch 2025: March 2025: documents on every record, for the job, the customer, the van and the companyApril 2025: April 2025: what happens after a quote is sentApril 2025: April 2025: searching inside your documents, not just their namesApril 2025: April 2025: expiry dates, so a certificate never runs out unnoticed

### Surveys, inspections and signatures (May to July 2025)

Site surveys, inspection checklists with evidence and sign-off, and one signature pad.

May 2025: May 2025: site surveys, because some jobs need looking at before you can price themJune 2025: June 2025: inspections, checklists with pass or fail, evidence and sign-offJuly 2025: July 2025: one signature pad, used wherever a customer or an engineer signs

### Maps and directions (August to October 2025)

Addresses, directions to the door and one set of maps on Google Maps.

August 2025: August 2025: getting the address right, with postcodes and map pinsSeptember 2025: September 2025: directions to the door, from the job or the customerOctober 2025: October 2025: one set of maps, built on Google Maps

### Live monitoring (November 2025 to January 2026)

Where is everybody, consent first, and trails and replay.

November 2025: November 2025: where is everybody? Live monitoring beginsDecember 2025: December 2025: consent first, and tracking a team fairlyJanuary 2026: January 2026: trails and replay, and what a day's route can tell you

### The phone, the day and more trades (February to April 2026)

Offline-first in practice, Plan my day, and one core for many trades.

February 2026: February 2026: working with no signal, offline-first in practiceMarch 2026: March 2026: Plan my day, decide, order, goApril 2026: April 2026: one core, many trades

### Looking back (September to October 2026)

Pricing, sign-in and trust, lessons, and the whole journey.

September 2026: How we thought about pricing TradeYoke: four plans, one price per businessOctober 2026: What building for tradespeople has taught us: seven lessons from the buildOctober 2026: From a 2019 idea to today: the whole TradeYoke journeyOctober 2026: From passwords to passkeys: how sign-in and trust grew with TradeYoke

### What the timeline does not show

It shows the order, not the effort. Some months, such as the ledger and the consent work, took far more care than their length suggests. And it shows what we built, not everything we tried. We have kept the account to what is in the product and true today. Where a part is still in pilot, the article says so.

### Where it stands now

Window cleaning and gardening are in pilot, with a first release very soon. Electricians, plumbers and solar installers are in pilot with real businesses. The web app is available now and works on a phone. The Android, iPhone and Windows apps are in pilot and not yet in the app stores; email hello@tradeyoke.net if you would like early access.

### Questions people ask

**What is the Building TradeYoke series?**

A month-by-month account of how TradeYoke was built, from the start of development in January 2024 to October 2026.

**When did TradeYoke development start?**

At the beginning of 2024, after an idea dating from around 2019 while helping manage window cleaning rounds.

Related: The platform · All features · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Our story</category>
      <category>Engineering</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-the-tradeyoke-build-timeline-jpg/cover-the-tradeyoke-build-timeline.jpg?v=1zvjr28n" type="image/jpeg" length="174333" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-the-tradeyoke-build-timeline-jpg/cover-the-tradeyoke-build-timeline.jpg?v=1zvjr28n" medium="image" />
    </item>
    <item>
      <title>From passwords to passkeys: how sign-in and trust grew with TradeYoke</title>
      <link>https://tradeyoke.com/blog/from-passwords-to-passkeys-sign-in-and-trust</link>
      <guid>https://tradeyoke.com/blog/from-passwords-to-passkeys-sign-in-and-trust</guid>
      <pubDate>Wed, 14 Oct 2026 08:34:00 GMT</pubDate>
      <description>A system that holds a business's customers and invoices has to be hard to break into. Here is how TradeYoke's sign-in grew, and what is live in the web browser today.</description>
      <content:encoded><![CDATA[Part 38 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: From a 2019 idea to today: the whole TradeYoke journey. Next: The TradeYoke build timeline: every part of the build, in order. See every part on the build timeline.

### Quick answer

Quick answer: TradeYoke's sign-in has grown in steps: it began with email and password, added Sign in with Google and optional two-factor authentication, then passkeys, and in October 2026 became passwordless. You now sign in with Google, Apple or Microsoft, an emailed six-digit code or link, or a passkey, and TradeYoke holds no passwords at all. Passkeys in the Android, iPhone and Windows apps are coming shortly; the apps themselves are in pilot.

### Key takeaways

Sign-in is now passwordless: Google, Apple, Microsoft, an emailed code or link, and passkeys. TradeYoke holds no passwords.Two-factor authentication can be required of everyone in a workspace.Permissions on every action and an audit trail sit behind the sign-in.Passkeys for the apps are coming shortly; the apps are in pilot.

### Why sign-in matters more than it looks

From the moment TradeYoke held invoices, the sign-in was the lock on the shop door. A stolen login could mean a changed bank detail on an invoice, which is exactly the kind of fraud that hits small businesses. So as the product grew, so did the effort we put into who can get in.

### The steps

Email and password. The starting point, with a proper account for each person. Sign-ins are not shared. Retired in October 2026; see the last step.Sign in with Google. For people who would rather not manage another password. Our article on signing in with Google goes through it.Two-factor authentication. An extra code on sign-in, which a workspace can require of everyone. It follows the person, so it is checked whichever way they sign in.Permissions and an audit trail. Behind the sign-in, every action is controlled by a permission, and a trail records who did what. Nobody can give someone more access than they have themselves, and nobody can edit their own roles.Passkeys. Live in the web browser since October 2026.No passwords at all. The newest step, in October 2026: Google, Apple, Microsoft, an emailed code or link, and passkeys all lead to one TradeYoke account, and people add or remove ways to sign in under My account.

### What a passkey is

A passkey is a way of signing in with something you have, your phone or computer, unlocked the way you already unlock it, instead of a password you type. There is no password to guess, phish or reuse. Passkeys: sign in without a password is the longer explanation.

### What is live, and what is not

Passkeys are live in the web browser. Passkeys in the Android, iPhone and Windows apps are coming shortly, and the apps themselves are in pilot and not yet in the app stores. We would rather tell you what is not finished than let you assume it is.

### The thread running through the build

Every year of the build added something worth protecting: customers in 2024, money in 2024 and 2025, locations in 2025. Each time the sign-in had to be at least as strong as the thing behind it. That is also why we wrote the terms and privacy notice so early.

### Questions people ask

**Can I sign in to TradeYoke without a password?**

Yes. TradeYoke has no passwords: you sign in with Google, Apple or Microsoft, an emailed code or link, or a passkey. Passkeys in the Android, iPhone and Windows apps are coming shortly.

**Can my whole team be required to use two-factor sign-in?**

Yes. A workspace can require two-factor authentication of everyone.

Related: Roles, permissions, audit and 2FA · Passkeys: sign in without a password · Sign in with Google · Invoice fraud and account takeover protection · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Product</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-from-passwords-to-passkeys-sign-in-and-trust-jpg/cover-from-passwords-to-passkeys-sign-in-and-trust.jpg?v=195r3j87" type="image/jpeg" length="98323" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-from-passwords-to-passkeys-sign-in-and-trust-jpg/cover-from-passwords-to-passkeys-sign-in-and-trust.jpg?v=195r3j87" medium="image" />
    </item>
    <item>
      <title>One app, four platforms: how we ship to web, iOS, Android and Windows at once</title>
      <link>https://tradeyoke.com/blog/one-app-four-platforms</link>
      <guid>https://tradeyoke.com/blog/one-app-four-platforms</guid>
      <pubDate>Sat, 05 Sep 2026 21:15:11 GMT</pubDate>
      <description>TradeYoke's web app and native apps are the same code. Here's what that buys customers — and the rules we follow to keep it true.</description>
      <content:encoded><![CDATA[Quick answer: TradeYoke is one shared codebase rendered on the web and packaged as native apps for Windows, Android and iOS, rather than four separate products built to look alike — a feature written once for the web is, by construction, the same feature on every other platform, not a separate rebuild that might drift out of sync.

 Key takeaways
 
 Every screen lives in one shared component library; the web server, the browser and the native apps are thin shells around the same code.
 A fix or a new feature ships to every platform together, because there is only one place it lives.
 The installed native apps work offline, and since November 2026 the web app keeps working with no signal after one visit too.
 Platform-specific things — the camera, GPS, file pickers — go behind one shared interface with a separate implementation per platform, never a special case in the shared screens.
 A missing platform implementation is treated as a bug to fix, not a "coming soon" to ship around.
 
 The rule: one codebase, four faces
 Most software that claims to run "everywhere" actually means two or three teams building look-alike apps against the same backend, which is how a mobile app quietly falls a version behind the web version, or gains a feature the web version never gets. TradeYoke doesn't work that way. Everything a user sees — the schedule, the job wizard, the invoice screen — lives in one shared component library. The web server, the browser (running the same code client-side), and the native Windows, Android and iOS apps are thin hosts around those same components. A feature built for the web is therefore, automatically, the same feature everywhere else, because there is no second version of it to fall behind.

 What it means day to day
 For the person using it, the practical difference is that there's no "that's only on the desktop version" moment. The office, planning the week on a monitor, and the person in the van, checking the same job on a phone, are looking at the same screen doing the same things — not a cut-down mobile view that's missing half the buttons. When something is fixed or improved, it reaches every platform in the same release, not the web this month and the app "eventually". And because the phone and Windows apps are properly installed, native apps rather than a web page wrapped in a shell, they carry TradeYoke's offline support: the day's jobs, customer records and prices are available and editable with no signal, syncing automatically once a connection returns. The browser-based web app is a little different: since November 2026 it keeps working with no signal after one visit, but a browser keeps your work less safely than an installed app does, so the apps remain the better place to carry a round.

 The discipline it takes to keep it true
 The rule only holds if it's enforced, so platform differences — the camera, GPS, a file picker, push notifications — are never called directly from the shared screens. Each goes behind one shared interface, with a separate implementation supplied by each platform: the web version might use a browser API, the native version the device's own SDK, but the shared component never knows or cares which one is underneath. A platform that hasn't got its own implementation yet is treated as an unfinished bug in that interface, not a reason to write a special-case branch in the shared code — the moment a screen starts asking "which platform am I on", the one-codebase promise starts breaking, so that question is never allowed to appear outside the interface boundary itself.

 Why this matters for a trade business, not just for engineers
 The instinct is to treat "one codebase" as an implementation detail that only interests developers, but it's the reason a business running TradeYoke never has to plan around a feature gap between "the app" and "the website". A team member who prefers a Windows laptop, one who lives on Android in the van, and an office manager who only ever opens a browser are all working from the same data, the same screens and the same day's plan — there's nothing to keep in sync between them because it was never four things to begin with.

 Questions people ask
 Does the web app have fewer features than the native apps?
 No — the same shared screens render on both; the meaningful difference is how offline support is kept: the installed native apps keep it on the device and send changes in the background, and the web app keeps working with no signal after one visit too, not a stripped-down web experience.

 If I use the app on Windows and my colleague uses Android, do we see the same thing?
 Yes. You're both running the same shared components against the same data; the only difference is the device drawing them.

 Does a new feature ever appear on one platform before another?
 The intent of building this way is that it doesn't — a feature is written once in the shared layer and ships wherever that layer runs. Platform-specific plumbing (like a device capability) can take a release longer on a platform that needs its own implementation, which is treated as a gap to close, not an accepted permanent difference.

 Does the web app work offline like the phone app does?
 A browser tab cannot promise as much as an installed app that data survives being closed, losing signal or being reopened days later. TradeYoke's installed apps on Windows, Android and iOS keep that support on the device, and since November 2026 the web app keeps working with no signal after one visit too, with a weaker copy on the device.

[Image: One app, the same feature, on every trade's phone.]

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-one-app-four-platforms-jpg/cover-one-app-four-platforms.jpg?v=yelslvq" type="image/jpeg" length="129319" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-one-app-four-platforms-jpg/cover-one-app-four-platforms.jpg?v=yelslvq" medium="image" />
    </item>
    <item>
      <title>April 2026: one core, many trades</title>
      <link>https://tradeyoke.com/blog/one-core-many-trades-adding-gardening-and-more</link>
      <guid>https://tradeyoke.com/blog/one-core-many-trades-adding-gardening-and-more</guid>
      <pubDate>Tue, 14 Apr 2026 08:30:00 GMT</pubDate>
      <description>With window cleaning solid, April 2026 was about whether the core could carry other trades. Each trade is a module on the same core: its own terms, forms and colour.</description>
      <content:encoded><![CDATA[Part 34 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: March 2026: Plan my day, decide, order, go. Next: How we thought about pricing TradeYoke: four plans, one price per business. See every part on the build timeline.

### Quick answer

Quick answer: TradeYoke is built as one shared core with a module for each trade. Window cleaning and gardening are in pilot, with a first release very soon; electricians, plumbers and solar installers are in pilot with real businesses. Each trade brings its own terminology, forms, documents and colour, while customers, scheduling, quoting and invoicing are shared, so one business can run compatible trades on one account.

### Key takeaways

There is one core, and each trade is a module on top.Window cleaning and gardening are in pilot, with a first release very soon; electricians, plumbers and solar installers are in pilot.Each trade brings its own terms, forms, documents and colour.A business can run compatible trades together on one account.

### The test of a good core

When you build for one trade it is easy to build something that only works for that trade. The test of the core we built in 2024 was whether it could carry another. In April 2026 we looked at where the line between shared and trade-specific fell, and what that meant for every new trade.

### What is shared, what is not

Shared: customers, the diary, jobs, quotes, invoices, payments, messages, documents and the map. A customer is one record whichever trade serves them.Per trade: the words (a gardener's visit is not a window cleaner's clean), the fields on a customer, the job steps, the forms and the paperwork, and a colour so you can tell them apart on the diary.

### Why that split

The shared parts are the things that would be wasteful to build twice and risky to build differently. The invoice ledger should work the same way for every trade. The per-trade parts are the things a tradesperson would notice if they were wrong. A plumber does not want to see "round" and "frequency" where their trade says "service" and "boiler".

### Where each trade stands

Window cleaning and gardening are live.Electricians, plumbers and solar installers are in pilot with real businesses. They bring their own paperwork, such as electrical certificates, gas safety records and solar commissioning documents, built on the shared document foundation.

"Pilot" means a small group of businesses use the module on their own work while we finish it. If you would like to join, email hello@tradeyoke.net.

### What it means for you

If you run two trades, say window cleaning and gardening, you do not need two systems. One diary, one customer list and one invoice run covers both. Two trades, one account goes through it.

### Next

The series now catches up with the present. The next articles look back across the whole build.

### Questions people ask

**Which trades does TradeYoke support?**

Window cleaning and gardening are in pilot, with a first release very soon. Electricians, plumbers and solar installers are in pilot with real businesses.

**Can I run two trades on one TradeYoke account?**

Yes, compatible trades such as window cleaning and gardening share one diary, one customer list and one invoice run.

Related: Several trades, one account · All trades · Two trades, one account · The platform · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Product</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-one-core-many-trades-adding-gardening-and-more-jpg/cover-one-core-many-trades-adding-gardening-and-more.jpg?v=1uf8qbyv" type="image/jpeg" length="193669" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-one-core-many-trades-adding-gardening-and-more-jpg/cover-one-core-many-trades-adding-gardening-and-more.jpg?v=1uf8qbyv" medium="image" />
    </item>
    <item>
      <title>February 2026: working with no signal, offline-first in practice</title>
      <link>https://tradeyoke.com/blog/working-with-no-signal-offline-first-in-practice</link>
      <guid>https://tradeyoke.com/blog/working-with-no-signal-offline-first-in-practice</guid>
      <pubDate>Tue, 10 Feb 2026 09:28:00 GMT</pubDate>
      <description>February 2026 put the offline-first idea from 2024 to work: the round on the device, changes queued, and a clear rule for when two people edit the same thing.</description>
      <content:encoded><![CDATA[Part 32 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: January 2026: trails and replay, and what a day's route can tell you. Next: March 2026: Plan my day, decide, order, go. See every part on the build timeline.

### Quick answer

Quick answer: In TradeYoke's phone and Windows apps, which are in pilot, changes made without a signal are saved on the device in a queue and sent when the connection returns. Each change is safe to send twice, and unsent work is never overwritten by something older from the server. The web app needs a connection.

### Key takeaways

Changes made offline are queued on the device and sent when signal returns.Each change is safe to retry, so a flaky connection cannot create duplicates.Unsent work is never overwritten.The apps are in pilot; the web app needs a connection.

### The idea, put to work

In June 2024 we wrote that the phone would hold what it needs and queue changes. By February 2026 the machinery to do it was working in the installed apps, and this article is the practical account of what it does.

### How it behaves

Your round is on the phone. Daily rounds for window cleaning and gardening are available without a connection, and you can create a new customer on the spot.Changes go into a queue. Marking a visit done, adding a note or a new customer saves on the device at once.The queue is sent when the signal returns, on opening the app, when the network comes back, and on returning to the app.Safe to retry. Each change carries a unique identity, so if the connection drops half-way and the change is sent again, it is applied once.Order is kept. If a customer was created offline and a job was added to them, the job waits for the customer. Dependent changes are held until what they depend on has gone through.

### When two people change the same thing

The hard case is a conflict. The office changed a job while you were out of signal and changed it differently on your phone. The rule is that unsent work is never overwritten. Your change is kept, the difference is visible, and a person decides. That rule matters more than any cleverness in how conflicts are merged.

### An honest status

Offline support covers a limited set of things today: window cleaning and gardening rounds, and creating customers. It does not cover everything, and certificates, quotes and invoices are not yet available offline. The Android, iPhone and Windows apps that carry it are in pilot and not yet in the app stores. The web app is the always-online office surface. If you want to try the pilot, email hello@tradeyoke.net.
Update, November 2026: quotes, invoices, payments in cash, messages and certificates now work with no signal too, and the web app keeps working with no signal after one visit.

### Why it still matters

Most days, signal is fine. The days it is not are the days a round gets lost. A tool that works on those days is a tool you trust on the others. Why offline-first matters more than any feature says the same thing from the owner's side.

### Next

March: the morning flow, Plan my day.

### Questions people ask

**Does TradeYoke work without a signal?**

The phone and Windows apps, which are in pilot, keep your round on the device and sync when the connection returns. Update, November 2026: the web app now keeps working with no signal after one visit too.

**What happens if I and the office change the same job?**

Unsent work is never overwritten. Your change is kept, the difference is shown, and a person decides.

Related: The mobile app · Why offline-first matters · The early engineering decisions · The platform · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Mobile</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-working-with-no-signal-offline-first-in-practice-jpg/cover-working-with-no-signal-offline-first-in-practice.jpg?v=3f8oyk9j" type="image/jpeg" length="198980" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-working-with-no-signal-offline-first-in-practice-jpg/cover-working-with-no-signal-offline-first-in-practice.jpg?v=3f8oyk9j" medium="image" />
    </item>
    <item>
      <title>January 2026: trails and replay, and what a day's route can tell you</title>
      <link>https://tradeyoke.com/blog/trails-and-replay-a-days-route</link>
      <guid>https://tradeyoke.com/blog/trails-and-replay-a-days-route</guid>
      <pubDate>Tue, 13 Jan 2026 08:27:00 GMT</pubDate>
      <description>January 2026 added trails to the live map and a way to replay a device's day. What a route can settle, and why it is worth having.</description>
      <content:encoded><![CDATA[Part 31 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: December 2025: consent first, and tracking a team fairly. Next: February 2026: working with no signal, offline-first in practice. See every part on the build timeline.

### Quick answer

Quick answer: Live monitoring in TradeYoke shows a trail behind each person sharing their location, and you can replay a device's trail to see the route it took. It helps settle questions such as when someone arrived, and it works for people, vehicles, jobs and customers shown on the same map. Live monitoring is part of the Ultimate plan.

### Key takeaways

A trail shows where a device has been, not just where it is now.Replay lets you watch a day's route back.It settles arrival-time questions with facts rather than memory.It is part of the Ultimate plan and only covers people who are sharing.

### A dot is not enough

A live dot answers where someone is now. A day on a round raises other questions: when did they get to the second job, did they come by the main road, how long was the stop? January 2026 added trails to answer those.

### What trails and replay do

A trail behind each dot shows where the device has been.Replay lets you pick a device and watch its route back, in order.Everything on one map: people, plus vehicles, jobs and customers as places, so a route can be read against the stops it was meant to reach.

### What it is for

The honest uses are mostly mundane. A customer says nobody came at ten; the trail shows the van was on the next street at five past. A job overran; the replay shows where the time went. Two jobs were swapped and the invoice needs to say which was done first. It turns an argument about memory into a look at the map, which is calmer for everyone.

### What it is not for

It is not a way to micromanage. The consent and sharing rules from December still apply: trails exist only for people who have agreed to share, and who can switch it off. If you use trails, say so to your team and say what you use them for.

### How long things are kept

The privacy policy sets out the retention periods for technical data. If you need to know exactly what is kept for how long, read the privacy policy rather than a blog post, because the policy is the document we are accountable for.

### Next

February: the other side of the phone, working with no signal.

### Questions people ask

**Can I replay where a vehicle or person has been in TradeYoke?**

Yes. Live monitoring shows trails and lets you replay a device's trail. It covers people who are sharing their location.

**Which plan includes live monitoring?**

Live monitoring is part of the Ultimate plan. See the pricing page for current details.

Related: Live monitoring · Van tracking without the hardware · Pricing · Privacy Policy · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Product</category>
      <category>Engineering</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-trails-and-replay-a-days-route-jpg/cover-trails-and-replay-a-days-route.jpg?v=1r7vx53r" type="image/jpeg" length="192129" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-trails-and-replay-a-days-route-jpg/cover-trails-and-replay-a-days-route.jpg?v=1r7vx53r" medium="image" />
    </item>
    <item>
      <title>November 2025: where is everybody? Live monitoring begins</title>
      <link>https://tradeyoke.com/blog/where-is-the-van-live-monitoring-begins</link>
      <guid>https://tradeyoke.com/blog/where-is-the-van-live-monitoring-begins</guid>
      <pubDate>Tue, 11 Nov 2025 10:25:00 GMT</pubDate>
      <description>Every business with more than one van asks the same question sooner or later. November 2025 began live monitoring: the team on one map, with the phone app as the tracker.</description>
      <content:encoded><![CDATA[Part 29 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: October 2025: one set of maps, built on Google Maps. Next: December 2025: consent first, and tracking a team fairly. See every part on the build timeline.

### Quick answer

Quick answer: TradeYoke's live monitoring shows everyone who is sharing their location on one Google map, with the phone app acting as the tracker so there is no extra hardware to fit. It is part of the Ultimate plan. The Android, iPhone and Windows apps are in pilot and not yet in the app stores.

### Key takeaways

Live monitoring shows who is where on one map.The phone app is the tracker, so no extra hardware is fitted.Customers, jobs and vehicles can be shown on the same map.It is part of the Ultimate plan, and the apps are in pilot.

### The question behind the feature

As soon as a business has two people working, a question appears: where is everybody? It is asked on the phone ("where are you?"), usually while someone is driving. The honest reason is rarely suspicion. It is usually practical: a customer is ringing about an arrival time, or a job has overrun, or someone needs to be sent to the nearest gap.

### The approach: the phone is the tracker

The traditional answer is a tracking box fitted to each van. That is cost and fitting time, and it only tells you where the van is, not where the person is. We took a different approach. The phone the person already carries, running TradeYoke, is the tracker. There is nothing to buy or fit. It also means you see people, not just vehicles, which matches how a small business actually works.

### What November delivered

A live map of everyone sharing their location, on the shared Google map.Different kinds of things on one map: people, plus customers, jobs and vehicles as places you can see.A current-location panel on a record, so you can see where a person or a job is from where you are already looking.A widget in the app so it is one tap away.

Van tracking without the hardware explains this in more detail for a business owner.

### What it depends on

Live monitoring is part of the Ultimate plan. The tracker is the phone app, and the Android, iPhone and Windows apps are in pilot and not yet in the app stores; email hello@tradeyoke.net if you would like early access. We have not finished checking every phone background mode on a real device, and we would rather say so than claim it.

### Next

December: the part that matters more than the map, which is consent.

### Questions people ask

**Does TradeYoke need tracking hardware in the van?**

No. The phone app is the tracker, so there is nothing to buy or fit. Live monitoring is part of the Ultimate plan.

**What can I see on the live map?**

Everyone who is sharing their location, plus customers, jobs and vehicles as places on the same map.

Related: Live monitoring · Van tracking without the hardware · Pricing · Team and safety · The build timeline

See also: canvassing a new round, with canvassers on Live Monitoring

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Product</category>
      <category>Engineering</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-where-is-the-van-live-monitoring-begins-jpg/cover-where-is-the-van-live-monitoring-begins.jpg?v=1t7d9jbr" type="image/jpeg" length="196327" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-where-is-the-van-live-monitoring-begins-jpg/cover-where-is-the-van-live-monitoring-begins.jpg?v=1t7d9jbr" medium="image" />
    </item>
    <item>
      <title>October 2025: one set of maps, built on Google Maps</title>
      <link>https://tradeyoke.com/blog/google-maps-across-tradeyoke</link>
      <guid>https://tradeyoke.com/blog/google-maps-across-tradeyoke</guid>
      <pubDate>Tue, 14 Oct 2025 09:24:00 GMT</pubDate>
      <description>By October 2025 TradeYoke needed maps in many places. We built one shared set on Google Maps, so a customer, a job and the whole team all use the same map.</description>
      <content:encoded><![CDATA[Part 28 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: September 2025: directions to the door, from the job or the customer. Next: November 2025: where is everybody? Live monitoring begins. See every part on the build timeline.

### Quick answer

Quick answer: TradeYoke uses one shared set of map components built on Google Maps, so the map on a customer, a job and the live team map behave the same. When a map is opened, your browser or app loads it from Google, which receives your IP address and the area you are viewing; TradeYoke does not send Google your name, account or workspace details.

### Key takeaways

One shared set of map components is used everywhere a map appears.Maps and directions are provided by Google Maps Platform.When you open a map, Google receives your IP address and the area you are viewing. It does not receive your name or workspace details from us.The privacy policy says this in plain words.

### Maps in more than one place

By October 2025 maps were needed in a lot of places: the customer's address, a job's location, the planner and, soon, where the team is. The easy way to do that is to build a map each time. The result is maps that look different and behave differently, and a bug fixed in one that is still there in the others. So we built one shared set of map components and used them everywhere.

### Why Google Maps

We chose Google Maps for the map itself because it is the map tradespeople already know: the satellite view shows a roof or a garden, and Street view shows a gate. Customers and staff do not need to learn anything.

### What you can do with it

See a customer or a job on a map, with the address pinned.Switch between Map and Satellite, useful for seeing a roof or a lawn.Choose what to show, such as vehicles, jobs and customers, on the full map.Get directions, from the same place.

### Being straight about privacy

Using Google Maps means Google is involved, and we think you should know how. When you open a map, your browser or app loads it directly from Google, so Google receives your IP address and the area of the map you are viewing. When you ask for a route from where you are, Google also receives that starting position. We do not send Google your name, your account or your workspace details, and maps in TradeYoke are not used for advertising. If you never open a map, nothing is sent. This is written into our privacy policy, in the section on who we share data with.

### The engineering lesson

A shared component is only worth it if everyone uses it. The rule we set was that no screen draws its own map: it asks for the shared one. That made later features, including live monitoring, far quicker to build.

### Next

November: the question every van owner asks at some point. Where is everybody?

### Questions people ask

**What does Google receive when I open a map in TradeYoke?**

Your IP address and the area of the map you are viewing, and your starting position if you ask for a route from where you are. TradeYoke does not send Google your name, account or workspace details.

**Can I see satellite view in TradeYoke?**

Yes. On the full-screen map you can switch between Map and Satellite.

Related: Live monitoring · Customers and CRM · Privacy Policy · A customer record on your phone · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Product</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-google-maps-across-tradeyoke-jpg/cover-google-maps-across-tradeyoke.jpg?v=2j5tel1z" type="image/jpeg" length="134424" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-google-maps-across-tradeyoke-jpg/cover-google-maps-across-tradeyoke.jpg?v=2j5tel1z" medium="image" />
    </item>
    <item>
      <title>August 2025: getting the address right, with postcodes and map pins</title>
      <link>https://tradeyoke.com/blog/getting-the-address-right-postcodes-and-pins</link>
      <guid>https://tradeyoke.com/blog/getting-the-address-right-postcodes-and-pins</guid>
      <pubDate>Tue, 12 Aug 2025 10:22:00 GMT</pubDate>
      <description>Everything on a round depends on the address. August 2025 added type-ahead address search, UK postcode lookup and a pin on a map for every customer.</description>
      <content:encoded><![CDATA[Part 26 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: July 2025: one signature pad, used wherever a customer or an engineer signs. Next: September 2025: directions to the door, from the job or the customer. See every part on the build timeline.

### Quick answer

Quick answer: TradeYoke helps you enter an address: a type-ahead search suggests addresses as you type, a UK postcode lookup fills in the county, and the address is turned into a map location so the customer appears as a pin. A pin is what lets the app show who is nearby and give directions.

### Key takeaways

Type-ahead suggestions mean fewer typos and fewer wrong addresses.A UK postcode lookup fills in the town and county.Each address becomes a map location, which is what makes routes and directions possible.Good addresses are the foundation for everything that comes after.

### A round is a set of places

Everything geographic in a field-service app starts with an address. A route is a list of places in an order. A map is a set of pins. Directions need somewhere to go. Until an address becomes a real point on a map, none of that works. So in August 2025 we made addresses properly.

### What we built

Type-ahead search. As you type an address, suggestions appear. Choosing one fills in the whole address, which is faster than typing and avoids typos.UK postcode lookup. Enter a postcode and the town and county are filled in.A map location for every address. The address is converted into a point on the map, so the customer appears as a pin. Without that step the map is empty.Shared map pieces. The same map components are used wherever a map appears, in a customer record, a job, and later the live map, so they behave the same everywhere.

### Why this was a separate piece of work

Addresses go wrong in familiar ways. "Rose Cottage, near the church" is not an address. "14A High Street" can be two places in two towns. A customer typed in from memory in 2019 may be wrong in ways nobody noticed because nobody needed it to be right. The moment a map appears, every wrong address is visible. We expected that, and that is why the map work came after the address work.

### A kindness to the data

When you import customers from a spreadsheet, you can fix addresses afterwards, as you meet each customer. You do not need a perfect list to start; you need a list that gets better as you use it.

### Next

September: the first thing a good address makes possible, which is getting to the door.

### Questions people ask

**Does TradeYoke look up UK postcodes?**

Yes. Entering a UK postcode fills in the town and county, and type-ahead suggests addresses as you type.

**Why does a customer need a map location?**

The location is what lets TradeYoke show the customer on a map, order a day's stops by distance and give directions to the door.

Related: Customers and CRM · Plan my day · Run your round from your phone · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Window cleaning</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-getting-the-address-right-postcodes-and-pins-jpg/cover-getting-the-address-right-postcodes-and-pins.jpg?v=1uz2xatz" type="image/jpeg" length="192829" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-getting-the-address-right-postcodes-and-pins-jpg/cover-getting-the-address-right-postcodes-and-pins.jpg?v=1uz2xatz" medium="image" />
    </item>
    <item>
      <title>June 2025: inspections, checklists with pass or fail, evidence and sign-off</title>
      <link>https://tradeyoke.com/blog/inspections-checklists-with-evidence-and-sign-off</link>
      <guid>https://tradeyoke.com/blog/inspections-checklists-with-evidence-and-sign-off</guid>
      <pubDate>Tue, 10 Jun 2025 08:20:00 GMT</pubDate>
      <description>June 2025 brought inspections: a checklist you build once, work through on site marking each item pass or fail, with evidence for every fail, signed off and sent as a report.</description>
      <content:encoded><![CDATA[Part 24 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: May 2025: site surveys, because some jobs need looking at before you can price them. Next: July 2025: one signature pad, used wherever a customer or an engineer signs. See every part on the build timeline.

### Quick answer

Quick answer: An inspection in TradeYoke is a checklist you build once and work through on site, marking each item pass or fail. A fail needs evidence, such as a photograph, and the finished inspection is signed off on the screen and sent as a report. Trades supply starter checklists, and inspections can repeat on a schedule.

### Key takeaways

You build a checklist template once and reuse it.Each item is pass or fail, and a fail needs evidence.Progress saves as you go, and the inspection can be signed off on the screen.The result becomes a report you can send, and inspections can recur.

### From survey to inspection

A survey happens before the work. An inspection checks work that is installed or underway: a vehicle check, a safety walk-round, a handover. In June 2025 we built the inspection tool on the same foundation as the survey, because the shape of the job is the same: a list of things to check, and a record of what you found.

### The design

Templates you build once. An inspection is a checklist, and you create it in a builder. Each item can carry guidance, such as a note or a picture, to show what a pass looks like.Starter templates from the trades. Each trade supplies sensible starting checklists, so you are editing, not starting from a blank page.Pass or fail, with evidence. Each item is marked pass or fail. A fail needs evidence, usually a photograph, so a failed item is never just a tick.Progress that saves. You can stop and carry on. An inspection that is half done is not lost.Sign-off. The finished inspection is signed on the screen.A report. The result is composed into a report you can send to the customer.

### Why evidence on a fail

The reason for the rule is simple. "Failed: cracked" is a statement. "Failed: cracked", with a photograph, is a record. A fail is the item most likely to be questioned later, so it is the item that most needs proof.

### Recurring checks

Many inspections come round again: a monthly vehicle check, a regular site walk. They can recur on a schedule and appear in the jobs list and on the diary like any other visit. The lone working guide shows how the same idea supports safety checks.

### Next

July: the signature pad, and where all this paperwork ends up.

### Questions people ask

**Can I build my own inspection checklist in TradeYoke?**

Yes. You build a template once, with guidance for each item, and reuse it. Trades also supply starter checklists.

**What happens when an inspection item fails?**

A fail needs evidence, such as a photograph, so it is recorded properly. The finished inspection is signed off and composed into a report you can send.

Related: Paperwork and compliance · Document library · Roles, permissions and audit · Keeping a lone worker safe · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Guides</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-inspections-checklists-with-evidence-and-sign-off-jpg/cover-inspections-checklists-with-evidence-and-sign-off.jpg?v=z8tuujb" type="image/jpeg" length="127977" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-inspections-checklists-with-evidence-and-sign-off-jpg/cover-inspections-checklists-with-evidence-and-sign-off.jpg?v=z8tuujb" medium="image" />
    </item>
    <item>
      <title>April 2025: searching inside your documents, not just their names</title>
      <link>https://tradeyoke.com/blog/searching-inside-your-documents-not-just-their-names</link>
      <guid>https://tradeyoke.com/blog/searching-inside-your-documents-not-just-their-names</guid>
      <pubDate>Tue, 15 Apr 2025 09:21:00 GMT</pubDate>
      <description>A library is only as good as your ability to find things in it. In April 2025 we made the library search inside the files, not just at their names.</description>
      <content:encoded><![CDATA[Part 21 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: April 2025: what happens after a quote is sent. Next: April 2025: expiry dates, so a certificate never runs out unnoticed. See every part on the build timeline.

### Quick answer

Quick answer: TradeYoke's document search reads the text inside PDFs, Word, Excel and PowerPoint files, plain text, web pages and scanned images (using optical character recognition), and shows a snippet of the match. A search for a serial number or a customer's name finds the document that mentions it, whatever the file is called.

### Key takeaways

Search looks at the words inside the file, not only at its name.It reads PDFs, Word, Excel and PowerPoint, text, HTML and scanned images.Results show a snippet, so you can tell the right one at a glance.New and older documents are indexed in the background, so nothing needs re-uploading.

### The file called scan0042

Every business has one. A scanner or a phone names the file for you, and months later you are looking for the certificate that mentioned a particular boiler, and all you have is a list of names that mean nothing. Filing against the job and customer helps, but only when you remember which job it was.

### What the search reads

In April 2025 we added a full-text index to the library. It reads the text inside the file:

PDFs, including the text layer.Word, Excel and PowerPoint files.Plain text and web pages.Images and scans, using optical character recognition, so a photographed page can be found by the words printed on it.

A search then shows a snippet around the match, so you can often tell it is the right document without opening it.

### Indexing that looks after itself

An index that has to be rebuilt by hand is an index nobody trusts. New documents are read as they arrive, and a background pass works through anything that was uploaded before the index existed, so older paperwork becomes searchable without anyone re-uploading it. If a file cannot be read the first time, it is picked up again on a later pass.

### Video too

A short video taken on site can hold the one useful sentence, such as a customer describing what is wrong. Videos can be transcribed, and the transcript is searchable alongside the documents.

### What it is good for

Finding the certificate that mentions a serial number.Finding every document that names a particular customer or street.Finding the manual page about an error code (the Knowledge shelf uses the same search).

### Next

Later in April: dates. A certificate you can find is good; one you are told about before it runs out is better.

### Questions people ask

**Can TradeYoke search inside a scanned PDF or a photo of a page?**

Yes. Scanned pages and images are read with optical character recognition, so a search for words printed on them finds the document.

**Does searching documents work on older files I uploaded earlier?**

Yes. A background pass indexes documents uploaded before search was added, so you do not need to upload them again.

Related: Documents and search · A document library that finds a certificate in seconds · Paperwork and compliance · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Product</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-searching-inside-your-documents-not-just-their-names-jpg/cover-searching-inside-your-documents-not-just-their-names.jpg?v=3g30uyw9" type="image/jpeg" length="196625" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-searching-inside-your-documents-not-just-their-names-jpg/cover-searching-inside-your-documents-not-just-their-names.jpg?v=3g30uyw9" medium="image" />
    </item>
    <item>
      <title>March 2025: the page a customer accepts a quote on</title>
      <link>https://tradeyoke.com/blog/the-page-a-customer-accepts-a-quote-on</link>
      <guid>https://tradeyoke.com/blog/the-page-a-customer-accepts-a-quote-on</guid>
      <pubDate>Tue, 11 Mar 2025 08:17:00 GMT</pubDate>
      <description>March 2025 gave the customer somewhere to say yes: a secure link to the quote, no login, with lines they can untick and a way to tell you when suits.</description>
      <content:encoded><![CDATA[Part 18 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: February 2025: quotes that start from the customer record, not a blank page. Next: March 2025: documents on every record, for the job, the customer, the van and the company. See every part on the build timeline.

### Quick answer

Quick answer: TradeYoke gives each quote a secure link. The customer opens it on any phone, with no app or login, and can accept or decline, untick optional lines, say when suits them and send a message back. What they do is recorded on the quote's timeline, and you can turn an accepted quote into a job.

### Key takeaways

The customer needs no app or login: the link is a plain web page that works on a phone.They can accept, decline, untick optional lines and say when suits.Every action is recorded on the quote's timeline.You can revoke a link if it was sent in error.

### A link, not an attachment

An emailed PDF has two problems: it gets lost, and there is no way to say yes to it. In March 2025 we built the other half of quoting: a link the customer opens to see the quote and respond.

### What the customer sees

The quote, laid out for a phone.Accept or decline, in one tap.Optional lines, which they can untick, with the total following every change.When suits them, so the preference reaches you with the answer.A box to message you, whose reply joins their communications thread.

They do not need an account, because asking a customer to register to accept a quote loses quotes.

### Keeping it safe

A link anyone can open needs care. Each link is a long random token, not something a person could guess, and you can revoke it from the quote at any time. The page does not expose anything beyond the quote itself. It is a public page, so it was built to be careful about what it shows and what it accepts.

### The timeline

Every response (opened, accepted, declined, preference stated, message sent) is recorded on the quote with the time. When a customer says "I never saw it", you can see whether and when they did. That is not about catching anyone out; it is about being able to answer the question calmly.

### From accepted to booked

You see accepted quotes on a board and claim one for booking. Doing so turns it into a job and carries its lines across. If you change your mind, you can release it. The point of the design is that the quote and the job stay one story.

### Next

April: what to do after the quote is sent, and keeping track of where every quote is.

### Questions people ask

**Does a customer need an account to accept a TradeYoke quote?**

No. The quote page is a plain web page that works on any phone, with no app or login.

**Can I stop a customer using a quote link?**

Yes. You can revoke the link from the quote.

Related: Quotes and estimates · Email and SMS messaging · Quoting faster on site · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Product</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-the-page-a-customer-accepts-a-quote-on-jpg/cover-the-page-a-customer-accepts-a-quote-on.jpg?v=29ov50yf" type="image/jpeg" length="161879" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-the-page-a-customer-accepts-a-quote-on-jpg/cover-the-page-a-customer-accepts-a-quote-on.jpg?v=29ov50yf" medium="image" />
    </item>
    <item>
      <title>November 2024: a ledger that cannot be quietly edited</title>
      <link>https://tradeyoke.com/blog/an-invoice-ledger-that-cannot-be-quietly-edited</link>
      <guid>https://tradeyoke.com/blog/an-invoice-ledger-that-cannot-be-quietly-edited</guid>
      <pubDate>Tue, 12 Nov 2024 08:13:00 GMT</pubDate>
      <description>November 2024 was about trust. The invoicing ledger only ever adds entries: a correction is a new line, not an edit. Here is why that makes the books easier to trust.</description>
      <content:encoded><![CDATA[Part 14 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: October 2024: why invoicing came next, and what it had to get right. Next: December 2024: part payments, receipts and knowing who owes you. See every part on the build timeline.

### Quick answer

Quick answer: TradeYoke's invoicing ledger is append-only: entries are added and never rewritten, and a correction is a new entry that reverses or adjusts the old one. That means the history of every invoice, payment and credit is always visible, and balances and ageing are worked out from the same record rather than stored separately.

### Key takeaways

The ledger only adds entries; it never edits or deletes them.A correction is a new entry, so the history stays visible.Balances and ageing are worked out from the ledger, so they cannot disagree with it.Payments that do not match exactly have three clear resolutions: over, short and unmatched.

### Why not just edit the invoice?

The obvious way to build invoices is to store them and let people edit them. It is simple and it goes wrong in a very ordinary way: someone changes an amount, the customer's statement no longer matches what they were sent, and nobody can say who changed what or when. For a small business, that is a dispute you cannot easily win.

### Append-only, by design

In November 2024 we built the invoicing core as a ledger. Every event (an invoice issued, a payment received, a credit given) is added as a new entry. Nothing already written is changed or removed. If something was wrong, you add an entry that corrects it, and the original stays where it was.

### What that buys you

A history you can read. For any customer you can see exactly what happened, in order.Balances that cannot disagree. What a customer owes, and how old the debt is, are worked out from the ledger when needed. They are not a second copy that might drift.Safe retries. Each entry has a key so that a payment notification arriving twice is recorded once.Three honest ways to deal with odd payments. When a payment is more than the invoice, less than the invoice, or cannot be matched to one, there are three defined resolutions, not a silent guess.

### Many things bill, one place records it

Another design choice: anything in TradeYoke that earns money does so through one doorway. A window cleaning visit, a gardening job or a certificate hands its amount to the invoicing module; it does not write to the ledger itself. That keeps the rules in one place. It is also why credit notes, late fees and statements, which came later, could be built on the ledger without special cases.

### The cost

An append-only design is more work to build than an editable table. We think the work is worth it when it means a customer's statement always agrees with what they were sent. Next month: part payments, receipts and the first version of "who owes me".

### Questions people ask

**Can an issued invoice be edited in TradeYoke?**

No. The ledger only adds entries. If something was wrong, a correction is recorded as a new entry, such as a credit note, and the original stays visible.

**How does TradeYoke work out what a customer owes?**

From the ledger. Balances and how overdue they are are calculated from the recorded entries, so they cannot disagree with the invoices and payments.

Related: Invoicing and payments · Who owes me · Invoice fraud and account protection · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Payments</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-an-invoice-ledger-that-cannot-be-quietly-edited-jpg/cover-an-invoice-ledger-that-cannot-be-quietly-edited.jpg?v=1z5lt0yf" type="image/jpeg" length="175909" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-an-invoice-ledger-that-cannot-be-quietly-edited-jpg/cover-an-invoice-ledger-that-cannot-be-quietly-edited.jpg?v=1z5lt0yf" medium="image" />
    </item>
    <item>
      <title>September 2024: getting an existing round in without retyping it</title>
      <link>https://tradeyoke.com/blog/getting-an-existing-round-in-import-and-duplicates</link>
      <guid>https://tradeyoke.com/blog/getting-an-existing-round-in-import-and-duplicates</guid>
      <pubDate>Tue, 10 Sep 2024 09:11:00 GMT</pubDate>
      <description>Nobody wants to retype four hundred customers. September 2024 was about import: check the file first, show what will happen, never silently merge, and flag the duplicates.</description>
      <content:encoded><![CDATA[Part 12 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: August 2024: a diary that fills itself from the round. Next: October 2024: why invoicing came next, and what it had to get right. See every part on the build timeline.

### Quick answer

Quick answer: TradeYoke can import customers from a spreadsheet (CSV): it checks the file first and shows what will happen to each row before anything is written, flags likely duplicates, and lets you merge two customers with a preview of the record it will keep. Importing the same file again changes nothing.

### Key takeaways

A trade business should not have to retype its customer list to try new software.Check first, then import: you see what will happen to each row before anything is written.Re-importing the same file changes nothing, so a mistake is not a disaster.Duplicates are flagged and merged with a preview, never silently.

### The biggest barrier is the first afternoon

By September 2024 the app could hold a round, but a round only helps if you can get yours into it. For most businesses that means a spreadsheet, a notebook or an export from something else. If getting started means retyping four hundred customers, most people do not start.

### Design rules for an import

Check before you write. Import starts with a dry run. It reads the file, shows what it will do with every row, and lists the rows with problems. Nothing is written until you say so.Be safe to repeat. Importing the same file twice must not create the same customer twice. Re-importing changes nothing.Say what went wrong. Rows that fail come back as your own file with a Problem column added, so you can fix the row and try again.Never assume consent. Marketing consent is never imported; it has to be given by the customer.

### Duplicates are the real work

A spreadsheet that has grown over years has the same customer in it three ways: "J. Smith, 12 High St", "John Smith, 12 High Street" and one with just a phone number. We made duplicate detection part of the customer list itself, grouping likely matches and letting you merge two customers. The merge shows you the record it will keep, so you can see the outcome before you commit. It is also the reason a person is one contact whatever their role.

### What it is not

Import today works from a CSV file, not directly from other software. We would rather it did one thing reliably than many things nearly. Getting your first round into TradeYoke walks through the steps, and paper to app in one afternoon shows what a first week looks like.

### What came next

By the end of September the build had customers, jobs, a diary and a way in. The one thing it could not do was send a bill. October is when that started.

### Questions people ask

**Can I import my customers into TradeYoke?**

Yes. Import a spreadsheet as a CSV file. TradeYoke checks it first and shows what will happen to each row before it writes anything.

**What happens if I import the same file twice?**

Nothing changes the second time. Re-importing the same file does not create duplicate customers.

Related: Customers and CRM · Getting your first round into TradeYoke · Paper to app in one afternoon · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Guides</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-getting-an-existing-round-in-import-and-duplicates-jpg/cover-getting-an-existing-round-in-import-and-duplicates.jpg?v=2gk9ygwn" type="image/jpeg" length="139274" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-getting-an-existing-round-in-import-and-duplicates-jpg/cover-getting-an-existing-round-in-import-and-duplicates.jpg?v=2gk9ygwn" medium="image" />
    </item>
    <item>
      <title>July 2024: a library for the paperwork, filed where you will look</title>
      <link>https://tradeyoke.com/blog/signatures-photos-and-filing-the-paperwork</link>
      <guid>https://tradeyoke.com/blog/signatures-photos-and-filing-the-paperwork</guid>
      <pubDate>Tue, 30 Jul 2024 10:10:00 GMT</pubDate>
      <description>Once customers and jobs worked, the paperwork started to pile up: photos, certificates, notes and PDFs. In July 2024 we built a document library that files things where you will look.</description>
      <content:encoded><![CDATA[Part 10 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: July 2024: customers and jobs working end to end for window cleaning. Next: August 2024: a diary that fills itself from the round. See every part on the build timeline.

### Quick answer

Quick answer: The TradeYoke document library is a folder tree you can upload to or photograph into, where each document can be filed against a job and the customer at the same time, so it shows on both. It began in July 2024, soon after customers and jobs worked end to end.

### Key takeaways

The library is a normal folder tree: create, rename, move and delete folders.A document can be attached to a job and to the customer at once, so it shows in both places.On a phone you can photograph straight into the library.Sensitive documents can be protected with a password, and anything sent to a customer is recorded.

### The paperwork problem

Doing the work is one thing; being able to prove it later is another. By the summer of 2024 customers and jobs worked end to end in TradeYoke, and almost immediately the paperwork began to pile up: a photo of a cracked sill, a PDF from a supplier, an insurance certificate, a note scanned at the kitchen table. A pile of unfiled files is only a slower notebook.

### A library, not a dumping ground

We built the document library as an ordinary folder tree, because that is what people already understand. You can create a folder, rename it, move it and delete it, and you can upload files into it. Nothing clever, on purpose. The clever part is where a document can be filed.

### Filed against the job and the customer

A document is not just in a folder; it can be attached to the record it is about. File a photo against a job and it shows on that job. Attach it to the customer at the same moment and it shows on the customer's record too. That means it appears in two places, and you find it from whichever end you start: open the job, or open the customer.

### From the phone

Most paperwork starts on site, not at a desk. So you can photograph a document or a piece of work and file it straight from the phone, without emailing it to yourself first and filing it later. Later is where paperwork goes to die.

### Keeping some things private

Not every document is for everyone in the business. A document can be protected with a password, so the sensitive ones stay behind a gate even when the folder is shared.

### Sending it

Paperwork that goes to a customer is sent through the same route as other messages, so it is recorded in their history. You can see what was sent and when, and the copy in the library is stamped as sent. That is the other half of being able to prove it.

### What came next

The library was the foundation. Over the following months it spread across the rest of the system: onto every record, then searching inside the files and keeping certificates in date.

### Next

August: how a diary fills itself, with recurring visits.

### Questions people ask

**Where does TradeYoke keep completed documents?**

In the document library, a folder tree where each document can be filed against the job and the customer, so it shows on both.

**Can I photograph a document straight into TradeYoke?**

Yes. On a phone you can capture a photo and file it into the library without emailing it to yourself first.

Related: Documents and search · Paperwork and compliance · A document library that finds a certificate in seconds · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Guides</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-signatures-photos-and-filing-the-paperwork-jpg/cover-signatures-photos-and-filing-the-paperwork.jpg?v=19naw569" type="image/jpeg" length="105487" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-signatures-photos-and-filing-the-paperwork-jpg/cover-signatures-photos-and-filing-the-paperwork.jpg?v=19naw569" medium="image" />
    </item>
    <item>
      <title>One codebase and offline-first: the early engineering decisions</title>
      <link>https://tradeyoke.com/blog/one-codebase-and-offline-first-the-early-decisions</link>
      <guid>https://tradeyoke.com/blog/one-codebase-and-offline-first-the-early-decisions</guid>
      <pubDate>Tue, 25 Jun 2024 09:08:00 GMT</pubDate>
      <description>Two decisions made in the first half of 2024 shaped everything since: one shared codebase for the web and the apps, and a phone that keeps working when the signal drops.</description>
      <content:encoded><![CDATA[Part 8 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: Why we published our terms and privacy notice from the start. Next: July 2024: customers and jobs working end to end for window cleaning. See every part on the build timeline.

### Quick answer

Quick answer: Two early engineering decisions shaped TradeYoke: build the screens once in a shared codebase that runs on the web and in the apps, and treat the phone as the source of truth while you work, so changes queue up and sync when the signal returns. The installed apps (in pilot) carry offline support, and since November 2026 the web app keeps working with no signal after one visit too.

### Key takeaways

The screens live in one shared codebase; the web app and the apps are thin shells around it.While you work, the phone holds the data and changes queue up to sync later.Platform differences (camera, GPS) go behind an interface, never into the shared screens.The Android, iPhone and Windows apps are in pilot and not yet in the app stores.

### Two decisions, made early

Most of an engineering team's important decisions are made in the first months, when they are cheap to make and expensive to reverse. By the middle of 2024 we had made two that everything since has relied on.

### Decision 1: build the screens once

A trade business uses a mix of devices: a laptop in the office, a phone in the van, perhaps a tablet. The easy way to support that is to build separate products and try to keep them in step. They never stay in step. So we decided that every screen would live in one shared codebase, and that the web app and the apps would be thin shells around it. A feature built once appears wherever that codebase runs. We wrote more about this in One app, four platforms.

### Decision 2: the phone is the source of truth while you work

A window cleaner will lose signal in a cul-de-sac, behind a hill or in a basement. An app that needs a connection to draw a screen is an app that fails at the worst moment. So the design assumption is that the device holds what it needs, changes are recorded as small repeatable operations, and they are sent when a connection returns. If two people have changed the same thing, neither change is silently thrown away. Why offline-first matters goes into the reasoning.

### What this cost

Both decisions slow you down at the start. Shared screens mean a missing piece on one platform is a gap to close, not a place to add a special case. Offline-first means thinking about conflicts before you have any. We think that was the right trade, and it is why later features, from invoices to maps, did not need rewriting for the phone.

### The honest status today

The web app is available now. The Android, iPhone and Windows apps are in pilot and not yet in the app stores; if you would like early access, email hello@tradeyoke.net. Since November 2026 the web app also keeps working with no signal after one visit.

### Questions people ask

**Does TradeYoke work offline?**

The installed apps for Android, iPhone and Windows, which are in pilot, are designed to keep your round on the device and sync when you are back in signal. Since November 2026 the web app also keeps working with no signal after one visit.

**Is TradeYoke one product or several?**

One. The screens are built once in a shared codebase, so a feature works the same wherever that code runs.

Related: The mobile app · One app, four platforms · Why offline-first matters · The platform · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Mobile</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-one-codebase-and-offline-first-the-early-decisions-jpg/cover-one-codebase-and-offline-first-the-early-decisions.jpg?v=20lmow7r" type="image/jpeg" length="172701" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-one-codebase-and-offline-first-the-early-decisions-jpg/cover-one-codebase-and-offline-first-the-early-decisions.jpg?v=20lmow7r" medium="image" />
    </item>
    <item>
      <title>Designing a job that repeats: every four weeks, for years</title>
      <link>https://tradeyoke.com/blog/designing-jobs-that-repeat</link>
      <guid>https://tradeyoke.com/blog/designing-jobs-that-repeat</guid>
      <pubDate>Tue, 14 May 2024 08:06:00 GMT</pubDate>
      <description>A window clean happens again and again. May 2024 was about designing a job that repeats: its frequency, its next-due date, and what happens when it is paused or skipped.</description>
      <content:encoded><![CDATA[Part 6 of 39 of Building TradeYoke, the story of how the platform was built, from January 2024 to today. Previous: The customer record a window cleaner actually needs. Next: Why we published our terms and privacy notice from the start. See every part on the build timeline.

### Quick answer

Quick answer: A repeating job in TradeYoke carries its own schedule (every N days, weeks or months, optionally on a weekday), a next-due date and a last-completed date, and can be paused or cancelled with a reason. Each job has a short reference such as WC-4F2A that never renames itself, even if it was created offline.

### Key takeaways

A repeating job stores its rule (every N days, weeks or months) and its next-due and last-completed dates.Pausing and cancelling take a reason, so the history makes sense later.Each job has a short derived reference, such as WC-4F2A, that never changes.

### The job is the unit of work

With the round and the customer sketched out, May 2024 was about the job. A job is one piece of work for one customer at one address. For a window cleaner that is usually the same job coming back round: this address, this price, every four weeks.

### One shape for every kind of job

We settled on one shape for a job, and the same shape is used across the trades that came later. It has a customer, a site address, a status, and either a single date or a repeating schedule. The repeating schedule is expressed the way people say it: every N days, weeks or months, optionally on a particular weekday. The job also carries when it is next due and when it was last completed.

### Why store the rule and the dates

You can work out the next clean from the last one and the rule, so it might seem enough to store only the rule. We store both, for a practical reason. When a clean is skipped for rain, the next one should be "four weeks from when it was actually done", not four weeks from when it was supposed to be. Keeping the last-completed date separate from the rule means the schedule follows what really happened.

### Pause, cancel, skip

Real rounds are full of exceptions. A customer is away for a month. Another has stopped using you. A third has asked you to skip this time. So a job can be paused or cancelled, and both ask for a reason, which is kept. A single visit can be skipped with a reason without ending the job. These reasons are not paperwork for its own sake. A year later, "paused: away until September" is the difference between a customer you meant to come back to and one you forgot.

### A reference that does not rename itself

Every job gets a short reference such as WC-4F2A, made from its type and a short code. We derive it from the job's own identity rather than from a counter held in one place, which matters for the offline case: a phone with no signal can create a job without clashing with one created in the office, and the reference does not change when the two meet.

### What we left for later

Payment on a visit, an invoice at the end of the month, a quote that turns into a job: all of that attaches to the job. We deliberately did the job first. The next articles, from July, are about getting real customers and jobs working end to end.

### Questions people ask

**How do repeating jobs work in TradeYoke?**

A job carries a repeat rule (every N days, weeks or months, optionally on a weekday), a next-due date and a last-completed date. The diary projects future visits from that rule.

**What happens if I pause or cancel a repeating job?**

Both ask for a reason, which is kept on the job. A single visit can also be skipped with a reason without ending the job.

Related: Jobs and the job wizard · Scheduling and rounds · Rain days and carried-over work · Pricing · The build timeline

### Try it on your own week

Thirty days of Essentials free, no card. Bring your customers and see it against a real week.

[Start your free trial](https://app.tradeyoke.com/signup)

]]></content:encoded>
      <dc:creator>AssemblySoft DevOps</dc:creator>
      <category>Engineering</category>
      <category>Window cleaning</category>
      <category>Building TradeYoke</category>
      <enclosure url="https://tradeyoke.com/media/media-seed-cover-designing-jobs-that-repeat-jpg/cover-designing-jobs-that-repeat.jpg?v=3g4os8pj" type="image/jpeg" length="196785" />
      <media:content url="https://tradeyoke.com/media/media-seed-cover-designing-jobs-that-repeat-jpg/cover-designing-jobs-that-repeat.jpg?v=3g4os8pj" medium="image" />
    </item>
  </channel>
</rss>