Where everything lives, what each form does, and what happens after you send one. Written against the site and app that are live today — nothing here is a promise about how they will work later.
Status: SynOdos HOS is approved by MTO/CVOR for use in lieu of paper logs. The app is still being extended, so anything marked (planned) is not built yet. There is no price list, no checkout, and no paid plan to buy on this site.
1. What is live right now
| Where | What it is | Needs an account? |
|---|---|---|
synodos.app | The marketing site: what SynOdos builds, the HOS product story, and the request forms. | No |
synodos.app/hos | The HOS product page — sample day, compliance model, the feature list. | No |
synodos.app/signup | Request early access to the logbook. | No |
synodos.app/request-website | Request a website for your operation, with a written scope reply. | No |
synodos.app/docs | This documentation: getting started, the user guide, the tutorial. | No |
hos.synodos.app | The logbook app itself — the 24-hour grid, dashboard, and 15-Day Record. | Yes |
Two forms, two different things: early access is a waitlist for the logbook, and a website request is a quote for a site built for your operation. Sending one does not sign you up for the other.
2. Requesting early access to the logbook
Who it is for: a driver who wants the logbook on their own tablet, or a fleet manager who wants it for a group of drivers.
What it does: puts your details on the early access list with the fleet size and role you give, so the first invite is sized for how you actually work.
Open synodos.app/signup, or press Sign up for early access in the site header —
it is shortened to Early access on a narrow phone screen. The home page carries the
same form near the bottom: its Sign up for early access button (hero) and Join the
waitlist link (roadmap) scroll straight to it.
2.1 The fields
| Field | Required | What it is used for |
|---|---|---|
| Name | Yes | Who to address the reply to. |
| Work email | Yes | Where the reply and the invite go. Check it before sending — everything happens over email. |
| Company | No | Only if you are asking on behalf of an operation. |
| Phone | No | Only if you would rather be called than emailed. |
| You are | No (defaults to Owner / operator) | Owner / operator, Fleet manager, Driver, or Something else. Sets how many seats the invite is scoped for. |
| Fleet size | No | 1–5, 6–20, 21–50, or More than 50 vehicles. Leave it blank if you do not know yet. |
| Consent checkbox | Yes | "You can email me about SynOdos HOS early access. No newsletter, no reselling my details." It is the permission to reply. |
Press Request early access. The button reads Sending… while it posts.
2.2 What you see afterwards
The card is replaced with "You're on the list", restating the email address you
entered, and pointing at [email protected] for questions in the meantime.
The form does not create a logbook account. Your account is created inside the app, on the sign-in screen — see section 5 and the user guide.
2.3 If the form refuses
| Message | Cause |
|---|---|
| Tell us who you are. | The Name field is empty when you press the button. |
| We need an email to reach you. | The Work email field is empty. |
| That does not look like an email address. | Something without an @ and a domain, for example me@. |
| We need your permission to reply. | The consent checkbox is unticked. |
| Too many attempts. Try again in a few minutes. | More than five submissions from one address within ten minutes. |
| We could not save that just now. Email [email protected] and we will add you. | The list could not be written at that moment. The email address in the message is the fallback. |
| We could not reach the server. Check your connection, or email [email protected]. | The browser could not complete the request at all. |
3. Requesting a website for your operation
Who it is for: a fleet operator who needs a site that shows the service, brings in school or contract enquiries, or replaces a page nobody has updated in years.
What it does: starts a scoped conversation. It is not an order, and nothing is charged for asking.
Open synodos.app/request-website — the header item Web development points there
from every page, as does Request a website in the home page's services section.
3.1 The fields
| Field | Required | What it is used for |
|---|---|---|
| Name | Yes | Who to address the scope to. |
| Work email | Yes | Where the written scope is sent. |
| Company | No | The operation the site is for. |
| Phone | No | Optional call-back number. |
| Current website | No | The address of an existing site, if there is one. Leave it blank when starting from scratch. |
| What do you need? | Yes, at least a sentence | Who the site should speak to, what it should do, anything you already know you want on it. |
| Timeline | No | As soon as possible, Within 1–3 months, Later this year, or Just exploring. |
| Consent checkbox | Yes | "SynOdos can email me about this request. No newsletter, no reselling my details." |
Press Send request; it reads Sending… while it posts. The line under the button is the whole commercial model today: "Free to ask. We quote per project after we understand the scope."
3.2 What you see afterwards
The card is replaced with "Request received", restating your email address, and saying what happens next: a reply with a couple of questions and a written plan.
3.3 If the form refuses
| Message | Cause |
|---|---|
| Tell us who you are. | Name is empty. |
| We need an email to reply to. | Work email is empty. |
| That does not look like an email address. | The address is malformed. |
| A sentence or two about what you need helps us reply properly. | What do you need? is empty or shorter than ten characters. |
| We need your permission to reply. | The consent checkbox is unticked. |
| Too many attempts. Try again in a few minutes. | More than five submissions from one address within ten minutes. |
| Our form could not save that. Email [email protected] and we will pick it up. | The request could not be recorded. Email it instead. |
4. Reading the documentation
synodos.app/docs is the front door for all three documents:
- Getting started — this page: the routes, the two forms, and what to expect back.
- User guide — every screen of the logbook, by task.
- Tutorial — a numbered first session that ends with a saved day, an exported PDF, and a working backup.
Each page carries its own table of contents in the left margin (above the text on a
phone), and every section is a normal anchor link, so #signing-in-style URLs can be
bookmarked or shared. The sub-navigation under the site header moves between the three
documents from any of them.
5. Getting into the logbook
The app at hos.synodos.app is gated: nothing but the sign-in screen is reachable
without an account.
| Path | How it works |
|---|---|
| Continue with Google | One tap. Recommended if you have a Google account. |
| Email + password | Press New here? Create an account, enter an address and a password of at least six characters, then confirm from the email if one is asked for. |
Both buttons are disabled while you are offline, with the line "You're offline. Reconnect to sign in — logs already on this device are safe." Reconnect, then sign in.
The log book itself is local-first: it is written to the device before anything touches the network, and signing in on a second device merges the two copies instead of overwriting either. After signing in once, the app keeps working offline for seven days; the account panel counts that window down.
Everything past this point — the daily grid, day details, presets, the dashboard, the 15-Day Record, PDF export, preferences, and the encrypted Drive backup — is covered screen by screen in the user guide.
6. What is not built yet
Approval is not one of the gaps: MTO/CVOR approval for use in lieu of paper logs is in place. What is missing is product, and it is listed here rather than left implied:
- Fleet administration is not built. No manager console, no driver roster, no assignments — each driver's log book is their own.
- No plans, prices, or checkout. Early access is a waitlist and website work is quoted per project by email.
- No self-serve account management for the site. There is no customer portal and no site login; the only account in the product is the logbook account.
- One shared login across site and app is planned, not shipped. They are separate today.
- No automated receipt emails. A person replies from
[email protected].
7. Where to get help
- Email:
[email protected] - In the app: System Settings → Version history lists what changed in the build you are running.
Next: the user guide for reference, or the tutorial if you would rather be walked through a first session.