Completion reports that send themselves

LecturePanda's Spreadsheet Report sends a board, registrar or accreditor without a data feed a scheduled file of completions, laid out in the columns they ask for. You attach the report to the credits that should be reported, and every completion of those credits goes into the next file, delivered by email, to a Google Drive folder, to an SFTP server or by HTTP POST. See the setup guide.

LecturePanda reports each completion in a Spreadsheet Report exactly once. Every completion of the attached credits is recorded against the report and carried in the next scheduled file, so a learner who finishes the night before a send is in that file and nobody appears in two. The file has one row per credit completed, so a course with two reported credits produces two rows per learner.

Yes. A LecturePanda Spreadsheet Report delivers to email, a Google Drive folder, an SFTP server and a web address by HTTP POST, and each send goes to every destination on the report. The HTTP POST carries the file as an upload, or the rows themselves as JSON keyed by your column headers, which is what a Zapier catch hook, Make or n8n wants, with an optional shared secret for signing each request.

A LecturePanda Spreadsheet Report can include any registration field you collect, such as name, email, license number, member ID or date of birth, plus course title, dates and location, credit name, hours and identifiers, the completion date, fixed values like your provider number, and a per-credit value such as a board's course number. Each column has a header typed exactly as the recipient expects, and formatting steps handle case, padding, digits only and date patterns.

A LecturePanda Spreadsheet Report sends on the schedule you set: every day, on a weekday each week, or on a day each month, at an hour in the report's timezone. The file name can carry the date, month or year, and when there are no new completions the report either skips the send or sends an empty file so the recipient knows it ran. Send a test proves each destination before the first scheduled send.

When a LecturePanda Spreadsheet Report can't reach a destination, that destination is retried with the same stored file, and the destinations that already received it aren't sent it twice. Send History lists every send with its period, its row count, each destination and whether it got the file, so a folder share or firewall rule that needs attention shows up right there.

Yes. Send History in LecturePanda has Resend on every past send, which sends the same rows again in each destination's current format, and a download of the rows as CSV or Excel. Sent files stay available for one year, long enough to correct a bad file with the recipient.

LecturePanda Spreadsheet Reports send CSV or Excel (.xlsx) files, chosen per destination, and a web address destination can also take the rows as JSON. Every cell is written as text, so license numbers and zip codes keep their leading zeros, and a value that starts with a formula character is written as text rather than run. A period with more than 10,000 completions goes out as several numbered files.

LecturePanda's Spreadsheet Report protects the file at each destination. Email can send a download link that stops working after a set number of days, so the data doesn't sit in an inbox. SFTP uploads pin the server's host key, come from a fixed address for your firewall and land under a temporary name until complete. In Google Drive LecturePanda sees only the folder you share, and passwords, keys and secrets are stored separately and never shown again.

Yes. A LecturePanda credit can carry a Spreadsheet Report alongside CE Broker, ACPE or PARS reporting, so one completion reaches the accreditor and lands in the recipient's file. The Spreadsheet Report is an accreditation type under Organization Settings, set up once and attached to credits like any other, and it's part of the subscription like every other integration.