General Disclaimer
The information, tools, checklists, examples, and generated outputs on this site are provided for engineering workflow support only. They do not replace project specifications, client requirements, statutory obligations, professional engineering judgement, independent checking, or formal approval processes.
Users remain responsible for verifying all results, assumptions, inputs, calculations, reports, and generated documents before relying on them for design, construction, review, or commercial decisions.
Confidential and Commercial Information
Users should be careful when entering project names, line names, asset identifiers, client information, commercial details, file paths, screenshots, reports, XML files, drawings, or any other information that may be confidential, commercially sensitive, export-controlled, personal, or subject to contractual restrictions.
Do not upload or enter confidential project information unless you are authorised to do so and the selected hosting environment is approved for that information.
Checklist Data
The PLS-CADD QA/QC checklist stores answers, comments, statuses, visual flags, and metadata in the browser's local storage. This means the checklist state is saved on the user's own browser and is not written to the Django database by normal checklist use.
The Save QA/QC Archive action creates a downloadable archive containing the checklist JSON, Excel report, manifest, and linked attachments. The downloaded archive is controlled by the user.
The Clear local data action clears the checklist state saved in the current browser and requests deletion of temporary evidence files associated with the current session. It does not erase files that may already have been downloaded by the user or shared outside the site.
Uploaded Evidence Files
Evidence files uploaded through checklist paperclip controls are stored in a temporary session-scoped media folder so that the browser can show links, include them in the QA/QC archive, and reload archives during the review workflow. These files are not stored as checklist answers in the database, but the uploaded files exist on the server file system while retained in temporary media storage.
Temporary QA/QC uploads are removed when the user clears local checklist data and by automatic cleanup after the session or retention period expires. Users should still avoid uploading confidential or commercially sensitive files unless the server and retention settings are approved for that use.
PLS-CADD XML and Data Analysis
PLS-CADD XML reports may contain project names, file paths, usernames, computer names, coordinate systems, asset identifiers, and design data. XML analysis tools should therefore be used only with files that the user is authorised to process in the selected environment.
Future XML analysis features should make metadata inclusion optional in generated reports and should avoid exposing source file paths unless the user explicitly chooses to include them.
Recommended Safe Use
- Use anonymised project names when possible.
- Do not upload confidential documents on an unapproved public server.
- Review generated Excel, Word, archive, and chart outputs before sharing them.
- Use Clear local data on shared computers.
- Keep downloaded QA/QC archives in an approved project location.
- Confirm retention and backup settings before production deployment.
Implementation Note
Current code review indicates that checklist responses are saved in browser local storage and exported by user action. The Django database stores checklist templates, admin-managed content, and Django session records, not ordinary checklist responses. Uploaded evidence files are saved in temporary session-scoped media storage to support links, archive generation, and archive reload, then removed by clear-local-data or cleanup.