Accept a contractor’s software with evidence
Ask the contractor for a staging address and two sample customers. Your assistant helps prepare a check of the promised boundary. Use the result to accept delivery, request a correction or record what still needs access.
Prepare my acceptance check →What to request from the contractor
- An address you are authorized to test and the version offered for acceptance.
- Two demo customers and one clearly private file owned by each.
- A named person who can fix the problem and arrange a retest before sign-off.
Prepare the check with your AI assistant
Sample conversation
My contractor says the portal is ready. Help me check that customers can see only their own files.
Assistant · What did the contractor promise about private files? I’ll use that rule to propose one permitted download and one that must be denied. Who controls the staging address?
On first setup, verify the target and grant the assistant access to the intended project. Review the draft and confirm the run in your workspace.
Illustrative result and next action
Customer B opened A’s sample file. Give the contractor the tested release, expected denial and redacted observation. Ask for the same test on the corrected version.
Questions before you start
Can the contractor help without sharing production credentials?
Yes. Have them prepare synthetic data on staging and enter credentials through the protected setup.
Does a passing check complete acceptance?
It supports a decision on the tested security boundary. Compare functionality, usability and contractual deliverables with the specification separately.
What if I cannot verify the domain?
Ask the contractor to help with domain or file verification and provide an authorized staging target. Record inaccessible areas as pending.
What evidence closes a repair request?
Ask for the corrected release and a retest showing the stranger denied while the owner still succeeds. Keep both observations with the acceptance record.
What can a public URL show?
An external check examines the reachable surface. Private workflows require authorized access and suitable test accounts. A source-code review or expert investigation has a different scope.
Can I reuse a prepared project?
Select the verified project, review the environment and permissions, then confirm the run. Recheck fixtures if the release changed the access model.