#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.
Estimated effort: Large. Establishes sign-in, saved records and secure shared access.
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.
Planning and scope agreed. First workspace underway.
Six stages, 31 app tickets. Open a stage for details and initial effort estimates.
An invited customer can sign in by email code, add a supplier, and return later to find their saved information.
Estimated effort: Large. Establishes sign-in, saved records and secure shared access.
Customers can start with a template or a blank form, edit their questions, and preview the questionnaire before sending it.
Estimated effort: Large. Builds the core editor and questionnaire preview.
Customers can invite their team and decide who can manage settings, run day-to-day work, or only view information.
Estimated effort: Medium. Adds team invitations, role changes and access removal.
Customers can keep each supplier company and its locations organized, then choose which company or location a request is for.
Estimated effort: Medium. Adds separate company and location records.
Customers can turn Word, Excel, CSV and readable PDF files into questionnaires they can review and edit.
Estimated effort: Large. Reads several document formats and preserves useful results when processing fails.
Customers can turn scans, photos, screenshots and handwriting into questions, then check and correct the results.
Estimated effort: Large. Handles scans, photos and handwriting, including uncertain results.
Customers can bring in a supplier list, review missing details or possible duplicates, and confirm the additions together.
Estimated effort: Medium. Adds batch review, duplicate checks and safe supplier confirmation.
Customers choose the supplier contacts, documents and due date, then confirm the invitation. Each supplier receives a fixed copy of what was sent.
Estimated effort: Large. Connects fixed questionnaire copies, invitations and supplier access.
Invited supplier contacts can work together, upload evidence, and return to unfinished answers. Customers see progress, not private drafts.
Estimated effort: Large. Combines shared answers, private evidence and safe handling of conflicting edits.
An approved supplier signer checks and signs the response before submitting it. The customer then reviews and accepts it.
Estimated effort: Large. Coordinates signing, final checks, submission and customer review.
Suppliers can suggest teammates, while customers approve their access and decide who is allowed to sign.
Estimated effort: Medium. Adds collaborator approvals and separate permission to sign.
Suppliers can make approved corrections without erasing the original response. The updated response needs a fresh signature and review.
Estimated effort: Medium. Adds controlled corrections, fresh sign-off and a clear revision history.
Customers can send a corrected version to previous recipients. Earlier records stay available, and the replacement starts with fresh answers.
Estimated effort: Medium. Reissues changed questionnaires while preserving each recipient’s earlier records.
Customers can add examples, explanations and upload instructions so suppliers understand what is being asked.
Estimated effort: Small. Adds question guidance while preserving the instructions already sent.
A supplier’s answers determine which follow-up questions appear. Skipped questions do not create false missing-answer warnings.
Estimated effort: Large. Adds branching questions and protects answers hidden by changing selections.
Customers can request clarification or additional evidence, set a due date, and review the supplier’s reply before closing the task.
Estimated effort: Medium. Adds follow-up tasks, private draft replies and customer-approved closure.
Customers can download response summaries, answer spreadsheets and supporting files without exposing unfinished supplier work.
Estimated effort: Medium. Produces reports and evidence downloads without exposing private work.
Customers can set or extend deadlines, control reminders, and receive alerts when important work needs attention.
Estimated effort: Large. Coordinates reminders, deadlines and alerts across changing response states.
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.
Estimated effort: Medium. Adds renewal timing, safe reuse of accepted answers and fresh sign-off.
Customers can define their own grading approach and understand each result. Questionnaires can also remain information-only, without a score.
Estimated effort: Large. Builds configurable grading with explainable results and preserved history.
Customers can review ratings, explain adjustments, and reassess existing answers under a new method while preserving earlier results.
Estimated effort: Medium. Adds reviewer decisions and new evaluations without rewriting earlier results.
Customer-defined rules suggest follow-up work for review. A person approves each task before it is sent to a supplier.
Estimated effort: Medium. Turns chosen answer patterns into suggestions that require customer approval.
New findings connect to related open tasks, while previously resolved work stays resolved unless someone deliberately starts new work.
Estimated effort: Medium. Matches related follow-up work without duplicating tasks or reopening resolved items.
Suppliers can describe the stages of their cargo flow in a clear map and submit it for customer review.
Estimated effort: Large. Creates guided cargo maps with private drafts, supplier submission and customer review.
Suppliers can prepare changes privately and submit an updated map for review without losing earlier versions.
Estimated effort: Medium. Adds private map updates, new versions and fresh customer review.
Customers can record concerns about locations or routes, along with supporting sources, dates and their reasoning.
Estimated effort: Medium. Adds research notes, supporting sources and a history of changes.
Customers review questionnaires, cargo maps, concerns and follow-up work together, then record a human assessment using their own method.
Estimated effort: Large. Brings multiple evidence sources together for a recorded human assessment.
Customers can see newer information and decide whether another assessment is needed. Earlier conclusions remain intact.
Estimated effort: Medium. Highlights newer information and supports reassessment without rewriting past decisions.
Customers can create or adapt inspection checklists, share them with suppliers, and review the completed evidence.
Estimated effort: Large. Adds an inspection editor, printable templates and completed-evidence review.
The complete app is backed up and restored separately to confirm that records, access and supporting files are preserved.
Estimated effort: Large. Proves that the complete app, its records and original files can be safely recovered.
The complete customer and supplier experience is checked against the agreed plan before it is presented for final acceptance.
Estimated effort: Large. Checks complete customer and supplier journeys, usability and capacity.
Build order, not a date promise. Questionnaire authoring is planned next; team access and company organization can follow the same first milestone.
These provisional estimates compare the full scope of each ticket, including building and checking it. They are not delivery dates or a measure of work remaining.
Sizes assume earlier required work is ready. Waiting for access or approvals is separate.
We’re still gathering delivery history to estimate timing. Planning and work inside open tickets remain part of our progress.
Estimates reviewed .
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 show how the scope, workflows and access rules were defined. They are part of the work behind the roadmap, with completed and retired items labeled separately.
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