Frequently asked questions

Greenlit turns agreed SOW language into agency-confirmed acceptance criteria, runs supported checks against an authorized staging build, presents the evidence to one named reviewer, and records the client's decision.

No. It focuses on the last mile between agreed scope, proof, approval, and invoice readiness. The agency can continue managing tasks in its existing system.

No. AI may draft criteria from exact source language. The agency confirms the criteria and mappings, supported checks observe the build, and the named client reviewer makes the business decision.

No. Subjective, external, unsafe, or unsupported claims should remain client-reviewed or be verified in the appropriate external system.

The review uses a recipient-bound link and separate access code. The client does not use the agency workspace.

The request is recorded against the milestone. The agency can determine whether it corrects an agreed criterion, needs clarification, or appears to add new scope.

Greenlit records a milestone decision, but it is not positioned as a replacement for a contract, notarization, or formal electronic-signature product where one is required.

It should not be. The agency should revoke the existing invitation and create the correct recipient-bound review.

It shows that a supported observation matched the frozen expected result for the identified build, time, environment, and check. It does not prove facts outside that scope.

Greenlit can preserve the difference between the visible state and the observed request result when that typed check is supported, preventing a cosmetic success message from hiding a failed operation.

Changes should create a new confirmed revision. The frozen revision and prior evidence remain part of the record rather than being silently rewritten.

No. It may support specific accessibility-related observations, but it does not certify conformance.

No. Approval never directly charges a payment method. Depending on prior agency configuration, it can make a milestone invoice-ready or start a disclosed Stripe invoice workflow.

No. The agency remains responsible for invoice accuracy, taxes, delivery, payment collection, refunds, disputes, and accounting.

The current beta notice describes 90 days for screenshot evidence and four years by default for approval and audit records, subject to configuration and legal holds.

The client receipt can be printed or saved as PDF, and retained agency records remain available through the authorized dashboard subject to the product's retention rules.

Use only the section needed for the milestone. Follow the analysis-screen notice about whether the deployment accepts authorized business content or only synthetic and expressly non-confidential material.

No. The public walkthrough uses sample builds. Custom verification belongs to the account-backed workflow and accepts only public HTTPS staging origins controlled by the agency and proven through the ownership flow.

Use the in-product Feedback button for bugs, confusion, and product ideas. Use the privacy request form for privacy or data questions, and check the Contact page for the currently available account and security channels.