Using LazyQS

LazyQS can only analyse the text it can read. Most poor results come from low quality scans (blurry, skewed, faint text, shadows, or photos of pages) or documents with very little readable text (some drawings).

• Upload the original digital file where possible (text searchable PDF or DOCX).
• If you must scan, re-scan at 300 DPI with straight pages and good contrast.
• If a drawing is hard to read, also upload the matching specification or schedule (drawings often have minimal text).

• Best: Text searchable PDFs, or DOCX files created from the source.
• Also supported: XLSX and CSV (tables are converted to text for analysis).
• Often problematic: Legacy DOC and XLS. If they fail, convert to DOCX and XLSX or CSV.
• Not supported for project uploads: image files (PNG, JPG) or zipped folders.

Tip: If you cannot select text in a PDF, it is likely a scan and results may depend on OCR quality.

Upload time depends on your connection and file size. Most uploads finish in seconds to a few minutes per file.

After you click Start Review, many projects complete in about 10 to 30 minutes. Large packs and scanned PDFs can take longer, sometimes up to an hour.

You can safely leave the page. Processing continues and you can come back later to see the results.

On the upload screen, a file is uploaded when it appears in the list with a completed progress bar and no error message.

• Refresh the page. Uploaded files should still appear under the same project.
• If a file shows an error, remove it and upload again (or try a smaller, clearer copy).
• Uploading does not start analysis. Select a review type and click Start Review when you are ready.

First check whether it is stuck while uploading, or stuck after you clicked Start Review.

• If it is stuck uploading: keep the tab open, try again, and consider disabling VPN or browser extensions that block requests. Large files close to 75MB take longer.
• If it is stuck processing: scanned PDFs and large packs take longer. If the processed count does not change for a long time, refresh and check again later.
• If it still does not move after about an hour, email support with your project link and any filenames that look problematic.

Needs Attention means we could not extract enough readable text from that file (common with scans, drawings, password protected PDFs, or legacy spreadsheets). The rest of the review can still complete.

Failed means the upload or processing did not complete for that file.

• Replace the file with an original text searchable PDF or a DOCX when possible.
• Convert DOC to DOCX and XLS to XLSX or CSV if you are using older Office formats.
• Make sure the file is under 75MB and not password protected.

No. LazyQS uses AI and OCR, so it can occasionally misread text (for example O and 0) or miss context, especially in scanned documents.

• Use the citations and page references to confirm key numbers, dates, and exclusions.
• Treat results as decision support. LazyQS is not legal advice.

• Upload the most complete pack you have (terms, specs, schedules, and key drawings).
• Prefer text searchable PDFs or DOCX. Convert DOC and XLS if they cause issues.
• If scanning, use 300 DPI with straight pages, good lighting, and high contrast.
• Select the correct review type before clicking Start Review.

ChatGPT is useful for quick questions, but LazyQS is built for end to end review of real tender packs and contracts.

• Upload a full multi document pack and keep it saved as a project.
• Extract text and run OCR where needed, then flag documents that need attention.
• Produce structured outputs with citations and page references so you can verify fast.
• Use your company profile and trade focus so the review prioritises what matters to you.
• Track progress and generate exports when available.

Tender packs are often large and messy. LazyQS helps you find the trade relevant information quickly and highlights what to check next.

• Coverage summary, plus a list of documents that need attention.
• Key submission requirements and critical actions to meet the tender rules.
• Scope and package boundaries, including common exclusions and assumptions to verify.
• Risk and opportunity highlights with citations and page references.