Overview

BizJournal is a relationship journal and sales workspace. It keeps the people you deal with, every conversation you have with them, the bids you put in front of them, and the projects that follow from the bids you win — all in one place, all linked to each other.

Almost everything in the application sits on one chain of records, so it is worth seeing the whole chain before you focus on any single screen:

Contact → Event (a call, a visit, an email …) → Bid → Project → Delivery. Territories decide who can see which links in that chain; to-dos and reminders hang off it and surface on your dashboard and calendar.

How the pieces fit together

This is the same map you will find in Configuration › Misc. Blue arrows are the normal flow of work; the orange arrows are the outbound send that happens when you log an SMS or Email event.

The BizJournal processing map.

Reading it from the top: a territory decides whose records you see. A contact belongs to one or more territories and to an organization (which is really an employment history — people move). An associate is a member of your team; if their email address matches a login account, the work assigned to them becomes “my tasks” for that person.

An event is one interaction with one or more contacts. Its event type can carry a checklist that is copied onto the event as to-dos. A bid holds line items and its own to-dos; when it is awarded you can start a project from it, which gives you a task pipeline, a full history of every status change, and a delivery log per bid item.

The workspace

You work in a single screen. The dark rail on the left lists the modules you are allowed to open; clicking one opens it as a tab across the top, so you can keep several modules open at once and switch between them. Each module then has its own row of sub-tabs.

The workspace: module rail on the left, module tabs across the top, and the module's own sub-tabs below them.

Who sees what

Two separate things decide what you see:

• Permissions decide which modules, tabs and buttons appear at all. They are set per role by an administrator.
• Territories decide whose records you see inside those screens. A contact is filed under one or more territories; you see the contacts in the territories your login is assigned to, plus anything assigned directly to you.

If a screen looks emptier than a colleague's, it is almost always one of those two.

Where to go next

If you are new, read 1. Getting Started, then the chapter for the module you spend most of your day in. If you are looking up one specific thing, use the search box at the top of this manual, or jump to 10. Reference for the code and status tables and 11. Quick Answers for the short questions.

1. Getting Started

1.1 Signing in

Enter your username and password and press Sign In. Remember me keeps you signed in on that browser.

The sign-in page.

Three things can happen after a correct password:

• You land on the Dashboard — the normal case.
• You are asked for a verification code. This happens if your account has MFA switched on. A six-digit code is emailed to you (and texted, if SMS is enabled for your account and for the system). Type it in and press Verify; Resend issues a fresh one if it never arrived or has expired.
• You are sent straight to Reset Password. This happens when an administrator has flagged your account for a password reset.

If you have forgotten your password, use Forgot password? on the sign-in page. You enter your email address, receive a one-time password, verify it, and then choose a new password.

1.2 The layout

The parts of the BizJournal screen.

From the top:

• Module rail (left) — one entry per module you are allowed to open. The arrow at the top of the rail collapses it to icons when you need the width.
• Top bar — the name of whatever you are looking at, a search box (see chapter 7), and ?, which opens this manual. Press Esc to close it again.
• Module tabs — every module you open becomes a tab. Drag them to reorder, click × to close.
• Sub-tabs — the tabs belonging to the open module (for example Bidding has Calendar, Bids and Bidding Tasks). If there are more than fit, the ‹ › arrows at the right scroll them.
• User card (bottom left) — click it for My Profile and Log Out.

1.3 Lists, Refresh and Excel

Nearly every list in BizJournal works the same way:

• Search box — filters the rows as you type.
• Refresh — re-runs the list. What you see is a snapshot from when the page loaded, so Refresh is how you pick up someone else's changes.
• ↓ Excel — downloads exactly what your filters are currently showing, as a CSV file that opens in Excel.
• Paging — long lists are paged; the count and the page numbers sit along the bottom (1–15 of 200).

1.4 Permissions

Your role decides what appears. A module missing from the rail, a tab missing from a module, or a button missing from a screen is nearly always a permission and not a fault. Ask your administrator; the grants are made under Configuration › Permissions.

Permissions only ever hide buttons. They never blank out data you are already allowed to see — if a screen is empty, that is a territory or a filter, not a permission.

1.5 Your profile and password

Open My Profile from the user card at the bottom of the rail. You can change your own name, email and phone here.

My Profile.

Change Password asks for your current password and a new one twice. The new password must be at least 8 characters and contain at least one uppercase letter, one number and one special character; the strength bar and the checklist update as you type.

Change Password.

1.6 Archive mode

If an amber Archive Mode banner is across the top of the screen, the system has been put into read-only mode by an administrator. You can look at everything, but creating, editing and deleting are all refused with the message “The requested process is currently locked in archive mode.” It is turned off again under Configuration › Misc.

2. Dashboard

The Dashboard is where you start the day. It has six tabs: Calendar, Overview, Journal, Bidding, Project and My Tasks. Every tab is read-only apart from the Calendar, which is where reminders are created. Each has a Refresh button, because the figures are a snapshot from when the tab was opened.

2.1 Overview tab

The whole business on one screen: active contacts, today's events, open bids and what they are worth, and how many to-dos are open and overdue.

Dashboard — Overview.

Underneath the counters are five lists: Today's Events, To-dos Due Soon (open to-dos due in the next week, plus anything already overdue — overdue dates are shown in red), Recent Activity (the ten most recently created events), Follow-ups (contacts whose next-contact date has arrived or passed) and Stale Contacts (active contacts you have not had an event with for 60 days or more, and who have no follow-up booked).

2.2 Journal tab

The same idea, narrowed to conversations: events coming up in the next 7 days, events this month, open to-dos and overdue to-dos, with the upcoming events and the to-dos due soon listed below.

Dashboard — Journal.

2.3 Bidding tab

Open bids and their total value, bids awarded and their value, bids lost, and the win rate. Below that, bids grouped by status, then the most recent open bids and the most recently awarded ones.

Dashboard — Bidding.

2.4 Project tab

Active projects, completed projects, open tasks and overdue tasks, then a list of the active projects with their task progress (for example 1 / 4 means one of four tasks has reached the last column of the pipeline), and the items still waiting to be delivered.

Dashboard — Project.

2.5 My Tasks tab

Everything currently on your plate, from all three sources, in one list sorted by due date. The Source badge tells you where each one comes from — EVENT, BID or PROJECT — and Reference shows the record it belongs to. Overdue dates are red.

Dashboard — My Tasks.

Clicking a row opens a read-only popup with the detail. To actually tick a to-do off, go to the tab that owns it: Journal › Event Tasks, Bidding › Bidding Tasks or Project › Project.

“Mine” means work assigned to the associate whose email address matches your login. If your tasks are not appearing here, check that your associate record in Directory › Associates carries the same email address as your user account.

2.6 Calendar tab

A month or week view of everything that is dated: events, to-dos that are due (from events, bids and projects), contact follow-ups, and reminders. Saturdays and Sundays are shaded. Use ‹ Today › to move around, Month / Week to change the view.

Dashboard — Calendar, month view.

How to read the chips on a calendar day.

Clicking a chip opens the record behind it — an event, a to-do, a follow-up or a reminder.

Reminders

+ Reminder adds a dated note to the calendar. A reminder has a name, a type (Holiday, Meeting, Deadline, Personal, Other — the list is configurable), a date, an optional time and duration, and a recurrence.

Recurrence is worked out from the date you give it, which acts as the anchor:

Months that are too short are handled for you: a reminder anchored on the 31st falls on the 30th in April and on the 28th or 29th in February. A recurring reminder shows a ★ on the calendar. Editing or deleting one changes the whole series — there is no per-occurrence exception.

The same calendar, with the same behaviour, also appears inside Journal, Bidding and Project. The only difference is which chips are emphasised.

3. Directory

The Directory is the people side of BizJournal: Contacts (the people you deal with), Organizations (where they work) and Associates (your own team). Everything else in the application points back to a contact, so this is usually the first record you create.

3.1 Contacts tab

Directory — Contacts.

One row per person. The columns worth knowing:

• No — the contact number, assigned automatically (C2026-12).
• Territories — which territories the contact is filed under. This is what decides who else can see them.
• Employer — their current organization.
• Next Contact — the follow-up date, if one is booked. It turns red once it has passed.

View opens Contact 360 (see 3.4). The search box matches on name, email, phone and organization.

3.2 Adding and editing a contact

+ Add Contact opens the form. Only First Name is required; everything else can be filled in later.

Add Contact.

The form is in sections:

• Photo — Upload Photo takes a JPEG or PNG up to 2048 px.
• Basic info — name, birthday, and the Active switch. Setting a contact inactive keeps their history but takes them out of the pick-lists you see when creating events and bids.
• Contact — email and two phone numbers. The email and phone are what the SMS and Email event channels send to, so they are worth getting right.
• Organization — start typing to find an existing organization, or type a new name to create one on the fly. Title is their job title there. This creates the employment link; a contact can accumulate several over time.
• Address — street address, plus latitude and longitude. 📍 Geocode fills the coordinates in from the address; 🗺 Map It opens the address in Google Maps.
• Territories — tick the territories this contact belongs to.

Delete removes the contact along with their territory and employment links. A contact who already has journal events or bids against them cannot be deleted — make them inactive instead.

3.3 Follow-ups (Next Contact)

A follow-up is a promise to get back to somebody. Set a Next Contact date and a short note (“send updated quote”) on the contact, and it will chase you:

• as an FU chip on every calendar, on that date;
• in the Follow-ups card on the Dashboard Overview, once the date is within a week or has passed;
• as a red date in the Next Contact column of the contacts list once it is overdue;
• in the Overdue Follow-ups report.

Clicking the Next Contact cell in the grid, or the FU chip on a calendar, opens a small dialog where you can change the date and the note, or clear them once the follow-up is done.

3.4 Contact 360

View on a contact row opens Contact 360 — a read-only summary of the whole relationship in one panel: the contact's details and territories, the date you last had an event with them, their follow-up, their employment history, their last 20 events, their last 20 bids, and every to-do still open against them (from both events and bids).

Use it before you pick up the phone. Nothing on it can be edited — close it and use the Edit form, or open the record itself, to make changes.

3.5 Organizations tab

Directory — Organizations.

Companies, with a type (Business, Customer, Vendor, Partner, Other), contact details, an address and a count of how many of your contacts work there. + Add Organization opens the same shape of form as a contact, with the same Geocode and Map It buttons and a free-text Notes box.

Add Organization.

You rarely need to come here first — typing a new organization name into a contact's form creates the organization for you, and you can fill in its details later.

3.6 Associates tab

Associates are the people on your side: whoever can be assigned an event, a to-do or a project task.

Directory — Associates.

The important column is Login. An associate is joined to a login account by email address: if the associate's email exactly matches the email on a user account, the grid shows Login and everything assigned to that associate turns up in that person's My Tasks. If the addresses do not match, the assignment still works, but the person will never see it as “mine”.

Edit Associate — the dialog confirms whether a login account is linked to this email address.

Territories on an associate says which territories they cover. Untick Active to retire someone: their history stays, but they drop out of the assignee pick-lists.

4. Journal

The Journal is the record of every interaction: calls, visits, demos, emails, texts, notes. It has three tabs — Calendar, Timeline and Event Tasks.

4.1 Timeline tab

The Timeline is the feed of events, newest first, grouped under a heading per day.

Journal — Timeline.

Four filters sit across the top: a search box (matching contact name, email, phone or organization), an event-type dropdown, and a from and to date. The feed opens on the last month and the next two months; Clear empties the filters, Refresh re-runs them. The feed shows the most recent 200 matching events.

Each card carries the channel icon, the title, the status, the time, the event type, the contacts, and small badges: ☑ 2/5 for to-dos done out of total, 📎 3 for attachments, and SENT or ERROR on events that were sent as an SMS or an email. Click anywhere on a card to open it.

4.2 Adding an event

+ Add Event opens the event form.

Add Event.

Working down the form:

• Title is required.
• Description is the body of the message when the channel is SMS or Email — so write it as if the contact will read it, because on those two channels they will.
• Event Type (Sales Call, Site Visit, Product Demo, Follow-up, Check-in Meeting, Support Visit …) and Channel (Call, Email, In-Person, Note, SMS, Video Call). The type may bring a checklist with it; the channel decides what actually happens on save.
• Schedule — a planned begin and end, and an actual begin and end. Planned is what you intended; actual is what happened. If you leave the actual times alone they simply default to the planned ones, so there is no extra work when the meeting runs to plan. The end must not be before the begin.
• Location — a location name (“Client Site”) and an address, with the same Geocode and Map It buttons as elsewhere. Some event types and channels ask for a location, others do not.
• Contacts — type to search, and pick at least one. An event with no contact cannot be saved.
• Primary associate — required. This is the person who owns the event.
• To-dos — the checklist. Choosing an event type pre-loads its default to-dos; you can add, rename or remove them, give each one an assignee and a due date. Anything you do not assign goes to the primary associate. Assigning a to-do to somebody else automatically adds them to the event as a participant.
• Links — related URLs (Website, Email, Social Media, Other).
• Attachments — + Photo and + File.

Saving gives the event a number of the form E2026-23 and a status of Scheduled.

4.3 Working an event

Clicking a card opens the event in a read-only view with everything on it: the schedule, the location, the contacts, the checklist, the links and the attachments. From here you can tick to-dos off directly, and the buttons along the bottom are:

• Complete — marks the event Completed.
• Cancel Event — marks it Canceled. Canceled events stay in the record and show with a line through them on the calendar.
• Reopen — on an event that is already completed or canceled, puts it back to Scheduled.
• 📅 Add to Calendar — downloads an .ics file you can drop into Outlook or any other calendar.
• Edit and Delete.

The life of an event.

4.4 SMS and Email events

Two of the six channels actually send something when you save the event:

• Email — the title becomes the subject and the description becomes the body. It goes to every contact on the event who has an email address.
• SMS — the description is texted to every contact with a usable phone number. This only works if SMS has been switched on for the whole system in Configuration › Misc; otherwise the event is still saved but is marked as an error.

The result is recorded on the event as a SENT or ERROR badge, and the error text is kept so you can see what went wrong (no recipient had an email address, SMS is disabled, the mail server refused it, and so on). The send happens once, when the event is first created — editing an event afterwards does not re-send it.

4.5 Event Tasks tab

Every to-do from every event, in one working grid.

Journal — Event Tasks.

Two sets of filters: My Tasks / All, and Open / Overdue / Done / All. Overdue due-dates are red.

What you can do on a row:

• Tick the checkbox to complete a to-do. A small dialog asks for the completion date and lets you confirm who did it.
• Response — type the outcome straight into the cell (“left voicemail”, “sent the revised quote”) and it saves as you leave the field.
• Expenses — the money button opens the expense list for that to-do. Add an expense with a type (Flights, Rent-Car, Hotel, Food, Entertainment, Supplies, Travel, Other), a description, an amount and a date, and attach receipts to it. Expenses roll up to the event's total cost and feed the Expenses by Type report.
• Detail — a running log of progress notes against the to-do, each with its own date and its own attachments. This is where you keep the story of a to-do that takes more than one attempt.

4.6 Calendar tab

The Journal's calendar, with events to the front. It behaves exactly as described in 2.6 Calendar tab — same chips, same reminders, same recurrence.

Journal — Calendar.

5. Bidding

A bid is a priced proposal to a contact. Bidding has three tabs — Calendar, Bids and Bidding Tasks — and it is where the pipeline lives.

5.1 Bids — the list

Bidding — Bids, list view.

Number, title, contact, organization, amount, the bid date and the status. The All Statuses dropdown and the search box narrow the list; View opens the bid. Bid numbers are issued per year (BID2026-10), and the amount is the sum of the bid's line items.

5.2 Adding and editing a bid

+ Add Bid opens the form.

Edit Bid — line items total automatically.

• Title is required. Primary contact is chosen by typing to search; picking the contact fills in their Organization for you.
• Bid Date is the date the bid is due / dated.
• Line items — item, memo, quantity and price. The amount per line and the Total are calculated as you type, and the total becomes the bid's value everywhere else in the system. If the bid is later awarded, these same line items become the things you deliver in the Project module — so put real quantities in.
• To-dos — the same checklist mechanism as an event: name, assignee, due date.
• Status can be changed here directly.

A bid with a project already started from it cannot be deleted.

5.3 The Pipeline view

The Pipeline toggle at the top left swaps the list for a board: one column per status, every bid as a card, with the count and the total value at the head of each column and a win-rate strip across the top.

Move a bid with the ‹ and › arrows on its card. Moving one to Lost asks for a reason (Price, Timing, Competitor, No Decision, Scope, Other) and the date it closed. Moving it to Awarded stamps the award date.

Bid statuses and what each move does.

The win rate is Awarded ÷ (Awarded + Lost), counting only bids closed in the last 90 days. Closed and Canceled bids are deliberately left out of it — they were never won or lost.

5.4 Bidding Tasks tab

Bidding — Bidding Tasks.

Identical in behaviour to Journal › Event Tasks (see 4.5): the same My Tasks / All and Open / Overdue / Done / All filters, the same checkbox to complete, the same Expenses and Detail buttons. The only differences are that the second column is the Bid rather than the event, and that there is no Response column.

5.5 Calendar tab

The bidding view of the calendar, with bid due dates and bid to-dos (BID and BT chips) to the front.

Bidding — Calendar.

6. Project

A project is what happens after you win. It is always born from an awarded bid, it inherits that bid's line items as the things to be delivered, and it gives you a task board, a full audit trail of every task move, and a delivery log. Five tabs: Calendar, Project, Task, Delivery and History.

6.1 Starting a project

Project — the project list. Each card shows the project number, the bid it came from, the customer, and task progress.

+ Start Project lists the bids that are Awarded and do not have a project yet. Pick one, and BizJournal:

• creates the project, numbered PRJ2026-7, named after the bid, with today as the start date and a status of Start;
• copies the currently active task statuses in as the project's pipeline columns.

One bid can only ever produce one project.

6.2 The project detail

Clicking a project card opens it.

A project: bid items at the top, the task pipeline underneath.

Status at the top right is yours to set — Start, In-Process, Completed, Canceled. It is not derived from the tasks; you decide when a project is done. Delete Project removes the project (the bid it came from is untouched).

Bid items are read straight from the bid: item, quantity, price, amount, and the contract total. They cannot be edited here — the bid is the contract. Change the bid if the scope changes.

Task pipeline is a board, one column per status:

• + Add Task — name, description, assignee, due date, and files. New tasks land in the first column.
• The ‹ and › buttons on a card move it one column left or right. Every move is written to the task's timeline.
• Manage Pipeline — choose which statuses this project's board uses, and in what order. You cannot remove a column that still has tasks sitting in it; move them out first.

The default task pipeline. The columns come from Configuration.

The progress figure on a project card (2/7 done) counts the tasks that have reached the last column of the pipeline.

6.3 Task tab

Every project task you can see, in one grid — tasks assigned to you, plus tasks in your territories.

Project — Task.

Filter by All Tasks / My Tasks and by status. Overdue dates are red. This tab is read-only: View opens the task with its files and its full timeline, showing every move it has been through, when, and who made it.

A task's timeline — every status change is kept.

To change a task, open its project on the Project tab.

6.4 Delivery tab

Delivery answers one question: of the things we sold, how much have we actually delivered?

Project — Delivery. Active projects only, with a delivered-vs-ordered bar.

Only Start and In-Process projects appear. Each card shows a progress bar and a count (2/8 delivered). Click a project to see its bid items:

The bid items of a project, each with quantity ordered, delivered and remaining.

Then click an item to open its delivery history and record against it.

Delivery history for one item.

+ Add Delivery records a date, a quantity and an optional note. Records can be edited or deleted afterwards. The delivered and remaining figures update immediately, all the way back up to the project card and the Dashboard.

Use ‹ Back to items and ‹ Back to projects to climb back out.

6.5 History tab

Every project in your territory, whatever its status, with progress, start and end dates.

Project — History.

This is the archive view: it is where completed and canceled projects go on being visible after they have dropped off the working tabs. View opens the full read-only detail of any project.

6.6 Calendar tab

The project view of the calendar. Project starts and ends appear as PROJ chips and project tasks as PT chips, alongside the usual events, to-dos, follow-ups and reminders.

Project — Calendar.

7. Search & the Activity page

7.1 The search box

The magnifying glass at the top right of every screen searches across the whole system. Type at least two characters and results appear as you type, tagged by what they are:

Contacts are limited to your territories. Press Esc to close the box.

7.2 The Activity page

Choosing a contact or an organization from the search results opens the Activity page — a full-screen view of everything that has ever happened with them.

The Activity page for a contact.

At the top is the record itself: their photo (or a street view of their address if there is no photo), the organization and job title, phone, email and address. Underneath, Activity History is a single timeline of that person's EV events, BID bids and PROJ projects, newest first, each with its number, date, status and value.

The small arrow at the left of a row expands it in place. View opens the full detail in a popup, and Print in that popup gives you a printable copy. Back returns you to whatever you were doing.

For an organization, the same page rolls up the activity of everybody who works there.

8. Reports

Five tabs — Directory, Journal, Bidding, Project and Audit — and 22 reports plus the audit log.

8.1 How every report works

A report tab: the report list on the left, the result on the right.

Every report tab is laid out the same way. The reports for that area are listed down the left; click one and its title, its description and its result appear on the right.

• ✔ Run re-runs the report with the filters as they now stand.
• ↓ Excel downloads the result as a CSV file.
• FROM and TO appear only on the reports that cover a period; the rest are a snapshot of right now. Where they do appear they default to the first of the current month up to today.

Each report is granted separately, so you may see fewer entries in the list than a colleague. If you have no grants at all on a tab, it will say No reports granted.

8.2 Directory reports

8.3 Journal reports

Report — Journal. Reports that cover a period get FROM and TO boxes.

8.4 Bidding reports

Report — Bidding.

8.5 Project reports

Report — Project.

8.6 Audit

The audit log is the record of every change made in the system.

Report — Audit.

Filter by area and by date range, and search across the method, the class and the statement itself. Each line gives the time, the area, the class, the method, the user and their IP address; Detail opens the full entry. This is the screen to open when the question is “who changed that, and when?”

9. Configuration

Configuration is the administrator's module. Nine tabs: Pages, Roles, Permissions, Territories, Users, Event Types, Options, Project Task Status and Misc.

If you are setting the system up from scratch, work in that order: territories and roles first, then users, then the pick-lists.

9.1 How permissions work

A user gets roles; a role is granted pages, tabs and actions.

A user has one or more roles. A role is granted pages (the modules in the rail), tabs (within a module) and actions (the buttons within a tab). A button only appears when the page, the tab and the action are all granted.

Two consequences worth knowing:

• A role with no page grants at all sees nothing.
• Permissions hide buttons; they never hide data. A read-only user still sees the whole grid — they just have no Add, Edit or Delete.

9.2 Pages tab

Configuration — Pages.

The tree of what exists: every page, its tabs, and each tab's actions. Add Tab registers a new tab under a page; Add Action registers a new button under a tab (its name, its label, and the method it calls). Clicking a tab or an action opens it for editing, where you can also change its sort order or delete it.

This tab defines what can be granted. It does not grant anything — that happens on the Permissions tab.

9.3 Roles tab

Configuration — Roles.

The list of roles, with a description, a sort order and an Active / Inactive status. + Add Role creates one; Edit Role changes or deletes it.

9.4 Permissions tab

Configuration — Permissions.

Pick a role on the left, and its grants appear on the right, one collapsible block per page. Toggle a page On or Off, expand it to reach its tabs, and expand a tab to reach its actions. ☑ Select All and ☐ Clear All do the whole role at once.

Nothing is written until you press Review & Save, which shows you exactly what is about to change — every grant added and every grant removed — before you confirm it.

A user has to sign out and back in for changed permissions to take effect.

9.5 Territories tab

Configuration — Territories.

Territories are how contacts are divided up — General, Business, Friends, Family, or however you want to slice your world. Each has a code, a name, a type, an optional address and contact details, a sort order and a status.

Territories are the backbone of visibility. A contact is filed under one or more of them; a user is assigned one or more of them (on the Users tab); and a user sees the contacts — and therefore the events, bids and projects — that fall in their territories.

9.6 Users tab

Configuration — Users.

Pick a user on the left to edit them, or press + Add User to register a new one. A user record carries:

• Name, email, phone, username and an Active / Inactive status. Inactive users cannot sign in.
• MFA — when on, the user must enter an emailed six-digit code at every sign-in.
• SMS — when on, that code is also texted to them.
• Photo — JPG or PNG up to 5 MB. It becomes their avatar at the bottom of the rail.
• Roles — one or more. This is what gives them their permissions.
• Territories — one or more. This is what gives them their data.

As on the Permissions tab, changes are staged and applied with Review & Save.

Reset Password sends the user a one-time password by email and flags the account, so that at their next sign-in they are taken straight to the reset screen. Delete User removes the login.

Do not forget the associate. A login account and an associate record are two different things. To have someone's assigned work appear in My Tasks, they need both — a user account here, and an associate in Directory › Associates carrying the same email address.

9.7 Event Types tab

Configuration — Event Types and Channels.

Two lists side by side.

Event types are the kinds of interaction you log: Sales Call, Site Visit, Product Demo, Follow-up, Check-in Meeting, Support Visit. Each has a code, a name, an optional description, a default channel, a sort order, an Active flag, and a Has location flag that decides whether the event form asks for an address. Each also carries a set of default to-dos — the checklist that is copied onto every new event of that type. Setting these up well is the single highest-leverage thing on this tab: it is how a process gets followed without anyone having to remember it.

Channels are how the interaction happened: Call, Email, In-Person, Note, SMS, Video Call. Two of them are special — Email and SMS actually send the message when the event is saved (see 4.4). The used counts on both lists tell you what is actually in play, which is useful before you delete anything.

9.8 Options tab

Configuration — Options.

Every pick-list in BizJournal, grouped by type. Choose a group on the left and its entries appear on the right; + Add Option and Edit maintain them. The groups you are most likely to touch:

These codes are wired into the application's logic, not just its labels. Renaming an entry is safe; changing or deleting a code that is already in use is not.

9.9 Project Task Status tab

Configuration — Project Task Status.

The statuses a project task can be in, and the order they run in. The order matters twice over: it is the left-to-right order of the columns on every project's task board, and the last status in the list is what counts as done for the progress figures on project cards, the Dashboard and the reports.

Use the ↑ and ↓ buttons to reorder. Each row shows how many tasks are currently sitting in that status, which tells you what you are about to disturb. New projects pick up whatever statuses are active at the moment they are started; projects already running keep their own pipeline, which is changed per project with Manage Pipeline.

9.10 Misc tab

Configuration — Misc, with the processing map and the system switches.

Two system switches, each visible only to administrators granted it:

• Run Mode — Normal is standard operation. Archived locks the whole application to read-only: the amber banner appears for everybody and every create, edit and delete is refused. Use it while migrating or closing a period. The switch itself still works in archive mode — otherwise you could never get out again.
• SMS — the master switch for all outbound text messaging. With it disabled, no SMS is sent by anything, and SMS events are saved with an error.

Below the switches is the Processing Map (the same diagram as in the Overview of this manual), and under that a read-only reference of every option code in the system, grouped by type. It is the fastest way to look up what a code means. To change any of them, use the Options tab.

10. Reference

10.1 Record numbering

Numbers are issued automatically and restart each year.

10.2 Statuses

Event

Bid

Project

Project tasks do not use a fixed list — their statuses are the pipeline columns, set in Configuration › Project Task Status (by default To Do, In Progress, Review, Done).

10.3 Channels and event types

Event types (Sales Call, Site Visit, Product Demo, Follow-up, Check-in Meeting, Support Visit) are yours to define, and each can carry its own default checklist. Both lists are maintained in Configuration › Event Types.

10.4 Who sees what

Two rules, applied together.

• Territory. You see a contact if the contact is filed in one of your territories — and with them, their events, their bids and the projects that came from those bids. Your territories are set on your user record.
• Assignment. You also see anything assigned to you, wherever it is. “You” means the associate whose email address matches your login's email address.

So a to-do assigned to you on a contact outside your territories still reaches you; and a colleague's to-do on a contact inside your territories is still visible to you. If someone's work is not showing up under My Tasks, the first thing to check is that the email address on their associate record matches the email address on their user account, exactly.

10.5 Exports

Every ↓ Excel button downloads a CSV file of exactly what is on screen, filters and all. It opens directly in Excel. Reports export the same way, from the report result.

On an event, 📅 Add to Calendar is different: it downloads an .ics file for that single event, which you can import into Outlook or any other calendar application.

11. Quick Answers