Use this checklist before requesting TradingView programming. A good Pine Script scope should explain the chart behavior well enough that a programmer can separate the visual idea from the actual rules TradingView has to execute.
Pine Script work usually falls into one of four paths: a new indicator, a new strategy, an alert workflow, or a repair/conversion. Each path needs different details. An indicator scope needs plots, colors, labels, and chart states. A strategy scope needs entry logic, exit logic, order sizing, session rules, and backtest assumptions. An alert scope needs timing, frequency, messages, and repainting expectations. A repair or conversion scope needs the existing script, error messages, and examples of the expected output.
Include these details
- indicator, strategy, alert, repair, or conversion
- Pine Script files and current errors
- screenshots of expected chart output
- alert conditions and messages
- repainting expectations
- timeframe and symbol assumptions
- examples of correct behavior
Clarify TradingView limits
TradingView is excellent for charting, alerts, and script-based strategy testing, but it is not the same as building a broker-side execution engine. If the goal is an alert, define what message should be sent and when it should fire. If the goal is strategy testing, define how entries, exits, stops, targets, commissions, and sessions should be handled. If the goal is automation outside TradingView, say that clearly so Moore Tech can route the request toward the right architecture instead of treating it like a simple indicator.
Define repainting expectations
Many Pine Script problems come from unclear repainting assumptions. If a signal can appear before a bar closes, explain whether it is allowed to move or disappear. If a signal should only confirm after bar close, include examples showing the final confirmed state. This matters for indicators, alerts, and strategy logic because a backtest can look different from live chart behavior when the timing rules are vague.
Send usable examples
Screenshots are useful, but marked-up examples are better. Include at least two correct examples and one example where the script should stay neutral. If you are converting from another platform, include the original script, a screenshot from the original platform, and the TradingView output you expect. If you are repairing an existing Pine Script, include the current error text and the smallest set of steps needed to reproduce it.
Clear scope makes the TradingView programmer quote more accurate. If the project is mostly alert behavior, also review the TradingView alert programming checklist. If you are still deciding whether you need TradingView or a different platform, compare the broader trading platform programming guide.