#9Sign in and save supplier records
In progressAn invited customer can sign in by email code, add a supplier, and return later to find their saved information.
The first workspace is built and through its initial checks. Shared access, email sign-in and final acceptance are still ahead.
Sign in and save supplier records
In progress. Initial checks passed; not yet accepted.
Build customer questionnaires
Starts after the first workspace is accepted.
Waiting on account owner
Update account access so the remaining shared-access setup can proceed.
Six stages, 31 app tickets. Open a stage to see what it adds.
An invited customer can sign in by email code, add a supplier, and return later to find their saved information.
Customers can start with a template or a blank form, edit their questions, and preview the questionnaire before sending it.
Customers can invite their team and decide who can manage settings, run day-to-day work, or only view information.
Customers can keep each supplier company and its locations organized, then choose which company or location a request is for.
Customers can turn Word, Excel, CSV and readable PDF files into questionnaires they can review and edit.
Customers can turn scans, photos, screenshots and handwriting into questions, then check and correct the results.
Customers can bring in a supplier list, review missing details or possible duplicates, and confirm the additions together.
Customers choose the supplier contacts, documents and due date, then confirm the invitation. Each supplier receives a fixed copy of what was sent.
Invited supplier contacts can work together, upload evidence, and return to unfinished answers. Customers see progress, not private drafts.
An approved supplier signer checks and signs the response before submitting it. The customer then reviews and accepts it.
Suppliers can suggest teammates, while customers approve their access and decide who is allowed to sign.
Suppliers can make approved corrections without erasing the original response. The updated response needs a fresh signature and review.
Customers can send a corrected version to previous recipients. Earlier records stay available, and the replacement starts with fresh answers.
Customers can add examples, explanations and upload instructions so suppliers understand what is being asked.
A supplier’s answers determine which follow-up questions appear. Skipped questions do not create false missing-answer warnings.
Customers can request clarification or additional evidence, set a due date, and review the supplier’s reply before closing the task.
Customers can download response summaries, answer spreadsheets and supporting files without exposing unfinished supplier work.
Customers can set or extend deadlines, control reminders, and receive alerts when important work needs attention.
Customers can see which responses are due for renewal and confirm a new request. Eligible previous answers can be reused, with a fresh signature and review.
Customers can define their own grading approach and understand each result. Questionnaires can also remain information-only, without a score.
Customers can review ratings, explain adjustments, and reassess existing answers under a new method while preserving earlier results.
Customer-defined rules suggest follow-up work for review. A person approves each task before it is sent to a supplier.
New findings connect to related open tasks, while previously resolved work stays resolved unless someone deliberately starts new work.
Suppliers can describe the stages of their cargo flow in a clear map and submit it for customer review.
Suppliers can prepare changes privately and submit an updated map for review without losing earlier versions.
Customers can record concerns about locations or routes, along with supporting sources, dates and their reasoning.
Customers review questionnaires, cargo maps, concerns and follow-up work together, then record a human assessment using their own method.
Customers can see newer information and decide whether another assessment is needed. Earlier conclusions remain intact.
Customers can create or adapt inspection checklists, share them with suppliers, and review the completed evidence.
The complete app is backed up and restored separately to confirm that records, access and supporting files are preserved.
The complete customer and supplier experience is checked against the agreed plan before it is presented for final acceptance.
Build order, not a date promise. Questionnaire authoring is planned next; team access and company organization can follow the same first milestone.
Accepted app tickets, separate from planning decisions.
Completion pace is not established yet. The work already completed inside an open ticket does not count as an accepted ticket.
Initial checks are progress, not final acceptance.
The current hold and the remaining work.
An account-access change is needed before the remaining shared-access setup can be completed. This is the current hold on final review.
Responsible Account owner, then development team
The shared app needs its own working sign-in emails. This must be checked before reviewers can use it.
Responsible Development team
Confirm that a reviewer can sign in, save a supplier, leave, and return to the saved record. Then the first ticket can be accepted.
Responsible Development team and project owner
These records explain how the plan was agreed. They are separate from the 31 app tickets and are not counted in completion pace.
Defined the first product outline and the decisions needed before building.
Decision completedA broad competitor audit was set aside as a delivery requirement. Existing research remains useful background.
Not proceedingA broad regulatory study was set aside as a software-planning requirement, not marked as completed research.
Not proceedingDefined how customers prepare requests, suppliers answer them, and customers review the results.
Decision completedDefined who can see, edit, review and sign information, including the privacy of supplier drafts.
Decision completedDefined corrections, follow-up, reminders and the renewal of older responses.
Decision completedRecorded the early release approach, which was later expanded into the full-app plan.
Decision completedKeeps the earlier questionnaire-focused plan as background, rather than the current delivery target.
Earlier planDefines the complete business-partner assessment app that the roadmap now delivers.
Current plan agreed