We develop custom tools for districts and psychologists: useful apps, professionally designed report templates, and connections between the systems your team uses.
Explore district report formats, coordinated intake and review steps, or a data map connecting approved systems. We scope accessibility, access roles, training and procurement requirements with your team.
Discuss a district project →Explore an app for a repeated task, a polished report template, or a connection that reduces manual re-entry. Start with the most time-consuming step and a clearly defined deliverable.
Discuss your workflow →Every project is scoped to your needs. These are examples of work we can discuss, not a promise that an existing product includes every feature.
Examples: referral intake, checklist coordination, or a report-preparation workspace.
Possible deliverable: a working app, agreed acceptance checks, and a user guide.
Examples: editable evaluation templates, standardized score tables, and clear family-facing summaries.
Possible deliverable: an editable master, sample report using fictional data, and formatting guidance.
Examples: mapping approved spreadsheet fields to template sections, validation rules, or a supported import/export workflow.
Possible deliverable: a field map, tested connection or import, error handling and maintenance notes.
We review your workflow using blank or fictional examples. You receive a proposed scope, success criteria and estimate before a commitment.
Review a template draft or working prototype, confirm the field mapping and give feedback on the experience.
Test the agreed workflow and acceptance criteria with your designated reviewers. Data access and permitted test materials are arranged in advance.
Receive the agreed deliverables, documentation and training. Ownership, hosting, support and maintenance terms are agreed in the project scope.
Imagine a district team that retypes the same information into several report sections.
This illustrates a possible scope. No client results, performance savings, or deployed integration are implied.
The answers below describe this website and its demonstration. App deployment, storage, integrations and contractual requirements are confirmed separately for each proposed project.
Yes. Use the built-in fictional profiles or enter synthetic scores. The SLD calculations and report rendering run in your browser. The score entries are not submitted by the demo or saved to browser storage. Copied or downloaded output stays wherever you choose to save it. The website itself loads hosting, fonts and other website services; this is not a claim that visiting the page creates no network traffic.
The contact form sends the details you enter to this website’s Cloudflare endpoint, which stores inquiries in a private Google Sheet. We use those details to respond. Keep the message general: do not include student names, records, scores or other confidential information. Direct email is also available at info@drvalentinespsychlab.com. Read the privacy policy for more information.
No. Where configured, Google sign-in verifies your identity; the website then checks the account’s access record. An invitation or inquiry does not itself establish a license, district integration, or permission to use student records. Ask us to confirm the access and deployment arrangement for your team.
That depends on the agreed app deployment and integration design. Before a pilot, we confirm the proposed data flow, storage locations, access roles, retention, deletion, and any external processors with the app development team and your district reviewers. This public demo does not establish those arrangements.
We can discuss your blank templates, permitted data sources and desired outputs. Discovery establishes the supported connection method, field map, validation rules and review steps. A named system is not assumed to have an existing integration; feasibility and access requirements are confirmed in the scope.
A description of the workflow, blank or synthetic examples, the number of intended users, accessibility needs, platform constraints, and your procurement and privacy review requirements. We then agree on a proposed scope, pilot acceptance criteria, training, and support responsibilities before a commitment.
Describe your workflow in general terms. We usually reply within one business day.