Education statistics workflow
Office Document Toolkit: PDFs, Images, Dates, and Data Formatting
This workflow helps office workers handle everyday document tasks: organize PDFs, compress files, estimate dates and business days, create QR codes, and inspect JSON data.
Updated:
Purpose
This workflow helps office workers handle everyday document tasks: organize PDFs, compress files, estimate dates and business days, create QR codes, and inspect JSON data.
Workflow steps
- Confirm the document purpose, the final page order, and whether the recipient needs one complete file or separate attachments, a cover, and a signature page, since that decision determines whether you merge first or split first.
- Use PDF merge to combine multiple sources into one working draft, rotate pages that face the wrong way, and split out separate files when needed; check the page count against the originals at every step, and work from a copy while keeping the source untouched.
- Before compressing an image or screenshot, confirm the file-size limit for the delivery channel, then zoom in after compressing to check text, table borders, and signature strokes, since scans and handwritten signatures blur first under heavy compression.
- Use date difference for the number of days between two dates and business-days for the count after excluding weekends; decide up front whether to also exclude public holidays and company leave, since the tool only skips the dates you enter manually and does not apply a regional calendar automatically.
- For announcements, internal forms, or on-site check-in, paste the final URL into the QR code generator, then scan the result with another phone or a guest account to confirm it points to the correct version with no unintended access.
- When a system exports JSON, run it through the JSON formatter first so field names, nesting, and obvious gaps are easier to read by eye; formatting only changes layout, not the data itself, so verify anything unusual against the source system rather than editing the formatted text directly.
- Before sending the final version, reopen it and check documents, date assumptions, and JSON fields together, since each step can pass individually while the merged result still contains a mismatched version or an outdated page.
Workflow integrity review:
Delivery standard: inputs, handoffs, and recovery
This section reworks three of the workflow’s own steps: the merge-before-split rule, the fact that business-day calculations only exclude dates entered manually, and the limit of what JSON formatting actually checks.
Confirm merge-first on a document that needs both a full file and a separate attachment
The workflow’s FAQ states directly: merge into one complete working draft first and confirm the overall page order, then split out attachments, a cover, or a signature page as the submission requires. Test this on a document with 5 source files that need to become one 12-page working draft plus a separately submitted 2-page appendix: merge all sources first, verify the working draft is 12 pages, and only then split out the 2-page appendix. Splitting the appendix out of one source file before merging the rest instead is where page-order mistakes are most often introduced — recheck the final order if that route was taken.
Build a business-days case that only excludes what was actually entered
The workflow step warns that a business-day tool only skips the dates entered manually and does not apply a regional calendar automatically. Test this directly: calculate business days between two dates that span a known public holiday in your region, without entering that holiday as an exclusion, and note the result. Then add the holiday as a manual exclusion and recalculate — the two results will differ by at least one day, concrete proof that the tool did not know about the holiday until told.
Self-check what JSON formatting does and does not verify
The workflow step is explicit that formatting only changes layout, not the data itself, and that anything unusual should be verified against the source system rather than edited directly in the formatted text. Self-test: take a JSON export with an obviously wrong value, such as a negative count or a date far in the future, and run it through the formatter — the formatter will make the structure easier to read but will not flag or correct that value. Confirm the next step is going back to the source system, not editing the formatted text and treating that as the fix.
Definition of done
- Merged all source files into one working draft and verified the total page count before splitting out any cover, appendix, or signature page.
- Calculated business days across a known regional holiday both without and with that holiday manually excluded, and confirmed the results differ.
- Ran an export with a deliberately wrong value through the JSON formatter and confirmed the formatter neither flagged nor corrected it.
- Verified any unusual JSON value against the source system rather than editing the formatted text and treating that as the correction.
Recommended tools
FAQ
- Can I use these tools for confidential company documents?
- They are browser-oriented, but you still need to follow company security rules. Use approved workflows for highly sensitive or regulated files.
- Does the business-day tool know every holiday?
- Not necessarily. Enter excluded dates based on your region and company rules, and keep your assumptions.
- What can PDF compression affect?
- Compression can affect scans, images, and small text. Open the file and spot-check important pages before sending it.
- Can JSON formatting fix bad data?
- No. It improves layout and readability; data meaning, types, and source accuracy still need review.
- Should I merge or split a PDF first?
- Merge into one complete working draft first and confirm the overall page order, then split out attachments, a cover, or a signature page as the submission requires; splitting first and merging afterward makes page order mistakes much easier to introduce.