Aykhan Rustamov

Synergy3 · NetSuite, scheduled · Jun 2026

Weekly partner report

A partner programme gets a branded email report on its own schedule: the jobs coming up, and the work completed, judged per project rather than per visit. Every revision since launch was asked for by the person who reads it.

  • Scheduled scripts
  • Saved searches
  • HTML email

What it replaced

The programme wanted a weekly picture of the work on its own Wednesday to Wednesday cycle. The quick option was a few saved searches emailing spreadsheets. They wanted one readable report, so it is one script that gathers the tasks, cases and orders for the window and sends a single branded email.

How it worksHow the weekly report is put together
yesnoOn a scheduleno one has toremember itGather the weekWednesday toWednesdayRead the servicetypefrom the order linesfirstProjectcomplete?Completedinsulation andinstall both doneStill openlisted with the weekaheadBranded emailto the programme,team in copy
  1. On a scheduleno one has to remember it
  2. Gather the weekWednesday to Wednesday
  3. Read the service typefrom the order lines first
  4. Project complete?yes completed · no still open
  5. Completedinsulation and install both done
  6. Still openlisted with the week ahead
  7. Branded emailto the programme, team in copy

Internal task notes never reach the email. Callbacks and drive-bys are left out.

Getting the facts right

Each revision came from the reader. Task notes came out, because dispatchers sometimes write internal things there. The service type is now read from the order’s lines first, because the order header said Installation on insulation jobs. A project counts as complete only when both its insulation and its installation are done, not when one visit closes. Callbacks and drive-bys are left out.

Changing it safely

Changes are made in a test copy that differs from the live script only in who it sends to. It is run by hand, sent to me, forwarded to the reader for approval, and only then copied over the live one.

What it includes

  1. The week ahead, job by job
  2. Completed work, counted per project
  3. Gas leaks and later phase work called out
  4. Service type read from the order lines
  5. Internal notes kept out
Described at the level of the work, never the data. No code, records or customer details from this system appear on this site. A walkthrough is available on request.

Contact

Tell me what slows your team down.

Available for ERP and NetSuite work, platform integration, and full product builds. The quickest way to reach me is email or WhatsApp. I reply within a day. If you are writing about a role or a build, a sentence on what the system has to do is more useful to me than a job description.

hello@arustamov.dev
Email meDownload CV