For procurement and facilities
Share the job with the contractor, not your internal notes.
Vendors get a private link to the specific work shared with them. Everything else, including internal discussion, stays inside your organisation.
What we can state plainly
Each line here is something the running system does today, not an ambition.
- A vendor link shows only the jobs explicitly shared with that vendor.
- Shared notes and internal notes are stored separately on the same job.
- Coverage records which vendor serves which branches and categories.
- Contract dates and contacts are held against the vendor record.
How it works in practice
- 1
Register the vendor
Contacts, coverage, categories and contract details.
- 2
Assign the work
Choose a vendor for the job; suggestions consider coverage and load.
- 3
Share a link
The vendor sees the job, the branch and what was shared with them.
- 4
Close it out
Vendor updates come back onto the job before verification.
What you get
Coverage map
Which vendor is expected to respond for which branch and work category.
No vendor accounts
A private token link, so contractors need no login to participate.
Contract records
Start and end dates, contacts and scope kept with the vendor.
Vendor reporting
Jobs per vendor, time taken and rework counted from real records.
The screens behind this page
Every entry names a real screen in the application and its state today.
/vendorsAvailable todayVendor records, coverage, contracts and shared jobs
Available today: vendor coverage and the work shared with each vendor.
Data shown: Sample refrigeration and cleaning vendors
/vendor/$tokenAvailable todayPrivate vendor link with no login required
Available today: a vendor sees only the work shared with them.
Data shown: Sample shared job
/scheduleAvailable todayWorkload, skills and availability used for assignment suggestions
Available today: suggestions only. A person still makes the assignment.
Data shown: Sample week of planned work
What's included
What you get on day one, and what we connect to your own systems during onboarding.
Included
- Vendor records, coverage, contracts, shared jobs and the private vendor link
Connected during setup
- Vendor invoicing and payment are not part of BranchFlow and remain in your finance system
Common questions
- Do vendors need an account?
- No. They use a private link that only shows the work shared with them.
- Can vendors see other branches?
- No. The link is limited to the specific work shared with that vendor.
How access and records are handled
Each organisation's records are separated in the database, and people only see the branches they are assigned to. Status changes, approvals, rejections and verifications are recorded with who did them and when. We do not claim any external certification or audit at this stage; if you need a formal security review, ask us and we will tell you exactly what exists today.