Current version: v0.1.0-alpha.178
Conduit is in alpha. Earlier updates have been numbered retrospectively from the documented project history; these numbers do not indicate separate historical deployments or production readiness.
October 19, 2026
Training is now in the sidebar, and under More on a phone: fourteen short step-by-step guides with pictures, one task per page, for creating PR, CR, SR and ER requests, approving or returning them, the required fields, what to do when a project, vendor or cost code is not listed, and adding Conduit to an iPhone or Android home screen. The User guide link at the bottom of the page opens the same guides.
October 19, 2026
Notification emails are now sent as formatted messages with a Conduit header, the key facts, the amounts and one button to open the request, with a plain-text copy for every mail program. No email is sent yet.
October 19, 2026
Notification subjects now say what the message is about: the action, the request, the project number and the amount, for example Approval needed: REQ-2026-0152 · 24-022 · $75,000.00 · Over budget. No email is sent yet.
October 19, 2026
Conduit now uses Industra's final Conduit logo, in white on black or black on white. The earlier logo choices were removed. The home-screen icon uses the final logo too; a phone that already added Conduit keeps the old icon until it is added again.
October 19, 2026
A new-vendor request now reaches Procurement when the request is submitted: Procurement gets a New vendor setup notice in the outbox, and the request shows New vendor setup pending in All requisitions. The requester's screens say where the vendor details go.
October 19, 2026
A purchase request now has a Special instructions field, printed on the purchase order with one bullet per line. Procurement can change it with Correct PO details. The Special instructions box always appears on the purchase order, and internal notes and approval reasons no longer print on it.
October 18, 2026
The purchase order now prints the Industra address in white inside the black header, below the logo, as on Industra's PO form. When terms are attached, every PO page reads Page X of Y counting the terms pages, and the attached-terms line no longer shows the internal terms type or the uploaded file name.
October 18, 2026
Four notices the client turned off on October 14 are paused: Financial approval complete, Update the buyout log, Procurement review complete and PO package email. Procurement downloads the PO package and sends it to the vendor. The submission confirmation and the Procurement attention notice are now sent once email is switched on.
October 18, 2026
A unit price, quantity or budget cleared in the purchase order correction dialog is now refused instead of being saved as zero.
October 18, 2026
A project can now finish setup without a Project director or District manager. Those roles are marked optional in Configuration > Projects and are skipped in approvals when not assigned.
October 18, 2026
Requests on a project with no Project director or District manager, or whose Project director or District manager account is deactivated, now go to the next assigned approver, and the skipped stage is recorded in the request's audit history. The approval policy and request summary text now say so.
October 16, 2026
More automatic checks now cover the email sending added in alpha.166, so a later change cannot quietly break it. Nothing changes for users.
October 16, 2026
Conduit can now send its notifications by email once an administrator turns it on. The outbox shows whether each message is held, sent, delivered or failed, and messages created before email was turned on are never sent. In the first phase, email goes only to approved recipient domains; other messages wait in the outbox, marked as held.
October 16, 2026
Addresses, links and emails no longer show the old preview path. Pages, images and styles now open from the plain site address, and the user guide, sandbox checklist and update history link back to Conduit without it.
October 15, 2026
Conduit now opens at the plain site address. Old links, bookmarks and emails still work and take you to the same page or request. New setup and notification links use the plain address. If you installed Conduit as an app on your device, reinstall it once so it uses the new address.
October 14, 2026
Pending Approvals, its count, its summary figures, its filter choices and the navigation badge now include only the requests waiting on your decision. Requests where you are a later approver or the requester stay in All requisitions and open as before. Procurement and administrators keep the full pending queue with the approver and requester filters.
October 14, 2026
The Preview PO and Print buttons now show for Procurement accounts only, on the request, the distribution view, the PO follow-up and the PO document. Administrators who are not in Procurement, approvers and requesters no longer see them. Everyone keeps the PO files they can already read and download.
October 14, 2026
A generated purchase order file is now named like Industra files it: “2600007 - Vendor name”, with “ - CO 1” for a change order and “ - PO only” for the PO-only copy. The download links in the PO package dialog show that same name. Files already generated keep the names they have. A corrected reissue of the same revision keeps its earlier version-based name until Industra says how those should be told apart.
October 14, 2026
The purchase order document you preview and print in the app now has the same layout as the PDF: a black header with the PO number, Vendor, Ship to / Job site and Order details columns, a Required submittals band of short tags (holdback appears as “Holdback 10%”), the item table with cost codes, a separate subtotal, tax lines and highlighted total, and Special instructions. Fields that were not selected are left out. Printing keeps the same order, repeats the table header on each page and keeps the totals together.
October 14, 2026
The purchase order PDF now follows the layout Industra supplied: a black header with the PO number and the company address line, Vendor, Ship to / Job site and Order details columns, a Required submittals band of short tags (holdback appears as “Holdback 10%”), an item table with cost codes and dollar amounts, a separate subtotal, tax lines and highlighted total, Special instructions, an attached-terms line and a footer reading “Page N of M”. Every value still comes from the issued version, and fields that were not selected are left out. PDFs already issued are not changed. The in-app PO document view follows in a later update.
October 14, 2026
The Cancel PO card now appears for an issued purchase order even when it has receipts, change orders, distribution or a vendor acknowledgment. Before cancelling it shows the issued subtotal, the received subtotal (“Not verified” when no amount has been verified), how many change requests pending approval will be cancelled with it, and what is kept. After cancelling, the PO summary and PO documents view show the same figures, and a cancelled change request reads “PO cancelled”. A PO recorded in Spectrum or marked Procurement-complete is still refused.
October 14, 2026
The service now lets Procurement cancel an issued purchase order at any time, including one with receipts, a change order, a distribution, a PO-only document or a vendor acknowledgment. Everything already recorded is kept, and the cancellation records the verified received subtotal. Pending change requests against the PO are cancelled with it. A PO recorded in Spectrum or marked Procurement-complete is still refused, pending the client’s answer. The screens follow in a later update.
October 14, 2026
When Procurement returns a corrected request for approval, the route now restarts from the person who submitted it and the corrected amount. A project director, district manager or executive keeps their own approval credit, and a request submitted on behalf of someone goes to that person first. Earlier decisions stay in the history, and the old approval notices are cancelled. Requests submitted for an executive or the COO are still not supported.
October 14, 2026
Procurement can now choose a project director or district manager in the Submitting for list and submit the request from the form. The approval preview shows that person first, then the roles above them, with no submission credit and no Procurement step. Submitting for an executive or the COO is still not supported and shows the same message as before.
October 14, 2026
Procurement can now submit a request on behalf of a project director or district manager. That person approves first, then the request continues to the roles above them: a project director at $50,000 or less approves alone, and above that the district manager and executive follow. No submission credit is given and Procurement is never an approver. Submitting for an executive or the COO is still not supported. The request form itself still blocks these choices until its own update.
October 14, 2026
A project director or district manager can now submit a request at or below the project manager limit from the request form. The approval preview says their submission counts as approval and no further approval is needed, and the request progress reads “Project director: submission counts as approval.” or the district manager equivalent. Above the limit the route is unchanged, and the project manager and executive wording is the same as before.
October 14, 2026
The service now approves a request at once when a project director or district manager submits it at or below the project manager limit. They receive credit for their role, the history says their submission counts as approval, and the requester receives the usual approved notice. Above the limit the route is unchanged. The request form still shows the earlier message until the next update.
October 13, 2026
On a completed emergency purchase, the approver now sees Acknowledge instead of Reject and a reason box, because the money is already spent. Procurement sees the Cancel request card on an emergency purchase that has no issued PO, and a cancelled emergency purchase says its PO number is kept and never reused. Purchase and change requests are unchanged.
October 13, 2026
The service now refuses to reject a completed emergency purchase, because the money is already spent. The approver acknowledges it instead, and the history says so. Procurement can cancel an emergency request that has no issued PO. The emergency PO number, history and figures stay on the record and the number is never reused. An approved emergency purchase still cannot be cancelled. The request form does not offer these yet. No notice is sent.
October 13, 2026
Procurement and administrators now see a Submitting for list on purchase, change and emergency request forms. The approval path shows that person first, then the approvers above them. A request submitted this way says who it was submitted for and by whom. Procurement cannot reassign the represented person's own approval and can cancel the request instead. Requesters see no change. No notice is sent beyond the usual approval notice.
October 13, 2026
The service now lets Procurement submit a purchase, change or emergency request for a named project coordinator or project manager. That person approves first, then the usual approvers above them, and nobody receives credit for the submission. Without a named person the request is still refused as before. Requests for a project director, district manager or executive, and for deactivated or unfinished accounts, are refused with the draft kept. The request form does not offer this yet. No notice is sent beyond the usual approval notice.
October 13, 2026
Project directors, district managers and executives can now submit from the request form. The route preview lists only the approvers above the author, and an executive sees that their own submission counts as approval. A director or district manager whose request needs no further approval is still held back until that case is confirmed. A request credited to a role other than project manager names that role in request progress.
October 13, 2026
The service now routes a request only to approvers above the person who submitted it. A project director or district manager above the project manager limit routes to the roles above them, and an executive’s own request is approved at once with an audit record. The request form still refuses these authors until the next update, so nothing changes on screen yet.
October 13, 2026
In People, a deactivated person now shows a Reactivate button after a confirmation. Their history is unchanged and no sign-in session is restored. Someone who was active when deactivated signs in again with their existing password. Anyone who never finished setup shows “Setup link revoked” and needs a new setup link. No notice is sent.
October 9, 2026
On an approved purchase request, Procurement now sees a Cancel PO card that asks for a reason and a confirmation, or the first reason the PO cannot be cancelled. A refusal from the service lists every reason. A cancelled PO shows who cancelled it, when and why, has no Correct or Distribution buttons, reads Cancelled in the PO list, is left out of the not-acknowledged filter, labels its earlier files “PO cancelled”, and is no longer offered when a change request chooses a PO. Open POs look the same as before. A PO cancellation leaves the project manager’s buyout reminder queued; it is not cancelled with the PO’s other unsent notices.
October 9, 2026
The shared service now lets Procurement cancel an approved purchase order that has no activity outside Conduit: no change order or revision, no receipt, no distribution, no PO-only document, no vendor acknowledgment, no Spectrum entry and no completed procurement. The PO number, its history and every file are kept, the number is never reused, and a cancelled PO refuses every later receipt, follow-up, Spectrum entry, PDF, distribution, completion, correction and change request. Any other PO is refused with the reason. Nothing is sent. The screen for this arrives in a later update.
October 9, 2026
Procurement now sees a Cancel request card on a purchase or change request that is waiting for approval or was returned and has no purchase order yet. It asks for a reason and a confirmation. A cancelled request shows who cancelled it, when and why at the top, its approval route shows no step waiting for a decision, its list line reads Cancelled, and the Approval value total leaves it out. Cancelled change requests no longer count toward near-limit warnings.
October 9, 2026
Procurement can now cancel a purchase or change request that is still waiting for approval or was returned and has no purchase order issued, giving a reason. The request keeps its REQ number and its history, its waiting approval notices are cancelled, and nothing new is sent. Sourcing and emergency requests, drafts, approved requests and requests with a PO under correction are refused with a clear message. The Cancel request button arrives in the next update.
October 9, 2026
On a request you started and have never submitted, the request view now has a Delete draft button that asks you to confirm. The draft and its attachments are removed, and its REQ number is not used again. Submitted and returned requests are kept, and emergency requests cannot be deleted. Only the person who started the draft can delete it, including when they are an administrator or in Procurement.
October 9, 2026
In Configuration > People an administrator can delete a person who was invited or whose setup link was revoked, and who never set up their account. Their old setup link stops working. An account that is named on a project, on a request, in the history or has signed in cannot be deleted; deactivate it instead. Your own account cannot be deleted.
October 9, 2026
In Configuration > People an administrator can reset another active person’s password. Their current password stops working, they are signed out, and the administrator gets a new single-use setup link to pass on. No password is ever shown. Until the person sets a new password they appear as Setup pending, new approvals cannot be routed to them and their notices wait for review; an approval already assigned to them stays assigned. Your own account and the last active administrator cannot be reset.
October 9, 2026
In Configuration > People an administrator can deactivate another person’s account. The person is signed out at once and can no longer sign in, and their name stays on every request and approval. The last active administrator, your own account and anyone who still holds a pending approval cannot be deactivated. A deactivated account cannot be brought back with a setup link.
October 9, 2026
The approver who is due to decide now sees a short summary first: the key facts, the budget picture with the variance amount and percentage, any over-budget explanation, the holdback, Request progress and the Reject and Approve controls. “View full requisition” opens the complete package, and “Back to summary” returns. Everyone else sees the same full request as before.
October 8, 2026
When a request is returned, the top of the request now shows the reason, who returned it, their role and the time, together with the approval route: earlier steps approved, the returning step marked, and later steps not reached. The details are still in the Audit history.
October 8, 2026
On a fully approved request the last step in Request progress is now the same green as the other approved steps, instead of amber. The approval message now reads “Requisition approved. Procurement will review and process the requisition before PO distribution.”
October 8, 2026
When a sourcing, emergency, urgent or large (over $50,000) request is submitted, one notice for Procurement is now prepared in the notification outbox, and the requester gets a submission confirmation. Both show as “Prepared, not sent”: nothing is emailed until email is switched on.
October 8, 2026
Approval, reminder and approved notices now say what kind of request it is, who asked, who approves and what it is for. A returned notice also says who returned it and the approval total. Lines with no value are left out. Workflows you already saved keep their wording; add the new description and returned-by fields to them by hand, or reset to the defaults.
October 8, 2026
Opening the notification outbox from a request now lists only that request's notices in a table with date, type, recipient, subject and status, newest first. The outbox in Configuration lists every notice in the same table. The raw JSON text is gone; the message content is still available under each subject. An empty outbox says so in plain words.
October 8, 2026
After a change order, the new version starts unacknowledged, as before. The purchase order now says so: “Not acknowledged for version 2 yet. Version 1 was acknowledged by … on ….” The follow-up delivery date you saved stays after a change order or a correction.
October 8, 2026
The footer no longer shows the Project rules link, which led to internal developer notes. The User guide and update history links remain.
October 8, 2026
Administrators and Procurement now have Sign out in the sidebar, after Configuration, and in the phone More menu, like every other account. It no longer exists only on the Configuration page. If you have unsaved work, Conduit still asks before signing you out.
October 8, 2026
The dialog for adding a cost code is now titled “Add cost codes” instead of showing an internal name. When you are signed in, the dashboard note now says that saved drafts are kept in Conduit and can be resumed from any device, because they are saved to the server. The note that drafts resume on this browser now appears only when the workspace is stored in the browser alone.
October 8, 2026
Recorded times now read in Vancouver local time in the format “Oct 6, 2026, 4:04 p.m.”, whatever time zone your device uses. This covers the Audit history on a request, notification times, the vendor acknowledgment on a purchase order, the Procurement panel and the import history. Before this update several of them showed raw UTC text such as “2026-10-06T23:04:09.159Z”, and a few followed the time zone of the device. The stored values are unchanged. The technical Before and after details keep their raw values.
October 8, 2026
A change request that reduces a purchase order, for example a credit line with a negative unit price, was refused until Procurement verified how much had been received, and nothing on screen let Procurement record that. The purchase order window now has a “Received amount” section that shows the verified received subtotal (excluding taxes) with who verified it and when, or “Not verified” when nobody has. Procurement and administrators see a “Verify received amount” button there. It opens a window where they enter the verified received subtotal from receiving or accounting records, or choose “Nothing received yet (verified zero)” after confirming that nothing was received, and add a note saying what they checked. The note is required every time, including for a verified zero, and it is visible to everyone who can open the purchase order. The window shows the current value, never fills in a zero on its own, and refuses a missing note or a missing, negative or non-numeric amount beside the field. If another person verified the same purchase order in the meantime, the window reloads, shows their value and asks you to review it before trying again; nothing is overwritten.
In a change request, as soon as a line’s unit price goes negative, a notice appears under that line saying the credit reduces the purchase order and that Procurement must verify the received amount before it can be submitted (or, when a verified amount exists, that the revised purchase order would fall below it). You can still continue to Review; Submit is refused as before and now also says what to do: save the request as a draft and ask Procurement to verify the received amount on that purchase order. The change summary’s “Revised total” and “Change” now update as you type. The checks themselves (rules FIN-013 and FIN-014) are unchanged on the server and in the browser, an unknown balance is never treated as zero, and no email or notification is created.
October 8, 2026
When Procurement corrects an approved purchase order, the correction window now shows the budget, the “Approval total (PST and HST included)” and whether the request is under or over budget, below the line items, and updates them while you change a quantity, price, budget or tax. The approval total includes PST and HST and excludes GST, and it is compared with the sum of the line budgets, so a correction can be over budget because of tax or because of another line. The Over-budget explanation field now sits right below that summary. It is marked required, with “Required while the request is over budget.”, only while the request is over budget, and a saved explanation stays visible when a correction brings the request back within budget. Saving an over-budget correction without an explanation now marks that field and moves to it, with “Add the over-budget explanation. The approval total (PST and HST included) is over the budget. Rule FIN-002.”, instead of a message asking you to revise the request. The correction reason is still separate and is not accepted as the over-budget explanation, because approvers read the explanation and the correction reason is kept in the change history. The budget rule itself has not changed.
October 8, 2026
When someone opens a setup link that was replaced by a newer one, has expired, was revoked or was already used, Conduit now says “This setup link no longer works” and “Your password was not saved. Ask your administrator for a new setup link.”, with a Go to sign in button. Before this update the page moved straight to sign-in as if the password had been saved, and signing in then failed. The account stays in setup until the person uses the current link. In Configuration > People, an administrator now sees when the current setup link for a person in setup was issued and when it expires, “Setup link expired” once it has expired, and a note when an earlier link was replaced and no longer works. Choosing New setup link for someone in setup first asks “Create a new setup link? The link you already sent will stop working.”; Cancel keeps the link already sent. Clicking Set password or Sign in twice now sends only one request, without an error message, and pressing Enter in the setup or sign-in fields submits the form.
October 8, 2026
An emergency PO number now appears in Purchase orders as soon as the emergency is recorded, so Procurement can find it before the purchase details are completed. The row is marked “Details pending”, shows the vendor, project, the approximate spend and the date the emergency was recorded, and opens the request. It has no PO document, acknowledgment, follow-up or Spectrum controls, because the PO is not ready to send. Once the completed request is approved, the same number is listed as an issued PO. The emergency screens no longer call the number provisional: it is issued when you record the emergency and does not change.
October 7, 2026
An administrator with Configuration open now receives the changes another administrator saves, and the imports they apply, automatically and without reloading, as every other screen already does. Before this update an open Configuration screen waited for its own Save even when nothing on it had been changed, because a few lists with nothing chosen yet (a project’s province and its approvers, and the terms document category) were treated as edited. On Import data, the Import history table now shows another administrator’s new run in place, on the page you are reading. Anything you have actually changed and not yet saved still holds the update until you save it, and saving then still tells you that a newer configuration was saved by another administrator, so nothing you chose or typed is replaced. When an update arrives, Configuration keeps your place: the field you were in keeps the cursor, the page stays at the same scroll position, and an expanded project stays open, showing the change.
October 7, 2026
The pop-ups that changed are request details, purchase order details, sign-in, Add person, Add record, Add province and Add purchase type, “Use the latest approved PO?”, the correction, reassignment, PO preview, distribution, PO package and received-amount views, document extraction and its review, the setup link, the outbox and “Request unavailable”. Each now takes its name from its own heading for assistive technology, and when it closes, keyboard focus returns to the control that opened it when that control is still on the screen, even if the screen refreshed in between. The close button, Cancel and Back now ask “Close without saving these edits?” when something was typed, the same as Escape and clicking outside already did; choosing Cancel keeps the typed values, and a pop-up with no edits still closes at once. The “View business rules” link in a status message asks the same question before leaving an edited pop-up. When the shared service refuses an action while a pop-up is open (including a refused sign-in), its message now also appears inside the pop-up, just below the heading, and the view scrolls to it, instead of only in the banner behind the pop-up. On phones the short status message now shows at the top of the screen across its width, clear of the fields and buttons being used, and no longer wraps into a narrow column; on desktop it is unchanged. Nothing about requests, approvals, purchase orders or email changes.
October 6, 2026
A request that asked for a new vendor now has a “Vendor setup” panel on its details. While the purchase details are still being completed it says the request is recorded and nothing has been handed off. Once a detailed purchase, change or emergency request is submitted with the vendor’s legal name, address, contact, phone, email and business or tax number, the panel lists those details with when and by whom they were recorded and “Not yet handed off”. Procurement and administrators then use “Record manual handoff” with a short note (the channel or reference used) to record that the details were passed to Accounting by hand; the panel shows who recorded it, when and the note, and the audit history carries the same line. Conduit sends nothing to Accounting, nothing is queued, and the purchase order never waits for the vendor setup. Changed vendor details on a later submission or correction start a new “Not yet handed off” version while the earlier record stays in the history.
October 6, 2026
Configuration > Import data now ends with an Import history table in the shared workspace. Each applied import is listed newest first with when it ran, the record type, how it was imported, who applied it, the added, updated and skipped counts and its result (“Applied” or “Applied with N rows skipped”). “Details” opens a row that repeats the counts in a sentence, names the file, lists the skipped rows by reason and says how many were left out by the import mode; the skipped-rows file itself is offered only when the import is applied and is not kept. The table shows 25 runs per page with Previous and Next, and after an import the Result screen’s “View import history” returns to the landing with the new run first. Procurement accounts that are not administrators now open Configuration to a read-only Import data page with this history instead of the administration notice; starting an import still needs administrator access. A refused import is not listed, because nothing was changed. After Save changes, keyboard focus now stays on the Save changes button. The “Not confirmed” result now says “Check the import history before trying again.”
October 6, 2026
When a file has a few rows with problems, the import Review now has an Outcome choice. “Fix the file first (nothing is applied)” stays the default, and Apply stays off. If you choose “Apply the valid rows and skip the N rows with problems”, Apply turns on and its label ends with how many rows are skipped. Only the rows without problems are saved; the skipped rows are counted by reason, and the result reads “Applied with N rows skipped” with a “Download the skipped rows (CSV)” link that lists each skipped row with its reason. The file contents of skipped rows never leave your browser. Some problems still stop the whole import and cannot be skipped: a problem with the whole file, “Stop the import” for projects not in Conduit, and any problem found by the shared service. When two rows share one key, both are now listed as problems, each naming the other row, so neither silently replaces the other. If a re-check changes the counts after you chose to skip, the choice goes back to “Fix the file first”. The Setup required checklist now uses the same labels as the project fields.
October 6, 2026
A cost-code file that names projects not yet in Conduit no longer has to wait for a projects import. On the upload step, “Projects not in Conduit” offers “Create them as Setup required” (the default), “Skip their rows” or “Stop the import”. Review shows a New projects count and lists the first ten with the names from the file, and Apply creates them in the same step as the cost codes. A created project has only its number and name: no province, approvers or limits are filled in, it is inactive, and requests cannot be started on it until an administrator completes its setup. Configuration > Projects now has filters for All, Setup required, Active and Inactive projects; a Setup required project shows a checklist (province, project manager, project director, district manager, executive and status Active) and what is still needed. Saving a complete project clears Setup required, and only then does it appear in the request form. A cost-code import can now also use the project names from the file, and Review says which name is used when a file gives one project two names. With “Update existing only” no project is ever created.
October 6, 2026
The upload step of Configuration > Import data now offers all three ways to import: “Add new and update existing” (still the default), “Add new only” and “Update existing only”. Rows the chosen way leaves out are counted under Warnings as skipped, for example “3 rows skipped: they match an existing vendor (mode: Add new only)”, and are never written. With “Update existing only”, cost-code rows for projects not in Conduit are skipped rather than listed as problems. Rows whose values already match Conduit are counted as unchanged and are not sent, so importing the same file again shows “Apply: nothing to change” with the note that everything is already in Conduit. When a projects file names a project differently from Conduit, Review lists those projects under “Name differs” and lets you keep the names in Conduit or use the names from the file. A cost-code file never changes project names; its differing names are listed for information only. The Apply button and the result screen state how many rows were skipped. Records absent from a file are still never deleted, and the counts always add up to the rows of the file.
October 6, 2026
Configuration > Import data now opens with “Start an import” and walks through four steps: choose what to import (projects, cost codes or vendors), upload the file, check the matched columns, then review what will change before applying. The upload step names the key used to find existing records and shows the first five rows; nothing is sent yet. Matched columns are shown as done, and only a required field without a column, or two columns that could fill one field, asks for a choice. Review shows how many records will be added, updated or stay unchanged, and how many rows have problems, grouped by reason with their row numbers and a download of those rows. The counts come from the same checks that save the import. If saved records change while you review, Conduit checks again on its own and asks you to look again when the result changed; nothing is ever applied without your click. Apply states exactly what it will do, and the result screen confirms what was saved. Cancel asks before discarding a chosen file. The screens work with a keyboard and on a phone. Only “Add new and update existing” is available for now.
October 6, 2026
In shared records, “Apply validated import” now saves projects, vendors and cost codes in that same step. There is no separate Save changes step for an import any more, and nothing is left waiting to be saved. Before Apply is available, the shared service checks the file with the same rules it uses to save it. After it saves, the import panel shows the time and how many records were added, updated and unchanged. If someone else saved records just before, nothing is changed and “Check again” checks the file against the newer records. If the connection drops, Conduit tries once more and, if it still cannot confirm the save, says so and reloads the shared records before Apply is offered again. A save is never counted twice. Unsaved configuration changes must be saved before an import is applied. Browser-only review mode is unchanged.
October 6, 2026
In the sandbox, reloading the demo workspace from Configuration now prepares the same approval reminders as starting the service with demo data, so the Demo workspace panel shows the same outbox entries either way. Reminders stay in the outbox and are never sent from a demo workspace. Records, sign-in and email behavior are otherwise unchanged.
October 6, 2026
The shared service now keeps an idle connection open longer than the web proxy in front of it does, so the proxy no longer reuses a connection the service has just closed. This prevents rare failed requests, most noticeable on large saves such as configuration changes and imports. When a form message is shown again after the project cost codes load, the page no longer scrolls to it if you have already moved to another field. Records, sign-in, email behavior and the outbox are unchanged.
October 6, 2026
When a form message takes you to a field and the project cost codes finish loading a moment later, the message, its highlight and the cursor now stay on that field instead of disappearing. If you have already moved to another field, the cursor stays where you are. When a PO change would bring a PO below its recorded received amount, the form now opens the first line that reduces the amount, rather than always the first line. Records, sign-in, email behavior and the outbox are unchanged.
October 6, 2026
More request form messages now take you back to the first step and place the cursor on the field that needs attention, with the message shown beside it. This covers the sourcing need-by date, need and budget; the reason for a PO change; the emergency vendor, reason and approximate spend; and choosing an assigned project. When the PO behind a change request has changed, the message points to the Use latest approved PO button. When a change would bring a PO below its recorded received amount, the form opens the line items at the first price. These messages also name their business rule where one exists. For an emergency request, a saved vendor that is no longer in the vendor list now stays visible in the vendor list as a saved value, so you can see what to replace. Records, sign-in, email behavior and the outbox are unchanged.
October 6, 2026
On a new request that has not been saved yet, opening the form or choosing the request type no longer counts as a change. The note at the top of the form says it has unsaved changes once you change something, and returns to Draft ready if you change it back. Leaving the form still saves your changes first, and leaving an untouched form still creates no draft. On Review, the sourcing need-by date, need and budget messages now say what is needed before submitting rather than before continuing, as does the tax choice message. The tax choice and received-balance messages only point to Configuration > Business rules for people who can open Configuration. Records, sign-in, email behavior and the outbox are unchanged.
October 6, 2026
A few request form messages are now more accurate. After a draft has been saved, the note at the top of the form says it has unsaved changes whenever you change it again, for example after adding a line or changing the project, until you save. For a PO change, if no PO is chosen yet, the form now asks you to select the approved PO you want to change instead of asking for a vendor. On Review, messages about the quote, the vendor or the new-vendor request now say what is needed before submitting rather than before continuing. The PO change quote rule only points to Configuration > Business rules for people who can open Configuration. The Choose file button now shows the usual focus outline when it is selected with the keyboard or by a form message. Records, sign-in, email behavior and the outbox are unchanged.
October 6, 2026
Before you sign in, the top of the page now says Sign in, or Account setup when you open a setup link, instead of the page you last used. When a session ends, the message that it has expired now appears once, on the sign-in page, instead of twice. In Configuration > Approval policy, the note about senior approval stages no longer mentions a $50,000 example; it now says every remaining stage is required in order, even when the limits are equal. Records, sign-in, email behavior and the outbox are unchanged.
October 6, 2026
In shared records, cost codes now have their own storage. A full cost-code list (about 17,000 lines) no longer travels with every page load or configuration save. The request form loads the codes for the selected project when needed. Configuration > Cost codes shows 50 codes at a time, with Previous, Next and a project number filter once there are more than 50; smaller lists look as before. A cost-code import is checked against the saved codes before Apply is available, and Apply saves the codes directly, without a separate Save changes. Columns that are not mapped keep their saved values, and no saved code is removed by an import. Budgets on cost codes are shown only to administrators, Procurement, Pre-construction and people assigned to that project; others see the code names they need to fill in a request. Configuration changes are now recorded as what changed, which keeps the history small.
Current version: v0.1.0-alpha.104
Conduit is in alpha. Earlier updates have been numbered retrospectively from the documented project history; these numbers do not indicate separate historical deployments or production readiness.
October 5, 2026
Changes saved by other people now appear automatically, within about 30 seconds while Conduit is open, and as soon as you return to its tab. You no longer need a Refresh button. Updates wait while you are filling in a request, have a request or dialog open, are typing in a field or have unsaved configuration changes, so your work is never replaced. If another administrator saves a newer configuration while you have unsaved changes, Conduit says so and lets you keep your changes or load the newer version. Configuration now shows a short status line with Save changes (renamed from Save shared configuration), Notification outbox and Sign out, in place of the Shared workspace panel and the View as selector. If your session expires, Conduit stops checking and asks you to sign in. Email and Spectrum behavior are unchanged.
October 5, 2026
Conduit now keeps a short private record of what happened when key actions succeed or fail, such as signing in, saving configuration, importing a CSV file, uploading a file or submitting a request. Support can use it to find out why something did not work without asking you to repeat it. The record holds only the kind of action, the result and counts. It never holds passwords, file or CSV contents, names, email addresses or amounts. It stays inside Conduit, is kept for at most 30 days, and nothing is sent anywhere. Screens, records, sign-in and email behavior are unchanged.
October 5, 2026
Opening the Conduit web address without a page path now goes straight to Conduit sign-in. Before, it showed an internal technical review page. Nothing else changes: records, sign-in, email behavior and the outbox stay the same.
October 5, 2026
A full cost-code export from the accounting system, with about 17,000 lines across 160 projects, can now be imported in shared records. Previously the preview took a long time, and saving the shared configuration was refused because the request was too large. The check now finishes in well under a second, and a shared configuration of this size saves and reloads with every record and value unchanged. Other requests keep their existing size limit. When a file names projects that are not configured yet, one message now gives the number of affected rows and lists the missing project numbers, instead of one message per row. Other errors and warnings show the first 50 with a count of the rest, and the preview lists the first 50 records. Nothing is applied while any error remains. Values, amounts and status text are saved as supplied; as before, spaces at the start or end of a value are removed.
October 5, 2026
The hosted app now opens on a Conduit sign-in page. No special link is needed, and it never shows sample or browser-only records. The sign-in page no longer offers a browser-only workspace or explains shared and browser records. It says your session has expired only when a session you were using has ended, and it offers Retry when Conduit cannot be reached. Signing out returns to the sign-in page. Records kept by an earlier browser-only trial stay untouched on that device; they are neither imported nor erased. The footer shows the Conduit version and no longer links the review answers, and Business rules no longer mentions saved browser test balances in shared records. A new shared workspace no longer fills in a $50,000 Executive limit or the payment terms Net 30, Net 60 and Due on receipt; an administrator enters the agreed values. Projects and people can be set up before approval limits are agreed. Until limits are set, a request is kept as a draft with a message asking an administrator to set them in Configuration > Approval policy. Until payment terms are set, the request form says to add them in Configuration > Payment terms. The supplied deliverables, holdback, province tax and purchase type settings are unchanged. Administrators can now add users in Configuration > People without stopping Conduit: enter the name and email, choose Administrator, Procurement or Pre-construction access, and select Add user. Conduit shows a one-time setup link to copy and send to the person; it expires after 72 hours, works once, and is not emailed or shown again. The person opens the link, chooses their own password, and signs in. People shows Setup pending until then, with New setup link and Revoke link. Procurement accounts still cannot originate project purchases. Email behavior is unchanged, and email stays held in the outbox.
October 4, 2026
In shared records, some requests are stopped because something on the first step still needs attention: the quote answer, the quote file (including the supplier quote a PO change needs), the vendor, the new-vendor setup request or the holdback percentage. The form now goes back to the first step, even when the request is stopped on Line items or Review. It then moves to the item that needs attention and repeats the message beside it, as it already did for the project and cost codes. For the quote file, that item is the file choice. For the new-vendor request, it is the button that records the request. For a PO change with no vendor, it is the PO choice, because the vendor comes from that PO. Nothing is sent and everything typed is kept. When a project is inactive, only people who can open Configuration are pointed to Configuration > Projects; everyone else is asked to choose an active project or ask an administrator to reactivate it. On Review, in shared and browser-only modes, a missing over-budget reason now says it is needed “before submitting”. Browser-only mode is otherwise unchanged, email behavior is unchanged, and email stays held in the outbox.
October 4, 2026
In shared records, when the “PM: update buyout log” workflow, or any workflow that goes only to the project manager when a request is fully approved, is changed to reach other recipients, it now sends its saved message to all of its selected recipients after each later full approval, including the project manager when still selected, even for a request that already received a buyout reminder from it. The buyout reminder already prepared for that request is kept unchanged and is not prepared again. Each message prepared by this version records whether it is the buyout reminder, and later workflow changes do not change that. Messages recorded by an earlier version are not fully classified: apart from held messages, they are checked once, by the workflows saved when this version first checks them. A workflow deleted or changed before upgrading can therefore still cause a repeated or missing buyout reminder for those requests, and an earlier-version message can still reach its original recipients after its request has moved on. A message held for review after a restore is never reclassified and stays unsent. A held message already recorded as the buyout reminder blocks any new buyout reminder for its request. A held buyout reminder made by the first alpha.96 build blocks a new reminder from that workflow while it stays PM-only. Other held messages, including earlier-version messages not recorded as the buyout reminder, no longer block the buyout reminder for a later approval. The “PM: update buyout log” workflow editor states the same limits.
October 4, 2026
In shared records, when a configuration change made outside the workflow editor replaces the configured notification workflows with the built-in notices, an unsent workflow message whose request has since moved beyond the event that triggered it, for example a “fully approved” message for a request that a correction sent back for approval, is now cancelled before it is sent. A message whose request has not moved is still sent once. A project manager buyout reminder already prepared by a workflow before that change still counts as the one buyout reminder for the request, so the built-in reminder does not add a second. Each workflow message now records when it is prepared whether it is the buyout reminder, so later changes to a workflow’s recipients, trigger or name never change whether its earlier messages count as that reminder: an unsent message prepared for someone else is still cancelled once the request moves on, and a message prepared for someone else never counts as the buyout reminder. One limit remains: messages recorded by an earlier version are classified once, by the workflows saved when this version first checks them, so a workflow deleted or changed before upgrading can cause a repeated, missing or outdated reminder for those requests. The “PM: update buyout log” workflow editor now says the reminder is sent at most once per request, after the PO is created, and states the same limit for messages recorded by an earlier version. Since alpha.96, an unsent built-in buyout reminder is also no longer cancelled by a correction that sends the request back for approval, and the built-in reminder is skipped when a workflow buyout reminder already exists for the request.
October 4, 2026
In shared records with configured notification workflows, the default “Requester: fully approved” and “PM: update buyout log” messages now say that financial approval is complete, that Procurement review and Spectrum entry are still pending and that the PO has not been sent to the vendor. The buyout message also says Conduit does not maintain the buyout log. The project manager’s buyout reminder is prepared once per request: a Procurement correction that sends the request back for approval no longer prepares a second one, and it no longer cancels the first. Workflows saved before this update keep their own wording. In the Notifications activity list and the outbox view, the private download link in a PO email now shows as hidden; the vendor’s email still carries the working link. Screens are otherwise unchanged, and email stays held in the outbox.
October 4, 2026
In shared records, if you keep typing while a draft is still being saved, the draft now stays marked “Unsaved shared draft. Save now.” instead of showing as saved, and your newer changes are saved when you leave the form. Opening a saved draft and leaving it without changes no longer saves it again, so a draft whose project has since been made inactive no longer stops you from returning to My requisitions or going Back. A draft you did change is still saved when you leave, and an inactive project still refuses that save. Screens, browser-only mode and email behavior are unchanged, and email stays held in the outbox.
October 4, 2026
Operator-only update for the hosted service. The setup step that creates accounts, the sandbox demo load and reset, and the restore, review and release steps of a recovery now refuse to run while the service is using the same records, even when they are started from a separate container, and they change nothing when refused. Taking a backup still works while the service runs. A production copy that starts from a clean setup now has a repeatable check: it opens with no requests, no demo accounts and no notices, and demo loading stays refused. Production has not been started, staff access is unchanged, screens, records and email behavior are unchanged, and email stays held in the outbox.
October 4, 2026
Guide-only update. The user guide and the shared sandbox checklist now describe the tested shared workspace instead of the browser preview. Both explain who can submit purchases: Procurement and administrator accounts cannot submit project purchases, and a project director, district manager or executive cannot yet submit a purchase on a project where they hold that role, and a purchase whose approval route would need one person in two required approval slots is also blocked. They also cover sourcing outcomes, manual Spectrum entry followed by procurement completion, approved terms attached by hand, the manual Accounting and new-vendor handoffs, and how to tell saved work from work kept only in the current tab. A separate section lists what is not yet available. The sandbox checklist is now a checklist for staff, without the administrator setup steps. Screens, records and email behavior are unchanged, and email stays held in the outbox. Use on a real phone has not yet been checked for this version.
October 4, 2026
The hosted sandbox now runs on the Node.js 24.21.0 LTS production runtime instead of the Node.js 26.3.0 build runtime, so Vancouver dates there follow the same time zone data as production. One image now serves every environment, and each environment sets its own type when it starts. Only one copy of the service can open a workspace’s records at a time; a second copy refuses to start instead of running alongside the first. When the service is stopped for an update, requests already in progress get their answers before the records close, and a replacement starts only after the old copy has stopped. Screens, records and email behavior are unchanged, and email stays held in the outbox.
October 3, 2026
In shared records, after the database is restored from a backup or rolled back, no earlier notice is sent again on its own, even one that looks unsent. Each restored notice that could still have been sent is held for review, and a notice recorded after the backup but missing from it is marked so it is never sent again. Email and daily reminders stay on hold until the operator records the review and sets the release time. After release, daily reminders start again on the following Vancouver day, and earlier or same-day notices are not sent late. Through the operator and service path (there is no new button), Procurement can deliberately send one fresh copy of a held approval reminder or PO email, with a reason and an acknowledgement that the earlier one may already have arrived; it reaches only the original recipients, for the current approval step or the current PO package, and retrying the same request sends nothing more. The server passed the same checks on the exact Node.js 24.21.0 LTS production runtime and the Node.js 26.3.0 build runtime, with one recorded difference: Node.js 26.3.0 carries older time zone data (2026a) that still moves Vancouver back to standard time on November 1, 2026, while Node.js 24.21.0 (2026c) keeps British Columbia on permanent UTC-7. The hosted sandbox is not yet moved. The Notifications activity list names a recovery hold and shows “Recipients not recorded” for held entries that have no recorded recipients. After release, the recovery entry says when the recovery was released, in Vancouver time, and that the held notices are never sent automatically. Screens are otherwise unchanged.
October 3, 2026
In shared records, a saved configuration is now refused, with nothing changed, if two vendors or cost codes share an ID, if two vendors share a name, if one project has the same cost code under two IDs, or if a new or changed cost code names no configured project number. The same cost code on two different projects stays two separate records. Import preview now points out any status other than Active or Inactive; that text is kept as written and does not change whether a project is available. In shared records, applying an import now says it is staged until Save shared configuration is selected, because nothing is saved for everyone before that. Budget, quantity and contract columns in an import stay reference information and never change request budgets. Blank padded columns and empty rows in a cost-code file remain ignored, and a file with headings but no rows imports nothing.
October 3, 2026
In shared records, when two administrators save configuration from the same starting point, the second save is refused with a short message and the values typed are kept, so the first person’s change is never silently replaced. The Save shared configuration button is locked while a save is in progress. Configuration already refused a project assignment naming someone without an account; it now also refuses a save that would give two people the same name, because an assignment must match exactly one account. A configuration save that leaves out preferences or imported records now keeps the saved values instead of clearing them. The Approval policy wording now describes the current rules: every routed role needs an entered limit, a blank limit stops new submissions above the PM limit until one is entered, and only an assigned PM within the PM limit has their own step counted as approved. The executive limit field now says “Enter an amount”. On the request form, an approver slot with no provisioned person shows “Not assigned”. In Configuration, a saved approver, project coordinator or site superintendent with no account shows as “(not provisioned)”, and a saved project province with no tax rule shows as “(not configured)”, instead of appearing blank. A saved purchase type that was later removed from Configuration stays visible on its draft as a saved value.
October 3, 2026
In shared records, saving a purchase order’s vendor acknowledgment or follow-up delivery date now checks against the version shown when the window was opened. If someone else saved a change in the meantime, the save is refused with a short message, the window stays open and the values typed are kept, so the other person’s change is never silently replaced. A warning also stays on the page after the window is closed. The Save follow-up button is locked while a save is in progress. A purchase order carried over from older records without a version number can now be saved. Acknowledgment still needs no note: it records that the vendor confirmed receipt of the purchase order, and never changes received amounts, Spectrum entry or Procurement completion. The Purchase orders list now says “No purchase orders yet.” when there are none at all, and “No matching purchase orders.” when a search or filter matches nothing.
October 3, 2026
In shared records, approval notices now go only to the person who currently holds the approval. When a stage is approved, reassigned or returned, any earlier notice that has not been sent is cancelled, and a reassignment back to the same person starts a fresh notice rather than reviving the old one. Each approver gets at most one daily reminder per assignment and calendar day, and a repeated manual reminder click sends one reminder. The configured workflows and the built-in notices now share the same identity, so the two can no longer both notify for the same approval.
Approval emails now show the amounts saved when the request was submitted: the approval total, budget, variance amount and percentage (or that the percentage is unavailable when no budget was allocated), the over-budget reason and the holdback percentage. Credits stay negative, and later configuration changes do not alter a reminder. The approved notice and the buyout log reminder now say what work remains: Procurement review and Spectrum entry are still pending, the PO has not been sent to the vendor, and Conduit does not keep the buyout log. The buyout reminder is sent once per request.
Under Notifications, each recorded notice now shows a plain status: prepared, not sent; queued for the email provider; send attempt in progress; accepted by the email provider; cancelled, no longer current; or needs review. The message content of built-in notices can now be opened as well. Live delivery also obeys a deployment hold: while it is on, nothing is sent to the email provider and the delivery description says so. Escalation to other people and the sourcing and emergency follow-up workflows stay paused until they are agreed.
October 3, 2026
In shared records, the purchase order package window now has a “Download PO only” button beside the package action. It makes a PDF of the current purchase order version with no terms attached, for Procurement to email by hand with the actual approved terms. That PDF is never sent by automated distribution, and the service refuses it if asked. The package action now needs an approved terms PDF chosen in the window; a configured rule is no longer preselected, and choosing nothing shows a message beside the terms field. Every generated PDF is kept unchanged and records its purchase order version. Earlier PDFs stay available to download in the window and are labelled superseded once the request or purchase order changes. The emailed vendor download link for a superseded package stops working. If the request or purchase order changes while a PDF is being made, that PDF is refused and nothing is saved. Automatic terms selection stays off until the applicability of approved terms is approved: final approval no longer assembles a package from a saved selection rule, a saved rule is never used to choose terms, and the shared service refuses a new or changed selection rule. Saved rules can still be removed. In Configuration, under Terms & conditions, “Automatic selection rules” now explains that approved terms PDFs come first and that automatic selection stays off until their applicability is approved, so terms are attached by hand for now. The “Add selection rule” button shows that explanation and adds no rule, and any saved rule is shown read-only with its Remove button.
October 3, 2026
The purchase order PDF that Procurement assembles now prints the exact issued version of the purchase order, so later follow-up edits, such as a changed delivery date, do not alter it. Each line now has its own “Delivery date” column, matching the print preview. The single “Required date” in the delivery section is removed. A line with a blank date reads “Not specified”. An older line that was saved before line dates existed shows the purchase order’s recorded date. Money and date cells no longer break across lines, and long descriptions wrap. The PDF and the print preview now leave out the same unselected requirements, including “Not required”, “No” and “None marked”, and repeated identical requirements print once. The return-signed-copy contact prints only when contract documents are selected. Vendor contact details come only from this purchase or from the same vendor’s record. The note under shared line items now says that line dates print on each line of the purchase order.
October 3, 2026
In shared records, Procurement now records that an approved purchase order was entered in Spectrum by hand, with a note, for the current version of that purchase order. An administrator can also record or correct this entry. Recording the entry does not complete the request and sends nothing. When the entry is recorded, a Procurement user completes the request as a separate step. The request stays financially approved and changes from “Under Procurement Review” to “Procurement complete”. One notice to the requester is prepared in the test outbox, using the completion message and the additional recipients set under Configuration. No email is sent and no vendor or Accounting message is added. An entry can be corrected to “not entered”, and the earlier entry stays in the history. When a change request is issued or Procurement corrects the purchase order, the new version returns to “Under Procurement Review” until it is entered and completed again, and an unsent notice for the earlier version is cancelled. The “Pending procurement”, “Spectrum ready” and “Spectrum not ready” filters, the Spectrum badges and the Spectrum column on Purchase orders now appear in shared records and show the current version only. An emergency request that holds a PO number but is not yet approved is not listed. Browser-only mode keeps its single combined button.
October 3, 2026
In shared records, submitting a sourcing request now needs an active project, a described need, an available budget and a real need-by date. An available budget of zero is accepted; a blank budget is not. A sourcing request goes to Procurement for research with no approval and no PO. Procurement returns findings to the requester by email and closes the request without a purchase; its history is kept. The “Convert to purchase” button is removed, and a sourcing request can no longer be turned into a purchase request. In both shared and browser-only modes, the requester of an open sourcing request sees this next step instead of Procurement’s closing card. If the requester decides to buy, they start a new purchase request, which goes through the normal checks and approvals. In browser-only mode, the request form also accepts an available budget of zero and refuses a blank one. The shared service can record, on a purchase request, a reference to the requester’s own sourcing request with a decision note; a change request never carries that reference, and Procurement can correct a change request on such a purchase order. No message is sent by the app.
October 3, 2026
In shared records, recording an emergency now needs exactly an active project, a vendor, a reason and an approximate spend greater than zero; a blank vendor or reason, or a spend that is not a number, is refused before any PO number is reserved. Once an emergency holds its PO number, its original approximate spend and reason are kept when the purchase details are completed or Procurement corrects the purchase order, and an emergency still waiting for its purchase details cannot be recorded a second time. Completing the details still needs at least one line and goes through normal approval under the same PO number. Emergency requests cannot be cancelled, deleted or have their number reused. When a new vendor is requested, the emergency can be recorded first; completing the purchase details then needs the vendor’s legal name, address, contact, phone, valid email and business/tax number, and records the vendor setup for manual handling by accounting. No payment details are asked for and no message is sent.
October 3, 2026
A change request now keeps its own “After-the-fact purchase” answer. Before, choosing or reloading a purchase order, or submitting the change in shared records, replaced that answer with the original purchase order’s answer. An after-the-fact change no longer asks for a supplier quote, when it is submitted or at final approval; an ordinary change still needs its saved quote. Cost codes, amounts, budgets, taxes and the change reason are still checked, and the approval route is the usual project route. For direct service requests, a submission whose after-the-fact answer is not a checkbox selection is refused (rule ATF-001) and nothing changes.
October 3, 2026
The correction window is now announced by its title, “Correct purchase order”, and focus moves to it when it opens. If you have typed changes, Cancel and the Escape key now ask before discarding them; choosing Cancel keeps what you typed. A blank correction reason is shown beside the field (rule CR-009) and, in shared records, nothing is sent. In shared records, request and purchase order history now label a correction that kept the approval as “Procurement correction, approval preserved”, as browser-only records already did. For direct service requests, a correction that sends only a change request’s lines is refused when it repeats the original purchase order lines (rule CR-010), so those lines are never added a second time; the correction screen itself always sends the full purchase order. Such a direct change correction returned for approval no longer needs the quote again, but a later resubmission by the requester does.
October 3, 2026
When a change would reduce a purchase order, the refusal now names its rule: FIN-014 when the received balance has not been verified, and FIN-013 when the revised subtotal would fall below the verified received subtotal. The existing checks are now covered by tests: an unknown balance is never treated as zero, a verified $0.00 balance is accepted, the balance is checked again at final approval, and credit lines keep their negative amounts.
October 3, 2026
After a change request is submitted, the confirmation now shows the base PO number on its own line, worded the same way as a purchase (“Your PO Number will be”), with a separate change label: “Change pending” until the change is issued, then its change order number, such as “CO 1”. In shared records, a change cannot be issued at final approval if its saved quote file is no longer on the request; the purchase order is left unchanged.
October 2, 2026
In shared records, Procurement can move the current approval only to the person configured for that role on the project, or to the configured COO for an executive approval, and must give a reason. A replacement who already approved, received submission credit or holds another approval on the same request, or who is the requester, is refused with a plain message and nothing changes. Reassigning to the person already assigned changes nothing. Each new assignment gets its own approval notice, and notices for an earlier assignment are cancelled rather than sent, even when the same person is assigned again later that day. A returned request needs a reason and sends one notice to the requester and earlier approvers; its pending approval notices are cancelled. A blank reason is shown beside the reason box, and an unsaved reason is kept after a refused or conflicting action and included in the recovery copy. Notices are queued in the notification outbox.
October 2, 2026
Only the project’s assigned project manager receives approval credit for their own submission: an in-limit request is approved at once, and a larger one starts with the project director. Every other request up to and including $50,000 needs the project manager, and above $50,000 it goes to the project manager, project director, district manager and executive in order, whatever the senior limits are. A project director, district manager, executive or COO submitting on their own project, or a route where one person would fill two required stages, now shows that this approval route is not yet supported and to contact Procurement, with the draft kept (rule APR-014). In shared records, Procurement cannot originate project purchases yet (rule APR-010), and a senior stage without a configured limit is refused instead of being treated as unlimited. “No limit” no longer appears on approval paths.
October 2, 2026
In shared records, each line’s delivery date replaces the separate order delivery date field. Line dates stay optional; a date that is not a real calendar date is refused with a message naming the item. A line whose date was cleared shows “Not specified”, and an older request that only has an order date keeps showing it on its lines without being rewritten. A newly issued purchase order’s required date is the earliest line date. Purchase order print and detail rows also show “Not specified” for a cleared line date. Unselecting holdback clears its percentage.
October 2, 2026
In shared records, when the service refuses a file during an upload, the message now names that file alongside the reason, and still lists any files from the same selection that were not sent.
October 2, 2026
In shared records, the attachment list on a request now comes only from files actually stored on the shared service, so a reopened request shows each original quote or phone photo as saved and links to the identical file. Files chosen in the quote area are saved as quotes. Answering “Yes, I have a quote” on an ordinary purchase or emergency follow-up now needs a saved quote file before submission (rule DOC-019); a filename, a generic attachment or the answer alone is not accepted. After-the-fact invoices stay exempt. Files over 10 MB are not sent and are named in the message, an upload refusal stops the rest of the batch, and the list is refreshed from the service after every upload attempt.
October 2, 2026
In shared records, submission now saves the financial basis of each submitted request (subtotal, GST, PST, HST, approval total, budget, variance and over-budget reason), and approvers see that saved snapshot. A project without a configured province tax rule can still save drafts but cannot submit taxed lines until an administrator configures the rule. A selected tax that has no configured rate for the project’s province (for example HST on a BC line) is now refused at submission. Blank prices and budgets are no longer treated as zero. Tax and over-budget refusals now name their rule and focus the line tax choices or the over-budget reason. The browser preview rounds totals the same way the shared service does. These calculations are an engineering convention pending Finance validation (FIN-011).
October 2, 2026
In shared records, when a save or submission is refused because of a project rule and the form returns to the first step, the save status now still reads “Unsaved shared draft” while edits remain unsaved, instead of showing the last saved time.
October 2, 2026
In shared records, an unfinished request can be saved before a project is chosen and keeps the same request number when it is reopened, with edited delivery, site and contact instructions intact. Those request edits never change the project’s own defaults. A project is still required to submit. A missing project or cost code, or an inactive project, now shows a lasting message naming the project rule (REQ-008, MASTER-010, MASTER-007, and MASTER-009 for a new change request on an inactive project), and the first field to fix is marked and focused. The save area shows “Saving to shared workspace…” while a save is in progress, a retried save is applied only once, and leaving an untouched new request no longer creates an empty draft. Small purchases below the PO threshold can still be submitted, and urgent requests follow the same approval route. Browser-only mode is unchanged apart from the rule names in its messages.
October 2, 2026
In shared records, a new request number takes its year from the Vancouver calendar, the same calendar that PO numbers use, and the request date is the Vancouver date. A request started on the evening of December 31 now keeps that year and date even when the server clock is already in the new year. Existing request numbers, the numbering sequence and retry handling are unchanged.
October 2, 2026
In shared records, the Configuration menu now appears only for administrator and Procurement accounts. Other accounts, such as a project member who submits requisitions, see Sign out in its place on desktop and in the phone More menu, and they land on My requisitions after signing in. The Pending approvals count is shown only to Procurement and to people with an approval decision waiting on them, with the same count as before. The server already refuses configuration saves, the notification outbox and approval decisions from accounts without that authority. Browser-only mode is unchanged.
October 2, 2026
Sandbox, demo and development instances can load the shared demo workspace: the same requests and purchase orders as the alpha.64 prototype, corrected to the current project rules (seven-digit PO numbers, change order 1 on PO 2600712, line delivery dates, BC tax settings, project cost codes and approval routes from the project assignments). While it is loaded, every signed-in view, PO preview and generated PDF shows a DEMO label, and demo records carry their illustrative-example notes. Administrators can load the demo workspace again or reset to a clean, empty start from Configuration > Imports; a verified backup is taken first and everyone signs in again. Production instances refuse both operations. New request references use four digits, starting from REQ-2026-0200 after a demo load.
October 2, 2026
When a new shared request or an approval is retried after a lost connection, the service now applies it once and returns the original result, so retries no longer create duplicate requests, approvals or PO numbers. New PO numbers use the seven-digit format without a hyphen, based on the Vancouver calendar year, and are assigned only when a PO is issued or an emergency request is recorded. New drafts no longer hold a number. Each issued change request keeps its CO number when it is later corrected. Older change requests whose CO number cannot be confirmed show “CO sequence unavailable”. Existing PO numbers, including older hyphenated ones, are unchanged.
October 2, 2026
Shared records are now visible only to the requester, everyone captured on the approval route (including an approver who was reassigned), Procurement and administrators. Project membership alone no longer opens other people’s requests, files or purchase orders, and an unavailable record shows the same message whether or not it exists. When a session expires or the service is unreachable, the sign-in and reconnect screen returns with no records shown. Unsaved request values stay in the tab, can be downloaded as a recovery copy and return after signing in again with the same account.
September 29, 2026
Adds a central, source-backed project rules reference with plain-English checks, stable rule IDs, source notes and document downloads. Corrects built-in demo PO identifiers and their linked references to the agreed seven-digit format, including saved demo workspaces where migration is unambiguous. Also repairs sample date sorting, recipient previews, copied delivery/cost details and sourcing confirmation. Missing example inputs are shown explicitly. Genuine imported historical identifiers and recorded edits are preserved.
September 29, 2026
Local preview of Spectrum-ready completion, pending Procurement filters and simulated requester notices. Adds line delivery dates with editable defaults, delivery and need-by sorting, first-line configured tax prefills, clearer emergency and CO identifiers, seven-digit new PO numbers without a hyphen, mandatory SR need-by and cleaner CSV mapping. Existing identifiers remain unchanged. New shared-service behavior and the agreed deferred integrations remain separate work.
Review scenarios and interim operation
September 25, 2026
The sample purchase orders now include created dates, including in previously saved demo workspaces.
September 25, 2026
Holdback now appears first in a separate highlighted section above the deliverables checklist, with its editable percentage alongside the selection.
September 25, 2026
Template downloads now match the supplied project CSV and vendor/cost-code headers. Import previews recognize those columns and retain source reference data. Vendor Code and Project Number match existing records; cost codes use project plus Full Reference. Partial uploads add or update matching records without deleting omitted records. Blank supplied fields clear values; unmapped fields stay unchanged.
September 24, 2026
Consolidated the call-driven changes and release notes. Independent source and implementation reviews are recorded with test evidence and remaining client dependencies.
September 24, 2026
Added request, approval, CR, emergency and PO-follow-up instructions with a practical training exercise and a separate administrator sandbox checklist.
September 24, 2026
Added a web-app manifest and install branding, plus iPhone/Android home-screen instructions. Shared data requires connectivity; offline operation is not claimed.
September 24, 2026
Documented isolated shared testing, controlled roles and test-outbox behavior. Vendor distribution preserves configured procurement-copy recipients. Real sandbox mail and hosted client testing still require agreed recipients, sender credentials and hosting.
September 24, 2026
Removed duplicate Conduit name and tagline text beneath the configurable logo.
September 24, 2026
CSV/JSON previews let administrators map actual source columns to app fields, including project-specific cost codes and project activity. Client export templates are still pending verification.
September 24, 2026
Configuration supports active/inactive projects. New intake excludes inactive projects while preserving historical records and approval access.
September 24, 2026
Added compact PO rows, creation/delivery dates, acknowledgment filters, date/project sorting and requester search. Related PO and requisition numbers link directly. Requisition lists also support sorting. Unknown historical dates remain Not recorded.
September 24, 2026
Acknowledgment saves without requiring a reference note, survives reload and retains independent follow-up versioning. Delivery-date edits are audited.
September 24, 2026
Configuration supports approved PDF uploads and ordered rules by project, purchase type, vendor and province. Shared final approval assembles matched terms automatically. Missing documents and matching rules remain explicit; browser-only mode provides configuration preview, not shared package assembly.
September 24, 2026
Vendor documents show selected requirements and tax percentages without internal approval records. Generated service PDFs retain all pages of the selected supplied terms.
September 24, 2026
Financial approval remains recorded while the completion page and service notifications identify the PO as under procurement review. No external accounting-system entry is claimed.
September 24, 2026
Each purchase line requires a selected tax or explicit Tax exempt. Exemption clears other taxes; HST excludes GST/PST. Emergency initial intake remains four fields without line items.
September 24, 2026
New POs use the spoken YY-NNNNN example with annual sequence allocation. The shared service allocates numbers atomically, and emergency completion retains its reserved number. Existing PO numbers remain unchanged. Final import format confirmation is pending.
September 24, 2026
Fixed the malformed approval-decision dropdown. Corrections load the complete issued PO, support explicit tax exemption and can restart required approvals. Validation messages appear inside the open dialog.
September 24, 2026
New CRs start with blank signed change lines and inherit original header, terms and requirements. Quote upload is required by default. The resulting PO retains original lines plus changes; older replacement CRs retain their previous interpretation.
September 24, 2026
PRs below the advisory threshold are allowed, and CRs have no minimum. Configuration exposes the advisory threshold, CR quote requirement and fixed received-floor explanation. Rule errors link to configuration.
September 23, 2026
My requisitions and All requisitions now match Pending approvals: the requisition number is the bold primary title, with the description and vendor underneath.
September 23, 2026
Choose from three supplied Conduit logos or upload a custom logo in Configuration. Adjust sizing and custom background, preview and reset. Original supplied files are preserved. Shared configuration requires administrator access.
September 23, 2026
Replaced the placeholder choices with the supplied deliverables and contract instructions list, including separate electronic and hard copy options. Holdback Applies retains its editable percentage, defaulting to 10%. Existing saved selections remain in request history and PO details.
September 23, 2026
Detail panels close on an outside click. Edited dialogs ask before discarding changes, using the app confirmation toast.
September 23, 2026
Added the Conduit name and Procure, Build, Achieve tagline while retaining the Industra logo until the final client asset arrives.
September 23, 2026
Added projectNumber to cost-code configuration and the provisional import template, with project filtering. Camillo’s actual source format remains pending.
September 23, 2026
Added sender and procurement-copy configuration. The shared service queues completed packages automatically from the package action, with expiring PDF links and saved email content. The public preview sends no email.
September 23, 2026
Renamed the approver action Reject, retaining mandatory reason and notification to requester and previous approvers, including configured workflows.
September 23, 2026
Removed received-amount entry from the first-release interface. Existing verified balances and change-request protections remain intact.
September 23, 2026
Added searchable PO list, condensed line details, expandable header, audited delivery follow-up and vendor acknowledgment. Financial corrections retain the existing audit and approval decision.
September 23, 2026
Selected holdback starts at 10%, remains editable and appears in approval summaries and PO documents.
September 23, 2026
Added editable checklist labels and add/remove controls in Configuration. Saved requests preserve their selected custom requirements. Final client checklist remains pending.
September 23, 2026
Connected province rules to new line taxes and actual totals. Rates are saved with lines. Applicable taxes start selected; exemptions can be unchecked. HST excludes GST and PST.
September 23, 2026
Equal $50,000 role values allow larger purchases through PM, PD, DM and executive in order. Removed the No Limit option and visible Review policy settings.
September 23, 2026
Added an Urgent flag to PR, CR and SR, visible to procurement in request lists and details.
September 23, 2026
Removed CR payment-term editing while retaining original PO terms. Removed the supporting-information text box; quote attachments remain.
September 23, 2026
Added the 10 province tax rules and six purchase types supplied by Albert as editable reference tables in Configuration. Rates, tax types and codes can be updated; rows can be added or removed. These reference tables do not yet drive line-item calculations.
September 23, 2026
Initial emergency requests now go directly from Request details to Review. The line-items step has been removed. Purchase requisitions, change requests and later emergency completion keep their existing steps.
September 22, 2026
Added a question-and-answer review page with the outstanding business inputs, linked from the app and version history.
September 22, 2026
Replaced large deliverable text fields with checkboxes. Selecting holdback requires a percentage. Return contact details use compact inputs when contract documents are selected. Camillo’s final list remains a follow-up.
September 22, 2026
Placed GST first in each line’s tax controls. Added project tax defaults and individual line overrides. Approval totals include selected PST/HST and exclude GST; PO totals include GST. Previously saved aggregate GST is retained until explicitly replaced.
September 22, 2026
Explained what notes and quotes to provide and where reviewers and approvers see them.
September 22, 2026
Administrators can edit the available terms and select a default for new requests. Existing requests and PO terms are retained.
September 22, 2026
Project, vendor, reason and approximate spend are required. Line items are optional. The existing steps remain, and a request without lines receives its provisional PO on the final page for follow-up.
September 22, 2026
Explained the near-limit review criteria and clarified that they do not reject requests or change routing. Removed the unused CCDC threshold input pending an agreed policy.
September 22, 2026
Added a control to apply one agreed limit to PD, DM and CEO. Equal limits preserve the required sequential approval stages. The agreed amount still needs confirmation.
September 22, 2026
Select the project first, then select one of its POs. Assigned projects remain the default, with Show all projects available. Changing projects clears the previous PO selection.
September 22, 2026
Requisition numbers are the bold primary titles, with descriptions underneath.
September 22, 2026
Filter pending approvals by approver and requester, together with the existing search.
September 22, 2026
Procurement can request a reminder for the current approver immediately, without waiting for or resetting the daily schedule.
September 22, 2026
Added the visible alpha version and this history. Every subsequent completed update increments the alpha number and records its changes here.
September 19, 2026 (committed September 22) · Retrospective entry
Removed the sourcing helper section, its additional fields and related controls from this phase. Retained the standard sourcing request form.
September 19, 2026 · Retrospective entry
Restored the multistep emergency flow, moved the provisional PO display to the successful final page and emphasized the number. Removed the browser workspace connection panel. Fresh emergency project selection remained a known gap.
September 19, 2026 · Retrospective entry
Added request-type workflows with configurable recipients, timing, content, repetitions and stop conditions. Notifications and Reports were subsequently hidden from navigation for this review.
September 19, 2026 · Retrospective entry
Added a searchable project selector and Show all projects toggle with help. Removed duplicate project text and unnecessary warnings. Added configurable units/categories, improved category placement, trash icons, in-app confirmation toasts and compact dropdowns.
September 18, 2026 · Retrospective entry
Implemented and locally tested authenticated shared records, durable storage, document extraction and optional email delivery. These services are not activated by the published static preview.
September 18, 2026 · Retrospective entry
Added project assignments and defaults, master-data imports and vendor setup capture. Improved PO preview and generated documents with approval records and selected supplied terms pages.
September 15–18, 2026 · Retrospective entry
Added configurable role limits, sequential senior approvals, PM submission approval, CEO/COO handling, project coverage, preconstruction access, after-the-fact requests, sourcing closure/conversion, change-request credits, received-amount protection and correction rerouting.
September 12, 2026 · Retrospective entry
Corrected typing focus, draft persistence, PO baseline handling, financial precision, attachment validation and conflicting updates. Expanded approver request details.
September 10–12, 2026 · Retrospective entry
Added PR, CR, SR and ER, saved drafts, requisition numbers, attachments, budget variance and explanations, project-based approvals, configuration and request history.
September 9, 2026 · Retrospective entry
Created desktop and mobile requisition screens, request details and the multistep form. Applied Industra branding and reviewed the supplied approval flow.
September 6, 2026 · Retrospective entry
Reviewed the supplied Power App, documented findings and published the technical review.
Actual CSV exports, approved terms and assignment rules, email sender/copy mailbox, controlled test recipients, dispatch timing and final compact PO format remain to be confirmed.
September 24 update review